| Summary: | Provide specialized SFrameCompatibilityPrefixBuffer constructors to avoid calling convention peculiarities | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Zan Dobersek <zan> | ||||
| Component: | New Bugs | Assignee: | Zan Dobersek <zan> | ||||
| Status: | RESOLVED INVALID | ||||||
| Severity: | Normal | CC: | eric.carlson, ews-watchlist, glenn, hta, jer.noble, philipj, sergio, tommyw, vjaquez, youennf | ||||
| Priority: | P2 | ||||||
| Version: | WebKit Nightly Build | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Attachments: |
|
||||||
|
Description
Zan Dobersek
2021-06-16 08:09:22 PDT
Created attachment 431548 [details]
Patch
This ends up not being a problem for such list initialization of different objects, since list initializations have specified (i.e. properly ordered) evaluation order of its arguments. Only function calls don't have that, leading to the usual use-after-move problems. So this change is not necessary. |