On 01/21/2013 01:37 PM, Brian Hackett wrote:
need in the future (e.g. parallel arrays).  Any configuration in which
a threadsafe build is noticeably slower than a non-threadsafe build
indicates a bug in the engine, and what we need right now is a better
handle on the problem rather than a workaround.

If it's any use, valgrind's callgrind tool can profile global bus events
(x86 LOCK, CAS, arm LL/SC) so it's at least possible to see if/where the
threadsafe config uses them a lot.  If necessary it'd be trivial to
backport this to the simpler profiler (cachegrind) that njn used to good
effect when tuning TM a couple of years back.

J

_______________________________________________
dev-tech-js-engine-internals mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals

Reply via email to