Bug 210181
| Summary: | Regression(r259676): JSC mips/armv7 build broken | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Aakash Jain <aakash_jain> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | aperez, ap, cgarcia, clopez, guijemont, pmatos, ticaiolima, tzagallo, webkit-bot-watchers-bugzilla |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=205578 | ||
Aakash Jain
JSC mips/armv7 build seems to be broken.
e.g.:https://build.webkit.org/builders/JSCOnly%20Linux%20ARMv7%20Thumb2%20Release/builds/11260/steps/compile-webkit/logs/stdio
../../Source/JavaScriptCore/dfg/DFGSpeculativeJIT32_64.cpp:2785:29: error: ‘class JSC::DFG::JITCompiler’ has no member named ‘isStrictModeFor’
callOperation(m_jit.isStrictModeFor(node->origin.semantic) ? operationPutByValWithThisStrict : operationPutByValWithThis,
^~~~~~~~~~~~~~~
In file included from ../../Source/JavaScriptCore/dfg/DFGJITCompiler.h:30,
from ../../Source/JavaScriptCore/dfg/DFGSpeculativeJIT.h:34,
from ../../Source/JavaScriptCore/dfg/DFGSpeculativeJIT32_64.cpp:28:
MIPS:
r259635 passed in https://build.webkit.org/builders/JSCOnly%20Linux%20MIPS32el%20Release/builds/4780
r259687 failed in https://build.webkit.org/builders/JSCOnly%20Linux%20MIPS32el%20Release/builds/4781
ARMv7:
r259675 passed in https://build.webkit.org/builders/JSCOnly%20Linux%20ARMv7%20Thumb2%20Release/builds/11259
r259699 failed in https://build.webkit.org/builders/JSCOnly%20Linux%20ARMv7%20Thumb2%20Release/builds/11260
Regression range: r259675 - r259687
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Aakash Jain
It's r259676. EWS also red for armv7/mips for corresponding bug https://bugs.webkit.org/show_bug.cgi?id=205578 with the same error: https://ews-build.webkit.org/#/builders/26/builds/13604
Aakash Jain
This is already tracked in Bug 210176.
*** This bug has been marked as a duplicate of bug 210176 ***