This is the mail archive of the gcc-patches@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: Various gp-related mips optimisations


> > 
> > Definitely don't like this block, but I think that we need it since we
> > can't accurately (or at all afaict) determine ahead of time whether or
> > not we're going to be deleting all of the constant pool references.
> > Anyone else see a way around this?
> 
> Do we need a way around it?  I think the block is correct in terms of
> what it's doing.  (i.e. I don't see it as a hack.)

The idea is that you don't delete any instruction that you decide to
emit in the prologue/epilogue (the famous flow abort) and that the reg
notes are kindof a hack around that. That said, I don't think there's
any sane way around this which is why I asked if anyone else had a way
around it :)

-eric

-- 
Eric Christopher <echristo@redhat.com>


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