public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: hjl@varesearch.com (H.J. Lu)
To: oliva@dcc.unicamp.br (Alexandre Oliva)
Cc: egcs-bugs@egcs.cygnus.com,
	libc-hacker@sourceware.cygnus.com (GNU C Library)
Subject: Re: A bad gcc 2.95 bug
Date: Wed, 14 Jul 1999 23:04:00 -0000	[thread overview]
Message-ID: <19990715060352.4039D3FC1@varesearch.com> (raw)
In-Reply-To: <or673mmsw3.fsf@cupuacu.lsd.dcc.unicamp.br>

> 
> 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.

       reply	other threads:[~1999-07-14 23:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <or673mmsw3.fsf@cupuacu.lsd.dcc.unicamp.br>
1999-07-14 23:04 ` H.J. Lu [this message]
1999-07-14 17:03 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=19990715060352.4039D3FC1@varesearch.com \
    --to=hjl@varesearch.com \
    --cc=egcs-bugs@egcs.cygnus.com \
    --cc=libc-hacker@sourceware.cygnus.com \
    --cc=oliva@dcc.unicamp.br \
    /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).