Closed Bug 1555990 Opened 6 years ago Closed 6 years ago

fix theoretical xptcodegen issue with nested array types

Categories

(Core :: XPCOM, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla69
Tracking Status
firefox69 --- fixed

People

(Reporter: froydnj, Assigned: froydnj)

Details

Attachments

(1 file)

No description provided.

When we're lowering extra types (e.g. array element types) and we find
that we haven't already lowered the type, we say that the new type is
going to live at the end of the types array. But we don't append a
new type (i.e. filling in the entry) until after we call lower_type,
which means that some other call to lower_extra_type might find
that its new type will live at the same position we "allocated" higher
up on the stack.

We don't appear to run into this issue, as the only nested array types
are things like Array<Array<uint8>>, and uint8 is guaranteed to
already have been lowered. But if people start doing more complicated
things, we're bound to run into this sooner or later.

Pushed by nfroyd@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/db5ce1365927 fix theoretical xptcodegen issue with nested array types; r=nika
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: