Commit 48e417a8 authored by chromium-autoroll's avatar chromium-autoroll Committed by Commit Bot

Roll src/third_party/swiftshader d69cdaba1445..e95eeb19a770 (1 commits)

https://swiftshader.googlesource.com/SwiftShader.git/+log/d69cdaba1445..e95eeb19a770


git log d69cdaba1445..e95eeb19a770 --date=short --no-merges --format='%ad %ae %s'
2019-03-05 bclayton@google.com SpirvShader: Add relational ops for integers


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

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/127282157
TBR=swiftshader-team+autoroll@chromium.org

Change-Id: Ic24afd6b9f2205ff33392b674ef67adbe95c9bd8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1503297Reviewed-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@{#637675}
parent b4f2e8be
......@@ -143,7 +143,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': 'd69cdaba1445a6dc99be8309175b10cc2b979209',
'swiftshader_revision': 'e95eeb19a770db0fcba5f835ebe8f36cc242d13a',
# 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