Re: Call for volunteers: GCC Bugzilla account approval
On 21 June 2017 at 06:17, R0b0t1 wrote: > P.S. David, not that I mind everyone knowing of my interest, but I > didn't reply publicly. This list seems to expect people to not want to > reply to the list by default, as hitting "reply" stuffs the responder > into the TO field and the message doesn't get sent to the list. This > was my intent in this case, so sorry if the message was confusing. It just expects you to use "Reply all" if you want to reply to all, or check where you're sending the email before hitting send. See http://www.unicom.com/pw/reply-to-harmful.html Lots of lists work that way, but whether the list is configured for reply-to-list or reply-to-sender, somebody is always surprised by it.
D Language accepted for inclusion in GCC
I am pleased to announce that the GCC Steering Committee has accepted the D Language front-end and runtime for inclusion in GCC and appointed Iain Buclaw as maintainer. The patches still require approval by a Global Reviewer. Please join me in congratulating Iain on his new role. Please update your listing in the MAINTAINERS file. Happy hacking! David
Andrew Jenner appointed PowerPC SPE maintainer
I am pleased to announce that the GCC Steering Committee has appointed Andrew Jenner as PowerPC SPE port maintainer. Please join me in congratulating Andrew on his new role. Andrew, please update your listing in the MAINTAINERS file. Happy hacking! David
Re: Andrew Jenner appointed PowerPC SPE maintainer
On 21/06/2017 16:40, David Edelsohn wrote: I am pleased to announce that the GCC Steering Committee has appointed Andrew Jenner as PowerPC SPE port maintainer. Please join me in congratulating Andrew on his new role. Andrew, please update your listing in the MAINTAINERS file. Happy hacking! Thanks, David! I've applied the following patch to update my listing in MAINTAINERS. Andrew * MAINTAINERS: Add myself as maintainer for PowerPC SPE port. Index: MAINTAINERS === --- MAINTAINERS (revision 249460) +++ MAINTAINERS (working copy) @@ -85,6 +85,7 @@ nios2 portChung-Lin Tang pdp11 port Paul Koning picochip port Daniel Towner +powerpcspe portAndrew Jenner riscv port Kito Cheng riscv port Palmer Dabbelt riscv port Andrew Waterman
Uh
Sent from my iPhone
Re: D Language accepted for inclusion in GCC
On 21 June 2017 at 15:44, David Edelsohn wrote: > I am pleased to announce that the GCC Steering Committee has > accepted the D Language front-end and runtime for inclusion in GCC > and appointed Iain Buclaw as maintainer. > > The patches still require approval by a Global Reviewer. > > Please join me in congratulating Iain on his new role. > Please update your listing in the MAINTAINERS file. > > Happy hacking! > David > Thank you. I have no words for how grateful I am of this, and I look forward to the next stage. Iain.
gcc-6-20170621 is now available
Snapshot gcc-6-20170621 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/6-20170621/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 6 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-6-branch revision 249486 You'll find: gcc-6-20170621.tar.xzComplete GCC SHA256=dcc81ad0ee8a67fab24269016b3830e7708addfc872db675198611181c711437 SHA1=3f526dae36e5e8535e3bfcb6779296cceb77f17d Diffs from 6-20170614 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-6 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
Re: Missing warning opportunity - code after break;
Doesn't look like I can create a GCC bugzilla account, but 7 years? Wow. On 20/06/2017 3:48 p.m., Eric Gallager wrote: On 6/19/17, Soul Studios wrote: Just noticed this: while(something) { // stuff if (num_elements == 0) { break; --current_group; } } doesn't trigger a warning in GCC 5.1, 6.3 and 7.1. The line after "break;" is unused, probably should be before the break, ie. user error. Matt Bentley This is bug 46476: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46476