search for: d47073

...m.org> wrote: > > Hi all- > I just wanted to bump this again, I know I sent it out on a Friday :) I realize this is a minor code change with significant implications, so it seems to me that I should ensure it gets extensive exposure. > See the review here: https://reviews.llvm.org/D47073 > -Erich > > -----Original Message----- > From: Keane, Erich > Sent: Friday, May 18, 2018 8:26 AM > To: llvm-dev at lists.llvm.org > Subject: RE: [llvm-dev] A Short Policy Proposal Regarding Host Compilers > > I've heard just about zero opposition to this, so I'...

I've heard just about zero opposition to this, so I've put a code review together here: https://reviews.llvm.org/D47073 With the intent of either implementing this policy change, or encouraging further discussion/bikeshed. Thanks all! -Erich -----Original Message----- From: Brooks Davis [mailto:brooks at freebsd.org] Sent: Sunday, May 13, 2018 10:34 AM To: Keane, Erich <erich.keane at intel.com> Cc: llvm-de...

...; > > > Hi all- > > I just wanted to bump this again, I know I sent it out on a Friday :) I realize this is a minor code change with significant implications, so it seems to me that I should ensure it gets extensive exposure. > > See the review here: https://reviews.llvm.org/D47073 <https://reviews.llvm.org/D47073> > > -Erich > > > > -----Original Message----- > > From: Keane, Erich > > Sent: Friday, May 18, 2018 8:26 AM > > To: llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org> > > Subject: RE: [llvm-dev] A...

...8-May/123182.html> Using C++14 code in LLVM (2017) <http://lists.llvm.org/pipermail/llvm-dev/2017-October/118673.html> Using C++14 code in LLVM (2016) <http://lists.llvm.org/pipermail/llvm-dev/2016-October/105483.html> Document and Enforce new Host Compiler Policy <http://llvm.org/D47073> Require GCC 5.1 and LLVM 3.5 at a minimum <http://llvm.org/D46723>When replying to this email, please avoid having the same discussions again. Please provide references to anything I might have missed. If you’re making a new point, say so. And don’t assume ill-will, I’m just trying to get...

...8-May/123182.html> Using C++14 code in LLVM (2017) <http://lists.llvm.org/pipermail/llvm-dev/2017-October/118673.html> Using C++14 code in LLVM (2016) <http://lists.llvm.org/pipermail/llvm-dev/2016-October/105483.html> Document and Enforce new Host Compiler Policy <http://llvm.org/D47073> Require GCC 5.1 and LLVM 3.5 at a minimum <http://llvm.org/D46723> Migrate to what? I’m only proposing that we migrate to C++14 for now. If you want to propose C++17, please do the work required by the policy. In particular, document which toolchains this would require, and what feature...

...org/pipermail/llvm-dev/2018-May/123505.html) for any remaining objections to turning on MachineOutliner by default for AArch64 under -Oz. * Erich Keane would [like more feedback](http://lists.llvm.org/pipermail/llvm-dev/2018-May/123527.html) on the [host compiler proposal](https://reviews.llvm.org/D47073). * Ulrich Weigand has shared a [lengthy update](http://lists.llvm.org/pipermail/llvm-dev/2018-May/123529.html) on the status of strict FP, ending with a detailed list of proposed next steps. * Peter Collingbourne [proposes](http://lists.llvm.org/pipermail/llvm-dev/2018-May/123514.html) support f...

On Fri, May 11, 2018 at 01:37:22PM +0000, Keane, Erich via llvm-dev wrote: > Hi All- > As we all know, the C++14 discussion is flaring up again. Chandler brought up that he would like a concrete plan to switch. In my opinion, this is insufficient, as it will result in us simply having this discussion AGAIN next release. Instead, I would prefer us to have a concrete Policy on our host

...VM (2017) > <http://lists.llvm.org/pipermail/llvm-dev/2017-October/118673.html> > - Using C++14 code in LLVM (2016) > <http://lists.llvm.org/pipermail/llvm-dev/2016-October/105483.html> > - Document and Enforce new Host Compiler Policy > <http://llvm.org/D47073> > - Require GCC 5.1 and LLVM 3.5 at a minimum <http://llvm.org/D46723> > > > *Migrate to what?* > > I’m only proposing that we migrate to C++14 for now. If you want to > propose C++17, please do the work required by the policy. In particular, > document which to...

...VM (2017) > <http://lists.llvm.org/pipermail/llvm-dev/2017-October/118673.html> > - Using C++14 code in LLVM (2016) > <http://lists.llvm.org/pipermail/llvm-dev/2016-October/105483.html> > - Document and Enforce new Host Compiler Policy > <http://llvm.org/D47073> > - Require GCC 5.1 and LLVM 3.5 at a minimum <http://llvm.org/D46723> > > > *Migrate to what?* > > I’m only proposing that we migrate to C++14 for now. If you want to > propose C++17, please do the work required by the policy. In particular, > document which to...

...g C++14 code in LLVM (2017) <http://lists.llvm.org/pipermail/llvm-dev/2017-October/118673.html> >>> Using C++14 code in LLVM (2016) <http://lists.llvm.org/pipermail/llvm-dev/2016-October/105483.html> >>> Document and Enforce new Host Compiler Policy <http://llvm.org/D47073> >>> Require GCC 5.1 and LLVM 3.5 at a minimum <http://llvm.org/D46723> >>> >>> Migrate to what? >>> >>> I’m only proposing that we migrate to C++14 for now. If you want to propose C++17, please do the work required by the policy. In particula...

...code in LLVM (2017) <http://lists.llvm.org/pipermail/llvm-dev/2017-October/118673.html> >>>> Using C++14 code in LLVM (2016) <http://lists.llvm.org/pipermail/llvm-dev/2016-October/105483.html> >>>> Document and Enforce new Host Compiler Policy <http://llvm.org/D47073> >>>> Require GCC 5.1 and LLVM 3.5 at a minimum <http://llvm.org/D46723> >>>> >>>> Migrate to what? >>>> >>>> I’m only proposing that we migrate to C++14 for now. If you want to propose C++17, please do the work required by the...

...rmail/llvm-dev/2017-October/118673.html> >>>> - Using C++14 code in LLVM (2016) >>>> <http://lists.llvm.org/pipermail/llvm-dev/2016-October/105483.html> >>>> - Document and Enforce new Host Compiler Policy >>>> <http://llvm.org/D47073> >>>> - Require GCC 5.1 and LLVM 3.5 at a minimum <http://llvm.org/D46723> >>>> >>>> >>>> *Migrate to what?* >>>> >>>> I’m only proposing that we migrate to C++14 for now. If you want to >>>> propose C++...

Hi All- As we all know, the C++14 discussion is flaring up again. Chandler brought up that he would like a concrete plan to switch. In my opinion, this is insufficient, as it will result in us simply having this discussion AGAIN next release. Instead, I would prefer us to have a concrete Policy on our host compilers. That way, changes like this are unsurprising to our users, and advance our

...017-October/118673.html> >>>>> - Using C++14 code in LLVM (2016) >>>>> <http://lists.llvm.org/pipermail/llvm-dev/2016-October/105483.html> >>>>> - Document and Enforce new Host Compiler Policy >>>>> <http://llvm.org/D47073> >>>>> - Require GCC 5.1 and LLVM 3.5 at a minimum >>>>> <http://llvm.org/D46723> >>>>> >>>>> >>>>> *Migrate to what?* >>>>> >>>>> I’m only proposing that we migrate to C++14 for...