Closed
Bug 902304
Opened 12 years ago
Closed 1 year ago
consider allowing the creation of array buffers with a length of 0x80000000.
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
DUPLICATE
of bug 1392234
People
(Reporter: dougc, Unassigned)
Details
Asm.js constrains the heap size to be a power of two, and combined with the constraint that the largest array length is 0x7fffffff this limits asm.js code to a maximum heap size of 1GB. It is quite likely that the asm.js compiler already generates code that could handle a 2GB heap size, and this should be practical on the x64
Comment 1•12 years ago
|
||
This seems fine; ArrayBufferObject::byteLength() and ElementsHeader::initializedLength already use uint32_t. It seems mostly just a matter of searching for the uses of INT32_MAX vm/TypedArrayObject.cpp (e.g. createBufferWithSizeAndCount). Do you see any problems Steve?
Comment 2•12 years ago
|
||
Also, this would be a VM-wide change, not specific to Odin.
Summary: Odinmonkey: consider allowing the creation of array buffers with a length of 0x80000000. → consider allowing the creation of array buffers with a length of 0x80000000.
Updated•12 years ago
|
Flags: needinfo?(sphink)
| Assignee | ||
Updated•11 years ago
|
Assignee: general → nobody
Comment 3•9 years ago
|
||
I'm going to clear this 3 year old needinfo, as I don't really having anything useful to say. This has come up again recently, though I wasn't involved -- or rather, a request for a 2^53 limit recently came up.
Flags: needinfo?(sphink)
Updated•3 years ago
|
Severity: normal → S3
Updated•1 year ago
|
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•