|
|
Description[regexp/string] Merge ExpandReplacement and GetSubstitution
R=littledan@chromium.org
BUG=v8:5339
Committed: https://crrev.com/5ab3874559475479efa2b93f53bf508b71890497
Cr-Commit-Position: refs/heads/master@{#39528}
Patch Set 1 #Patch Set 2 : Rebase #Patch Set 3 : Compile fixes #Patch Set 4 : Rebase once more #Patch Set 5 : And again #Patch Set 6 : Optimize for performance #Patch Set 7 : Fix test failures #Messages
Total messages: 45 (33 generated)
The CQ bit was checked by jgruber@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: v8_mac_rel_ng on master.tryserver.v8 (JOB_FAILED, http://build.chromium.org/p/tryserver.v8/builders/v8_mac_rel_ng/builds/8718)
The CQ bit was checked by jgruber@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: v8_linux64_avx2_rel_ng on master.tryserver.v8 (JOB_FAILED, http://build.chromium.org/p/tryserver.v8/builders/v8_linux64_avx2_rel_ng/buil...) v8_linux64_rel_ng on master.tryserver.v8 (JOB_FAILED, http://build.chromium.org/p/tryserver.v8/builders/v8_linux64_rel_ng/builds/12620)
The CQ bit was checked by jgruber@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: v8_linux64_rel_ng on master.tryserver.v8 (JOB_FAILED, http://build.chromium.org/p/tryserver.v8/builders/v8_linux64_rel_ng/builds/12622) v8_linux_dbg_ng on master.tryserver.v8 (JOB_FAILED, http://build.chromium.org/p/tryserver.v8/builders/v8_linux_dbg_ng/builds/12616) v8_linux_mipsel_compile_rel on master.tryserver.v8 (JOB_FAILED, http://build.chromium.org/p/tryserver.v8/builders/v8_linux_mipsel_compile_rel...) v8_linux_nodcheck_rel_ng on master.tryserver.v8 (JOB_FAILED, http://build.chromium.org/p/tryserver.v8/builders/v8_linux_nodcheck_rel_ng/bu...)
The CQ bit was checked by jgruber@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: v8_linux64_gyp_rel_ng on master.tryserver.v8 (JOB_FAILED, http://build.chromium.org/p/tryserver.v8/builders/v8_linux64_gyp_rel_ng/build...) v8_linux64_rel_ng on master.tryserver.v8 (JOB_FAILED, http://build.chromium.org/p/tryserver.v8/builders/v8_linux64_rel_ng/builds/12624) v8_linux_arm64_rel_ng on master.tryserver.v8 (JOB_FAILED, http://build.chromium.org/p/tryserver.v8/builders/v8_linux_arm64_rel_ng/build...) v8_linux_mips64el_compile_rel on master.tryserver.v8 (JOB_FAILED, http://build.chromium.org/p/tryserver.v8/builders/v8_linux_mips64el_compile_r...) v8_linux_rel_ng on master.tryserver.v8 (JOB_FAILED, http://build.chromium.org/p/tryserver.v8/builders/v8_linux_rel_ng/builds/12556) v8_presubmit on master.tryserver.v8 (JOB_FAILED, http://build.chromium.org/p/tryserver.v8/builders/v8_presubmit/builds/23913)
The CQ bit was checked by jgruber@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
It's definitely nicer-looking code, but does this patch cause any performance regression?
On 2016/09/13 at 17:14:53, Dan Ehrenberg wrote: > It's definitely nicer-looking code, but does this patch cause any performance regression? For this, I think it'd be nice to do a replacement string microbenchmark locally to be sure.
Description was changed from ========== [regexp/string] Merge ExpandReplacement and GetSubstitution R=littledan@chromium.org BUG= ========== to ========== [regexp/string] Merge ExpandReplacement and GetSubstitution R=littledan@chromium.org BUG=v8:5339 ==========
The CQ bit was checked by jgruber@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
On 2016/09/13 17:28:20, Dan Ehrenberg wrote: > On 2016/09/13 at 17:14:53, Dan Ehrenberg wrote: > > It's definitely nicer-looking code, but does this patch cause any performance > regression? > > For this, I think it'd be nice to do a replacement string microbenchmark locally > to be sure. I tweaked the implementation a bit and we're now at around a 3% regression on a local replace microbenchmark (octane/regexp modified to only run replace operations). See also perf bot results on this CL.
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: v8_mac_rel_ng on master.tryserver.v8 (JOB_FAILED, http://build.chromium.org/p/tryserver.v8/builders/v8_mac_rel_ng/builds/8815) v8_mac_rel_ng_triggered on master.tryserver.v8 (JOB_FAILED, http://build.chromium.org/p/tryserver.v8/builders/v8_mac_rel_ng_triggered/bui...)
The CQ bit was checked by jgruber@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
ptal. Seems like the trade-off is ~2% performance loss on replace vs. more maintainable code.
On 2016/09/16 at 07:28:27, jgruber wrote: > ptal. Seems like the trade-off is ~2% performance loss on replace vs. more maintainable code. The code looks good to me; could you add another reviewer to determine whether this regression is acceptable?
jgruber@chromium.org changed reviewers: + bmeurer@chromium.org
+bmeurer for opinions on 2% regression for Symbol.replace.
LGTM on 2%
On 2016/09/20 07:24:48, Benedikt Meurer wrote: > LGTM on 2% LGTM on code
The CQ bit was checked by jgruber@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Description was changed from ========== [regexp/string] Merge ExpandReplacement and GetSubstitution R=littledan@chromium.org BUG=v8:5339 ========== to ========== [regexp/string] Merge ExpandReplacement and GetSubstitution R=littledan@chromium.org BUG=v8:5339 ==========
Message was sent while issue was closed.
Committed patchset #7 (id:120001)
Message was sent while issue was closed.
Description was changed from ========== [regexp/string] Merge ExpandReplacement and GetSubstitution R=littledan@chromium.org BUG=v8:5339 ========== to ========== [regexp/string] Merge ExpandReplacement and GetSubstitution R=littledan@chromium.org BUG=v8:5339 Committed: https://crrev.com/5ab3874559475479efa2b93f53bf508b71890497 Cr-Commit-Position: refs/heads/master@{#39528} ==========
Message was sent while issue was closed.
Patchset 7 (id:??) landed as https://crrev.com/5ab3874559475479efa2b93f53bf508b71890497 Cr-Commit-Position: refs/heads/master@{#39528} |