- 29 Sep, 2015 25 commits
-
-
mlippautz authored
See bug description. BUG=chromium:536231 LOG=N Review URL: https://codereview.chromium.org/1378693002 Cr-Commit-Position: refs/heads/master@{#31012}
-
dusan.m.milosavljevic authored
TEST= BUG= Review URL: https://codereview.chromium.org/1334793004 Cr-Commit-Position: refs/heads/master@{#31011}
-
mstarzinger authored
This prevents the internal incremental-marking.h to be usable outisde of the "heap" directory. The logic inside that component is only useful within the GC and is now properly encapsulated. R=hpayer@chromium.org Review URL: https://codereview.chromium.org/1374203002 Cr-Commit-Position: refs/heads/master@{#31010}
-
mstarzinger authored
This changes the operators for JSCreate[Block|Script]Context to take their ScopeInfo as a static parameter as opposed to a value input and in turn allows for easier access to that parameter during lowerings. R=jarin@chromium.org Review URL: https://codereview.chromium.org/1379593002 Cr-Commit-Position: refs/heads/master@{#31009}
-
jacob.bramley authored
It is not safe to access memory below sp, and this is also forbidden by the ABI. When pushing, we must either use an atomic operation (such as vstm+db_w) or move sp before writing the data. This patch fixes one stack access, and also adds vpush and vpop helpers to simplify similar code. BUG= Review URL: https://codereview.chromium.org/1378563002 Cr-Commit-Position: refs/heads/master@{#31008}
-
mstarzinger authored
The NodeProperties helpers are here to stay and won't go away anytime soon. This removes a TODO from the graph verifier in that regard. R=jarin@chromium.org Review URL: https://codereview.chromium.org/1375923002 Cr-Commit-Position: refs/heads/master@{#31007}
-
jarin authored
BUG=v8:4446 LOG=n Review URL: https://codereview.chromium.org/1369313004 Cr-Commit-Position: refs/heads/master@{#31006}
-
jarin authored
This is necessary because these operators can read heap (equality can actually write heap when flattening strings). BUG=v8:4446 LOG=n Review URL: https://codereview.chromium.org/1374683002 Cr-Commit-Position: refs/heads/master@{#31005}
-
mlippautz authored
- Remove the hack the resets the new space top pointer from SeqString::Truncate. - Remove NewSpace::set_top completely as there are no callers (and there should be no!) R=hpayer@chromium.org BUG=chromium:536163 LOG=N Review URL: https://codereview.chromium.org/1376753002 Cr-Commit-Position: refs/heads/master@{#31004}
-
ishell authored
It was broken by https://codereview.chromium.org/1376443002. Review URL: https://codereview.chromium.org/1374923002 Cr-Commit-Position: refs/heads/master@{#31003}
-
vogelheim authored
(This is somewhat experimental; hence protected by #ifdef.) R=epertoso@chromium.org, jochen@chromium.org BUG=chromium:508898 LOG=N Review URL: https://codereview.chromium.org/1367953002 Cr-Commit-Position: refs/heads/master@{#31002}
-
hablich authored
NOTRY=true NOPRESUBMIT=true R=machenbach@chromium.org Review URL: https://codereview.chromium.org/1373223003 Cr-Commit-Position: refs/heads/master@{#31001}
-
mvstanton authored
The LiteralsArray will soon hold a type feedback vector. Code treats it as an ordinary fixed array, and needs to stop that. BUG= Review URL: https://codereview.chromium.org/1374723002 Cr-Commit-Position: refs/heads/master@{#31000}
-
hablich authored
R=machenbach@chromium.org NOPRESUBMIT=true NOTRY=true Review URL: https://codereview.chromium.org/1375533003 Cr-Commit-Position: refs/heads/master@{#30999}
-
hpayer authored
BUG= Review URL: https://codereview.chromium.org/1374163002 Cr-Commit-Position: refs/heads/master@{#30998}
-
cbruni authored
[run-tests.py] - adding more detailed information about the flags - show more detailed error message on failing Popen commands BUG= Review URL: https://codereview.chromium.org/1369343002 Cr-Commit-Position: refs/heads/master@{#30997}
-
yurys authored
BUG=v8:4444,v8:4151 LOG=N Review URL: https://codereview.chromium.org/1371253002 Cr-Commit-Position: refs/heads/master@{#30996}
-
mstarzinger authored
This is mostly removing dead code and also dropping MUST_USE_RESULT annotations from methods that cannot throw an exception anyways. R=hpayer@chromium.org Review URL: https://codereview.chromium.org/1370153002 Cr-Commit-Position: refs/heads/master@{#30995}
-
jacob.bramley authored
The return value is expected to be the number of padding slots added to the frame. However, the original logic would return -1 if padding was required, so insufficient stack space would be reserved. This function now returns either 0 or 1, as the existing calling code expects. BUG= Review URL: https://codereview.chromium.org/1369303002 Cr-Commit-Position: refs/heads/master@{#30994}
-
bmeurer authored
This adds ES6 compliant Object::ToInteger, Object::ToInt32, Object::ToUint32 and Object::ToLength, and replaces the old Execution wrappers of those abstract operations (which were not using the correct ToPrimitive). This also introduces proper %ToInteger and %ToLength runtime entries, with a fast path %_ToInteger supported in fullcodegen and Crankshaft (for now). Internal JavaScript code should use TO_INTEGER and TO_LENGTH respectively. CQ_INCLUDE_TRYBOTS=tryserver.v8:v8_linux_layout_dbg,v8_linux_nosnap_dbg BUG=v8:4307 LOG=n Review URL: https://codereview.chromium.org/1378533002 Cr-Commit-Position: refs/heads/master@{#30993}
-
https://codereview.chromium.org/1362333002/machenbach authored
Reason for revert: [Sheriff] Seems to break layout tests: http://build.chromium.org/p/client.v8.fyi/builders/V8-Blink%20Linux%2064/builds/2073 https://storage.googleapis.com/chromium-layout-test-archives/V8-Blink_Linux_64/2073/layout-test-results/results.html Please request rebaseline upstream first. Original issue's description: > Clean up rewriter. > > The main changes are: > - Fix treatment of loops, which was incorrect and sometimes resulted in > the wrong completion value. > - Get rid of unnecessary variables. > > This is in preparation of implementing ES6 completion semantics. > > R=rossberg > BUG= > > Committed: https://crrev.com/b466dc14791844b7ae6d1e9ebd00a778965c206d > Cr-Commit-Position: refs/heads/master@{#30981} TBR=rossberg@chromium.org,neis@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG= Review URL: https://codereview.chromium.org/1379513002 Cr-Commit-Position: refs/heads/master@{#30992}
-
bmeurer authored
Revert of [heap] Remove retry space from AllocateRaw. (patchset #3 id:40001 of https://codereview.chromium.org/1370123002/ ) Reason for revert: Breaks arm64 nosnap simulator (bogus cctest?): https://chromegw.corp.google.com/i/client.v8/builders/V8%20Linux%20-%20arm64%20-%20sim%20-%20nosnap%20-%20debug%20-%201/builds/2934/steps/Bisect%202786ceec.Retry/logs/IncrementalWriteBarri.. Original issue's description: > [heap] Remove retry space from AllocateRaw. > > BUG= > > Committed: https://crrev.com/2786ceec1eb491494d24d29a59eefbe3b6704be2 > Cr-Commit-Position: refs/heads/master@{#30984} TBR=mstarzinger@chromium.org,hpayer@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG= Review URL: https://codereview.chromium.org/1379493003 Cr-Commit-Position: refs/heads/master@{#30991}
-
mtrofin authored
When all heuristics fail, we run a "last resort" heuristic. Before, it was splitting at the first found splittable position either before or after a use position. That turns out to be too naive: it may split in loops, when alternative split positions exist outside loops. This change chooses a "before" use case location that is outside the loop. Review URL: https://codereview.chromium.org/1372213005 Cr-Commit-Position: refs/heads/master@{#30990}
-
v8-autoroll authored
Rolling v8/buildtools to e7111440c07a883b82ffbbe6d26c744dfc6c9673 TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org Review URL: https://codereview.chromium.org/1374833002 Cr-Commit-Position: refs/heads/master@{#30989}
-
chunyang.dai authored
port 09626525 (r30957). original commit message: BUG= Review URL: https://codereview.chromium.org/1370283003 Cr-Commit-Position: refs/heads/master@{#30988}
-
- 28 Sep, 2015 15 commits
-
-
alph authored
Drive-by: remove unnecessary includes. Review URL: https://codereview.chromium.org/1356223004 Cr-Commit-Position: refs/heads/master@{#30987}
-
oth authored
BUG=v8:4280 LOG=N Review URL: https://codereview.chromium.org/1374613002 Cr-Commit-Position: refs/heads/master@{#30986}
-
mstarzinger authored
R=hpayer@chromium.org Review URL: https://codereview.chromium.org/1372063002 Cr-Commit-Position: refs/heads/master@{#30985}
-
hpayer authored
BUG= Review URL: https://codereview.chromium.org/1370123002 Cr-Commit-Position: refs/heads/master@{#30984}
-
oth authored
The comparison operators and ToBoolean are implemented by calling into the runtime. There are new runtime methods are prefixed with Interpreter to make use case clear. BUG=v8:4280 LOG=N Review URL: https://codereview.chromium.org/1369123002 Cr-Commit-Position: refs/heads/master@{#30983}
-
ishell authored
Revert of Introduce a V8_NORETURN macro and use it to make GCC 4.9.2 happy again. (patchset #3 id:80001 of https://codereview.chromium.org/1361763004/ ) Reason for revert: This CL breaks cross-compiling to arm. Original issue's description: > Introduce a V8_NORETURN macro and use it to make GCC 4.9.2 happy again. > > Without that, it has a few false positives about out-of-bounds array accesses. > Also makes the clang static-analyzer happy. > > Original code review from Sven Panne: > https://codereview.chromium.org/790723002/ > > Committed: https://crrev.com/0b48b2a8ebfc791a36f4ec1f299f46db76265a3a > Cr-Commit-Position: refs/heads/master@{#30977} TBR=jochen@chromium.org,bmeurer@chromium.org,jkummerow@chromium.org,karl@skomski.com NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true Review URL: https://codereview.chromium.org/1370203002 Cr-Commit-Position: refs/heads/master@{#30982}
-
neis authored
The main changes are: - Fix treatment of loops, which was incorrect and sometimes resulted in the wrong completion value. - Get rid of unnecessary variables. This is in preparation of implementing ES6 completion semantics. R=rossberg BUG= Review URL: https://codereview.chromium.org/1362333002 Cr-Commit-Position: refs/heads/master@{#30981}
-
ishell authored
NOTRY=true Review URL: https://codereview.chromium.org/1371913006 Cr-Commit-Position: refs/heads/master@{#30980}
-
caitpotter88 authored
BUG=v8:2899 LOG=N R= Review URL: https://codereview.chromium.org/1364583004 Cr-Commit-Position: refs/heads/master@{#30979}
-
ben authored
Review URL: https://codereview.chromium.org/1369913002 Cr-Commit-Position: refs/heads/master@{#30978}
-
karl authored
Without that, it has a few false positives about out-of-bounds array accesses. Also makes the clang static-analyzer happy. Original code review from Sven Panne: https://codereview.chromium.org/790723002/ Review URL: https://codereview.chromium.org/1361763004 Cr-Commit-Position: refs/heads/master@{#30977}
-
machenbach authored
This was copied into test262. BUG=v8:4254 NOTRY=true LOG=n Review URL: https://codereview.chromium.org/1368313002 Cr-Commit-Position: refs/heads/master@{#30976}
-
jkummerow authored
Replacing it with SMI_ACCESSORS. This change makes accesses to Smi fields in objects more regular (the accessors now always consume/return an int rather than a Smi*), which avoids a bunch of manual Smi::FromInt() and Smi::value() conversions, and is a step on the way towards being able to generate objects-inl.h. Review URL: https://codereview.chromium.org/1371893002 Cr-Commit-Position: refs/heads/master@{#30975}
-
ishell authored
Review URL: https://codereview.chromium.org/1372003002 Cr-Commit-Position: refs/heads/master@{#30974}
-
mstarzinger authored
R=hpayer@chromium.org Review URL: https://codereview.chromium.org/1371943002 Cr-Commit-Position: refs/heads/master@{#30973}
-