search for: d57264

...for driving this. On Fri, Jan 25, 2019 at 3:57 PM JF Bastien via llvm-dev < llvm-dev at lists.llvm.org> wrote: > The discussion seems to have died down and gotten good consensus. I’ve > therefore create a patch which applies the proposed soft-errors: > > https://reviews.llvm.org/D57264 > > > We’ll only migrate to hard-error (and start using new features) when we > get consensus to do so, at the earliest end of March 2019. The patch will > allow us to start warning developers, especially those who only compile > branches (in this case, LLVM 8). > > > On...

...olks (except fans of April 1st: this is *not* a joke), > > We discussed migrating past C++11 > <http://lists.llvm.org/pipermail/llvm-dev/2019-January/129452.html> recently > and got consensus. This led us to bump our minimum toolchain requirements > <https://reviews.llvm.org/D57264> to a point where C++14 was supported by > all compilers. Following our policy > <http://llvm.org/docs/DeveloperPolicy.html#toolchain>, I’m now suggesting > that we make this official by creating a patch which will: > > > - Update the C++ standard version > <h...

...Hello folks (except fans of April 1st: this is not a joke), >> >> We discussed migrating past C++11 <http://lists.llvm.org/pipermail/llvm-dev/2019-January/129452.html> recently and got consensus. This led us to bump our minimum toolchain requirements <https://reviews.llvm.org/D57264> to a point where C++14 was supported by all compilers. Following our policy <http://llvm.org/docs/DeveloperPolicy.html#toolchain>, I’m now suggesting that we make this official by creating a patch which will: >> >> Update the C++ standard version <http://llvm.org/docs/Codi...

...olks (except fans of April 1st: this is not a joke), >>> >>> We discussed migrating past C++11 <http://lists.llvm.org/pipermail/llvm-dev/2019-January/129452.html> recently and got consensus. This led us to bump our minimum toolchain requirements <https://reviews.llvm.org/D57264> to a point where C++14 was supported by all compilers. Following our policy <http://llvm.org/docs/DeveloperPolicy.html#toolchain>, I’m now suggesting that we make this official by creating a patch which will: >>> >>> Update the C++ standard version <http://llvm.org/d...

...gt;>> >>>> We discussed migrating past C++11 >>>> <http://lists.llvm.org/pipermail/llvm-dev/2019-January/129452.html> recently >>>> and got consensus. This led us to bump our minimum toolchain >>>> requirements <https://reviews.llvm.org/D57264> to a point where C++14 >>>> was supported by all compilers. Following our policy >>>> <http://llvm.org/docs/DeveloperPolicy.html#toolchain>, I’m now >>>> suggesting that we make this official by creating a patch which will: >>>> >>>...

Hello fans of the auto keyword! We now have a policy on how LLVM toolchains get updated <https://reviews.llvm.org/rL351765>! Let’s put that policy to good use, and talk about how we’ll move all monorepo projects past C++11. Previous Discussions LLVM dev meeting 2018 BoF "Migrating to C++14, and beyond! <http://llvm.org/devmtg/2018-10/talk-abstracts.html#bof3>" A Short

...>>>> We discussed migrating past C++11 >>>>> <http://lists.llvm.org/pipermail/llvm-dev/2019-January/129452.html> recently >>>>> and got consensus. This led us to bump our minimum toolchain >>>>> requirements <https://reviews.llvm.org/D57264> to a point where C++14 >>>>> was supported by all compilers. Following our policy >>>>> <http://llvm.org/docs/DeveloperPolicy.html#toolchain>, I’m now >>>>> suggesting that we make this official by creating a patch which will: >>>>&...