This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Your g++ breaks glibc.
- To: law at cygnus dot com
- Subject: Re: Your g++ breaks glibc.
- From: Mark Mitchell <mark at codesourcery dot com>
- Date: Wed, 14 Jul 1999 23:37:38 -0700
- Cc: hjl at varesearch dot com, jason at cygnus dot com, egcs-patches at egcs dot cygnus dot com, libc-hacker at sourceware dot cygnus dot com
- Organization: CodeSourcery, LLC
- References: <19990714195521.1BA043FC1@varesearch.com><17627.932018957@upchuck.cygnus.com>
>>>>> "Jeffrey" == Jeffrey A Law <law@cygnus.com> writes:
Jeffrey> I've got conflicting reports from Jason and Alexandre
Jeffrey> about this one. I need a definitive answer before I wake
Jeffrey> up in the morning or it will not be in gcc-2.95.
Both Jason and Alexandre are right.
The code is indeed buggy:
[except.spec]
If any declaration of a function has an exception-specification, all
declarations, including the definition and an explicit specialization,
of that function shall have an exception-specification with the same
set of type-ids.
It couldn't be any clearer.
If autoconf is generating the code fragment H.J. shows, then autoconf
is broken.
However, the patch should still go on the branch. After all, autoconf
is in widespread use. There is no non-conformance issue here since we
will still warn if -pedantic.
H.J., please follow up with whatever tool is producing this bogus
code, and get that tool fixed. In the next major version, we should
make this a warning, even without -pedantic. In the next major
version after that, we should probably disallow this usage, period.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com