Commit 19a302fc by angle-autoroll Committed by Commit Bot

Roll SwiftShader from bfb211914759 to bae138de13ac (8 revisions)

https://swiftshader.googlesource.com/SwiftShader.git/+log/bfb211914759..bae138de13ac 2020-12-02 amaiorano@google.com Reactor: add Type* member to Value and remove vtable 2020-12-02 amaiorano@google.com Fix crash from rr::Array with ENABLE_RR_DEBUG_INFO enabled 2020-12-02 natsu@google.com Guard VK_GOOGLE_SAMPLER_FILTERING_PRECISION 2020-12-02 amaiorano@google.com LLVM: add option to emit asm file to aid debugging 2020-12-02 amaiorano@google.com Coroutine: allow a name to be passed in for routine generation 2020-12-02 amaiorano@google.com ReactorUnitTests: use test name as Routine names 2020-12-02 amaiorano@google.com LLVM: store input name in JITRoutine 2020-12-02 amaiorano@google.com Fix FunctionT not forwarding its varargs 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 ianelliott@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/+doc/master/autoroll/README.md Bug: None Tbr: ianelliott@google.com Change-Id: Ic8144902a237feefdf7b8d841bbf411f08043ee5 Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2570399Reviewed-by: 's avatarangle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>
parent 8670d618
......@@ -241,7 +241,7 @@ deps = {
},
'third_party/SwiftShader': {
'url': '{swiftshader_git}/SwiftShader@bfb211914759cc5deffbe9419cd1c2cae0573488',
'url': '{swiftshader_git}/SwiftShader@bae138de13ac876cbca0e30a40b89dc808e2b29d',
'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