Currently you can build with either --enable-debug, which enables debugging symbols but also enables all the assertions in the code. The issue with such built is that it's barely usable on all but the most powerful machines. It would be great to have a --disable-debug-assertions that works in combination with --enable-debug , which would disable all assertions. Making a much more usable build. The advantage of using --enable-debug also turn on features that greatly speed up compilation time, such as incremental linking.
What is even the point of --enable-debug if you can turn off the assertions? You might as well just use an opt build at that point. And if things like incremental linking don't work with opt, we should make them work.
you're right. On windows, as per bug 1341504, incremental linking in effect is only enabled on debug build. On a very fast dell xps 159560 laptop, any relink of XUL takes over 3 minutes, as opposed to a debug build where it will take only 6s. Adding export LDFLAGS="-OPT:NOREF -OPT:NOICF" unfortunately to mozconfig unfortunately doesn't have the intended effect. I'm guessing, that a work around would be to compile with those flags when --disable-optimize is set.
OS: Unspecified → Windows
See Also: → bug 1341504
Summary: Add a --disable-debug-assertions parameters → --disable-optimize should enable incremental linking
Actually fixing bug 1341504 will accomplish what's described here, so let's make it a dupe.
Status: NEW → RESOLVED
Last Resolved: 11 months ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1341504
You need to log in before you can comment on or make changes to this bug.