* Re: A bad gcc 2.95 bug
[not found] <or673mmsw3.fsf@cupuacu.lsd.dcc.unicamp.br>
@ 1999-07-14 23:04 ` H.J. Lu
0 siblings, 0 replies; 2+ messages in thread
From: H.J. Lu @ 1999-07-14 23:04 UTC (permalink / raw)
To: Alexandre Oliva; +Cc: egcs-bugs, GNU C Library
>
> On Jul 14, 1999, hjl@varesearch.com (H.J. Lu) wrote:
>
> > Why does it return in gcc 2.95?
>
> gcc 2.95 has become much stricter about C++ rules. You need
> -fpermissive to get it less strict.
>
It is a real bug. I posted a patch:
http://egcs.cygnus.com/ml/egcs-bugs/1999-07/msg00534.html
http://egcs.cygnus.com/ml/egcs-bugs/1999-07/msg00537.html
H.J.
^ permalink raw reply [flat|nested] 2+ messages in thread
* A bad gcc 2.95 bug
@ 1999-07-14 17:03 H.J. Lu
0 siblings, 0 replies; 2+ messages in thread
From: H.J. Lu @ 1999-07-14 17:03 UTC (permalink / raw)
To: egcs-bugs; +Cc: GNU C Library
Hi,
With egcs 1.1.2, I got
# gcc foo.cc
foo.cc:4: warning: declaration of `exit(int)' throws different exceptions
foo.cc:3: warning: previous declaration here
But with gcc 2.95 19990711, now I got
# gcc foo.cc
foo.cc:4: declaration of `exit(int)' throws different exceptions
foo.cc:3: previous declaration here
That is a bug fixed for egcs 1.1.2. Why does it return in gcc 2.95?
It will screw up glibc. It has to be fixed in gcc 2.95.
--
H.J. Lu (hjl@gnu.org)
---foo.cc-
extern "C" {
void exit (int);
void exit (int) __attribute__ ((__noreturn__));
void exit (int) throw () __attribute__ ((__noreturn__));
};
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~1999-07-14 23:04 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <or673mmsw3.fsf@cupuacu.lsd.dcc.unicamp.br>
1999-07-14 23:04 ` A bad gcc 2.95 bug H.J. Lu
1999-07-14 17:03 H.J. Lu
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).