search for: rl353374

...r LLVM, Clang and clang-tools-extra) don't get updated at the moment. They stopped updating somewhere between r353327 <https://reviews.llvm.org/rL353327> (which made it to http://clang.llvm.org/extra/clang-tidy/checks/modernize-avoid-c-arrays.html) and r353374 <https://reviews.llvm.org/rL353374> (which didn't make it to https://llvm.org/docs/GettingStarted.html#host-c-toolchain-both-compiler-and-standard-library). The llvm-sphinx-docs <http://lab.llvm.org:8011/builders/llvm-sphinx-docs>, clang-sphinx-docs <http://lab.llvm.org:8011/builders/clang-sphinx-docs> (until rece...

...ORARILY_ALLOW_OLD_TOOLCHAIN is not propagated down to the NATIVE configuration when you set LLVM_OPTIMIZED_TABLEGEN. If that's going to be a permanent deficiency, it should be mentioned in the docs as well. > > Someone mentioned MSVC was having issues that way? https://reviews.llvm.org/rL353374#624722 <https://reviews.llvm.org/rL353374#624722> > That seems like general badness in the way that configuration is set up, no? It should probably get fixed separately > > "Somebody else ought to get around to fixing that someday so why bother documenting something that might...

...e LLVM_TEMPORARILY_ALLOW_OLD_TOOLCHAIN is not propagated down to the NATIVE configuration when you set LLVM_OPTIMIZED_TABLEGEN. If that's going to be a permanent deficiency, it should be mentioned in the docs as well. Someone mentioned MSVC was having issues that way? https://reviews.llvm.org/rL353374#624722 <https://reviews.llvm.org/rL353374#624722> That seems like general badness in the way that configuration is set up, no? It should probably get fixed separately. > Thanks, > --paulr >   <> > From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of JF B...

...ed updating somewhere between r353327 <https://reviews.llvm.org/rL353327> (which made it to http://clang.llvm.org/extra/clang-tidy/checks/modernize-avoid-c-arrays.html <http://clang.llvm.org/extra/clang-tidy/checks/modernize-avoid-c-arrays.html>) and r353374 <https://reviews.llvm.org/rL353374> (which didn't make it to https://llvm.org/docs/GettingStarted.html#host-c-toolchain-both-compiler-and-standard-library <https://llvm.org/docs/GettingStarted.html#host-c-toolchain-both-compiler-and-standard-library>). The llvm-sphinx-docs <http://lab.llvm.org:8011/builders/llvm-sphi...

...don't get updated at the moment. They stopped updating >> somewhere between r353327 <https://reviews.llvm.org/rL353327> (which >> made it to >> http://clang.llvm.org/extra/clang-tidy/checks/modernize-avoid-c-arrays.html) >> and r353374 <https://reviews.llvm.org/rL353374> (which didn't make it to >> https://llvm.org/docs/GettingStarted.html#host-c-toolchain-both-compiler-and-standard-library). >> The llvm-sphinx-docs <http://lab.llvm.org:8011/builders/llvm-sphinx-docs> >> , clang-sphinx-docs <http://lab.llvm.org:8011/builders/clang...

After a few attempts I think we’re in sight of success: we only have the two following bots remaining with old versions of libstdc++ and new versions of clang: polly-amd64-linux polly-arm-linux Once fixed the toolchain bump should stick. > On Jan 31, 2019, at 2:07 PM, JF Bastien via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > >> On Jan 31, 2019, at 2:03 PM,