@BruceDawson0xB Hey; regarding https://randomascii.wordpress.com/2018/08/16/24-core-cpu-and-i-cant-type-an-email-part-one/ … - Was this when Chrome was compiled with msvc? Otherwise I'm confused about how CFG was affecting V8 allocations if you were compiling with clang-cl and only using CFG on system libraries....?
Wait, we think we figurd it out. Chrome enabled CFG on all libraries with the linker, so I guess CFG would get enabled on V8 even on clang-cl... https://cs.chromium.org/chromium/src/build/config/win/BUILD.gn?type=cs&q=guard:cf&g=0&l=402 …
-
-
If CFG is enabled for the process then there will be a 2 TiB CFG reservation. This CFG bitmap will be used for all executable pages in the process, including v8. Don't say "Chrome enabled CFG on all libraries" say "Chrome enable CFG for the process"
-
Well, the reservation will there if CFG is enabled on anything; but all pages don't get bitmap entries automatically I don't think. (Unless they get everything-is-a-valid-target entries?) 1/2
-
You need to specify PAGE_TARGETS_INVALID+SetProcessValidCallTargets for executable VirtualAlloc-ed pages; and you can have CFG on for some libraries but not others...
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.