- 19 Jan, 2018 1 commit
-
-
Sathya Gunasekaran authored
Bug: v8:6889 Change-Id: Id79989b5ea65fa4a622205769e961a6e200641b7 Reviewed-on: https://chromium-review.googlesource.com/874996 Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org> Reviewed-by: Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/master@{#50700}
-
- 18 Nov, 2016 1 commit
-
-
marja authored
It originates from the era where we used to run a separate preparse step before parsing and store the function data. Now the usage of preparser is something completely different, so this flag doesn't make sense any more. In addition, this way we get more test coverage for preparser (for small scripts). BUG= Review-Url: https://codereview.chromium.org/2513563002 Cr-Commit-Position: refs/heads/master@{#41110}
-
- 04 Nov, 2016 1 commit
-
-
adamk authored
The flag has been on since at least Chrome 53. R=littledan@chromium.org Review-Url: https://codereview.chromium.org/2478883002 Cr-Commit-Position: refs/heads/master@{#40780}
-
- 16 Mar, 2016 1 commit
-
-
littledan authored
Function declarations were previously permitted by V8 in many locations which no ECMAScript specification allowed; the ECMAScript 2015 spec enumerates a few locations (in blocks, as well as after labels and in conditionals when in sloppy mode). This patch ships the flag to restrict the usage of function declarations to those contexts. R=adamk LOG=Y BUG=v8:4824 CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_chromium_rel_ng;tryserver.blink:linux_blink_rel Review URL: https://codereview.chromium.org/1799233003 Cr-Commit-Position: refs/heads/master@{#34828}
-
- 15 Aug, 2015 1 commit
-
-
caitpotter88 authored
Second item in section 13.7.5.1 states that the error should be a SyntaxError, when previously CheckAndRewriteReferenceExpression would always emit a ReferenceError. BUG=v8:4373 R=adamk, rossberg LOG=N CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_chromium_rel_ng;tryserver.blink:linux_blink_rel Review URL: https://codereview.chromium.org/1292393002 Cr-Commit-Position: refs/heads/master@{#30184}
-
- 25 Jul, 2013 1 commit
-
-
machenbach@chromium.org authored
The stand-alone test driver is changed a bit: - Don't use the errorMessage list. It is used differently in the embedded driver. There it collects parser errors - instead of failure messages. - Remove html links in description texts. Some test descriptions print a web reference. The migrated tests fall into 3 categories: 1. Tests outside fast/js 2. Tests that print FAIL messages (and also expect those) - these tests should be examined later if they make sense at all 3. Tests with html links in the test description R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/20280003 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@15889 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-