Closed
Bug 2003461
Opened 3 months ago
Closed 2 months ago
Use StringChars instead of JSStringBuilder for toBase64/toHex
Categories
(Core :: JavaScript: Standard Library, enhancement, P1)
Core
JavaScript: Standard Library
Tracking
()
RESOLVED
FIXED
149 Branch
| Tracking | Status | |
|---|---|---|
| firefox149 | --- | fixed |
People
(Reporter: anba, Assigned: anba)
References
(Blocks 2 open bugs)
Details
Attachments
(1 file)
No description provided.
| Assignee | ||
Comment 1•3 months ago
|
||
StringChars allows to directly pass the allocated characters to the result JSString*.
Comment 2•3 months ago
|
||
Similar perf (if not better) than my ugly patch. I also like that it localizes the Append code to the ToBase64 function, as that will make SIMD'ing or coaxing the auto-vectorizer easier. I was not liking the circular paths that tracing infallibleAppend was taking me down.
Updated•3 months ago
|
Pushed by andre.bargull@gmail.com:
https://github.com/mozilla-firefox/firefox/commit/bba50f0189be
https://hg.mozilla.org/integration/autoland/rev/eb91afc120a7
Use StringChars instead of JSStringBuilder for toBase64/toHex. r=iain
Comment 4•2 months ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 2 months ago
status-firefox149:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 149 Branch
Updated•24 days ago
|
QA Whiteboard: [qa-triage-done-c150/b149]
You need to log in
before you can comment on or make changes to this bug.
Description
•