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: c++/4862 and PRs marked (or not) as parser bugs

From: "H . J . Lu" <hjl at lucon dot org>
To: Paolo Carlini <pcarlini at unitus dot it>
Cc: gcc at gcc dot gnu dot org, jason at redhat dot com
Date: Sat, 2 Feb 2002 12:52:26 -0800
Subject: Re: c++/4862 and PRs marked (or not) as parser bugs
References: <3C5BC603.2355A224@unitus.it> <20020202110516.B340@lucon.org> <3C5C49E5.756B9CF7@unitus.it>

On Sat, Feb 02, 2002 at 09:19:49PM +0100, Paolo Carlini wrote:
> "H . J . Lu" wrote:
> 
> > I have sent a testcase long time ago:
> >
> > http://gcc.gnu.org/ml/gcc-patches/2001-08/msg01378.html
> >
> > Are they the same thing? Here is a patch I have been using without any
> > problem. BTW, I have no ideas what I am doing.
> 
> :-)
> 
> How about c++/5577?? Does it fix this one too?? In that case it would be really nice
> to have it for 3.1 too...

No, my patch doesn't fix 5577. It has been long time since I worked
on it last time. I don't have time to look into it. I am not sure if
they are related. Besides, my users haven't been bitten by it yet.

H.J.

Follow-Ups:
- c++/5577 (was: Re: c++/4862 and PRs...)
  - From: Paolo Carlini

References:
- c++/4862 and PRs marked (or not) as parser bugs
  - From: Paolo Carlini
- Re: c++/4862 and PRs marked (or not) as parser bugs
  - From: H . J . Lu
- Re: c++/4862 and PRs marked (or not) as parser bugs
  - From: Paolo Carlini

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