This is the mail archive of the
mailing list for the GCC project.
Re: -Wno-c++11-extensions addition
- From: Jack Howarth <howarth dot at dot gcc at gmail dot com>
- To: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Wed, 25 Mar 2015 12:55:16 -0400
- Subject: Re: -Wno-c++11-extensions addition
- Authentication-results: sourceware.org; auth=none
- References: <CAJMcOU_LAt=AYNDxau66HO3HAO=ZCgwa5DBopLNrAJysRGv5Cg at mail dot gmail dot com> <CAH6eHdSHe8c43NdvMBEg0fzKdun2P2CZn3k2WdMwXM1EF4XZcw at mail dot gmail dot com>
On Wed, Mar 25, 2015 at 12:41 PM, Jonathan Wakely <firstname.lastname@example.org> wrote:
> On 25 March 2015 at 16:16, Jack Howarth wrote:
>> Does anyone remember which FSF gcc release first added the
>> -Wno-c++11-extensions option for g++? I know it exists in 4.6.3
> Are you sure? It doesn't exist for 4.6.4 or anything later.
> Are you thinking of -Wc++0x-compat ?
On x86_64 Fedora 15...
$ /usr/bin/g++ --version
g++ (GCC) 4.6.3 20120306 (Red Hat 4.6.3-2)
Copyright (C) 2011 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$ /usr/bin/g++ -Wno-c++11-extensions hello.cc
So gcc 4.6.3 appears to at least tolerate that warning without
claiming that it is unknown.