tags:v8JITchrome original link: Return of the JIT newsletter link: exploits.club Weekly Newsletter 30
Exploits Club Summary:
A short fun and short post from @winterknife discussing recent changes to the behavior of the V8 optimizer toggle in Chrome. Previously, individuals were using this toggle as a means disabling JIT and switching V8 to interpreter-only mode. However, since late June, the behavior of this toggle was changed to only disable the 2 higher tiers of JIT compilation, leaving Sparkplug enabled. The theory is this may have been introduced to not break WASM, but if its something youâre worried about, the blog offers a workaround using theÂ
jitless command-line flag.