projects / platform / upstream / llvm.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 60bcec4) | patch
Follow-up build fix for rGae6f78824031
authorJeremy Morse <jeremy.morse@sony.com>
Sat, 22 Aug 2020 18:05:25 +0000 (19:05 +0100)
committerJeremy Morse <jeremy.morse@sony.com>
Sat, 22 Aug 2020 18:09:30 +0000 (19:09 +0100)
commit93af37043b9c1a8ea47890ad2bcf277f9b36c47d
tree4f3e3edb127629b20f140d562de09142a6f76638tree | snapshot
parent60bcec4eead73996877c389d439af337f186c3aecommit | diff
Follow-up build fix for rGae6f78824031

One of the bots objects to brace-initializing a tuple:

  http://lab.llvm.org:8011/builders/clang-cmake-x86_64-sde-avx512-linux/builds/43595/steps/build%20stage%201/logs/stdio

As the tuple constructor is apparently explicit. Fall back to the (not
as pretty) explicit construction of a tuple. I'd thought this was
permitted behaviour; will investigate why this fails later.
llvm/lib/CodeGen/LiveDebugValues/InstrRefBasedImpl.cpp diff | blob | history
Domain: System / Toolchain;