Re: patching gcc to allow other calling conventions

[Stefan Israelsson Tampe]

I can code an independent assembler later I do now most of the complexites now and a lot of the code can be removed.

But the used sbcl derivative although not gnu is either in the public domain or bsd so we should be able to publish what we are doing. I prefere now to start working on a simple jit scheme for the fun of it, because it is a good learning experience and that getting results are a good driver to continueu.

/stefan

Den 18 jun 2012 02:43 skrev "Noah Lavine" <address@hidden>:

Hello,

> Did you consider starting from GNU/MIT Scheme?  It supports only IA32
> and x86_64, I think, but it’s in Scheme, and it’s GNU.

Actually, that's an interesting thought in general. I looked at MIT
scheme a bit a long time ago, but I believe it uses two intermediate
languages, a high-level one similar to Tree-IL and a low-level one
that I don't know much about. We might be able to turn Tree-IL into
the high-level one and use their compiler infrastructure. Since
they're a GNU project, there might not be copyright issues.

However, I'm not sure if this has advantages over just building it
ourselves. And I don't know if the MIT Scheme developers would like
this or not.

Noah