On Tue, 27 Mar 2012, Martin Jambor wrote:
> Hi,
>
> this fixes a thinko that leads to wrong-code generation that is in the
> "new" SRA since the beginning. When there are two unscalarizable
> regions in an access tree, one within another, the aggregate
> assignment modification code may use them
Hi,
this fixes a thinko that leads to wrong-code generation that is in the
"new" SRA since the beginning. When there are two unscalarizable
regions in an access tree, one within another, the aggregate
assignment modification code may use them as basis of new memory
accesses, which means it very l
