Closed Bug 1677312 Opened 5 years ago Closed 5 years ago

Directly encode/decode ParserAtomEntry at once

Categories

(Core :: JavaScript Engine, task, P1)

task

Tracking

()

RESOLVED FIXED
86 Branch
Tracking Status
firefox86 --- fixed

People

(Reporter: arai, Assigned: arai)

References

Details

Attachments

(4 files)

No description provided.
Pushed by arai_a@mac.com: https://hg.mozilla.org/integration/autoland/rev/7a954fd0ec57 Part 1: Remove validation for TaggedParserAtomIndex in XDR. r=tcampbell https://hg.mozilla.org/integration/autoland/rev/cdb90231cbe4 Part 2: Use uint32_t flag in ParserAtomEntry to make it packed. r=tcampbell https://hg.mozilla.org/integration/autoland/rev/eca69583fbb3 Part 3: Encode/decode ParserAtomEntry content at once. r=tcampbell
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → 86 Branch

Re-opening to fix an alignment issue in another patch.

Status: RESOLVED → REOPENED
Resolution: FIXED → ---

When peeking the ParserAtomEntry header, use an explicit memcpy to allow
the compiler to decide if we should use unaligned access to the fields. At
the same time, rearange the code a bit to prepare for a future where we use
the ParserAtomEntry directly from the (then aligned) XDR buffer.

Attachment #9193537 - Attachment description: Bug 1677312 - Avoid accessing unaligned XDR ParserAtom directly. r?arai! → Bug 1677312 - Part 4: Avoid accessing unaligned XDR ParserAtom directly. r?arai!
Pushed by tcampbell@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/c4101c6211c7 Part 4: Avoid accessing unaligned XDR ParserAtom directly. r=arai
Status: REOPENED → RESOLVED
Closed: 5 years ago5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: