Star6
57
代码
代码
Issues91
Pull Requests87
流水线
讨论
Wiki
分析
Star6
57
VV8 LUCI CQ[build] Use a new google_benchmark location to avoid conflicts
66253e1b创建于 2024年1月10日历史提交
文件最后提交记录最后更新时间
BUILD.gn
[build] Use a new google_benchmark location to avoid conflicts Using the same path for DEPS'ed and previously checked-in files causes conflicts when going back and forth between new and old revisions. Since all references here are v8 stand-alone, the exact location shouldn't be important. Therefore we use some new name to avoid conflicts when locally running gclient sync. Bug: chromium:1513046 Change-Id: Icf1ecc4d9b1f9c7e67b5a542c2be08ff9738d045 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5184217 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Liviu Rau <liviurau@google.com> Cr-Commit-Position: refs/heads/main@{#91760}
2 年前
DEPS
[build] Use a new google_benchmark location to avoid conflicts Using the same path for DEPS'ed and previously checked-in files causes conflicts when going back and forth between new and old revisions. Since all references here are v8 stand-alone, the exact location shouldn't be important. Therefore we use some new name to avoid conflicts when locally running gclient sync. Bug: chromium:1513046 Change-Id: Icf1ecc4d9b1f9c7e67b5a542c2be08ff9738d045 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5184217 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Liviu Rau <liviurau@google.com> Cr-Commit-Position: refs/heads/main@{#91760}
2 年前
allocation_perf.cc
[build] Use a new google_benchmark location to avoid conflicts Using the same path for DEPS'ed and previously checked-in files causes conflicts when going back and forth between new and old revisions. Since all references here are v8 stand-alone, the exact location shouldn't be important. Therefore we use some new name to avoid conflicts when locally running gclient sync. Bug: chromium:1513046 Change-Id: Icf1ecc4d9b1f9c7e67b5a542c2be08ff9738d045 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5184217 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Liviu Rau <liviurau@google.com> Cr-Commit-Position: refs/heads/main@{#91760}
2 年前
benchmark_main.cc
[build] Use a new google_benchmark location to avoid conflicts Using the same path for DEPS'ed and previously checked-in files causes conflicts when going back and forth between new and old revisions. Since all references here are v8 stand-alone, the exact location shouldn't be important. Therefore we use some new name to avoid conflicts when locally running gclient sync. Bug: chromium:1513046 Change-Id: Icf1ecc4d9b1f9c7e67b5a542c2be08ff9738d045 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5184217 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Liviu Rau <liviurau@google.com> Cr-Commit-Position: refs/heads/main@{#91760}
2 年前
benchmark_utils.cc
cppgc: Initialize benchmark process only once Otherwise, DCHECKs complain that the PageAllocator used for the GlobalGCInfoTable may differ when setting up the platform repeatedly through benchmarking SetUp(). Change-Id: I7e87e8c9d8c283105e1bd75a4cd176df7f304315 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3283075 Reviewed-by: Omer Katz <omerkatz@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#77920}
4 年前
benchmark_utils.h
[build] Use a new google_benchmark location to avoid conflicts Using the same path for DEPS'ed and previously checked-in files causes conflicts when going back and forth between new and old revisions. Since all references here are v8 stand-alone, the exact location shouldn't be important. Therefore we use some new name to avoid conflicts when locally running gclient sync. Bug: chromium:1513046 Change-Id: Icf1ecc4d9b1f9c7e67b5a542c2be08ff9738d045 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5184217 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Liviu Rau <liviurau@google.com> Cr-Commit-Position: refs/heads/main@{#91760}
2 年前
binary-trees_perf.cc
[build] Use a new google_benchmark location to avoid conflicts Using the same path for DEPS'ed and previously checked-in files causes conflicts when going back and forth between new and old revisions. Since all references here are v8 stand-alone, the exact location shouldn't be important. Therefore we use some new name to avoid conflicts when locally running gclient sync. Bug: chromium:1513046 Change-Id: Icf1ecc4d9b1f9c7e67b5a542c2be08ff9738d045 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5184217 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Liviu Rau <liviurau@google.com> Cr-Commit-Position: refs/heads/main@{#91760}
2 年前
trace_perf.cc
[build] Use a new google_benchmark location to avoid conflicts Using the same path for DEPS'ed and previously checked-in files causes conflicts when going back and forth between new and old revisions. Since all references here are v8 stand-alone, the exact location shouldn't be important. Therefore we use some new name to avoid conflicts when locally running gclient sync. Bug: chromium:1513046 Change-Id: Icf1ecc4d9b1f9c7e67b5a542c2be08ff9738d045 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5184217 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Liviu Rau <liviurau@google.com> Cr-Commit-Position: refs/heads/main@{#91760}
2 年前