Closed
Bug 953410
Opened 12 years ago
Closed 12 years ago
JS_ION define is inconsistently used
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
mozilla29
People
(Reporter: martin, Assigned: h4writer)
References
Details
Attachments
(3 files)
|
6.63 KB,
patch
|
bhackett1024
:
review-
|
Details | Diff | Splinter Review |
|
900 bytes,
patch
|
h4writer
:
review-
|
Details | Diff | Splinter Review |
|
1.01 KB,
patch
|
bhackett1024
:
review+
|
Details | Diff | Splinter Review |
Builds without JS_ION fail due to inconsistent usage of the define. This is all very messy, one way to fix it is to #ifdef a lot places (see attached patch), another option would be to make js/src/jit/IonCode.h compilable without JS_ION.
Comment 1•12 years ago
|
||
Comment on attachment 8351703 [details] [diff] [review]
Add #ifdef JS_ION around includes of IonCode.h and usages
Do you see the same build failure as on bug #953210 ? If so the two bugs could be merged..
(i'm not sure commenting out needGC=true in jscompartment.h will work out :)
Attachment #8351703 -
Flags: review?(bhackett1024)
| Reporter | ||
Comment 2•12 years ago
|
||
Yes, without this patch I see the same problem as bug #953210.
The commenting of needGC = true may be unrelated, but I could not find a definition for needGC and it made the compile fail.
Comment 3•12 years ago
|
||
Comment on attachment 8351703 [details] [diff] [review]
Add #ifdef JS_ION around includes of IonCode.h and usages
Review of attachment 8351703 [details] [diff] [review]:
-----------------------------------------------------------------
Generally it'd be good to avoid sprinkling #ifdef JS_ION around the codebase except where absolutely necessary. Things are in kind of bad shape right now wrt this idea but this patch makes things worse. This build failure is a recent regression from bug 939614 and modifying the header added by that bug makes --disable-ion builds work for me, patch in a minute.
Attachment #8351703 -
Flags: review?(bhackett1024) → review-
Comment 4•12 years ago
|
||
Attachment #8354265 -
Flags: review?(hv1989)
| Assignee | ||
Comment 6•12 years ago
|
||
(In reply to Brian Hackett (:bhackett) from comment #4)
> Created attachment 8354265 [details] [diff] [review]
> change JitOptions.h
I can't find the place where we would need JitOptions.h when JS_ION is false?
Comment 7•12 years ago
|
||
Try compiling with a --disable-ion build.
| Assignee | ||
Comment 8•12 years ago
|
||
Comment on attachment 8354265 [details] [diff] [review]
change JitOptions.h
Review of attachment 8354265 [details] [diff] [review]:
-----------------------------------------------------------------
We don't need to compile jitOptions.h for --disable-ion builds. It looks like I forgot to add #ifdef JS_ION to IonOptimizationLevels.h. I'll publish patch.
Attachment #8354265 -
Flags: review?(hv1989) → review-
| Assignee | ||
Comment 9•12 years ago
|
||
This fixes the compiler issues when compiling with --disable-ion
Attachment #8355219 -
Flags: review?(bhackett1024)
Comment 10•12 years ago
|
||
Comment on attachment 8355219 [details] [diff] [review]
Add JS_ION to IonOptimizationLevels.h
Review of attachment 8355219 [details] [diff] [review]:
-----------------------------------------------------------------
Whatever.
Attachment #8355219 -
Flags: review?(bhackett1024) → review+
| Assignee | ||
Comment 11•12 years ago
|
||
Thanks for the quick review!
https://hg.mozilla.org/integration/mozilla-inbound/rev/e11a69d3d4ba
Comment 12•12 years ago
|
||
Assignee: nobody → hv1989
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla29
You need to log in
before you can comment on or make changes to this bug.
Description
•