From: hjl@varesearch.com (H.J. Lu)
To: egcs-bugs@egcs.cygnus.com
Cc: libc-hacker@sourceware.cygnus.com (GNU C Library)
Subject: A bad gcc 2.95 bug
Date: Wed, 14 Jul 1999 17:03:00 -0000 [thread overview]
Message-ID: <19990714193206.B31013FC1@varesearch.com> (raw)
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__));
};
next reply other threads:[~1999-07-14 17:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-14 17:03 H.J. Lu [this message]
[not found] <or673mmsw3.fsf@cupuacu.lsd.dcc.unicamp.br>
1999-07-14 23:04 ` H.J. Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19990714193206.B31013FC1@varesearch.com \
--to=hjl@varesearch.com \
--cc=egcs-bugs@egcs.cygnus.com \
--cc=libc-hacker@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).