This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Problem with 447.dealII in spec2006 because of r240707
- From: Marek Polacek <polacek at redhat dot com>
- To: Andrew Pinski <pinskia at gmail dot com>
- Cc: Bill Seurer <seurer at linux dot vnet dot ibm dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Tue, 4 Oct 2016 17:41:12 +0200
- Subject: Re: Problem with 447.dealII in spec2006 because of r240707
- Authentication-results: sourceware.org; auth=none
- References: <96168ad5-2966-59a8-f15d-f953f99b32b9@linux.vnet.ibm.com> <CA+=Sn1mXuf5_cMftrkMNHe9facRngTPJNhMns1Mu47KXGgUbGw@mail.gmail.com>
On Tue, Oct 04, 2016 at 08:38:00AM -0700, Andrew Pinski wrote:
> On Tue, Oct 4, 2016 at 8:33 AM, Bill Seurer <seurer@linux.vnet.ibm.com> wrote:
> > parameter_handler.cc: In member function 'double
> > ParameterHandler::get_double(const string&) const':
> > parameter_handler.cc:777:28: error: ISO C++ forbids comparison between
> > pointer and integer [-fpermissive]
> > AssertThrow ((s.c_str()!='\0') || (*endptr == '\0'),
> > ^
> > With the recent revision r240707 comparing a pointer with \0 became an
> > error. Unfortunately this is used in several spots in the test case
> > 447.dealII in spec2006 (one example above). There doesn't appear to be a
> > way to disable this error check and we're not supposed to change the spec
> > test cases. Any ideas on how to work around this?
>
> Did you try -fpermissive ? Because that seems like it was listed ...
-fpermissive ought to help, but really best would be to use NULL instead
of '\0'...
Marek