Open
Bug 636711
Opened 14 years ago
Updated 2 years ago
Using JSString * for JSScript::filename
Categories
(Core :: JavaScript Engine, enhancement)
Core
JavaScript Engine
Tracking
()
NEW
People
(Reporter: igor, Unassigned)
References
Details
+++ This bug was initially created as a clone of Bug #632253 +++
Currently JSScript::filename is const char * stored in a specialized hash that implements its own GC-marking machinery. We should try to replace that with JSString * to simplify code.
Comment 1•14 years ago
|
||
We don't need uint16 chars for filenames and that would be a loss for debugging and needless decimation code for diagnostics.
More, the script filename table shares filename strings aggressively and keeps track of prefixes for the system bit. Blake says we still need that bit, and the space savings were significant (see bug 127130). Please do not rip this stuff out lightly.
/be
Comment 2•14 years ago
|
||
That's an NSS/SSL bug -- probably not the one you meant to post, I'm guessing?
Comment 3•14 years ago
|
||
Oops, that was the attachment id (copied from the cvs log message): attachment 127130 [details] for bug 208030.
/be
Assignee | ||
Updated•10 years ago
|
Assignee: general → nobody
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•