Bug 242816
| Summary: | [JSC] Improve same-register moves in AirAllocateRegistersAndStackAndGenerateCode | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Joseph Griego <joseph.j.griego> |
| Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Joseph Griego
When we are emitting a `Move` from a Tmp to a named-register Tmp that matches
its current allocation, we currently generate code that spills the source tmp to
the stack, allocates a new (distinct) register for it, restores it there, and
then moves it; this seems wasteful and, although this kind of situation in Air
is not common on x86_64, we do generate it on 32-bit ARM targets
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Joseph Griego
Pull request: https://github.com/WebKit/WebKit/pull/2462
Radar WebKit Bug Importer
<rdar://problem/97452075>