[LLVMdev] 64 bit special purpose registers
michael.hliao at gmail.com
Thu Sep 6 21:05:57 PDT 2012
On Thursday, September 6, 2012, Akira Hatanaka wrote:
> If no i64 reg classes are registered, then type-legalization will expand a
> 32b x 32b = 64b multiply node into a 32-bit mult node with two i32 results
> (for example, SMUL_LOHI). The problem is that there isn't an easy way to
> have RA assign two consecutive hi/lo registers to the two i32 registers,
> once the 64-bit result is split into two 32-bit results.
> Is there a constraint I can use (something like register hints) to force
> RA to allocate consecutive registers?
No. RA has no such constraints. I once hacked similar issue (i.e. some data
type has very limited support or special usage at processor level) by
registering register class after computeRegisterProperties(). This way you
won't tell SelectionDAG i64 is a legal type but only an available type at
machine level. Ofc, you need very special code emitter to emit SMUL_LOHI
into your MUL followed by subreg extractions. Anyway,it once worked for me
but may not be a desired approach.
> On Thu, Sep 6, 2012 at 5:06 AM, Ivan Llopard <ivanllopard at gmail.com>wrote:
> Hi Akira, Micah,
> On 05/09/2012 21:44, Akira Hatanaka wrote:
> Do you mean we should make GPR64 available to register allocator by
> calling addRegisterClass?
> addRegisterClass(MVT::i64, &GPR64RegClass)
> I have a related question to this thread. Does the RA use target lowering
> Because if it doesn't, you don't need to register your i64 reg class.
> If we add register class GPR64, type legalization will stop expanding i64
> operations because i64 is now a legal type.
> Then we will probably have to write lots of code to custom-lower
> unsupported 64-bit operations during legalization. Note that mips32/16
> lacks support for most of the basic 64-bit instructions (add, sub, etc.).
> I don't think setting operation action by calling setOperationAction(...
> ,MVT::i64, Expand) would work either. Judging from the code I see in
> Legalize.cpp, operation legalization doesn't seem to do much to expand
> unsupported i64 operations.
> On Tue, Aug 7, 2012 at 9:24 AM, Villmow, Micah <Micah.Villmow at amd.com>wrote:
> This can be done by declaring a register class with these registers and
> only using that register class as an operand in the instructions where it
> is legal.
> You then set as sub registers what you want to represent as the hi and lo
> registers for those 64bit registers.
> So something like this:
> def lo_comp : SubRegIndex;
> def hi_comp : SubRegIndex;
> def R1 : Register<1>;
> def R2 : Register<2>;
> def R3 : Register<1>;
> def R4 : Register<2>;
> def D1 : RegisterWithSubRegs<1, [R1, R2], [lo_comp, hi_comp]>;
> This says that D1 is a register with two components, lo and hi. When you
> allocate D1, you also use R1/R2.
> def GPR32 : RegisterClass<..., [i32], , (add (sequence "R%u", 1, 4))>
> def GPR64 : RegisterClass<..., [i64], , (add D1)> ...;
> So in your instruction it would be something like:
> def mul : Inst<(dst GPR64:$dst), (src GPR32:$src0, GPR32:$src1), ...>;
> This would mean you take in two inputs and you have 64bit output. When D1
> is not being used, R1/R2 will get allocated to instructions that use GPR32
> register class, otherwise they will be seen as used and not get allocated.
> Hope this helps,
> > -----Original Message-----
> > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu]
> > On Behalf Of reed kotler
> > Sent: Monday, August 06, 2012 4:52 PM
> > To: llvmdev at cs.uiuc.edu
> > Subject: [LLVMdev] 64 bit special purpose registers
> > On Mips 32 there is traditionally a 64 bit HI/LO register for the result
> > of multiplying two 64 bit numbers.
> > There are corresponding instructions to load the LO and HI parts into
> > individual 32 registers.
> > On Mips with the DSP ASE (an application specific extension), there are
> > actual 4 such pairs of registers.
> > Is there a way to have special purpose 64 bit registers without actually
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev