This is the mail archive of the
mailing list for the GCC project.
Re: Redundant check for prologue_epilogue_contains in init_alias_analysis?
- From: Zdenek Dvorak <rakdver at atrey dot karlin dot mff dot cuni dot cz>
- To: Jim Wilson <wilson at tuliptree dot org>
- Cc: gcc at gcc dot gnu dot org, rth at redhat dot com
- Date: Sun, 7 Sep 2003 11:59:36 +0200
- Subject: Re: Redundant check for prologue_epilogue_contains in init_alias_analysis?
- References: <20030906170936.GA4648@atrey.karlin.mff.cuni.cz> <3F5A90DC.firstname.lastname@example.org>
> 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
> 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?