Roll src/third_party/swiftshader 024f271ae0c7..fe3d4978886b (1 commits)

https://swiftshader.googlesource.com/SwiftShader.git/+log/024f271ae0c7..fe3d4978886b


git log 024f271ae0c7..fe3d4978886b --date=short --no-merges --format='%ad %ae %s'
2019-02-26 chrisforbes@google.com Fix various issues in vertex fetch setup


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

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

Change-Id: Ib549139ede1a70db9e5b8f60d712fa7a8846f734
Reviewed-on: https://chromium-review.googlesource.com/c/1488960Reviewed-by: chromium-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@{#635690}

DEPS

@@ -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': '024f271ae0c7084f1035e129f0d2139f2a302a75',
+  'swiftshader_revision': 'fe3d4978886bbbedf5b9c91dd2a539fcf3404455',
   # Three lines of non-changing comments so that
   # the commit queue can handle CLs rolling PDFium
   # and whatever else without interference from each other.