[Bug debug/44610] VTA produces wrong variable location information

[aoliva at gcc dot gnu dot org]

--- Comment #6 from aoliva at gcc dot gnu dot org  2010-06-25 21:11 ---
Subject: Bug 44610

Author: aoliva
Date: Fri Jun 25 21:11:32 2010
New Revision: 161413

URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=161413
Log:
PR debug/44610
* simplify-rtx.c (delegitimize_mem_from_attrs): Don't use a base
address if the offset is unknown.

Modified:
trunk/gcc/ChangeLog
trunk/gcc/simplify-rtx.c


-- 


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

[Bug debug/44610] VTA produces wrong variable location information

[aoliva at gcc dot gnu dot org]

--- Comment #7 from aoliva at gcc dot gnu dot org  2010-06-25 21:12 ---
Subject: Bug 44610

Author: aoliva
Date: Fri Jun 25 21:11:56 2010
New Revision: 161414

URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=161414
Log:
PR debug/44610
* simplify-rtx.c (delegitimize_mem_from_attrs): Don't use a base
address if the offset is unknown.

Modified:
branches/gcc-4_5-branch/gcc/ChangeLog
branches/gcc-4_5-branch/gcc/simplify-rtx.c


-- 


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

[Bug debug/44610] VTA produces wrong variable location information

[aoliva at gcc dot gnu dot org]

--- Comment #8 from aoliva at gcc dot gnu dot org  2010-06-25 21:13 ---
Fixed


-- 

aoliva at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution||FIXED


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

[Bug debug/44610] VTA produces wrong variable location information

[aoliva at gcc dot gnu dot org]

--- Comment #4 from aoliva at gcc dot gnu dot org  2010-06-23 04:30 ---
Mine


-- 

aoliva at gcc dot gnu dot org changed:

   What|Removed |Added

 AssignedTo|unassigned at gcc dot gnu   |aoliva at gcc dot gnu dot
   |dot org |org
 Status|UNCONFIRMED |ASSIGNED
 Ever Confirmed|0   |1
   Last reconfirmed|-00-00 00:00:00 |2010-06-23 04:30:09
   date||


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

[Bug debug/44610] VTA produces wrong variable location information

[aoliva at gcc dot gnu dot org]

--- Comment #5 from aoliva at gcc dot gnu dot org  2010-06-23 04:35 ---
Created an attachment (id=20984)
 -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=20984action=view)
Patch that fixes the problem

The MEMs for each HImode in the DImode args all have NULL MEM_OFFSET (we indeed
don have a constant offset within the loop, for it varies), but when we
delegitimize those addresses during var-tracking, we assume no MEM_OFFSET means
zero MEM_OFFSET, which maps all MEMs to the same VALUE.  The assumption turns
out to be wrong.  We can't delegitimize a MEM to the base address when it may
be offset by an unknown amount.  Testing the patch now.


-- 


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

[Bug debug/44610] VTA produces wrong variable location information

[hariharans at picochip dot com]

--- Comment #1 from hariharans at picochip dot com  2010-06-21 13:55 ---
Created an attachment (id=20961)
 -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=20961action=view)
The test sourcecode


-- 


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

[Bug debug/44610] VTA produces wrong variable location information

[hariharans at picochip dot com]

--- Comment #2 from hariharans at picochip dot com  2010-06-21 13:56 ---
Created an attachment (id=20962)
 -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=20962action=view)
The test assembly


-- 


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

[Bug debug/44610] VTA produces wrong variable location information

[hariharans at picochip dot com]

--- Comment #3 from hariharans at picochip dot com  2010-06-21 13:59 ---
In my first comment, bug 43982 should have been bug 43983


-- 


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