Re: Compiler back-ends [Q]

collberg@cs.aukuni.ac.nz (Christian Collberg) writes:


> The BEG back-end generator automatically generates a register
> allocator based on a description of the register set (register
> names, register classes, double registers, etc). You also get
> a choice between a fast/dumb and a slow/smart allocator.


So what's the slow/smart allocator based on?


Can you "automatically" handle ABI's where float args must be passed
in int registers, and there's no float<->int move instructions
(must go through memory)? Automatically here means you don't write
code that sez "if this is a call with float args, then st/ld them
through a magic address", but instead sez something like "I got a
value in register class F, but I need it in register class I, and
there's no F->I move, so spill it & load it & now it's in memory
should I need to spill it later".


Cliff
--
Cliff Click Compiler Researcher & Designer
RISC Software, Motorola PowerPC Compilers
cliffc@risc.sps.mot.com (512) 891-7240


--

Return to the comp.compilers page.
Search the comp.compilers archives again.