Closed
Bug 526639
Opened 16 years ago
Closed 16 years ago
nanojit: do debug builds by default
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: n.nethercote, Assigned: n.nethercote)
Details
(Whiteboard: fixed-in-nanojit)
Attachments
(1 file)
2.65 KB,
patch
|
graydon
:
review+
|
Details | Diff | Splinter Review |
At the moment, if you want a debug build of nanojit-central you need to configure with this non-obvious command:
CXXFLAGS="$CXXFLAGS -DDEBUG" ../configure
And since nanojit-central is only used for testing purposes -- it's not distributed to users except as part of TM or TR -- I think that debug builds (and hence assertions) should be turned on by default. This would immediately strengthen the testing provided by the tinderboxes and also that done by developers in their own workspaces.
This patch enables debug builds and turns on debug builds by default. You can configure with --disable-debug to turn them off. The patch also moves some things around so that more of the AC_SUBSTs are in one place.
Attachment #410370 -
Flags: review?(graydon)
Updated•16 years ago
|
Attachment #410370 -
Flags: review?(graydon) → review+
![]() |
Assignee | |
Comment 1•16 years ago
|
||
Whiteboard: fixed-in-nanojit
![]() |
Assignee | |
Comment 2•16 years ago
|
||
Hey, I guess I can mark this as resolved since it doesn't have to be merged to TM.
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•