http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50063
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P2 |P4
--- Comment #14 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-12-19
19:12:56 UTC ---
Well, it is certainly desirable not to process the prologue insns during
init_alias_analysis. The fact that stack pointer has the same value as frame
pointer after the prologue is not usual and something the generic code isn't
prepared for (usually either frame pointer is eliminated (of course then the
register can be used for something else) or frame pointer is initialized from
stack pointer and then decremented (or incremented) still inside of the
prologue).
So you need to tell the alias analysis about that, as the prologue isn't
scanned, it is the backend responsibility to tell that.
