Commit 3e4d1e9f authored by chromium-autoroll's avatar chromium-autoroll Committed by Commit Bot

Roll src/third_party/swiftshader ea38f958d072..9283b2559c05 (1 commits)

https://swiftshader.googlesource.com/SwiftShader.git/+log/ea38f958d072..9283b2559c05


git log ea38f958d072..9283b2559c05 --date=short --no-merges --format='%ad %ae %s'
2019-06-17 chrisforbes@google.com Wire up some required external functions for arm32


Created with:
  gclient setdep -r src/third_party/swiftshader@9283b2559c05

The AutoRoll server is located here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel

BUG=chromium:b/135298866
TBR=swiftshader-team+autoroll@google.com

Change-Id: I7984d86247e87e7421bb4655ea317b6f924af3bb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1662750Reviewed-by: default avatarchromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#669832}
parent a862914f
......@@ -154,7 +154,7 @@ vars = {
# Three lines of non-changing comments so that
# the commit queue can handle CLs rolling SwiftShader
# and whatever else without interference from each other.
'swiftshader_revision': 'ea38f958d07254e3cda97a7347058da130973746',
'swiftshader_revision': '9283b2559c0580dbb8fb6effffd11dc3f28b5f42',
# Three lines of non-changing comments so that
# the commit queue can handle CLs rolling PDFium
# and whatever else without interference from each other.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment