Changeset 194376 in webkit
- Timestamp:
- Dec 22, 2015, 3:12:43 PM (11 years ago)
- Location:
- trunk/Source/JavaScriptCore
- Files:
-
- 2 edited
-
ChangeLog (modified) (1 diff)
-
runtime/Options.cpp (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/Source/JavaScriptCore/ChangeLog
r194373 r194376 1 2015-12-22 Saam barati <sbarati@apple.com> 2 3 Cloop build fix after https://bugs.webkit.org/show_bug.cgi?id=152511. 4 5 Unreviewed build fix. 6 7 * runtime/Options.cpp: 8 (JSC::recomputeDependentOptions): 9 1 10 2015-12-22 Saam barati <sbarati@apple.com> 2 11 -
trunk/Source/JavaScriptCore/runtime/Options.cpp
r194373 r194376 27 27 #include "Options.h" 28 28 29 #include "CCallHelpers.h"30 29 #include <algorithm> 31 30 #include <limits> … … 318 317 } 319 318 320 if (isARM64()) { 321 // FIXME: https://bugs.webkit.org/show_bug.cgi?id=152510322 // We're running into a bug where some ARM64 tests are failing in the FTL323 // with what appears to be an llvm bug where llvm is miscalculating the324 // live-out variables of a patchpoint. This causes us to not keep a325 // volatile register alive across a C call in a patchpoint, even though326 // that register is used immediately after the patchpoint.327 Options::assumeAllRegsInFTLICAreLive() = true;328 } 319 #if CPU(ARM64) 320 // FIXME: https://bugs.webkit.org/show_bug.cgi?id=152510 321 // We're running into a bug where some ARM64 tests are failing in the FTL 322 // with what appears to be an llvm bug where llvm is miscalculating the 323 // live-out variables of a patchpoint. This causes us to not keep a 324 // volatile register alive across a C call in a patchpoint, even though 325 // that register is used immediately after the patchpoint. 326 Options::assumeAllRegsInFTLICAreLive() = true; 327 #endif 329 328 330 329 // Compute the maximum value of the reoptimization retry counter. This is simply
Note:
See TracChangeset
for help on using the changeset viewer.