Closed
Bug 1160278
Opened 9 years ago
Closed 9 years ago
Many SpiderMonkey compilation units are sensitive to unified compilation
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: nbp, Assigned: nbp)
References
Details
Attachments
(1 file)
14.86 KB,
patch
|
sstangl
:
review+
|
Details | Diff | Splinter Review |
+++ This bug was initially created as a clone of Bug #1155006 +++ Disabling unified builds in js/src causes many build failures, which means that different unification groupings will also fail.
Assignee | ||
Comment 1•9 years ago
|
||
Attachment #8600037 -
Flags: review?(jdemooij)
Comment 2•9 years ago
|
||
I'm building the ARM64 branch without unified compilation, and a merge from master breaks the build about twice a week, usually from missing headers. Is there some plausible way we could occasionally build without unification on to catch these errors as they crop up? Otherwise it looks like we'll be seeing a lot more of this bug.
Comment 3•9 years ago
|
||
Dropping non-unified builds in production was a conscious decision. We used to run them.
Assignee | ||
Comment 4•9 years ago
|
||
Comment on attachment 8600037 [details] [diff] [review] Fix non-unified build in js/src. Changing reviewer based on comment 2.
Attachment #8600037 -
Flags: review?(jdemooij) → review?(sstangl)
Comment 5•9 years ago
|
||
Comment on attachment 8600037 [details] [diff] [review] Fix non-unified build in js/src. Review of attachment 8600037 [details] [diff] [review]: ----------------------------------------------------------------- Oh gosh, this is old! Sorry for not noticing it until now! I don't know whether the patch is still relevant, but the changes look plausible. Make sure to run the check-style script before checking in. ::: js/src/jit/Ion.cpp @@ +48,5 @@ > #include "jsobjinlines.h" > +#include "jsscriptinlines.h" > + > +#include "jit/JitFrames-inl.h" > +#include "vm/ScopeObject-inl.h" This will break #include ordering, right? Run "make check-style" or "make style-check" or whatever we're calling it these days.
Attachment #8600037 -
Flags: review?(sstangl) → review+
Assignee | ||
Comment 6•9 years ago
|
||
Unfortunately, after a rebase, I noticed that most of the modification I made got applied in a different way by different patches.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•