[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Cross-compiling Guile 2.0
From: |
Andy Wingo |
Subject: |
Re: Cross-compiling Guile 2.0 |
Date: |
Mon, 21 Mar 2011 21:42:31 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) |
On Mon 21 Mar 2011 20:58, address@hidden (Ludovic Courtès) writes:
> At some point there will have to be a triplet → arch → endianness
> conversion.
Indeed.
> I’d rather have that conversion occur as close to the UI as
> possible—i.e., close to ‘scripts/compile.scm’—rather than deep down in
> (system base compile) because the triplet string is really a UI notion IMO.
Actually I think it's more fundamental than that. The compilation
process tries, generically, to find a path through the language tower
path from the source language to the target language. There is nothing
bytecode-specific in (scripts compile), except for a couple default
target languages.
It seems to me that the value of the target-type fluid at the time that
`compile-passes' is called should be what determines the compilation
path and target-specific settings. For example, to continue the ARM
compilation example, perhaps it would cause a different target language
to be selected.
Dunno. All of that could just be too complicated, and maybe you are
right.
Andy
--
http://wingolog.org/
- Re: Cross-compiling Guile 2.0, (continued)
- Re: Cross-compiling Guile 2.0, Ludovic Courtès, 2011/03/06
- Re: Cross-compiling Guile 2.0, Andy Wingo, 2011/03/17
- Re: Cross-compiling Guile 2.0, Ludovic Courtès, 2011/03/18
- Re: Cross-compiling Guile 2.0, Andy Wingo, 2011/03/19
- Re: Cross-compiling Guile 2.0, Ludovic Courtès, 2011/03/20
- Re: Cross-compiling Guile 2.0, Andy Wingo, 2011/03/20
- Re: Cross-compiling Guile 2.0, Ludovic Courtès, 2011/03/20
- Re: Cross-compiling Guile 2.0, Andy Wingo, 2011/03/20
- Re: Cross-compiling Guile 2.0, Ludovic Courtès, 2011/03/21
- Re: Cross-compiling Guile 2.0,
Andy Wingo <=
Re: Cross-compiling Guile 2.0, Jan Nieuwenhuizen, 2011/03/16