[Bug target/20126] [3.3/3.4/4.0/4.1 Regression] Inlined memcmp makes one argument null on entry

[aoliva at redhat dot com]

------- Additional Comments From aoliva at gcc dot gnu dot org  2005-04-02 17:22 -------
Subject: Re: [PR target/20126, RFC] loop DEST_ADDR biv replacement may fail

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



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20126