[Openmcl-devel] Porting the OpenMCL Compiler
helink at sandia.gov
Thu Jul 7 16:11:38 UTC 2005
As far as register usage goes, and in particular the number of
immediates vs. caller-save vs. callee-save etc. registers, how much of
that could be parameterized (vs. having to be written in an
architecture-specific portion of the back end) if the compiler back end
was revised to be more cleanly separated from the compiler front end?
Just curious, since we've idly talked about separating syntax tree
manipulation from register allocation and code generation.
On Jul 6, 2005, at 4:58 AM, Gary Byers wrote:
> On Wed, 6 Jul 2005, James Bielman wrote:
>> I've been spending a fair bit of time studying the OpenMCL internals
>> and I now think I'm dangerous enough to consider a port to ARM
>> (probably Linux first, then hopefully Windows CE).
> I actually have a Zaurus (under a pile of papers on my desk, I think
> and occasionally think of the same thing.
> Any processor with a "SoftWare Interrupt if Not Equal" (SWINE)
> instruction can't be all bad ...
> (I'm thinking about doing a port to a totally bizarre register-starved
> architecture, and would think seriously about this approach.)
More information about the Openmcl-devel