- 29 May, 2015 9 commits
-
-
conradw authored
Implements the strong mode proposal's restrictions on changing a strong object's writable, non-configurable property to non-writable. Setting the strong bit is still wip, so this change will only affect those objects that have the bit correctly set. The tests reflect this, and will be expanded as more objects can be marked as strong. BUG=v8:3956 LOG=N Review URL: https://codereview.chromium.org/1142393003 Cr-Commit-Position: refs/heads/master@{#28698}
-
jarin authored
BUG= Review URL: https://codereview.chromium.org/1148293009 Cr-Commit-Position: refs/heads/master@{#28697}
-
yangguo authored
R=mstarzinger@chromium.org BUG=chromium:492522 LOG=Y Review URL: https://codereview.chromium.org/1154163006 Cr-Commit-Position: refs/heads/master@{#28696}
-
mstarzinger authored
R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/1162633002 Cr-Commit-Position: refs/heads/master@{#28695}
-
erikcorry authored
R=ulan@chromium.org BUG= Review URL: https://codereview.chromium.org/1142343009 Cr-Commit-Position: refs/heads/master@{#28694}
-
hpayer authored
BUG= Review URL: https://codereview.chromium.org/1158423002 Cr-Commit-Position: refs/heads/master@{#28693}
-
bmeurer authored
R=jarin@chromium.org Review URL: https://codereview.chromium.org/1157423003 Cr-Commit-Position: refs/heads/master@{#28692}
-
rodolph.perfetta authored
vmov immediate was always emitting movt for some immediates wether or not the CPU supported ARMv7. BUG=v8:4019 LOG=n Review URL: https://codereview.chromium.org/1160093002 Cr-Commit-Position: refs/heads/master@{#28691}
-
v8-autoroll authored
Rolling v8/tools/clang to 5413f2a11e1b56c30e28769b9ff1086797c11b28 TBR=machenbach@chromium.org Review URL: https://codereview.chromium.org/1167453002 Cr-Commit-Position: refs/heads/master@{#28690}
-
- 28 May, 2015 22 commits
-
-
arv authored
Follow up to https://codereview.chromium.org/1135243004 For now we need to call set_base_id in AstNumberingVisitor because TurboFan needs a bailout id for super.prop in a lot of cases. BUG=None LOG=N R=adamk@chromium.org, mstarzinger@chromium.org Review URL: https://codereview.chromium.org/1153053005 Cr-Commit-Position: refs/heads/master@{#28689}
-
bbudge authored
Revert of Clean up aligned allocation code in preparation for SIMD alignments. (patchset #14 id:300001 of https://codereview.chromium.org/1150593003/) Reason for revert: Breaks mjsunit, webkit, mozilla, benchmarks. TBR=hpayer@chromium.org Original issue's description: > Clean up aligned allocation code in preparation for SIMD alignments. > > Moves alignment fill calculations into two static Heap methods. > Adds a Heap method to handle the complex case where filler is potentially needed before and after a heap object. > Makes DoubleAlignForDeserialization explicitly fill after an already > aligned object. > > LOG=N > BUG=v8:4124 > > Committed: https://crrev.com/fcfb080eb9a637f0ae066bed4c45095e60df8a84 > Cr-Commit-Position: refs/heads/master@{#28687} TBR=hpayer@chromium.org,bmeurer@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=v8:4124 Review URL: https://codereview.chromium.org/1159123002 Cr-Commit-Position: refs/heads/master@{#28688}
-
bbudge authored
Moves alignment fill calculations into two static Heap methods. Adds a Heap method to handle the complex case where filler is potentially needed before and after a heap object. Makes DoubleAlignForDeserialization explicitly fill after an already aligned object. LOG=N BUG=v8:4124 Review URL: https://codereview.chromium.org/1150593003 Cr-Commit-Position: refs/heads/master@{#28687}
-
mbrandy authored
Port 3a1d7335 Original commit message: This finishes up work begun by CL (https://codereview.chromium.org/546683003/) some months ago. R=mvstanton@chromium.org, dstence@us.ibm.com, michael_dawson@ca.ibm.com BUG= Review URL: https://codereview.chromium.org/1160933003 Cr-Commit-Position: refs/heads/master@{#28686}
-
mbrandy authored
R=bmeurer@chromium.org, dstence@us.ibm.com, michael_dawson@ca.ibm.com BUG= Review URL: https://codereview.chromium.org/1143153013 Cr-Commit-Position: refs/heads/master@{#28685}
-
sergiyb authored
This will land with https://chromereviews.googleplex.com/202967013 R=akuegel@chromium.org, machenbach@chromium.org BUG=471767 NOTRY=true LOG=N Review URL: https://codereview.chromium.org/1161873004 Cr-Commit-Position: refs/heads/master@{#28684}
-
mvstanton authored
This finishes up work begun by CL (https://codereview.chromium.org/546683003/) some months ago. BUG= Review URL: https://codereview.chromium.org/1149053004 Cr-Commit-Position: refs/heads/master@{#28683}
-
bmeurer authored
This is an initial step towards a faster and less incorrect implementation of for-in in TurboFan. R=jarin@chromium.org Review URL: https://codereview.chromium.org/1153403002 Cr-Commit-Position: refs/heads/master@{#28682}
-
mstarzinger authored
This introduces a conservative prediction for each exception handler whether it will locally catch an exception or re-throw it to outside the code bondaries. It will allow for a more intuitive prediction of whether an exception is considered "caught" or "uncaught". R=bmeurer@chromium.org,yangguo@chromium.org BUG=chromium:492522 LOG=N Review URL: https://codereview.chromium.org/1158563008 Cr-Commit-Position: refs/heads/master@{#28681}
-
erikcorry authored
R=hpayer@chromium.org BUG= Review URL: https://codereview.chromium.org/1158933007 Cr-Commit-Position: refs/heads/master@{#28680}
-
machenbach authored
NOTRY=true Review URL: https://codereview.chromium.org/1156663009 Cr-Commit-Position: refs/heads/master@{#28679}
-
jochen authored
BUG=4134 R=vogelheim@chromium.org LOG=n Review URL: https://codereview.chromium.org/1154423004 Cr-Commit-Position: refs/heads/master@{#28678}
-
bmeurer authored
We need the shared function info of inlined functions to prevent code flushing for their unoptimized code, and also to make sure that liveedit can find the proper functions to deoptimize. R=jarin@chromium.org Review URL: https://codereview.chromium.org/1156403002 Cr-Commit-Position: refs/heads/master@{#28677}
-
machenbach authored
BUG=chromium:489254 LOG=n Review URL: https://codereview.chromium.org/1143173005 Cr-Commit-Position: refs/heads/master@{#28676}
-
bmeurer authored
R=jarin@chromium.org Review URL: https://codereview.chromium.org/1156393002 Cr-Commit-Position: refs/heads/master@{#28675}
-
bmeurer authored
The control flow optimization should work independent of the JSGraph. We used the JSGraph there because it was convinient, not because it was necessary. R=jarin@chromium.org Review URL: https://codereview.chromium.org/1160863003 Cr-Commit-Position: refs/heads/master@{#28674}
-
bmeurer authored
The SimplifiedOperatorReducer is (mostly) unused, except for the very rough store elimination, and just eats compilation time. R=jarin@chromium.org Review URL: https://codereview.chromium.org/1162563002 Cr-Commit-Position: refs/heads/master@{#28673}
-
bmeurer authored
The list of inlined functions is used in exactly two places - for live edit and to prevent code flushing for inlined functions - and those are fine with SharedFunctionInfo and don't require a closure. This is one additional step towards inlining based on SharedFunctionInfo instead of JSFunction. R=jarin@chromium.org Review URL: https://codereview.chromium.org/1145893003 Cr-Commit-Position: refs/heads/master@{#28672}
-
yangguo authored
R=arv@chromium.org BUG=chromium:492526 LOG=N Review URL: https://codereview.chromium.org/1146923004 Cr-Commit-Position: refs/heads/master@{#28671}
-
yangguo authored
R=mstarzinger@chromium.org BUG=chromium:490680 LOG=Y Review URL: https://codereview.chromium.org/1157563005 Cr-Commit-Position: refs/heads/master@{#28670}
-
bmeurer authored
Neither the increment nor the comparison can deoptimize, so we don't need proper frame states there. R=jarin@chromium.org Review URL: https://codereview.chromium.org/1148323003 Cr-Commit-Position: refs/heads/master@{#28669}
-
v8-autoroll authored
Rolling v8/build/gyp to 29e94a3285ee899d14d5e56a6001682620d3778f Rolling v8/tools/clang to dc8f173e7fe10badbd9e29cd6eadc32ec552e691 TBR=machenbach@chromium.org Review URL: https://codereview.chromium.org/1156373003 Cr-Commit-Position: refs/heads/master@{#28668}
-
- 27 May, 2015 9 commits
-
-
akos.palfi authored
This test is little-endian specific and therefore it can't run correctly on big-endian platforms. BUG= Review URL: https://codereview.chromium.org/1155113008 Cr-Commit-Position: refs/heads/master@{#28667}
-
mbrandy authored
Port 5450fc07 Original commit message: Also adapt code generation to pass the slot to the store/keyed-store ic. AST nodes ObjectLiteral, Assignment, ForEach, Call and CountOperation now include one or more feedback vector ic slot ids. R=mvstanton@chromium.org, dstence@us.ibm.com, michael_dawson@ca.ibm.com BUG= Review URL: https://codereview.chromium.org/1156503003 Cr-Commit-Position: refs/heads/master@{#28666}
-
mbrandy authored
Port 44e98103 Original commit message: When we enter a method that needs access to the [[HomeObject]] we allocate a local variable `.home_object` and assign it the value from the [[HomeObject]] private symbol. Something along the lines of: method() { var .home_object = %ThisFunction()[home_object_symbol]; ... } R=arv@chromium.org, dstence@us.ibm.com, michael_dawson@ca.ibm.com BUG= Review URL: https://codereview.chromium.org/1161603004 Cr-Commit-Position: refs/heads/master@{#28665}
-
conradw authored
Implements the strong mode proposal's restrictions on the ability of user code to modify the prototype of strong objects. Setting the strong bit is still wip, so this change will only affect those objects that have the bit correctly set. The tests reflect this, and will be expanded as more objects can be marked as strong. BUG=v8:3956 LOG=N Review URL: https://codereview.chromium.org/1143623002 Cr-Commit-Position: refs/heads/master@{#28664}
-
machenbach authored
BUG=chromium:489254 LOG=n Review URL: https://codereview.chromium.org/1158903002 Cr-Commit-Position: refs/heads/master@{#28663}
-
ulan authored
Make sure that when manual evacuation candidate selection is enabled we do not select more pages than requested. BUG= TBR=hpayer@chromium.org Review URL: https://codereview.chromium.org/1157293002 Cr-Commit-Position: refs/heads/master@{#28662}
-
vogelheim authored
The DCHECK was a lie. The idea was that - when a bookmark is set - the scanner must clearly be at a character boundary and hence the bookmark does not need to save a 'partial' UTF-8 code point. The first part is true - the Scanner is always at a character boundary - but the 'partial' UTF-8 code point is at the end of a block, not at the current character position of the Scanner. Hence, the 'partial' character needs to be saved as well. jkummerow: Thanks for noticing. BUG=chromium:470930 R=jochen@chromium.org, jkummerow@chromium.org LOG=N Review URL: https://codereview.chromium.org/1154773004 Cr-Commit-Position: refs/heads/master@{#28661}
-
jochen authored
Also deprecate ForceSet BUG=chromium:475206 R=adamk@chromium.org,verwaest@chromium.org LOG=y Review URL: https://codereview.chromium.org/1154233003 Cr-Commit-Position: refs/heads/master@{#28660}
-
mvstanton authored
Also adapt code generation to pass the slot to the store/keyed-store ic. AST nodes ObjectLiteral, Assignment, ForEach, Call and CountOperation now include one or more feedback vector ic slot ids. BUG= Review URL: https://codereview.chromium.org/1161623002 Cr-Commit-Position: refs/heads/master@{#28659}
-