This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Redundant check for prologue_epilogue_contains in init_alias_analysis?


Hello,

> Zdenek Dvorak wrote:
> >the following check in init_alias_analysis seems partially redundant,
> >partially wrong to me:
> 
> In many cases like this, the best answer is to look at the historical 
> info.  We have 6 years of CVS and mailing list logs.  It isn't hard to 
> find that the patch came from here
> 	http://gcc.gnu.org/ml/gcc-patches/1999-08n/msg00048.html
> and this message also explains why the patch is there.
> 
> For those that don't click through, the answer is that the FP won't be 
> considered a constant base pointer if we process prologue/epilogue 
> insns.  There are other ways to handle this problem without ignoring all 
> prologue/epilogue instructions.

would then just forcing fp to be considered a constant base pointer
unconditionally be a solution?

Zdenek


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]