Re: [JS-internals] --enable-threadsafe on by default has broken my shell builds

2013-10-24 Thread Jason Orendorff
On 10/24/13 7:01 PM, Jason Orendorff wrote: > Mac-specific detail: When you build the way I do, the resulting js > shell executable expects NSPR libraries in the same directory as > itself (according to otool -L, the executable wants > /usr/lib/libz.1.dylib but @executable_path/libnss3.dylib; and l

Re: [JS-internals] --enable-threadsafe on by default has broken my shell builds

2013-10-24 Thread Jason Orendorff
On 10/24/13 6:51 PM, Jason Orendorff wrote: > This is one of those rare cases where the documentation actually > contains exactly the useful bits you need: [...] > > All this documentation work is due to Jim Blandy. It is of course exactly the kind of documentation work we didn't do with the recen

Re: [JS-internals] --enable-threadsafe on by default has broken my shell builds

2013-10-24 Thread Jason Orendorff
On 10/24/13 5:53 PM, Nicholas Nethercote wrote: > On Thu, Oct 24, 2013 at 5:36 PM, Jason Orendorff > wrote: >> Everyone please at least consider fixing up your dev environment to >> build with NSPR. > Where are the instructions? > > Nick This is one of those rare cases where the documentation ac

Re: [JS-internals] --enable-threadsafe on by default has broken my shell builds

2013-10-24 Thread Nicholas Nethercote
On Thu, Oct 24, 2013 at 5:36 PM, Jason Orendorff wrote: > > Everyone please at least consider fixing up your dev environment to > build with NSPR. Where are the instructions? Nick ___ dev-tech-js-engine-internals mailing list dev-tech-js-engine-interna

Re: [JS-internals] --enable-threadsafe on by default has broken my shell builds

2013-10-24 Thread Jason Orendorff
On 10/24/13 5:32 PM, Nicholas Nethercote wrote: > I tried to build the JS shell today for the first time in a few days > and got this: > > dist/system_wrappers_js/pratom.h:2:15: fatal error: 'pratom.h' file not > found > > Apparently --enable-threadsafe is now the default. When did that > happe

[JS-internals] --enable-threadsafe on by default has broken my shell builds

2013-10-24 Thread Nicholas Nethercote
Hi, I tried to build the JS shell today for the first time in a few days and got this: dist/system_wrappers_js/pratom.h:2:15: fatal error: 'pratom.h' file not found Apparently --enable-threadsafe is now the default. When did that happen? Some warning would have been nice -- I no longer know

Re: [JS-internals] Performance impact of Debugger

2013-10-24 Thread Jim Blandy
I lose, evidently. Anyway, it's attached to the bug: https://bugzilla.mozilla.org/show_bug.cgi?id=914429 ___ dev-tech-js-engine-internals mailing list dev-tech-js-engine-internals@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-js-engine-

Re: [JS-internals] Performance impact of Debugger

2013-10-24 Thread Jim Blandy
That doesn't seem to have worked. Attached: ___ dev-tech-js-engine-internals mailing list dev-tech-js-engine-internals@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals

Re: [JS-internals] Performance impact of Debugger

2013-10-24 Thread Jim Blandy
OMG I made a plot: plot of performance impact of Debugger with various JITs I really don't understand why we have that much impact even against the interpreter. I would like to. ___ dev-tech-js-engine-internals mailing list dev-tech-js-engine-interna