зеркало из https://github.com/mozilla/gecko-dev.git
de8d036db1
It's okay to have `JSOp::SetArg` and still enable the lazy arguments optimisation, as long as the `JSOp::SetArg` is always unreachable. The assertion was kept from code which was added before the `arguments` analysis code rewritten to use IonBuilder. But with the current `arguments` analysis, it's no longer useful to have this assertion, because any reachable (!) `JSOp::SetArg` will currently always disable lazy arguments, cf. `IonBuilder::jsop_setarg()`. Differential Revision: https://phabricator.services.mozilla.com/D66229 --HG-- extra : moz-landing-system : lando |
||
|---|---|---|
| .. | ||
| ductwork/debugger | ||
| examples | ||
| ipc | ||
| public | ||
| rust | ||
| src | ||
| xpconnect | ||
| app.mozbuild | ||
| ffi.configure | ||
| moz.build | ||
| moz.configure | ||
| sub.configure | ||