public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@dcc.unicamp.br>
To: hjl@varesearch.com (H.J. Lu)
Cc: egcs-bugs@egcs.cygnus.com,
libc-hacker@sourceware.cygnus.com (GNU C Library)
Subject: Re: A bad gcc 2.95 bug
Date: Sat, 31 Jul 1999 23:33:00 -0000 [thread overview]
Message-ID: <or673mmsw3.fsf@cupuacu.lsd.dcc.unicamp.br> (raw)
In-Reply-To: <19990714193206.B31013FC1@varesearch.com>
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.
--
Alexandre Oliva http://www.dcc.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
oliva@{dcc.unicamp.br,guarana.{org,com}} aoliva@{acm.org,computer.org}
oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org}
** I may forward mail about projects to mailing lists; please use them
next prev parent reply other threads:[~1999-07-31 23:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-14 17:03 H.J. Lu
1999-07-31 23:33 ` Alexandre Oliva [this message]
1999-07-14 23:04 ` H.J. Lu
1999-07-31 23:33 Mike Stump
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=or673mmsw3.fsf@cupuacu.lsd.dcc.unicamp.br \
--to=oliva@dcc.unicamp.br \
--cc=egcs-bugs@egcs.cygnus.com \
--cc=hjl@varesearch.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).