- 13 Mar, 2016 2 commits
-
-
jarin authored
BUG=chromium:582702 LOG=N Review URL: https://codereview.chromium.org/1781393002 Cr-Commit-Position: refs/heads/master@{#34736}
-
v8-autoroll authored
Rolling v8/tools/clang to 1e45fb0482b997a87bff1d5edfeac5b2c5458943 TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org Review URL: https://codereview.chromium.org/1796443002 Cr-Commit-Position: refs/heads/master@{#34735}
-
- 12 Mar, 2016 1 commit
-
-
v8-autoroll authored
Rolling v8/buildtools to 7274f1c726640bce4cd4c4198e1ee62a0b29bb89 Rolling v8/third_party/icu to 6d3b55dfa17d9a597c064eeef7ceac18c73184b7 Rolling v8/tools/clang to ec17c92cc70fcd8f5f39eaa17f3dbbd99e29c1f9 TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org Review URL: https://codereview.chromium.org/1781313004 Cr-Commit-Position: refs/heads/master@{#34734}
-
- 11 Mar, 2016 35 commits
-
-
littledan authored
This patch removes some [PASS, FAIL_OK] lines which consistently pass, and it declares some tests to be test bugs as appropriate. R=adamk Review URL: https://codereview.chromium.org/1784063002 Cr-Commit-Position: refs/heads/master@{#34733}
-
adamk authored
ES2015 Object.prototype.toString semantics were enabled in version 4.9, which has been in stable Chrome for nearly two weeks at this point. R=littledan@chromium.org Review URL: https://codereview.chromium.org/1784033002 Cr-Commit-Position: refs/heads/master@{#34732}
-
balazs.kilvady authored
Port 21b331e3 BUG= Review URL: https://codereview.chromium.org/1784353003 Cr-Commit-Position: refs/heads/master@{#34731}
-
titzer authored
R=bradnelson@chromium.org,binji@chromium.org BUG= Review URL: https://codereview.chromium.org/1787733002 Cr-Commit-Position: refs/heads/master@{#34730}
-
mlippautz authored
The code actually setting this flag has already been removed. This CL merely removes dead code. BUG= Review URL: https://codereview.chromium.org/1788753002 Cr-Commit-Position: refs/heads/master@{#34729}
-
mlippautz authored
This is a fix that removes a left over from https://crrev.com/4566531c6e593ae8bffc2ef96f82c91d15a68acf With this flag set to false still present, we would race on inserting in the local old-to-new remembered set. R=ulan@chormium.org BUG=chromium:524425 LOG=N Review URL: https://codereview.chromium.org/1783283003 Cr-Commit-Position: refs/heads/master@{#34728}
-
jkummerow authored
Just disable optimization, like we used to. This undoes a part of r34396's changes in behavior. BUG=chromium:593094 LOG=n R=mvstanton@chromium.org Review URL: https://codereview.chromium.org/1785183003 Cr-Commit-Position: refs/heads/master@{#34727}
-
Hannes Payer authored
BUG=chromium:561449 LOG=n R=ulan@chromium.org Review URL: https://codereview.chromium.org/1790433005 . Cr-Commit-Position: refs/heads/master@{#34726}
-
ofrobots authored
Post-mortem metadata generation broke as a result of https://codereview.chromium.org/1696043002 BUG= Review URL: https://codereview.chromium.org/1780933004 Cr-Commit-Position: refs/heads/master@{#34725}
-
joransiu authored
GCC on S390 31-bit treats size_t as 'long unsigned int', which is incompatible with %d format specifier that expects an 'int'. Introduce a new V8 SIZET PREFIX to use %zd instead. R=danno@chromium.org,jkummerow@chromium.org,jochen@chromium.org,jyan@ca.ibm.com,michael_dawson@ca.ibm.com,mbrandy@us.ibm.com,yangguo@chromium.org BUG= Review URL: https://codereview.chromium.org/1782293002 Cr-Commit-Position: refs/heads/master@{#34724}
-
mythria authored
Updates cctest.status and also updates the test cctest/test-serialize/SerializeInternalReference to return success when FLAG_ignition is true. This test tests for internal references and is not relevant for interpreter. BUG=v8:4280,v8:4680 LOG=N Review URL: https://codereview.chromium.org/1782893002 Cr-Commit-Position: refs/heads/master@{#34723}
-
hpayer authored
BUG=chromium:561449 LOG=n Review URL: https://codereview.chromium.org/1783313003 Cr-Commit-Position: refs/heads/master@{#34722}
-
titzer authored
R=ahaas@chromium.org BUG= Review URL: https://codereview.chromium.org/1779713007 Cr-Commit-Position: refs/heads/master@{#34721}
-
neis authored
R=rossberg BUG= Review URL: https://codereview.chromium.org/1784203003 Cr-Commit-Position: refs/heads/master@{#34720}
-
jkummerow authored
BUG=chromium:593867 LOG=y Review URL: https://codereview.chromium.org/1783343002 Cr-Commit-Position: refs/heads/master@{#34719}
-
ishell authored
These checks can fail if there bottommost function is a tail caller and the next function has different number of arguments than the bottommost one. BUG=chromium:593697,v8:4698 LOG=N Review URL: https://codereview.chromium.org/1785253003 Cr-Commit-Position: refs/heads/master@{#34718}
-
vogelheim authored
FullCodegen generates 2 statement positions for the loop init block, like so: for(var i = 0; i.... ^ ^ This change removes the first of those, updates unit tests, and removes text expectations for Ignition. --- An alternative would be to emulate the existing behaviour in Ignition, but: - The new behaviour seems more logical, - Ignition generates no bytecodes for the 'var', meaning there is no code position to attach the break position to. BUG=v8:4690 LOG=Y Review URL: https://codereview.chromium.org/1784883002 Cr-Commit-Position: refs/heads/master@{#34717}
-
ishell authored
BUG=chromium:593697,v8:4698 LOG=N Review URL: https://codereview.chromium.org/1781303002 Cr-Commit-Position: refs/heads/master@{#34716}
-
mstarzinger authored
This converts another test case that is expected to throw a TypeError but no SyntaxError to have better test coverage (exact message is being checked now). R=machenbach@chromium.org TEST=message,preparser Review URL: https://codereview.chromium.org/1786623002 Cr-Commit-Position: refs/heads/master@{#34715}
-
mlippautz authored
Revert of [platform] Change default platform max thread pool size 4 -> 8 (patchset #1 id:1 of https://codereview.chromium.org/1782833006/ ) Reason for revert: Seems to trigger bugs, needs investigation. Original issue's description: > [platform] Change default platform max thread pool size 4 -> 8 > > BUG= > > Committed: https://crrev.com/ddc0f9982057e76dd4dc35b6ca80d2322adc9141 > Cr-Commit-Position: refs/heads/master@{#34711} TBR=hpayer@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/1780353003 Cr-Commit-Position: refs/heads/master@{#34714}
-
mstarzinger authored
This converts existing "preparser" tests that expect a certain exception message to be produced into "message" tests. Thereby we get much better coverage because the former test suite degraded by now to just check whether each test case threw or not, the exception message was not being checked at all. This also deprecates the ability of "preparser" to specify that single test cases based on JS files are expected to throw, "messages" is far superior, use that test suite instead. R=machenbach@chromium.org TEST=message,preparser Review URL: https://codereview.chromium.org/1784013003 Cr-Commit-Position: refs/heads/master@{#34713}
-
ulan authored
BUG=chromium:578883 LOG=NO Review URL: https://codereview.chromium.org/1784643010 Cr-Commit-Position: refs/heads/master@{#34712}
-
mlippautz authored
BUG= Review URL: https://codereview.chromium.org/1782833006 Cr-Commit-Position: refs/heads/master@{#34711}
-
m0609.shim authored
After histrogram timer added time recaling functionality, some events, e.g. parse, histogram timer generates event log ending with 'MicroSeconds'. Since ProfViz can't recorgnize it, this patch cuts off 'MicroSeconds' postfix. R=vogelheim@chromium.org, yangguo@chromium.org BUG=chromium: LOG=N Review URL: https://codereview.chromium.org/1771293002 Cr-Commit-Position: refs/heads/master@{#34710}
-
danno authored
Review URL: https://codereview.chromium.org/1777013004 Cr-Commit-Position: refs/heads/master@{#34709}
-
mstarzinger authored
This also runs the message test suite against Ignition. By now most of the source positions (and exception messages) are accurate, the failing ones have been blacklisted. R=machenbach@chromium.org Review URL: https://codereview.chromium.org/1783773003 Cr-Commit-Position: refs/heads/master@{#34708}
-
cbruni authored
Avoid creating and initializing timer scopes for builtins as well. BUG=chromium:589679 LOG=N Review URL: https://codereview.chromium.org/1784833002 Cr-Commit-Position: refs/heads/master@{#34707}
-
machenbach authored
Revert of Replace PushIfAbsent by a Stack object and move StringBuilderJoin to JS (patchset #6 id:100001 of https://codereview.chromium.org/1775403008/ ) Reason for revert: [Sheriff] This lets a gc stress test time out: https://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20gc%20stress/builds/2337/steps/Mjsunit%20%28flakes%29/logs/regress-542823 The test ran in <2sec before this. Please fix the test as well on a reland. Original issue's description: > Replace PushIfAbsent by a Stack object and move StringBuilderJoin to JS > > This significantly speeds up String(array). > BUG= > > Committed: https://crrev.com/c91faa0b39b62025460eb9f8b578e20d88f3549e > Cr-Commit-Position: refs/heads/master@{#34696} TBR=cbruni@chromium.org,adamk@chromium.org,bmeurer@chromium.org,verwaest@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/1785003004 Cr-Commit-Position: refs/heads/master@{#34706}
-
yangguo authored
R=jkummerow@chromium.org BUG=v8:4810 LOG=N Review URL: https://codereview.chromium.org/1780173002 Cr-Commit-Position: refs/heads/master@{#34705}
-
v8-autoroll authored
Rolling v8/tools/clang to 96f43fa6c1232981bc401c0b6f2e2697a318356b TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org Review URL: https://codereview.chromium.org/1781183002 Cr-Commit-Position: refs/heads/master@{#34704}
-
yangguo authored
TBR=littledan@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/1783853003 Cr-Commit-Position: refs/heads/master@{#34703}
-
yangguo authored
R=littledan@chromium.org BUG=v8:4810 LOG=N Review URL: https://codereview.chromium.org/1780183002 Cr-Commit-Position: refs/heads/master@{#34702}
-
ahaas authored
R=binji@chromium.org Review URL: https://codereview.chromium.org/1779123002 Cr-Commit-Position: refs/heads/master@{#34701}
-
zhengxing.li authored
port 5096492f (r34627) original commit message: - Eliminate stubs with a variable number of arguments. (That only worked due to their very limited use. These stubs' interface descriptors were basically lying about their number of args, which will fail when used generically.) - Fix all CallApi*Stubs' interface descriptors to no longer lie about their arguments. - Unify CallApi*Stub, for * in Function, Accessor, FunctionWithFixedArgs. (Since these are now all doing the same thing.) - Rename the unified stub (and interface descriptors) to *ApiCallback*, since that's really what they're doing. - Refuse inlining an API callback if its number of parameters exceeds the supported number of args. BUG= Review URL: https://codereview.chromium.org/1784623006 Cr-Commit-Position: refs/heads/master@{#34700}
-
adamk authored
Now that the destructuring flags are gone, we always call CheckAndRewriteReferenceExpression, so unified the two methods again. Also cleaned up the code within, e.g. removing unnecessary Scanner::Location construction. Review URL: https://codereview.chromium.org/1781933003 Cr-Commit-Position: refs/heads/master@{#34699}
-
- 10 Mar, 2016 2 commits
-
-
littledan authored
- Make separate iterator functions for TypedArrays which do a type check (and in the future should check for detached TypedArrays) - Share the toString method with Arrays BUG=v8:4785 R=adamk LOG=Y Review URL: https://codereview.chromium.org/1780113002 Cr-Commit-Position: refs/heads/master@{#34698}
-
littledan authored
When the TypedArray iterator constructor code path was added, a technically incorrect optimization was added which uses the arraylike code path on array arguments, even though the %ArrayIterator% could have been monkey-patched to give different behavior. A previous patch removed this optimization, and this patch restores it due to the huge performance regression that resulted. The optimization was previously removed in https://codereview.chromium.org/1767893002 BUG=chromium:593644 R=adamk LOG=Y Review URL: https://codereview.chromium.org/1779373002 Cr-Commit-Position: refs/heads/master@{#34697}
-