This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC trunk SPEC2000 performance
- From: law at redhat dot com
- To: David Edelsohn <dje at watson dot ibm dot com>
- Cc: Andreas Jaeger <aj at suse dot de>, Jan Hubicka <jh at suse dot cz>, Diego Novillo <dnovillo at redhat dot com>, Mark Mitchell <mark at codesourcery dot com>, gcc at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- Date: Thu, 20 Jun 2002 15:12:23 -0600
- Subject: Re: GCC trunk SPEC2000 performance
- Reply-to: law at redhat dot com
In message <200206202034.QAA24414@makai.watson.ibm.com>, David Edelsohn writes:
> >>>>> law writes:
>
> Jeff> But how/why did we have a non-REG thingie in the register replacement
> array?
> Jeff> That's key to knowing if Jan's patch is correct or just papering over
> a problem
> Jeff> elsewhere.
>
> If Honza is papering over a problem, then other parts of the
> compiler have been papering over the same problem for over five years. It
> certainly looks like a MEM could occur.
What I'd like to see is a reference to the actual code that turns a REG
expression into a MEM tha tcan occur before reload. Given a pointer to
that hunk of code, then we clearly know Honza's patch is correct and we
can ask him (or anyone) to update it slightly to include suitable comments
about MEMs appearing in the register array and install it. Without that
basic information we have no idea if his patch is actually correct or not.
The fact that other code may or may not be papering over a bug has no bearing
on whether or not Jan's patch is correct.
jeff