On 9/20/2013 9:23 AM, Mike Hommey wrote:
We're already statically linking js libraries info libxul. Except on
windows, but that's work in progress in bug 915735
I am primarily worried about doing this on Windows.
, although we don't
know yet if it's going to work at all: after dealing with the xpcshell
crash during the instrumentation phase, we'll have to see how much
memory the linker is going to use, and that might not be very good news
ahead.
We will probably have a complete solution for linker memory issues when
VC2013 is released. Let's plan as if that were the case.
For xpcshell, I think there's a bug around to essentially fold it into
libxul, except for a thin layer. Ted might have been the one to file it
a long time ago.
Does anyone own that currently? If not, I'm looking for volunteers!
With that being said, relatedly, while I'm hopeful we could kill the
--enable-shared-js option (for libxul) at some point, Boris raised an
interesting point in that it is useful to him with Instruments, so that
it can flatten everything from libmozjs in a profile. I hope we'll find
an alternative for him, because I wouldn't like to make things painful
for Boris. OTOH, supporting --enable-shared-js is already causing
headaches, not exporting symbols might add to the complexity.
Hrm. Can profilers (Instruments in particular) profile by C++
namespace? I don't particularly mind have that kind of build option for
self-build profiling, as long as it's not on in release builds, but I
imagine that with the new ICU combinations it could get messy quickly.
Boris how strong is your opinion/need for this?
--BDS
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
