Bug 175248
| Summary: | Considering abstracting gigacages more rigorously | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Filip Pizlo <fpizlo> |
| Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | ||
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | All | ||
| OS: | All | ||
Filip Pizlo
You can imagine adding a constant somewhere like:
constexpr Gigacage::Kind TypedArrayGigacageKind = Gigacage::Primitive;
And similarly for other things. I didn't do it that way because I find it useful to see that typed arrays use the primitive gigacage inline in the code, since this is a fundamental assumption. But, maybe others feel differently.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |