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: IRA and two-phase load/store


I think this is what secondary reload is for.  Check the internals manual.

Something like this shows up in the pdp11 port, where float registers f4 and f5 can't be loaded/stored directly.  You can see in that port how this is handled; it seems to work.

	paul

On Apr 27, 2012, at 5:31 PM, Greg McGary wrote:

> I'm working on a port that does loads & stores in two phases.
> Every load/store is funneled through the intermediate registers "ld" and "st"
> standing between memory and the rest of the register file.
> 
> Example:
>        ld=4(rB)
>        ...
>        ...
>        rC=ld
> 
>        st=rD
>        8(rB)=st
> 
> rB is a base address register, rC and rD are data regs.  The ... represents
> load delay cycles.
> 
> The CPU has only a single instance of "ld", but the machine description
> defines five in order to allow overlapping live ranges to pipeline loads.
> 
> My mov insn patterns have constraints so that a memory destination pairs with
> the "st" register source, and a memory source pairs with "ld" destination
> reg.  The trouble is that register allocation doesn't understand the
> constraint, so it loads/stores from/to random data registers.
> 
> Is there a way to confine register allocation to the "ld" and "st" classes,
> or is it better to let IRA do what it wants, then fixup after reload with
> splits to turn single insn rC=MEM into the insn pair ld=MEM ... rC=ld ?
> 
> Greg


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