------- Comment #10 from amacleod at redhat dot com 2007-11-06 15:28 -------
Partitioning doesn't really seem to be the root problem.
looking at testcase-min.i:
There are about 820 SFTs associated with the giant structure, and we decide
that they *all* can be affected by the memory access and try to issue VOPS for
them.
An int is loaded via MEM[base: Hoopster_ptr_17, offset: 3552].
In get_tmr_operands(), we always call add_virtual_operands() with an offset of
0 and a size of -1. This seems wrong. we should be able to use the size of the
load and offset information to figure out the right SFT(s) to add. Instead,
because the size is -1, we simply include all of them.
Is this offset of 0 and size of -1 to paper over something else? I understand
there might be issues trying to get the right offset and base calculations
under some conditions...
--
amacleod at redhat dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2007-08-14 08:44:16 |2007-11-06 15:28:16
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31976
