Commit 37f7316e by angle-autoroll Committed by Commit Bot

Roll third_party/SwiftShader 102fd19c65f4..aba1020d3914 (7 commits)

https://swiftshader.googlesource.com/SwiftShader.git/+log/102fd19c65f4..aba1020d3914 git log 102fd19c65f4..aba1020d3914 --date=short --no-merges --format='%ad %ae %s' 2019-11-15 bclayton@google.com Remove the now unused sw::Event. 2019-11-15 bclayton@google.com VkQueryPool: Migrate from sw sync to marl 2019-11-15 bclayton@google.com VkDevice: Migrate to using marl::Event::any() 2019-11-15 bclayton@google.com VkFence: Migrate to marl::Event 2019-11-15 bclayton@google.com Merge changes Ifb21caa2,Iaca5897d 2019-11-15 swiftshader.regress@gmail.com Regres: Update test lists @ cc221e83 2019-11-15 chrisforbes@google.com Update deqp to b64acc6c3371607583b3aa6d12c7290b4aaae747 Created with: gclient setdep -r third_party/SwiftShader@aba1020d3914 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/swiftshader-angle-autoroll Please CC cnorthrop@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Bug: None TBR=cnorthrop@google.com Change-Id: Ie779409c1316d9b30cb91c6ad0df18a71ebfa634 Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1921748Reviewed-by: 's avatarangle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>
parent 51b5a322
......@@ -184,7 +184,7 @@ deps = {
},
'third_party/SwiftShader': {
'url': '{swiftshader_git}/SwiftShader@102fd19c65f46242f5f1477c6596cbacdfcd2c9f',
'url': '{swiftshader_git}/SwiftShader@aba1020d39145285f8d8df82d6f0b83d0b0e5386',
'condition': 'not build_with_chromium',
},
......
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