Re: Moving to C++11

2019-09-26 Thread Eric Gallager
On 9/26/19, Nicholas Krause wrote: > Greetings, > > I asked about moving to C/C++ 11 as it would make it easier to > > allow multithreading support due to having a memory model > > alongside other features. Jason Merill mentioned due to it > > being so common it may be a good time to. > > Moving

Re: Moving to C++11

2019-09-26 Thread Pedro Alves
On 9/26/19 9:08 AM, Richard Biener wrote: > Note the main issue is host compiler support. I'm not sure if C++11 would > be the step we'd gain most - for some hashtable issues I'd have needed > std::move support for example. There's always the possibility to > require an intermediate step (first

gcc-7-20190926 is now available

2019-09-26 Thread gccadmin
Snapshot gcc-7-20190926 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/7-20190926/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 7 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-7

Re: Reposurgeon status

2019-09-26 Thread Eric S. Raymond
Joseph Myers : > On Thu, 26 Sep 2019, Eric S. Raymond wrote: > > > > You might want to update the state of reposurgeon on that page. > > > > I will do so. > > Note that once you've created an account, someone will need to add it to > the EditorGroup page before you can edit. I'm having trouble

Re: Reposurgeon status

2019-09-26 Thread Joseph Myers
On Thu, 26 Sep 2019, Eric S. Raymond wrote: > > You might want to update the state of reposurgeon on that page. > > I will do so. Note that once you've created an account, someone will need to add it to the EditorGroup page before you can edit. -- Joseph S. Myers jos...@codesourcery.com

Re: Moving to C++11

2019-09-26 Thread Richard Sandiford
Tom Tromey writes: >> "Jason" == Jason Merrill writes: > > Jason> Note that std::move is from C++11. > >>> I'm not too worried about requiring even a C++14 compiler, for the >>> set of products we still release latest compilers we have newer >>> GCCs available we can use for building them (ev

Re: Reposurgeon status

2019-09-26 Thread Eric S. Raymond
Jeff Law : > Probably the most important thing to know is the project will make a > decision on Dec 16 to choose the conversion tool. The evaluation is > based on the state of tool's conversion on that date. More details: > > > https://gcc.gnu.org/wiki/GitConversion > > You should consider the

Re: Moving to C++11

2019-09-26 Thread Tom Tromey
> "Jason" == Jason Merrill writes: Jason> Note that std::move is from C++11. >> I'm not too worried about requiring even a C++14 compiler, for the >> set of products we still release latest compilers we have newer >> GCCs available we can use for building them (even if those are >> not our p

Re: Moving to C++11

2019-09-26 Thread Jason Merrill
On Thu, Sep 26, 2019 at 4:08 AM Richard Biener wrote: > On Thu, Sep 26, 2019 at 9:23 AM Jonathan Wakely wrote: > > On Thu, 26 Sep 2019, 05:10 Nicholas Krause, wrote: > > > > > > Greetings, > > > > > > I asked about moving to C/C++ 11 as it would make it easier to > > > > > > allow multithreading

Re: Moving to C++11

2019-09-26 Thread Nicholas Krause
On 9/26/19 4:08 AM, Richard Biener wrote: On Thu, Sep 26, 2019 at 9:23 AM Jonathan Wakely wrote: On Thu, 26 Sep 2019, 05:10 Nicholas Krause, wrote: Greetings, I asked about moving to C/C++ 11 as it would make it easier to allow multithreading support due to having a memory model alongsid

Re: Reposurgeon status

2019-09-26 Thread Jeff Law
On 9/25/19 2:32 PM, Eric S. Raymond wrote: > Since the subject of repository conversions has come up, a situation report... > > I am in the very last stages of qualifying the Go port of reposurgeon. > Most importantly to your project, the Go code passed all of the > existing regression tests for r

Re: GCC Git hooks

2019-09-26 Thread Joel Brobecker
> But before I say more I should point to the documentation which, > for historical reasons, is available on the GDB wiki rather than > the git-hooks GitHub repository. I will fix that, but in the meantime: > > https://sourceware.org/gdb/wiki/GitHooksUsersGuide Just a quick note to confirm th

Re: Kyrylo Tkachov and Richard Sandiford appointed AArch64 maintainers.

2019-09-26 Thread Richard Sandiford
Kyrill Tkachov writes: > On 9/26/19 8:02 AM, Ramana Radhakrishnan wrote: >> Hi, >> >> I'm pleased to announce that the GCC steering committee has appointed >> Kyrylo Tkachov and Richard Sandiford as AArch64 maintainers. >> >> Please join me in congratulating them both on their additional roles >>

Re: Kyrylo Tkachov and Richard Sandiford appointed AArch64 maintainers.

2019-09-26 Thread Kyrill Tkachov
On 9/26/19 8:02 AM, Ramana Radhakrishnan wrote: Hi, I'm pleased to announce that the GCC steering committee has appointed Kyrylo Tkachov and Richard Sandiford as AArch64 maintainers. Please join me in congratulating them both on their additional roles in the community. Kyrill / Richard, please

Re: Moving to C++11

2019-09-26 Thread Richard Biener
On Thu, Sep 26, 2019 at 9:23 AM Jonathan Wakely wrote: > > On Thu, 26 Sep 2019, 05:10 Nicholas Krause, wrote: > > > > Greetings, > > > > I asked about moving to C/C++ 11 as it would make it easier to > > > > allow multithreading support due to having a memory model > > > > alongside other feature

Re: Moving to C++11

2019-09-26 Thread Jonathan Wakely
On Thu, 26 Sep 2019, 05:10 Nicholas Krause, wrote: > > Greetings, > > I asked about moving to C/C++ 11 as it would make it easier to > > allow multithreading support due to having a memory model > > alongside other features. Jason Merill mentioned due to it > > being so common it may be a good ti

Kyrylo Tkachov and Richard Sandiford appointed AArch64 maintainers.

2019-09-26 Thread Ramana Radhakrishnan
Hi, I'm pleased to announce that the GCC steering committee has appointed Kyrylo Tkachov and Richard Sandiford as AArch64 maintainers. Please join me in congratulating them both on their additional roles in the community. Kyrill / Richard, please update your listings in the MAINTAINERS file. Tha