SpiderMonkey dtrace build breakage

RESOLVED FIXED in mozilla10

Status

()

Core
JavaScript Engine
RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: sfink, Assigned: sfink)

Tracking

unspecified
mozilla10
x86_64
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments, 1 obsolete attachment)

Created attachment 566279 [details] [diff] [review]
Header juggling

jsprobes.h uses JSObject and JSScript when compiling with --enable-dtrace, so it needs to include the appropriate headers.
Attachment #566279 - Flags: review?(luke)
Assignee: general → sphink
I think this is going to be a problem, since jsprobes.h is in INSTALLED_HEADERS and jsobj.h is not.
...although it looks like we can remove jsprobes.h from INSTALLED_HEADERS!
Created attachment 566285 [details] [diff] [review]
Header juggling

Oh, I put jsprobes.h in INSTALLED_HEADERS? Ugh. I guess that was before I knew better.

I'd actually like to create something someday that *would* go into INSTALLED_HEADERS, but jsprobes.h in its current form is not that.
Attachment #566279 - Attachment is obsolete: true
Attachment #566279 - Flags: review?(luke)
Attachment #566285 - Flags: review?(wmccloskey)
Attachment #566285 - Flags: review?(wmccloskey) → review+
Created attachment 566302 [details] [diff] [review]
Fix other SM build problems

Misusing this bug for further followup problems in SM builds.

This patch fixes 2 problems: (1) a warning where I initialize class members out of order, and (2) an error where I use mjit:: stuff when --disable-methodjit is on.
Attachment #566302 - Flags: review?(wmccloskey)
Comment on attachment 566302 [details] [diff] [review]
Fix other SM build problems

Thanks!

By the way, it's outside the scope of this bug, but I noticed that jsprobes.h uses different capitalization than the rest of SM. I think normally it would be probes::DiscardExecutableRegion, rather than Probes::discardExecutableRegion (lowercase for namespaces and uppercase for top-level functions).
Attachment #566302 - Flags: review?(wmccloskey) → review+
(In reply to Bill McCloskey (:billm) from comment #5)
> Comment on attachment 566302 [details] [diff] [review] [diff] [details] [review]
> Fix other SM build problems
> 
> By the way, it's outside the scope of this bug, but I noticed that
> jsprobes.h uses different capitalization than the rest of SM. I think
> normally it would be probes::DiscardExecutableRegion, rather than
> Probes::discardExecutableRegion (lowercase for namespaces and uppercase for
> top-level functions).

Yeah, you're right. I should fix that. Everything used to be in a js::Probes class, and I should've switched Probes::stuff to probes::Stuff at the same time.
(In reply to Steve Fink [:sfink] from comment #6)
> (In reply to Bill McCloskey (:billm) from comment #5)
> > Comment on attachment 566302 [details] [diff] [review] [diff] [details] [review] [diff] [details] [review]
> > Fix other SM build problems
> > 
> > By the way, it's outside the scope of this bug, but I noticed that
> > jsprobes.h uses different capitalization than the rest of SM. I think
> > normally it would be probes::DiscardExecutableRegion, rather than
> > Probes::discardExecutableRegion (lowercase for namespaces and uppercase for
> > top-level functions).
> 
> Yeah, you're right. I should fix that. Everything used to be in a js::Probes
> class, and I should've switched Probes::stuff to probes::Stuff at the same
> time.

Filed bug 693838
https://hg.mozilla.org/mozilla-central/rev/c515dbded0c2
https://hg.mozilla.org/mozilla-central/rev/9ee34cc1d186
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla10
You need to log in before you can comment on or make changes to this bug.