This is the mail archive of the 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: PING: gimplifier ICE fix

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.

This won't prove anything for Java, Ada, and Fortran, but at least
it's a start.


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