- 07 May, 2015 3 commits
-
-
ben authored
On systems that have CLOCK_REALTIME_COARSE with good enough resolution, we can avoid making a system call to get the current time; it's serviced from the vDSO. BUG= LOG=N Review URL: https://codereview.chromium.org/1125003002 Cr-Commit-Position: refs/heads/master@{#28280}
-
chunyang.dai authored
port 7798548a (r28260) original commit message: typeof was implemented as a runtime function. Calling it in optimized code with a non-constant input becomes burdensome. BUG= Review URL: https://codereview.chromium.org/1124263005 Cr-Commit-Position: refs/heads/master@{#28279}
-
chunyang.dai authored
port 06a792b7 (r28263). original commit message: Make the parser handle references to "this" as unresolved variables, so the same logic as for the rest of function parameters is used for the receiver. Minor additions to the code generation handle copying the receiver to the context, along with the rest of the function parameters. Based on work by Adrian Perez de Castro <aperez@igalia.com> BUG= Review URL: https://codereview.chromium.org/1124393002 Cr-Commit-Position: refs/heads/master@{#28278}
-
- 06 May, 2015 34 commits
-
-
machenbach authored
Revert of Wrap runtime.js in a function. (patchset #2 id:20001 of https://codereview.chromium.org/1126213002/) Reason for revert: [Sheriff] Breaks nosnap: http://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20nosnap/builds/2872 Original issue's description: > Wrap runtime.js in a function. > > R=jkummerow@chromium.org > > Committed: https://crrev.com/65c56d49b2d671ac9e379de726bff3eb03a508c1 > Cr-Commit-Position: refs/heads/master@{#28275} TBR=jkummerow@chromium.org,yangguo@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true Review URL: https://codereview.chromium.org/1123353004 Cr-Commit-Position: refs/heads/master@{#28277}
-
scottmg authored
R=jochen@chromium.org BUG=chromium:485155 LOG=y Review URL: https://codereview.chromium.org/1124293002 Cr-Commit-Position: refs/heads/master@{#28276}
-
yangguo authored
R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/1126213002 Cr-Commit-Position: refs/heads/master@{#28275}
-
hpayer authored
BUG=chromium:436911 LOG=n Review URL: https://codereview.chromium.org/1130833002 Cr-Commit-Position: refs/heads/master@{#28274}
-
mbrandy authored
Port 7798548a Original commit message: typeof was implemented as a runtime function. Calling it in optimized code with a non-constant input becomes burdensome. R=mvstanton@chromium.org, dstence@us.ibm.com, michael_dawson@ca.ibm.com BUG= Review URL: https://codereview.chromium.org/1124243002 Cr-Commit-Position: refs/heads/master@{#28273}
-
mbrandy authored
Port 18619d35 Original commit message: Make the parser handle references to "this" as unresolved variables, so the same logic as for the rest of function parameters is used for the receiver. Minor additions to the code generation handle copying the receiver to the context, along with the rest of the function parameters. Based on work by Adrian Perez de Castro <aperez@igalia.com>. R=wingo@igalia.com, dstence@us.ibm.com, michael_dawson@ca.ibm.com BUG= Review URL: https://codereview.chromium.org/1129803003 Cr-Commit-Position: refs/heads/master@{#28272}
-
wingo authored
Use of arguments is tracked as a variable, like any other variable. R=arv@chromium.org LOG=N BUG= Review URL: https://codereview.chromium.org/1124233002 Cr-Commit-Position: refs/heads/master@{#28271}
-
caitpotter88 authored
BUG=v8:4007 LOG=N R=arv@chromium.org, rossberg@chromium.org Review URL: https://codereview.chromium.org/548833002 Cr-Commit-Position: refs/heads/master@{#28270}
-
mbrandy authored
Port cf53fed9 Original commit message: ArgumentsAdaptorStub for derived constructor (the one that needs new.target) works in this way: - If the constructor is invoked via the Construct stub, we know that actual arguments always include new.target. ``arguments`` object however should not include a new.target, therefore we remove it. We achieve this by decrementing the argument count. - If the constructor is invoked as a call, we do not care for a correct ``arguments`` array since the constructor will immediately throw on entrance. The bug is that the call could actually pass 0 actual arguments, but I decrement unconditionally :(. The fix is to detect this case and avoid decrementing. ``arguments`` is bogus, but it is ok as constructor throws. Long-term we should just remove mucking about with arguments for new.target and just get it from the stack. R=dslomov@chromium.org, dstence@us.ibm.com, michael_dawson@ca.ibm.com BUG= Review URL: https://codereview.chromium.org/1125223002 Cr-Commit-Position: refs/heads/master@{#28269}
-
wingo authored
Use of the "this" variable is now tracked using scopes, like any other variable. R=arv@chromium.org LOG=N BUG= Review URL: https://codereview.chromium.org/1129823002 Cr-Commit-Position: refs/heads/master@{#28268}
-
hpayer authored
BUG=chromium:436911 LOG=n Review URL: https://codereview.chromium.org/1128923002 Cr-Commit-Position: refs/heads/master@{#28267}
-
conradw authored
https://codereview.chromium.org/1125783002 did not handle all cases for some architectures. These cases are now covered, and tests have been extended to check them. BUG=v8:4073 LOG=N Review URL: https://codereview.chromium.org/1128143002 Cr-Commit-Position: refs/heads/master@{#28266}
-
hpayer authored
Revert of New insertion write barrier. (patchset #3 id:200001 of https://codereview.chromium.org/1073953006/) Reason for revert: Various performance regressions. Original issue's description: > New insertion write barrier. > > BUG= > > Committed: https://crrev.com/6e9e2c08292b553602c74b16b8ccff4e4ccac003 > Cr-Commit-Position: refs/heads/master@{#28199} TBR=ulan@chromium.org,erikcorry@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG= Review URL: https://codereview.chromium.org/1131583002 Cr-Commit-Position: refs/heads/master@{#28265}
-
mvstanton authored
BUG= R=yangguo@chromium.org Review URL: https://codereview.chromium.org/1116943002 Cr-Commit-Position: refs/heads/master@{#28264}
-
wingo authored
Make the parser handle references to "this" as unresolved variables, so the same logic as for the rest of function parameters is used for the receiver. Minor additions to the code generation handle copying the receiver to the context, along with the rest of the function parameters. Based on work by Adrian Perez de Castro <aperez@igalia.com>. BUG=v8:2700 LOG=N Review URL: https://codereview.chromium.org/1130733003 Cr-Commit-Position: refs/heads/master@{#28263}
-
hpayer authored
BUG=chromium:436911 Review URL: https://codereview.chromium.org/1127993002 Cr-Commit-Position: refs/heads/master@{#28262}
-
ben authored
I know the bug has been closed but this seems like a simple addition that may be useful in other ways as well. BUG=v8:2180 LOG=N Review URL: https://codereview.chromium.org/1128553002 Cr-Commit-Position: refs/heads/master@{#28261}
-
mvstanton authored
typeof was implemented as a runtime function. Calling it in optimized code with a non-constant input becomes burdensome. BUG= Review URL: https://codereview.chromium.org/1114563003 Cr-Commit-Position: refs/heads/master@{#28260}
-
bmeurer authored
This revives the Terminate operator and removes the weird Always operator. As a first step we let the ControlReducer connect non terminating loops via Terminate. The next step will be to change the graph builder to insert Terminate nodes into every loop. Review URL: https://codereview.chromium.org/1123213002 Cr-Commit-Position: refs/heads/master@{#28259}
-
jochen authored
Make sure all lists are either regularly cleared or trimmed R=hpayer@chromium.org BUG=none LOG=n Review URL: https://codereview.chromium.org/1123213003 Cr-Commit-Position: refs/heads/master@{#28258}
-
titzer authored
R=hpayer@chromium.org, erikcorry@chromium.org BUG= Review URL: https://codereview.chromium.org/1105693002 Cr-Commit-Position: refs/heads/master@{#28257}
-
rossberg authored
R=yangguo@chromium.org BUG= Review URL: https://codereview.chromium.org/1130723002 Cr-Commit-Position: refs/heads/master@{#28256}
-
verwaest authored
Review URL: https://codereview.chromium.org/1116003005 Cr-Commit-Position: refs/heads/master@{#28255}
-
ben authored
Fix the following build error: ../deps/v8/src/compiler/graph-visualizer.h:23:1: error: 'FILE' does not name a type See https://github.com/iojs/io.js/issues/1637 for background. BUG=v8:4079 LOG=N Review URL: https://codereview.chromium.org/1128053002 Cr-Commit-Position: refs/heads/master@{#28254}
-
conradw authored
The Hydrogen representation for binops was never changed to care about the language mode. We thought this was ok, but it turns out we need to keep track of it to make sure inlining doesn't mess with the "strongness" of binops. Also added more rigorous inlining testing. BUG=v8:3956 LOG=N Review URL: https://codereview.chromium.org/1123043002 Cr-Commit-Position: refs/heads/master@{#28253}
-
vogelheim authored
long and trivial functions, so that they can be eagerly compiled after all. This essentially allows the parser to renege on its earlier decision to lazy-parse, if additional information suggests it was a bad decision. BUG=chromium:470930 LOG=Y Review URL: https://codereview.chromium.org/1102523003 Cr-Commit-Position: refs/heads/master@{#28252}
-
bmeurer authored
An AdvancedReducer is basically a regular Reducer with an editor that can perform graph editing operations beyond changing or replacing the node that is currently being reduced. The GraphReducer is the default implementation of the AdvancedReducer::Editor interface. The ControlReducerImpl is now just an AdvancedReducer, which temporarily requires a Finish method in the reducer to implement the dead node trimming until we move that to the GraphReducer (which in turn requires that all loops are connected to End). Review URL: https://codereview.chromium.org/1122423003 Cr-Commit-Position: refs/heads/master@{#28251}
-
yangguo authored
R=mvstanton@chromium.org Review URL: https://codereview.chromium.org/1118273004 Cr-Commit-Position: refs/heads/master@{#28250}
-
machenbach authored
TBR=yangguo@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/1125123002 Cr-Commit-Position: refs/heads/master@{#28249}
-
yangguo authored
NOTRY=true TBR=machenbach@chromium.org BUG=4078 LOG=N Review URL: https://codereview.chromium.org/1123183003 Cr-Commit-Position: refs/heads/master@{#28248}
-
https://codereview.chromium.org/1100993003/machenbach authored
Revert of [V8] Reland https://codereview.chromium.org/1100993003/ (patchset #1 id:1 of https://codereview.chromium.org/1121833003/) Reason for revert: [Sheriff] Speculative revert for breaking layout tests - will reland if it doesn't help: http://build.chromium.org/p/client.v8/builders/V8-Blink%20Linux%2064/builds/3178 Original issue's description: > [V8] Reland https://codereview.chromium.org/1100993003/ > > Chromium tests were prepared in https://codereview.chromium.org/1118743003/ > Blink tests in https://codereview.chromium.org/1115193002/ > > LOG=Y > BUG=chromium:480652 > R=yangguo@chromium.org > > Committed: https://crrev.com/19b62e211d1829108e5c85c5043dd755afa17178 > Cr-Commit-Position: refs/heads/master@{#28229} TBR=yangguo@chromium.org,kozyatinskiy@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=chromium:480652 Review URL: https://codereview.chromium.org/1125113003 Cr-Commit-Position: refs/heads/master@{#28247}
-
chunyang.dai authored
port cf53fed9 (r28242). original commit message: ArgumentsAdaptorStub for derived constructor (the one that needs new.target) works in this way: - If the constructor is invoked via the Construct stub, we know that actual arguments always include new.target. ``arguments`` object however should not include a new.target, therefore we remove it. We achieve this by decrementing the argument count. - If the constructor is invoked as a call, we do not care for a correct ``arguments`` array since the constructor will immediately throw on entrance. The bug is that the call could actually pass 0 actual arguments, but I decrement unconditionally :(. The fix is to detect this case and avoid decrementing. ``arguments`` is bogus, but it is ok as constructor throws. Long-term we should just remove mucking about with arguments for new.target and just get it from the stack. BUG= Review URL: https://codereview.chromium.org/1124063002 Cr-Commit-Position: refs/heads/master@{#28246}
-
v8-autoroll authored
Rolling v8/tools/clang to 8ed88fc35e20182d6ecc3dde107606f609c46b23 TBR=machenbach@chromium.org Review URL: https://codereview.chromium.org/1130663002 Cr-Commit-Position: refs/heads/master@{#28245}
-
chunyang.dai authored
"RunAllocate" test case is added in d6945db7. it invokes Linkage::GetStubCallDescriptor which is unimplemented for turbofan unsupported platform. BUG= Review URL: https://codereview.chromium.org/1129483003 Cr-Commit-Position: refs/heads/master@{#28244}
-
- 05 May, 2015 3 commits
-
-
dpranke authored
As part of the migration from GYP->GN, we want to make sure that we can track when new targets are added to either the GYP or GN builds and that we are building everything we expect to build. In GN, unlike GYP, if a build file gets referenced from other files, building 'all' will cause every target to be built in it. This means in particular, that we can end up trying to build targets that are not necessarily intended to be visible to the rest of the build. To get around this, any target that is defined but hidden (like 'v8_snapshot', in V8's case) should still be visible to a top-level target called "//:gn_visibility". R=brettw@chromium.org, machenbach@chromium.org BUG=461019 LOG=N Review URL: https://codereview.chromium.org/1120093005 Cr-Commit-Position: refs/heads/master@{#28243}
-
dslomov authored
ArgumentsAdaptorStub for derived constructor (the one that needs new.target) works in this way: - If the constructor is invoked via the Construct stub, we know that actual arguments always include new.target. ``arguments`` object however should not include a new.target, therefore we remove it. We achieve this by decrementing the argument count. - If the constructor is invoked as a call, we do not care for a correct ``arguments`` array since the constructor will immediately throw on entrance. The bug is that the call could actually pass 0 actual arguments, but I decrement unconditionally :(. The fix is to detect this case and avoid decrementing. ``arguments`` is bogus, but it is ok as constructor throws. Long-term we should just remove mucking about with arguments for new.target and just get it from the stack. R=arv@chromium.org,rossberg@chromium.org BUG=chromium:474783 LOG=Y Review URL: https://codereview.chromium.org/1126783003 Cr-Commit-Position: refs/heads/master@{#28242}
-
dusan.milosavljevic authored
- Add long branche mode for FPU branches. - Fix FPU branches for unordered conditions. - Provide FPU [un]ordered condition negation schema. TEST=mjsunit/miror-objects, constant-folding-2, external-array BUG= Review URL: https://codereview.chromium.org/1120753010 Cr-Commit-Position: refs/heads/master@{#28241}
-