This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Redundant check for prologue_epilogue_contains ininit_alias_analysis?
On Sun, 2003-09-07 at 02:59, Zdenek Dvorak wrote:
> would then just forcing fp to be considered a constant base pointer
> unconditionally be a solution?
That could work if there is no target that ever modifies FP during the
function, and if we can safely distinguish between real uses of the FP,
and cases where the FP was used by the register allocator. This seems
likely to be true.
Another possible solution is to disregard instructions that modify FP if
they are prologue/epilogue instructions. This seems safer, but is a bit
more code.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com