Closed
Bug 612624
Opened 14 years ago
Closed 14 years ago
dtoa.c Omit_Private_Memory option fails to compile
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
People
(Reporter: andrew, Unassigned)
Details
(Whiteboard: fixed-in-tracemonkey)
Attachments
(1 file)
|
455 bytes,
patch
|
mrbkap
:
review+
|
Details | Diff | Splinter Review |
We use the Omit_Private_Memory option so that dtoa always uses allocators. This Omit_Private_Memory option used to work but now fails because code accessing state->pmem_next and state->private_mem is not checking the #define that is used to declare them. The attached patch adds the necessary #ifndef Omit_Private_Memory around this access so that dtoa.c builds properly with this option enabled.
|
||
Updated•14 years ago
|
Attachment #490914 -
Flags: review+
|
|
||
Comment 1•14 years ago
|
||
http://hg.mozilla.org/tracemonkey/rev/8f24dc55e169
Whiteboard: fixed-in-tracemonkey
|
||
Comment 2•14 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/8f24dc55e169
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•