discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: PING: gimplifier ICE fix


From: Steven Bosscher
Subject: Re: PING: gimplifier ICE fix
Date: Tue, 25 Jan 2005 01:40:17 +0100
User-agent: KMail/1.7.1

On Tuesday 25 January 2005 01:34, Ziemowit Laski wrote:
> On 24 Jan 2005, at 16.34, Steven Bosscher wrote:
> > On Tuesday 25 January 2005 01:01, Ziemowit Laski wrote:
> >> On 24 Jan 2005,@15.39, Richard Henderson wrote:
> >>> On Mon, Jan 24, 2005@03:29:06PM -0800, Ziemowit Laski wrote:
> >>>> Please show me how you enumerate that set.
> >>>
> >>> You don't.
> >>
> >> Thanks for the constructive response (as always) ...
> >
> > You're not always being very constructive yourself, you know...
> >
> > Anyway, here's something you could do.
> > - get preprocessed sources of a full gcc build tree.  You can do
> >   that by bootstrapping with -save-temps, and then collect all
> >   the .i and .ii files in one place.
> > - do "for $f in *.i; \
> >   do $build/gcc/cc1 -quiet -fdump-tree-optimized -O2 $f; \
> >   done".  Do the same for all .ii files.  Do this for a patched
> >   and an unpatched compiler, and compare all the .optimized files.
> >   If they are identical, you've taken the first hurdle.
> > - hack the test suite scripts to dump the .optimized tree dump in
> >   some directory (but *not* the $build/gcc/testsuite/ directory)
> >   Do this again for the patched and unpatched compilers, and again
> >   compare them.
>
> Sounds like a plan, Steven!  Go to it.  I don't have the time.

See, that's what I mean.  I'm trying to help you somewhat, and all
I get is this kind of arrogant answer.  Go fuck yourself.

Gr.
Steven




reply via email to

[Prev in Thread] Current Thread [Next in Thread]