This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PR target/20126, RFC] loop DEST_ADDR biv replacement may fail
- From: Alexandre Oliva <aoliva at redhat dot com>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: gcc-patches at gcc dot gnu dot org, gcc-bugzilla at gcc dot gnu dot org
- Date: 02 Apr 2005 14:22:15 -0300
- Subject: Re: [PR target/20126, RFC] loop DEST_ADDR biv replacement may fail
- Organization: Red Hat Global Engineering Services Compiler Team
- References: <ord5ubyvb0.fsf@livre.redhat.lsd.ic.unicamp.br><20050309014713.GF853@devserv.devel.redhat.com><orwtshii0v.fsf@livre.redhat.lsd.ic.unicamp.br><20050309092115.GH853@devserv.devel.redhat.com><or7jkfload.fsf@livre.redhat.lsd.ic.unicamp.br><ork6oecl2w.fsf@livre.redhat.lsd.ic.unicamp.br>
On Mar 11, 2005, Alexandre Oliva <aoliva@redhat.com> wrote:
> On Mar 10, 2005, Alexandre Oliva <aoliva@redhat.com> wrote:
>> + ??? Should this should search new for new volatile MEMs and reject
>> + them? */
> Here's a stricter version that does test for this.
> Index: gcc/ChangeLog
> from Alexandre Oliva <aoliva@redhat.com>
> PR target/20126
> * loop.c (loop_givs_rescan): If replacement of DEST_ADDR failed,
> set the original address pseudo to the correct value before the
> original insn, if possible, and leave the insn alone, otherwise
> create a new pseudo, set it and replace it in the insn.
> * recog.c (validate_change_maybe_volatile): New.
> * recog.h (validate_change_maybe_volatile): Declare.
Ping?
http://gcc.gnu.org/PR20126
--
Alexandre Oliva http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}