Re: Feature request: -Wno-unknown-warnings to silently ignore unknown warning control flags.

2017-10-12 Thread Oren Ben-Kiki
On Fri, Oct 13, 2017 at 4:47 AM, Martin Sebor wrote: > My organization was particularly focused on warnings so I'm quite > familiar with the challenges you're hoping to overcome. I figured I wasn't the only one :-) But it is good to hear from others. > My > best advice is to either write a sc

Re: Feature request: -Wno-unknown-warnings to silently ignore unknown warning control flags.

2017-10-12 Thread Martin Sebor
On 10/12/2017 02:46 AM, Oren Ben-Kiki wrote: Motivation/Use case: * Since gcc/g++ intentionally does not have `-Weverything`, there is a number of explicit `-W...` flags one might wish to specify explicitly. Fair enough. * Additional `-W...` flags are introduced in new gcc/g++ versions, which c

gcc-7-20171012 is now available

2017-10-12 Thread gccadmin
Snapshot gcc-7-20171012 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/7-20171012/ 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: Calling functions through a pointerI

2017-10-12 Thread Jonathan Wakely
On 12 October 2017 at 18:09, Toshi Morita via gcc wrote: > This isn't a GCC question specifically - it's more of a C language question. And so is off-topic here. > I'm involved in a discussion involving C language function pointers. > The other party claims calling functions through a function p

Calling functions through a pointerI

2017-10-12 Thread Toshi Morita via gcc
This isn't a GCC question specifically - it's more of a C language question. I'm involved in a discussion involving C language function pointers. The other party claims calling functions through a function pointer is "undefined behavior" because it's not specifically mentioned in the C language

Re: Feature request: -Wno-unknown-warnings to silently ignore unknown warning control flags.

2017-10-12 Thread Oren Ben-Kiki
On Thu, Oct 12, 2017 at 10:10 PM, Jonathan Wakely wrote: > > "Most" != "All". > > > > IMVHO it is too strong to say "you don't need to know about [other > ones]". > > I didn't say that. I said you don't need to know about the -Wall ones, > because you get them anyway. > Ah, sorry, I misunderstoo

Re: Feature request: -Wno-unknown-warnings to silently ignore unknown warning control flags.

2017-10-12 Thread Oren Ben-Kiki
On Thu, Oct 12, 2017 at 9:40 PM, Andrew Pinski > -Wno-unkown-warning has already been handled silently since 4.6.0 > (which was released March 25, 2011): > https://gcc.gnu.org/onlinedocs/gcc-4.6.0/gcc/Warning-Options.html > > When an unrecognized warning option is requested (e.g., > -Wunknown-war

Re: Feature request: -Wno-unknown-warnings to silently ignore unknown warning control flags.

2017-10-12 Thread Jonathan Wakely
On 12 October 2017 at 19:10, Oren Ben-Kiki wrote: > On Thu, Oct 12, 2017 at 1:14 PM, Jonathan Wakely> * Additional `-W...` flags > are introduced in new gcc/g++ versions, which >> >> > check for new potential code smells, possibly related to later language >> > standards. That's great (thanks!). >>

Removal

2017-10-12 Thread Kurstin Roberts
I would like all software removed from my phone.accounts. etc immediately

Re: Feature request: -Wno-unknown-warnings to silently ignore unknown warning control flags.

2017-10-12 Thread Andrew Pinski
)4.On Thu, Oct 12, 2017 at 1:46 AM, Oren Ben-Kiki wrote: > Motivation/Use case: > > * Since gcc/g++ intentionally does not have `-Weverything`, there is a > number of explicit `-W...` flags one might wish to specify explicitly. Fair > enough. > > * Additional `-W...` flags are introduced in new gc

Re: Feature request: -Wno-unknown-warnings to silently ignore unknown warning control flags.

2017-10-12 Thread Oren Ben-Kiki
On Thu, Oct 12, 2017 at 1:14 PM, Jonathan Wakely> * Additional `-W...` flags are introduced in new gcc/g++ versions, which > > check for new potential code smells, possibly related to later language > > standards. That's great (thanks!). > > And the most widely useful ones are added to -Wall so yo

Re: RFC: Update top level libtool files

2017-10-12 Thread Eric Gallager
On Tue, Oct 10, 2017 at 11:20 AM, Nick Clifton wrote: > Hi Joseph, > >> As per previous discussions on the issue: it's necessary to revert libtool >> commit 3334f7ed5851ef1e96b052f2984c4acdbf39e20c, see >> . > > OK - thanks for that pointer

Re: reload ICE during ada and go bootstrap on x86_64

2017-10-12 Thread Vladimir Makarov
On 10/11/2017 10:43 PM, Martin Sebor wrote: Hi Vladimir, On a hunch I backed out r253656. That let the Ada and Go bootstrap complete. It looks like your fix for bug 82353 is triggering this ICE. Martin, thank you for informing me. I used the default bootstrap. I've reverted LRA changes be

Re: Feature request: -Wno-unknown-warnings to silently ignore unknown warning control flags.

2017-10-12 Thread Jonathan Wakely
On 12 October 2017 at 09:46, Oren Ben-Kiki wrote: > Motivation/Use case: > > * Since gcc/g++ intentionally does not have `-Weverything`, there is a > number of explicit `-W...` flags one might wish to specify explicitly. Fair > enough. > > * Additional `-W...` flags are introduced in new gcc/g++ ve

Feature request: -Wno-unknown-warnings to silently ignore unknown warning control flags.

2017-10-12 Thread Oren Ben-Kiki
Motivation/Use case: * Since gcc/g++ intentionally does not have `-Weverything`, there is a number of explicit `-W...` flags one might wish to specify explicitly. Fair enough. * Additional `-W...` flags are introduced in new gcc/g++ versions, which check for new potential code smells, possibly re