Piers Cawley wrote:
Targeting Parrot from GCC Discussion in the thread entitled 'WxWindows Support / Interfacing Libraries' centred on writing a Parrot backend to GCC. (No, I have no idea what that has to do with the thread subject.) Tupshin Harper, Leo Tötsch and Benjamin Goldberg discussed possibilities and potential pit/pratfalls. At one point, Tupshin suggested emulating a 'more traditional stack-oriented processor' and I don't think he was joking...
Indeed, I wasn't, but I wish somebody would at least have the decency to tell me how insane this is. ;-)
Oh, sorry.
You're insane. :)
Traditional processors aren't stack-oriented, not even ones that are more register-starved than the x86 family. (I'm thinking of the 6502 with it's 1.75 registers here)
The base architecture's fixed, and I'm not inclined to change it at
this point. GCC could handle it if someone wanted to work it out--it
can already deal with multiple register classes, since most machines
these days have at least two (general purpose and float) and the ones
with vector processors arguably have three types. It'd probably have
to do less work for parrot than for other systems, as we have more
registers, and register starvation's one of the more annoying things
a compiler has to deal with.
--
Dan--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
