- 04 Nov, 2015 1 commit
-
-
hpayer authored
BUG= Review URL: https://codereview.chromium.org/1430943004 Cr-Commit-Position: refs/heads/master@{#31766}
-
- 03 Nov, 2015 39 commits
-
-
mlippautz authored
Revert of [heap] Turn on parallel compaction (patchset #1 id:1 of https://codereview.chromium.org/1364693002/ ) Reason for revert: Fails on gc stress https://chromegw.corp.google.com/i/client.v8/builders/V8%20Linux%20-%20gc%20stress/builds/157/ Original issue's description: > [heap] Turn on parallel compaction > > R=hpayer@chromium.org > BUG=chromium:524425 > LOG=N > > Committed: https://crrev.com/04db5bfa915766b228218ddc748af308b57ae8ea > Cr-Commit-Position: refs/heads/master@{#31763} TBR=hpayer@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=chromium:524425 Review URL: https://codereview.chromium.org/1424313008 Cr-Commit-Position: refs/heads/master@{#31765}
-
bradnelson authored
Only cast to integer with xor (closer to the spec which allows only ~~). Check type matching on the bitwise operations. Prevent mixing of types with the arthimetic operations. BUG= https://code.google.com/p/v8/issues/detail?id=4203 TEST=test-asm-validator R=titzer@chromium.org,aseemgarg@chromium.org LOG=N Review URL: https://codereview.chromium.org/1405383007 Cr-Commit-Position: refs/heads/master@{#31764}
-
mlippautz authored
R=hpayer@chromium.org BUG=chromium:524425 LOG=N Review URL: https://codereview.chromium.org/1364693002 Cr-Commit-Position: refs/heads/master@{#31763}
-
mlippautz authored
BUG=chromium:524425 LOG=N Review URL: https://codereview.chromium.org/1410633005 Cr-Commit-Position: refs/heads/master@{#31762}
-
balazs.kilvady authored
BUG= Review URL: https://codereview.chromium.org/1396133002 Cr-Commit-Position: refs/heads/master@{#31761}
-
ishell authored
BUG=v8:3886 LOG=Y Review URL: https://codereview.chromium.org/1422853004 Cr-Commit-Position: refs/heads/master@{#31760}
-
ishell authored
BUG=v8:3101, v8:3330 LOG=Y Review URL: https://codereview.chromium.org/1424283002 Cr-Commit-Position: refs/heads/master@{#31759}
-
machenbach authored
Revert of Implement flag and source getters on RegExp.prototype. (patchset #3 id:50001 of https://codereview.chromium.org/1419823010/ ) Reason for revert: [Sheriff] Changes layout tests. Please rebase upstream first. E.g.: http://build.chromium.org/p/client.v8.fyi/builders/V8-Blink%20Linux%2064/builds/2686 Original issue's description: > Implement flag and source getters on RegExp.prototype. > > R=littledan@chromium.org > BUG=v8:3715, v8:4528 > LOG=Y > > Committed: https://crrev.com/60e8877e161fe6175e19fafce2d6ed1c3999cdb1 > Cr-Commit-Position: refs/heads/master@{#31753} TBR=littledan@chromium.org,jochen@chromium.org,ulan@chromium.org,yangguo@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=v8:3715, v8:4528 Review URL: https://codereview.chromium.org/1427733005 Cr-Commit-Position: refs/heads/master@{#31758}
-
rmcilroy authored
Corrects LdaGlobal to deal with TypeofMode::INSIDE_TYPEOF so that it doesn't throw a reference error on undefined globals. BUG=v8:4280 LOG=N Review URL: https://codereview.chromium.org/1422443006 Cr-Commit-Position: refs/heads/master@{#31757}
-
ishell authored
Original issue's description: > [es6] Fix Function and GeneratorFunction built-ins subclassing. > > BUG=v8:3101, v8:3330 > LOG=Y > > Committed: https://crrev.com/99e7f872d3d0a5fb799dcbafb05537cda491314a > Cr-Commit-Position: refs/heads/master@{#31708} The problem was in another CL, this is a clean reland with improved tests. BUG=v8:3101, v8:3330 LOG=Y Review URL: https://codereview.chromium.org/1415683007 Cr-Commit-Position: refs/heads/master@{#31756}
-
adamk authored
This matches the approach used for @@isConcatSpreadable, and seems to match what Mozilla is planning to do in Firefox. Given that there's already little compatibility around cross-origin toString results, there seems to be little hazard in making this change even before spec language hits the HTML spec. BUG=v8:3502, v8:4289, chromium:532469 LOG=n Review URL: https://codereview.chromium.org/1432543002 Cr-Commit-Position: refs/heads/master@{#31755}
-
ishell authored
Review URL: https://codereview.chromium.org/1432493003 Cr-Commit-Position: refs/heads/master@{#31754}
-
yangguo authored
R=littledan@chromium.org BUG=v8:3715, v8:4528 LOG=Y Review URL: https://codereview.chromium.org/1419823010 Cr-Commit-Position: refs/heads/master@{#31753}
-
ahaas authored
Review URL: https://codereview.chromium.org/1424333002 Cr-Commit-Position: refs/heads/master@{#31752}
-
neis authored
If the property is a data property on the holder (or does not exist) and is a readonly data property in the receiver, then we must fail. R=rossberg, verwaest@chromium.org BUG= Review URL: https://codereview.chromium.org/1424233005 Cr-Commit-Position: refs/heads/master@{#31751}
-
jkummerow authored
BUG=v8:4534 LOG=n R=yangguo@chromium.org Review URL: https://codereview.chromium.org/1413723011 Cr-Commit-Position: refs/heads/master@{#31750}
-
mstarzinger authored
R=bmeurer@chromium.org TEST=mozilla/js1_5/Regress/regress-343713 Review URL: https://codereview.chromium.org/1424313007 Cr-Commit-Position: refs/heads/master@{#31749}
-
bmeurer authored
The JSNativeContextSpecialization class is getting rather huge with all the stuff related to property and element access going in. Splitting off the global object related stuff into JSGlobalObjectSpecialization seems like a natural separation, especially since the global object specialization is sort of separate issue anyway. This is neutral functionality- and performance-wise. R=jarin@chromium.org BUG=v8:4470 LOG=n Review URL: https://codereview.chromium.org/1417043006 Cr-Commit-Position: refs/heads/master@{#31748}
-
rossberg authored
R=neis@chromium.org BUG= Review URL: https://codereview.chromium.org/1422803003 Cr-Commit-Position: refs/heads/master@{#31747}
-
mstarzinger authored
R=yangguo@chromium.org TEST=cctest/test-debug/Backtrace Review URL: https://codereview.chromium.org/1415463017 Cr-Commit-Position: refs/heads/master@{#31746}
-
neis authored
R=verwaest@chromium.org BUG=chromium:548194 LOG=y Review URL: https://codereview.chromium.org/1426293003 Cr-Commit-Position: refs/heads/master@{#31745}
-
ishell authored
Review URL: https://codereview.chromium.org/1410023013 Cr-Commit-Position: refs/heads/master@{#31744}
-
ishell authored
1) The Map::CopyInitialMap() did not set descriptor's array if the source initial map had one. 2) Subclasses are temporarily disallowed to have more in-object properties than the parent class (for GC reasons). BUG=v8:3101, v8:3330, v8:4531 LOG=N Review URL: https://codereview.chromium.org/1431593003 Cr-Commit-Position: refs/heads/master@{#31743}
-
mstarzinger authored
This changes the inlining candidates to be stored in a sorted set of unique entries instead of a vector. We can avoid the final sorting operation by amortizing the cost across insertions and also duplicate entries are not created in the first place. Duplicate entries cause crashes when candidates are processed. R=bmeurer@chromium.org BUG=chromium:549113 LOG=n Review URL: https://codereview.chromium.org/1430553003 Cr-Commit-Position: refs/heads/master@{#31742}
-
rmcilroy authored
Existing code was assuming that 'lexical' blocks were the same as basic blocks, therefore code which emitted jumps within a lexical block (e.g., logical or) would in some occassions incorrectly omit a necessary ToBoolean. This change removes Enter/LeaveBlock from BytecodeArrayBuilder and instead tracks basic blocks via label bindings and jump operations. The change also ensures we don't emit dead code at the end of a basic block, and adds tests of the edge cases. BUG=v8:4280 LOG=N Review URL: https://codereview.chromium.org/1406983010 Cr-Commit-Position: refs/heads/master@{#31741}
-
machenbach authored
The flake detection is done on the infra-side according to the contents of the json test results. We don't want the runner to fail after flakes. This was controlled on the infra side by accepting any exit codes so far. After the swarming switch, this is more difficult, because the runner is wrapped by the swarming collect script. There, failing exit codes can mean many things, including network failures. Therefore, we now force exit code 0 with test failures if those failures are reported in the formal test results json. The infrastructure will take care of reporting the flakes and failures accordingly. BUG=chromium:535160 LOG=n Review URL: https://codereview.chromium.org/1416373005 Cr-Commit-Position: refs/heads/master@{#31740}
-
bmeurer authored
TurboFan is actually able to generate property access to all prototypes of all primitives, except the special Oddball primitives that have no wrapper counterparts (namely null and undefined from the ES6 point of view). R=jarin@chromium.org BUG=v8:4470 LOG=n Review URL: https://codereview.chromium.org/1409163007 Cr-Commit-Position: refs/heads/master@{#31739}
-
jkummerow authored
This CL fixes an invalid cast in Slow_ArrayConcat (a Proxy on a DICTIONARY_ELEMENTS array's prototype chain). It also adds some comments and minor drive-by refactorings to other PrototypeIterator use sites. R=verwaest@chromium.org Review URL: https://codereview.chromium.org/1402393003 Cr-Commit-Position: refs/heads/master@{#31738}
-
yangguo authored
R=machenbach@chromium.org BUG=v8:4534 LOG=N Review URL: https://codereview.chromium.org/1426453005 Cr-Commit-Position: refs/heads/master@{#31737}
-
Michael Achenbach authored
Cr-Commit-Position: refs/heads/master@{#31736}
-
yangguo authored
R=ishell@chromium.org Committed: https://crrev.com/aa26f5d4a11a1e5655d425ff40ced79c8ecdd55f Cr-Commit-Position: refs/heads/master@{#31722} Review URL: https://codereview.chromium.org/1421703004 Cr-Commit-Position: refs/heads/master@{#31735}
-
yangguo authored
R=machenbach@chromium.org BUG=v8:3079 LOG=N Review URL: https://codereview.chromium.org/1406293010 Cr-Commit-Position: refs/heads/master@{#31734}
-
neis authored
When the property is an accessor property in the receiver but not on the holder (ES6 "target"), we must fail. R=rossberg, verwaest@chromium.org BUG= Review URL: https://codereview.chromium.org/1427113002 Cr-Commit-Position: refs/heads/master@{#31733}
-
bmeurer authored
Revert of [turbofan] Remove redundant code. (patchset #1 id:1 of https://codereview.chromium.org/1428943004/ ) Reason for revert: This CL reintroduces all kinds of funny moves for Merges of deferred code, which makes jump threading ineffective. Original issue's description: > [turbofan] Remove redundant code. > > When I centralized the treatment of memory operands, I forgot to delete > the old code. > > There is a semantic difference between the old and new code. The old > code was handling either memory operands, or ranges that had a spilled > predecessor. The new code handles just memory operands. It may > happen that (using LinearScan) an active range is spilled when trying > to allocate another range (see SplitAndSpillIntersecting). That may make > it a candidate for the old version of the code, however, since we would > have spilled up to a register use, the old code wouldn't have had taken > effect. > > Perf data shows this nuance doesn't make a difference in perf. > > BUG= > > Committed: https://crrev.com/c03d7a7f03657a452f71277d84e435ed73566327 > Cr-Commit-Position: refs/heads/master@{#31729} TBR=jarin@chromium.org,mtrofin@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG= Review URL: https://codereview.chromium.org/1416293004 Cr-Commit-Position: refs/heads/master@{#31732}
-
bmeurer authored
Implement the missing bits for named access to Number values, which is basically always done on the Number prototype. Crankshaft only deals with Number primitives in the polymorphic case, while we generally support Numbers even for monomorphic access. R=jarin@chromium.org BUG=v8:4470 LOG=n Review URL: https://codereview.chromium.org/1425293004 Cr-Commit-Position: refs/heads/master@{#31731}
-
yangguo authored
R=littledan@chromium.org BUG=v8:4003 LOG=N Review URL: https://codereview.chromium.org/1423993006 Cr-Commit-Position: refs/heads/master@{#31730}
-
mtrofin authored
When I centralized the treatment of memory operands, I forgot to delete the old code. There is a semantic difference between the old and new code. The old code was handling either memory operands, or ranges that had a spilled predecessor. The new code handles just memory operands. It may happen that (using LinearScan) an active range is spilled when trying to allocate another range (see SplitAndSpillIntersecting). That may make it a candidate for the old version of the code, however, since we would have spilled up to a register use, the old code wouldn't have had taken effect. Perf data shows this nuance doesn't make a difference in perf. BUG= Review URL: https://codereview.chromium.org/1428943004 Cr-Commit-Position: refs/heads/master@{#31729}
-
zhengxing.li authored
On X87 the count of double register number is landed on the top of x87 register stack for deoptimization. (chunyang.dai@intle.com) R=weiliang.lin@intel.com BUG= Review URL: https://codereview.chromium.org/1411223010 Cr-Commit-Position: refs/heads/master@{#31728}
-
littledan authored
R=adamk Review URL: https://codereview.chromium.org/1429963002 Cr-Commit-Position: refs/heads/master@{#31727}
-