- 20 Jul, 2016 37 commits
-
-
bbudge authored
Fixes bug in test-gap-resolver.cc that didn't test different move reps. Fixes test canonicalization so all slots have the same type (non-float). Improve test failure text output. LOG=N BUG=v8:5187 Review-Url: https://codereview.chromium.org/2169493002 Cr-Commit-Position: refs/heads/master@{#37915}
-
adamk authored
SharedFunctionInfo::name is always a String if present (never a Symbol), so there's no need to first test it for IsName() before testing IsString(). This is enforced by a check in %FunctionSetName. As a bonus, the code no longer looks invalid (unconditionally casting a Name to a String). The logic came into this broken-looking state accidentally in the flag cleanup CL https://codereview.chromium.org/2096933002/. Review-Url: https://codereview.chromium.org/2162853003 Cr-Commit-Position: refs/heads/master@{#37914}
-
mattloring authored
Allows jitted code to be annotated in perf. To use: 1) Report generated code in code-(pid)-1.asm. perf record -- d8 --print-code --redirect-code-traces script.js 2) Run perf report from the directory containing the above code file. perf report --objdump=v8/tools/objdump-v8 This script supports generated code from both crankshaft or turbofan. BUG= Review-Url: https://codereview.chromium.org/2167553002 Cr-Commit-Position: refs/heads/master@{#37913}
-
verwaest authored
NewScope automatically uses scope(), whereas NewScopeWithParent can pass along any local Scope* as outer scope. The number of calls to NewScopeWithParent should be reduced over time. BUG=v8:5209 Review-Url: https://codereview.chromium.org/2164943002 Cr-Commit-Position: refs/heads/master@{#37912}
-
ahaas authored
This CL more or less reverts commit https://codereview.chromium.org/2107733002/ The use of the MathPow code stub that was introduced by that commit caused problems on arm64, and the MathPow code stub was also an obstacle in the implementation of parallel code generation. In addition this CL turns on the mjsunit/wasm/embenchen tests for arm64 which were turned off because of problems with MathPow on arm64. R=titzer@chromium.org, bradnelson@chromium.org Review-Url: https://codereview.chromium.org/2166793002 Cr-Commit-Position: refs/heads/master@{#37911}
-
ishell authored
This CL fixes weird performance implications when changing layout of Code::flags field: it happened that the unused ICStateField with MONOMORPHIC value in the handlers' flags was accidentally offsetting the underflow bug in stub cache probing code on arm, arm64, mips and mips64. Stub cache tests now work even when snapshot is enabled. Drive-by-change: Fixed counters manipulation on arm64 and mips64. BUG=chromium:618701 Review-Url: https://codereview.chromium.org/2161153002 Cr-Commit-Position: refs/heads/master@{#37910}
-
jgruber authored
R=yangguo@chromium.org BUG= Review-Url: https://codereview.chromium.org/2163933002 Cr-Commit-Position: refs/heads/master@{#37909}
-
jgruber authored
This ports a large portion of Error methods to C++, including the constructor, stack setter and getter, and Error.prototype.toString. BUG= Committed: https://crrev.com/5742da056a290caa13a0b8717ddb1e43424e0d31 Review-Url: https://codereview.chromium.org/2142933003 Cr-Original-Commit-Position: refs/heads/master@{#37870} Cr-Commit-Position: refs/heads/master@{#37908}
-
verwaest authored
It's the only Scope type that has outer scope nullptr; and it always has outer scope nullptr. BUG=v8:5209 Review-Url: https://codereview.chromium.org/2158913005 Cr-Commit-Position: refs/heads/master@{#37907}
-
jochen authored
BUG=v8:5215 R=marja@chromium.org Review-Url: https://codereview.chromium.org/2161033003 Cr-Commit-Position: refs/heads/master@{#37906}
-
jochen authored
That way, backtraces should work BUG= R=machenbach@chromium.org Review-Url: https://codereview.chromium.org/2168593002 Cr-Commit-Position: refs/heads/master@{#37905}
-
klaasb authored
For some bytecodes it is beneficial to always look for a Star bytecode when dispatching to the next and inline perform it without dispatching to the Star handler. BUG=v8:4280 LOG=N Review-Url: https://codereview.chromium.org/2142273003 Cr-Commit-Position: refs/heads/master@{#37904}
-
machenbach authored
BUG=chromium:629025 NOTRY=true NOPRESUBMIT=true TBR=sergiyb@chromium.org Review-Url: https://codereview.chromium.org/2165883003 Cr-Commit-Position: refs/heads/master@{#37903}
-
verwaest authored
This additionally makes the invariant obvious that outer_scope==nullptr+is_with_scope is impossible. BUG=v8:5209 Review-Url: https://codereview.chromium.org/2165923002 Cr-Commit-Position: refs/heads/master@{#37902}
-
jochen authored
It takes the number of additional elements, not the total target capacity. Also, avoid right-shifting a negative integer as this is undefined in general BUG=v8:4909 R=verwaest@chromium.org Review-Url: https://codereview.chromium.org/2162333002 Cr-Commit-Position: refs/heads/master@{#37901}
-
mstarzinger authored
By now TurboFan is shipping on a broad range of language constructs and wholesale disabling TurboFan can still be done with the --turbo-filter flag. A dedicated flag controlling AST numbering heuristics is no longer needed. R=bmeurer@chromium.org Review-Url: https://codereview.chromium.org/2155243006 Cr-Commit-Position: refs/heads/master@{#37900}
-
bmeurer authored
Revert of [turbofan] Introduce TruncateTaggedToBit operator for ToBoolean truncation. (patchset #2 id:20001 of https://codereview.chromium.org/2167593002/ ) Reason for revert: Breaks arm64 gc stress: https://build.chromium.org/p/client.v8.ports/builders/V8%20Linux%20-%20arm64%20-%20sim%20-%20gc%20stress/builds/1605 Original issue's description: > [turbofan] Introduce TruncateTaggedToBit operator for ToBoolean truncation. > > Add a dedicated simplified operator to inline the general case for the > ToBoolean conversion. In a follow up CL we will also use the ToBoolean > hints gathered by the baseline compiler. > > Committed: https://crrev.com/8c50b51ab3d21efcd2f6900d83962159f21e1590 > Cr-Commit-Position: refs/heads/master@{#37882} TBR=jarin@chromium.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true Review-Url: https://codereview.chromium.org/2170433002 Cr-Commit-Position: refs/heads/master@{#37899}
-
verwaest authored
This creates the guarantee that we can compute the parent scope later on. We'll do the same for other types of scopes as well (with perhaps a limited number of exceptions that will need to be eagerly allocated). BUG=v8:5209 Review-Url: https://codereview.chromium.org/2168563002 Cr-Commit-Position: refs/heads/master@{#37898}
-
neis authored
As required by the spec. This is a variant of what I reverted in f47e7224. It will probably still cause a regression but now it's easier to migrate (parts of) the current implementation to C++, which is expected to make things faster again. BUG=chromium:627729,v8:5113 Review-Url: https://codereview.chromium.org/2164923002 Cr-Commit-Position: refs/heads/master@{#37897}
-
machenbach authored
This prepares for relanding: https://codereview.chromium.org/2058033002/ All toplevel variables are visible in files including v8.gni. This works around potential name clashes. BUG=chromium:616034 Review-Url: https://codereview.chromium.org/2169443002 Cr-Commit-Position: refs/heads/master@{#37896}
-
jacob.bramley authored
This avoids implementation-defined signed overflow in the simulator's AddWithCarry implementation. The implementation of AddWithCarry now uses unsigned arithmetic exclusively. Testing coverage is also significantly improved. BUG= Review-Url: https://codereview.chromium.org/2157283003 Cr-Commit-Position: refs/heads/master@{#37895}
-
verwaest authored
BUG=v8:5209 Review-Url: https://codereview.chromium.org/2158393002 Cr-Commit-Position: refs/heads/master@{#37894}
-
marja authored
Using Isolate is unsafe, because we might parse (and do scope analysis) on a background thread. The illegal access happens when encountering f(arguments) { ... }. Kudos to verwaest@ for finding this bug. R=verwaest@chromium.org, rossberg@chromium.org BUG= Review-Url: https://codereview.chromium.org/2158343002 Cr-Commit-Position: refs/heads/master@{#37893}
-
yangguo authored
Review-Url: https://codereview.chromium.org/2162503002 Cr-Commit-Position: refs/heads/master@{#37892}
-
bmeurer authored
Look at the output type instead of the output representation, when converting to tagged representation. R=jarin@chromium.org Review-Url: https://codereview.chromium.org/2159373004 Cr-Commit-Position: refs/heads/master@{#37891}
-
jarin authored
BUG=chromium:608617 Review-Url: https://codereview.chromium.org/2163173002 Cr-Commit-Position: refs/heads/master@{#37890}
-
mstarzinger authored
R=adamk@chromium.org,bmeurer@chromium.org,littledan@chromium.org,rossberg@chromium.org Review-Url: https://codereview.chromium.org/2156083002 Cr-Commit-Position: refs/heads/master@{#37889}
-
zhengxing.li authored
X87: Revert of [builtins] Introduce a builtin for Abort(). (patchset #5 id:80001 of https://codereview.chromium.org/2156923002/ ). port 3e8f49ab (r37883) original commit message: Reason for revert: Blocks roll: https://build.chromium.org/p/client.v8.ports/builders/V8%20Linux%20-%20arm64%20-%20sim%20-%20debug/builds/1622 Original issue's description: > [builtins] Introduce a builtin for Abort(). > > Calling Runtime::kAbort through a builtin instead of the c-entry stub > will allow to generate the call in a background thread, because a > builtin provides its own handle, whereas a code stub does not. > > @v8-mips-ports: Could you take a special look at the padding that is > done in MacroAssembler::Abort()? > > R=bmeurer@chromium.org, titzer@chromium.org, mstarzinger@chromium.org, v8-mips-ports@googlegroups.com, v8-arm-ports@googlegroups.com > > Committed: https://crrev.com/9be015a254cfff871c56cd129523a729637e9158 > Cr-Commit-Position: refs/heads/master@{#37854} BUG= Review-Url: https://codereview.chromium.org/2168573002 Cr-Commit-Position: refs/heads/master@{#37888}
-
verwaest authored
This frees up a field in Scope and untangles scope a little from the parser. BUG=v8:5209 Review-Url: https://codereview.chromium.org/2160943004 Cr-Commit-Position: refs/heads/master@{#37887}
-
oth authored
LOG=N BUG= Review-Url: https://codereview.chromium.org/2157363003 Cr-Commit-Position: refs/heads/master@{#37886}
-
jgruber authored
R=yangguo@chromium.org BUG=v8:5197 Review-Url: https://codereview.chromium.org/2165593002 Cr-Commit-Position: refs/heads/master@{#37885}
-
nikolaos authored
In a few places in the parser base, we were forced to initialize variables of type ExpressionT even if it's not necessary, as they are assigned to later on before their use. This was required because, for the case of the preparser, ExpressionT is PreParserExpression which had no default constructor. This patch adds a default constructor, equivalent to EmptyExpression for this class, and gets rid of the unnecessary initializations. R=adamk@chromium.org, littledan@chromium.org BUG= LOG=N Review-Url: https://codereview.chromium.org/2162763003 Cr-Commit-Position: refs/heads/master@{#37884}
-
hablich authored
Revert of [builtins] Introduce a builtin for Abort(). (patchset #5 id:80001 of https://codereview.chromium.org/2156923002/ ) Reason for revert: Blocks roll: https://build.chromium.org/p/client.v8.ports/builders/V8%20Linux%20-%20arm64%20-%20sim%20-%20debug/builds/1622 Original issue's description: > [builtins] Introduce a builtin for Abort(). > > Calling Runtime::kAbort through a builtin instead of the c-entry stub > will allow to generate the call in a background thread, because a > builtin provides its own handle, whereas a code stub does not. > > @v8-mips-ports: Could you take a special look at the padding that is > done in MacroAssembler::Abort()? > > R=bmeurer@chromium.org, titzer@chromium.org, mstarzinger@chromium.org, v8-mips-ports@googlegroups.com, v8-arm-ports@googlegroups.com > > Committed: https://crrev.com/9be015a254cfff871c56cd129523a729637e9158 > Cr-Commit-Position: refs/heads/master@{#37854} TBR=bmeurer@chromium.org,mstarzinger@chromium.org,titzer@chromium.org,v8-arm-ports@googlegroups.com,v8-mips-ports@googlegroups.com,akos.palfi@imgtec.com,ahaas@chromium.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true Review-Url: https://codereview.chromium.org/2163603003 Cr-Commit-Position: refs/heads/master@{#37883}
-
bmeurer authored
Add a dedicated simplified operator to inline the general case for the ToBoolean conversion. In a follow up CL we will also use the ToBoolean hints gathered by the baseline compiler. Review-Url: https://codereview.chromium.org/2167593002 Cr-Commit-Position: refs/heads/master@{#37882}
-
jgruber authored
Revert of Move Error methods to C++ (patchset #11 id:200001 of https://codereview.chromium.org/2142933003/ ) Reason for revert: Clusterfuzz failures: https://bugs.chromium.org/p/chromium/issues/detail?id=629749 Original issue's description: > Move Error methods to C++ > > This ports a large portion of Error methods to C++, > including the constructor, stack setter and getter, > and Error.prototype.toString. > > BUG= > > Committed: https://crrev.com/5742da056a290caa13a0b8717ddb1e43424e0d31 > Cr-Commit-Position: refs/heads/master@{#37870} TBR=yangguo@chromium.org,bmeurer@chromium.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG= Review-Url: https://codereview.chromium.org/2159223004 Cr-Commit-Position: refs/heads/master@{#37881}
-
zhengxing.li authored
port 9be015a2 (r37854) original commit message: Calling Runtime::kAbort through a builtin instead of the c-entry stub will allow to generate the call in a background thread, because a builtin provides its own handle, whereas a code stub does not. @v8-mips-ports: Could you take a special look at the padding that is done in MacroAssembler::Abort()? BUG= Review-Url: https://codereview.chromium.org/2166703002 Cr-Commit-Position: refs/heads/master@{#37880}
-
v8-autoroll authored
Rolling v8/build to 4b2ee7d1824cdc45d8e3d4076c05f9a8af10e4ac Rolling v8/tools/mb to 3f6bbf669fa2b89399cead251fe693ce71132779 TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org Review-Url: https://codereview.chromium.org/2166433004 Cr-Commit-Position: refs/heads/master@{#37879}
-
- 19 Jul, 2016 3 commits
-
-
neis authored
In parser.{cc,h}, replace CHECK_OK_CUSTOM by CHECK_OK_VOID, as that's all we need. Use this to convert all void* functions to void. R=adamk@chromium.org, nikolaos@chromium.org BUG= Review-Url: https://codereview.chromium.org/2165513004 Cr-Commit-Position: refs/heads/master@{#37878}
-
bjaideep authored
Port 9be015a2 Original commit message: Calling Runtime::kAbort through a builtin instead of the c-entry stub will allow to generate the call in a background thread, because a builtin provides its own handle, whereas a code stub does not. R=ahaas@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, mbrandy@us.ibm.com BUG= LOG=N Review-Url: https://codereview.chromium.org/2166553002 Cr-Commit-Position: refs/heads/master@{#37877}
-
peterssen authored
Add additional sanity checks for implicit parameters, mainly to prevent passing a wrong context, which can lead to obscure errors. This is a regression test after https://crrev.com/da4f2491501e54d436ed448c5e345480d1f5906b BUG=chromium:508898 Review-Url: https://codereview.chromium.org/2160563003 Cr-Commit-Position: refs/heads/master@{#37876}
-