This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Recent warning regression in libstdc++-v3/libsupc++

From: Paolo Carlini <paolo dot carlini at oracle dot com>
To: Sebastian Redl <wasti at windmuehlgasse dot getdesigned dot at>
Cc: gcc at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org, dseketel at redhat dot com
Date: Wed, 23 Jul 2008 10:21:31 -0500 (CDT)
Subject: Re: Recent warning regression in libstdc++-v3/libsupc++
Accept-language: en-US
References: <20158202.1216824857228.JavaMail.oracle@acsmt305.oracle.com> <4887483E.6090002@windmuehlgasse.getdesigned.at>

Hi,

> However, a svn log shows that neither unwind-cxx.h nor except.c
> in the C++ frontend changed this year in a relevant way. So my guess
> is that the warning is what changed. Either the warning settings during
> compilation, or a new warning was introduced/activated in the
> compiler itself.

I agree. I suspect the below change may have to do with it. Dodji, could you please have a look? ... and in case suggest a fix?

Many thanks in advance,
Paolo.

///////////

2008-07-16  Dodji Seketeli  <dseketel@redhat.com>

	PR c++/13699
	* name-lookup.c (lookup_extern_c_fun_binding_in_all_ns): New function.
	(pushdecl_maybe_friend): Check if a redeclaration of extern C function
	complies with exception specification constraints.

Follow-Ups:
- Re: Recent warning regression in libstdc++-v3/libsupc++
  - From: Paolo Carlini

References:
- Recent warning regression in libstdc++-v3/libsupc++
  - From: Paolo Carlini
- Re: Recent warning regression in libstdc++-v3/libsupc++
  - From: Sebastian Redl

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]