- 03 Jul, 2015 6 commits
-
-
bmeurer authored
Currently we lower shifts directly to machine operators, and add an appropriate Word32And to implement the & 0x1F operation on the right hand side required by the specification. However for Word32And we assume Int32 in simplified lowering, which is basically changes the right hand side bit interpretation for the shifts from Uint32 to Int32, which is obviously wrong. So now we represent that explicitly by proper simplified operators for the shifts, which are lowered to machine in simplified lowering. R=jarin@chromium.org Review URL: https://codereview.chromium.org/1213803008 Cr-Commit-Position: refs/heads/master@{#29465}
-
yangguo authored
R=machenbach@chromium.org BUG=v8:4127 LOG=N Review URL: https://codereview.chromium.org/1215123002 Cr-Commit-Position: refs/heads/master@{#29464}
-
yangguo authored
LOG=N R=bmeurer@chromium.org BUG=chromium:506443 Review URL: https://codereview.chromium.org/1217673003 Cr-Commit-Position: refs/heads/master@{#29463}
-
Ilija.Pavlovic authored
MIPS: Disassembler enhancement. Disassembled branch instruction displays branch target absolute address. TEST=cctest/test-disasm-mips[64] BUG= Review URL: https://codereview.chromium.org/1213553004 Cr-Commit-Position: refs/heads/master@{#29462}
-
mstarzinger authored
This makes sure that the GC fully flushes the optimized code map when the serializer is preparing a snapshot. Otherwise closures and contexts could end up in the startup snapshot. R=hpayer@chromium.org TEST=cctest/test-serialize/SerializeInternalReference Review URL: https://codereview.chromium.org/1215063007 Cr-Commit-Position: refs/heads/master@{#29461}
-
titzer authored
Also add control inputs to 64-bit integer divide and modulus operations. R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/1223613002 Cr-Commit-Position: refs/heads/master@{#29460}
-
- 02 Jul, 2015 29 commits
-
-
dstence authored
R=mbrandy@us.ibm.com, michael_dawson@ca.ibm.com BUG= Review URL: https://codereview.chromium.org/1222133004 Cr-Commit-Position: refs/heads/master@{#29459}
-
ulan authored
BUG= Review URL: https://codereview.chromium.org/1222203003 Cr-Commit-Position: refs/heads/master@{#29458}
-
ulan authored
BUG=chromium:505776 LOG=NO Review URL: https://codereview.chromium.org/1221573003 Cr-Commit-Position: refs/heads/master@{#29457}
-
hpayer authored
BUG= Review URL: https://codereview.chromium.org/1222013002 Cr-Commit-Position: refs/heads/master@{#29456}
-
verwaest authored
BUG=v8:4137 LOG=n Review URL: https://codereview.chromium.org/1225493002 Cr-Commit-Position: refs/heads/master@{#29455}
-
ulan authored
BUG= TBR=hpayer@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true Review URL: https://codereview.chromium.org/1219863003 Cr-Commit-Position: refs/heads/master@{#29454}
-
mbrandy authored
Port 1fa4285e Original commit message: This involves: - Enabling the tail call optimization reducer in all cases. - Adding an addition flag to CallFunctionParameters to mark call sites that can be tail-called enabled. - Only set the tail-call flag for %_CallFunction. R=danno@chromium.org, dstence@us.ibm.com, michael_dawson@ca.ibm.com BUG= Review URL: https://codereview.chromium.org/1224533002 Cr-Commit-Position: refs/heads/master@{#29453}
-
jochen authored
BUG=v8:4134 R=vogelheim@chromium.org LOG=n Review URL: https://codereview.chromium.org/1219133004 Cr-Commit-Position: refs/heads/master@{#29452}
-
ulan authored
BUG=490559 LOG=NO Review URL: https://codereview.chromium.org/1218863002 Cr-Commit-Position: refs/heads/master@{#29451}
-
verwaest authored
Additionally rips out (now) unnecessary duplicate code in DefineArrayProperty. BUG= Review URL: https://codereview.chromium.org/1224523002 Cr-Commit-Position: refs/heads/master@{#29450}
-
conradw authored
Keeping this CL separate in case there are more GC-stress problems. BUG=v8:3956 LOG=N Review URL: https://codereview.chromium.org/1217543006 Cr-Commit-Position: refs/heads/master@{#29449}
-
conradw authored
BUG=v8:3956 LOG=N Review URL: https://codereview.chromium.org/1219663009 Cr-Commit-Position: refs/heads/master@{#29448}
-
verwaest authored
BUG=v8:4137 LOG=n Review URL: https://codereview.chromium.org/1221713003 Cr-Commit-Position: refs/heads/master@{#29447}
-
ulan authored
BUG= Review URL: https://codereview.chromium.org/1221083004 Cr-Commit-Position: refs/heads/master@{#29446}
-
jochen authored
BUG=none R=vogelheim@chromium.org LOG=n Review URL: https://codereview.chromium.org/1218153006 Cr-Commit-Position: refs/heads/master@{#29445}
-
verwaest authored
BUG=v8:4137 LOG=n Review URL: https://codereview.chromium.org/1226473003 Cr-Commit-Position: refs/heads/master@{#29444}
-
ulan authored
BUG= Review URL: https://codereview.chromium.org/1213593004 Cr-Commit-Position: refs/heads/master@{#29443}
-
erikcorry authored
BUG= Review URL: https://codereview.chromium.org/1077153004 Cr-Commit-Position: refs/heads/master@{#29442}
-
Michael Achenbach authored
Cr-Commit-Position: refs/heads/master@{#29441}
-
mstarzinger authored
This is an adaptation of test-profile-generator/BailoutReason to when try-catch statements are optimizable. They will no longer cause any bailout reason to be reported. R=yangguo@chromium.org TEST=cctest/test-profile-generator/BailoutReason Review URL: https://codereview.chromium.org/1213113007 Cr-Commit-Position: refs/heads/master@{#29440}
-
ishell authored
The only right way to enable access checks is to install access check callbacks on an object template via v8::ObjectTemplate::SetAccessCheckCallbacks(). It does not make sense to enable access checks on an arbitrary object. Review URL: https://codereview.chromium.org/1217893012 Cr-Commit-Position: refs/heads/master@{#29439}
-
danno authored
Review URL: https://codereview.chromium.org/1223583003 Cr-Commit-Position: refs/heads/master@{#29438}
-
dcheng authored
Clang warns if there are missing braces around a subobject initializer. The most common idiom that triggers this is: STRUCT s = {0}; if the first field of STRUCT is itself a struct. This can be more simply written as: STRUCT s = {}; which also prevents the warning from firing. BUG=chromium:505297 LOG=n Review URL: https://codereview.chromium.org/1219233003 Cr-Commit-Position: refs/heads/master@{#29437}
-
danno authored
This involves: - Enabling the tail call optimization reducer in all cases. - Adding an addition flag to CallFunctionParameters to mark call sites that can be tail-called enabled. - Only set the tail-call flag for %_CallFunction. R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/1216933011 Cr-Commit-Position: refs/heads/master@{#29436}
-
martyn.capewell authored
Support 32-bit cmp with shift/extend by reusing the existing add/sub shift and extend code. Review URL: https://codereview.chromium.org/1218103005 Cr-Commit-Position: refs/heads/master@{#29435}
-
chunyang.dai authored
port 7281f801 (r29384) Fix a bug in R29384. original commit message: Revert "Revert relanded strong property access CL" Regression issues should be solved. Initial patchset is the original, subsequent patchsets are the fixing modifications. This reverts commit 4ac7be56. BUG= Review URL: https://codereview.chromium.org/1210873007 Cr-Commit-Position: refs/heads/master@{#29434}
-
chunyang.dai authored
port 7015fd20 (r29402) original commit message: Up until now the context register was listed explicitly in each stub's CallInterfaceDescriptor. This was problematic, because it was listed first in the list of register parameters--which is fine for Crankshaft, which is more or less built to handle the context as the first parameter-- but not ideal for TurboFan, which adds the context at the end of all function parameters. Now the context register is no longer in the register list and can be handled appropriately by both compilers. Specifically, this allows the FunctionType specified for each CallInterfaceDescriptor to exactly match the parameter register list. BUG= Review URL: https://codereview.chromium.org/1216543004 Cr-Commit-Position: refs/heads/master@{#29433}
-
chunyang.dai authored
port b4275a70 (r29378) original commit message: This change makes possible to save and restore the FP registers in the Prologue and Return parts for the CallAddress kind functions. BUG= Review URL: https://codereview.chromium.org/1214573006 Cr-Commit-Position: refs/heads/master@{#29432}
-
v8-autoroll authored
Rolling v8/third_party/icu to 7fe225d77f307fdbe24695179a84336ef95c1253 TBR=machenbach@chromium.org Review URL: https://codereview.chromium.org/1225463002 Cr-Commit-Position: refs/heads/master@{#29431}
-
- 01 Jul, 2015 5 commits
-
-
littledan authored
Conditionally including Array and TypedArray methods seems to cause a slowdown in V8 context creation, possibly due to the new code added. BUG=chromium:504629 R=adamk@chromium.org LOG=Y Review URL: https://codereview.chromium.org/1215863003 Cr-Commit-Position: refs/heads/master@{#29430}
-
erikcorry authored
R=hpayer@chromium.org BUG= Review URL: https://codereview.chromium.org/1217813012 Cr-Commit-Position: refs/heads/master@{#29429}
-
adamk authored
This was added in https://chromium.googlesource.com/v8/v8/+/4a709dd65, but the only check for it that remained in the final patch is inside a DCHECK. It appears that the approach for checking use of class names in methods evolved quite a bit over the review of the original patch. Review URL: https://codereview.chromium.org/1219993002 Cr-Commit-Position: refs/heads/master@{#29428}
-
verwaest authored
BUG= Review URL: https://codereview.chromium.org/1220883006 Cr-Commit-Position: refs/heads/master@{#29427}
-
binji authored
This is more consistent with the DOM API, and is clearer w.r.t. which values are available in the lexical environment of the Worker. BUG=chromium:497295 R=jarin@chromium.org LOG=n Review URL: https://codereview.chromium.org/1218553004 Cr-Commit-Position: refs/heads/master@{#29426}
-