Displaying 3 results from an estimated 3 matches for "llvm_force_use_old_toolchain".
2019 Feb 07
2
[RFC] migrating past C++11
> On Feb 7, 2019, at 11:01 AM, paul.robinson at sony.com wrote:
>
> It seems the CMake changes have landed; but the docs are still a bit out of date?
> CMake.html talks about LLVM_FORCE_USE_OLD_TOOLCHAIN but not LLVM_TEMPORARILY_ALLOW_OLD_TOOLCHAIN.
>
> I’m. Not sure how one updates the website’s docs, I had assumed the RST files would automatically get rebuilt and pushed? Agreed we want it fixed, but I don’t think it’s good reason to revert since the error message is pretty clear.
>
&...
2019 Feb 07
5
[RFC] migrating past C++11
...u broken at the moment. I’m inclined to leave it checked in, and try to get it into the LLVM 8 branch as well.
> On Feb 7, 2019, at 9:18 AM, paul.robinson at sony.com wrote:
>
> It seems the CMake changes have landed; but the docs are still a bit out of date?
> CMake.html talks about LLVM_FORCE_USE_OLD_TOOLCHAIN but not LLVM_TEMPORARILY_ALLOW_OLD_TOOLCHAIN.
I’m. Not sure how one updates the website’s docs, I had assumed the RST files would automatically get rebuilt and pushed? Agreed we want it fixed, but I don’t think it’s good reason to revert since the error message is pretty clear.
> Also, it loo...
2019 Feb 02
2
[RFC] migrating past C++11
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,