Closed Bug 951488 Opened 11 years ago Closed 11 years ago

jsinfer.h:784:24: warning: inline function ‘static void js::types::TypeObjectAddendum::writeBarrierPre(js::types::TypeObjectAddendum*)’ used but never defined [enabled by default]

Categories

(Core :: JavaScript Engine, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 952619

People

(Reporter: dholbert, Unassigned)

References

(Blocks 1 open bug)

Details

I'm getting tons of instances of the following GCC warning (for various .cpp files that directly or indirectly #include this header): { js/src/jsinfer.h:784:24: warning: inline function ‘static void js::types::TypeObjectAddendum::writeBarrierPre(js::types::TypeObjectAddendum*)’ used but never defined [enabled by default] } I'm seeing this on current mozilla-central and mozilla-inbound. The first two instances are for js/src/frontend/Parser.cpp and js/src/ctypes/CTypes.cpp, FWIW.
hg bisect says the first bad revision is: > changeset: 160664:dbeea0e93b56 > user: Brian Hackett > date: Mon Dec 16 10:53:02 2013 -0800 > summary: Bug 785905 - Build Ion MIR graph off thread, r=jandem.
Blocks: 785905
Bug 952619 apparently got "rid of the annoying writeBarrierPre warnings"... Maybe the warnings this bug is about?
Flags: needinfo?(terrence)
Yeah, I think the bugs are dupes. (Per comment 0 here, I was apparently getting "tons of instances" of that warning, which is consistent with the "out of hand" summary in bug 952619) I don't recall seeing this warning anytime recently, so I'll consider this a dupe of the other bug (and fixed by the patch that landed there).
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(terrence)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.