Closed
Bug 553824
Opened 14 years ago
Closed 14 years ago
Squeeze more chars into the short string using JSString::mOffset
Categories
(Core :: JavaScript Engine, enhancement)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
People
(Reporter: igor, Assigned: igor)
References
Details
+++ This bug was initially created as a clone of Bug #553541 +++ The short strings from the bug 553541 can hold more chars if JSString::mOffset would be made the last field in JSString and shared with short string chars.
Comment 1•14 years ago
|
||
I did some quick sampling of the string population of gmail and SS. I have now serious doubts this patch will do anything but complicate the code (the overlap is really weird). I would like to see real world or SS speedups before we land a fix for this bug.
Assignee | ||
Comment 2•14 years ago
|
||
(In reply to comment #1) > but complicate the code (the overlap is really weird). Hm, what kind of code of code complexity this brings? AFAICS the necessary changes would be to replace mOffset with union { size_t mOffset; jschar data[1]; }, add a static assert to verify that the offset of data matches mOffset, and add a const to denote the real string size. With that there would be no need for JSShortString.
Updated•14 years ago
|
Comment 3•14 years ago
|
||
The fix for 578205 (which redid the backed-out patch for 553541) keeps the first few string characters in the first string header in JSShortString, which essentially fixes this issue.
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
•