Hi Dan,
Reply below.
Best regards
On Thu, 4 Aug 2005 02:05, Dan Kegel wrote:
> "Paul C. Leopardi" <[EMAIL PROTECTED]> wrote:
> > So I seem to be left with a large ( >2.5MB ) preprocessed source file.
> > Should I try to report the bug using this large file as a test case?
>
> Sure. But you might
Hi Volker,
On Thu, 4 Aug 2005 02:31 am, Volker Reichelt wrote:
> You might want to try a recent snapshot of gcc 4.0.2, first.
> Two aliasing bugs got fixed after the 4.0.1 release:
>
> http://gcc.gnu.org/PR22591
> http://gcc.gnu.org/PR23192
>
> The first even caused std::list::swap to be miscompile
Paul Leopardi wrote:
> I have now downloaded, bootstapped and installed gcc 4.0.1. The bug in g++
> optimization is still there. I've made an attempt to follow the instructions
> on minimizing test cases and have so far accomplished:
> wc of old preprocessed source:
> 99412 260586 2965538 peg
2nd implementation?:
http://www.cs.berkeley.edu/~dsw/
This is what we all use, AFAIK :)
"Paul C. Leopardi" <[EMAIL PROTECTED]> wrote:
> So I seem to be left with a large ( >2.5MB ) preprocessed source file. Should
> I try to report the bug using this large file as a test case?
Sure. But you might want to try using an automated tool
to reduce the test case first. There's one called
Hi Janis,
A belated reply to your message is below.
Best regards, Paul Leopardi
On Tue, 17 May 2005 03:23 am, Janis Johnson wrote:
> On Sat, May 14, 2005 at 12:16:54PM +1000, Paul C. Leopardi wrote:
> > Hi all,
> > I originally posted these messages to gcc-help, but had no reply, so I am
> > re-po
On Sat, May 14, 2005 at 12:16:54PM +1000, Paul C. Leopardi wrote:
> Hi all,
> I originally posted these messages to gcc-help, but had no reply, so I am
> re-posting links to them here.
>
> I think I have found a bug in g++ 4.0.0, but need help in reporting it.
> Maintainers like their bug repor
Andrew,
Thanks for reminding me about this. I'll need to take a good look at this.
The effect of the workaround is to change any instance of _GLUCAT_PRIVATE to
public. This does not affect the validity or otherwise of the g++ bug I'm
currently trying to report.
I wrote GluCat at a time when ea
On May 13, 2005, at 10:16 PM, Paul C. Leopardi wrote:
+//* workaround for ICC, G++ 3.3+, G++ 4.0+
Why do you need this work around? Why has this not been filed or really
fixed in their sources?
-- Pinski
Hi all,
I originally posted these messages to gcc-help, but had no reply, so I am
re-posting links to them here.
I think I have found a bug in g++ 4.0.0, but need help in reporting it.
Maintainers like their bug reports to include short test cases, but I don't
know how to generate a short test
10 matches
Mail list logo