| Summary: | [JSC][32-bits] Build failure after r259676 (Not using strict mode within ClassDeclaration statement) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Pablo Saavedra <psaavedra> | ||||
| Component: | JavaScriptCore | Assignee: | Guillaume Emont <guijemont> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | aakash_jain, ews-watchlist, guijemont, keith_miller, mark.lam, msaboff, pmatos, saam, ticaiolima, tzagallo, webkit-bug-importer, ysuzuki | ||||
| Priority: | P2 | Keywords: | InRadar | ||||
| Version: | WebKit Nightly Build | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Attachments: |
|
||||||
|
Description
Pablo Saavedra
2020-04-08 00:42:22 PDT
Created attachment 395789 [details]
Patch
First attempt at the patch. This fixes building on armv7, relying on EWS to run tests
*** Bug 210181 has been marked as a duplicate of this bug. *** Comment on attachment 395789 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=395789&action=review Informal review there. LGTM. > Source/JavaScriptCore/jit/JITPropertyAccess32_64.cpp:404 > + ECMAMode ecmaMode = ECMAMode::strict(); Is there a reason to initialize it? IIUC, load will set a value below based on `bytecode.m_ecmaMode`; Comment on attachment 395789 [details]
Patch
setting r+ and cq+ since it passes EWS and fix the build breakage. Further improvements (if any) can be done in follow-up patch.
Committed r259715: <https://trac.webkit.org/changeset/259715> All reviewed patches have been landed. Closing bug and clearing flags on attachment 395789 [details]. (In reply to Caio Lima from comment #3) > Comment on attachment 395789 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=395789&action=review > > Informal review there. LGTM. > > > Source/JavaScriptCore/jit/JITPropertyAccess32_64.cpp:404 > > + ECMAMode ecmaMode = ECMAMode::strict(); > > Is there a reason to initialize it? IIUC, load will set a value below based > on `bytecode.m_ecmaMode`; That's a good question I'd like to forward to Tadeu, since I basically cut and paste his code from JITPropertyAccess.cpp: https://github.com/WebKit/webkit/blob/master/Source/JavaScriptCore/jit/JITPropertyAccess.cpp#L308 but yeah, it doesn't look like it's needed. (In reply to Guillaume Emont from comment #7) > (In reply to Caio Lima from comment #3) > > Comment on attachment 395789 [details] > > Patch > > > > View in context: > > https://bugs.webkit.org/attachment.cgi?id=395789&action=review > > > > Informal review there. LGTM. > > > > > Source/JavaScriptCore/jit/JITPropertyAccess32_64.cpp:404 > > > + ECMAMode ecmaMode = ECMAMode::strict(); > > > > Is there a reason to initialize it? IIUC, load will set a value below based > > on `bytecode.m_ecmaMode`; > > That's a good question I'd like to forward to Tadeu, since I basically cut > and paste his code from JITPropertyAccess.cpp: > > https://github.com/WebKit/webkit/blob/master/Source/JavaScriptCore/jit/ > JITPropertyAccess.cpp#L308 > > but yeah, it doesn't look like it's needed. The reason is that ECMAMode doesn't have a default initializer. I found it easier to not add one while refactoring so I'd look at all usages of it. |