Nathan Froyd 88c9734950 Bug 1555990 - fix theoretical xptcodegen issue with nested array types; r=nika ... 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. Differential Revision: https://phabricator.services.mozilla.com/D33299 --HG-- extra : moz-landing-system : lando		2019-05-31 16:46:24 +00:00
..
xptcall	Bug 1538236 - fix LTO issues with arm xptcstubs; r=mccr8	2019-04-04 21:14:18 +00:00
xptinfo	Bug 1555990 - fix theoretical xptcodegen issue with nested array types; r=nika	2019-05-31 16:46:24 +00:00
moz.build