Closed
Bug 735519
Opened 14 years ago
Closed 14 years ago
Fix a bunch of "inlined function used but not defined" warnings
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla14
People
(Reporter: sfink, Assigned: sfink)
Details
Attachments
(1 file)
2.96 KB,
patch
|
dmandelin
:
review+
|
Details | Diff | Splinter Review |
I wish I had a simpler way of tracking these buggers down.
Assignee | ||
Comment 1•14 years ago
|
||
Attachment #605595 -
Flags: review?(dmandelin)
Comment 2•14 years ago
|
||
One trick is to change the signature of the inline function's declaration, and compile the file giving those warnings. gdb at least should then give a not-useless error message pointing to the call it found.
Assignee | ||
Comment 3•14 years ago
|
||
Ooh, that sounds much nicer than what I was doing!
I would compile without -j to see what .cpp generated the warning, then delete everything in that file but the #includes, then binary search through those (expanding them inline into the file when I found one, and recursing). And even then it was sometimes totally cryptic why a particular header would trigger the warnings.
![]() |
||
Updated•14 years ago
|
Attachment #605595 -
Flags: review?(dmandelin) → review+
Comment 4•14 years ago
|
||
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla14
You need to log in
before you can comment on or make changes to this bug.
Description
•