- 11 Oct, 2017 1 commit
-
-
peterwmwong authored
- Expose fast paths for RegExpPrototypeMatchBody/RegExpPrototypeSearchBody as TFS builtins - Add StringPrototypeMatch and StringPrototypeSearch TFJ builtins - Add StringMatchSearchAssembler to ensure same search/match behavior - Remove functionality from string.js A quick benchmark shows gains of 20-30% for unoptimized code and 0-20% for optimized code. https://github.com/peterwmwong/v8-perf/blob/master/string-search-match/README.md Bug: v8:5049 Change-Id: I0fffee6e94e62ecae049c9e5798da52d67ae1823 Reviewed-on: https://chromium-review.googlesource.com/707824 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#48452}
-
- 17 Nov, 2016 1 commit
-
-
vegorov authored
V8 was applying incorrect optimization to them advancing the start position. This would cause /foo$/y too match "barfoo", which it should not. BUG= Review-Url: https://codereview.chromium.org/2510743003 Cr-Commit-Position: refs/heads/master@{#41077}
-
- 25 Mar, 2016 1 commit
-
-
adamk authored
It's been on since M49. Also moved tests from harmony -> es6, one of which was merged with another test of the same name. While moving stuff over to regexp.js, I also noticed that there were unused calls to %FunctionSetName and %SetNativeFlag (those calls are already handled by InstallGetter()). Review URL: https://codereview.chromium.org/1838563003 Cr-Commit-Position: refs/heads/master@{#35076}
-
- 06 Oct, 2015 1 commit
-
-
erikcorry authored
R=yangguo@chromium.org BUG= Review URL: https://codereview.chromium.org/1378693004 Cr-Commit-Position: refs/heads/master@{#31133}
-
- 19 Sep, 2014 1 commit
-
-
https://codereview.chromium.org/567313003/erik.corry@gmail.com authored
R=svenpanne@chromium.org, yangguo@chromium.org BUG= Review URL: https://codereview.chromium.org/580383003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24065 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 18 Sep, 2014 2 commits
-
-
rossberg@chromium.org authored
Causes a flaky failure on buildbots. Here is the (deterministic) repro step (thanks to Michael Stanton): first go to flag-definitions.h and set this to false. DEFINE_BOOL(enable_sse4_1, false, "enable use of SSE4.1 instructions if available") Run the following and it should fail: tools/run-tests.py --arch=ia32 --mode=release cctest/test-api/Regress2107 R=yangguo@chromium.org BUG= Review URL: https://codereview.chromium.org/580123002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24045 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
erik.corry@gmail.com authored
R=yangguo@chromium.org, rossberg@chromium.org BUG= Review URL: https://codereview.chromium.org/567313003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24031 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-