-
bmeurer authored
It is not always safe to allocate new heap objects in the JSGraph. We might have to revisit this later once we do the canonicalization for HeapConstants. R=jarin@chromium.org BUG=chromium:545364 LOG=n Review URL: https://codereview.chromium.org/1413373002 Cr-Commit-Position: refs/heads/master@{#31421}
d168a1e8
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| benchmarks | Loading commit data... | |
| cctest | ||
| intl | ||
| js-perf-test | ||
| memory | ||
| message | ||
| mjsunit | ||
| mozilla | ||
| preparser | ||
| promises-aplus | ||
| simdjs | ||
| test262 | ||
| unittests | ||
| webkit | ||
| bot_default.gyp | ||
| bot_default.isolate | ||
| default.gyp | ||
| default.isolate | ||
| optimize_for_size.gyp | ||
| optimize_for_size.isolate |