[m-dev.] 32-bit sources on 64-bit target

Julien Fischer jfischer at opturion.com
Thu Mar 7 15:17:26 AEDT 2013

On Thu, Mar 7, 2013 at 3:06 PM, Peter Wang <novalazy at gmail.com> wrote:
> On Thu, 7 Mar 2013 12:17:20 +1100, Peter Wang <novalazy at gmail.com> wrote:
>> So there will be problems whenever a data structure with those
>> characteristics crosses the standard library/user program boundary.
>> I think I can fix the first by allocating two words to a `float'
>> constructor argument whenever --no-unboxed-float is used, even when it
>> is unnecessary on 64-bit.
>> The second, I'm guessing, does not actually occur in the standard
>> library.  A solution would be to restrict enum packing to using at
>> most 32 bits of a word, with an option like --max-arg-packing-bits=32.
> Actually, why don't we "just" make the srcdist build and install the
> proper stage 2 compiler/library, since everyone is recommended to do
> that anyway.  The stage1 compiler from the pregenerated C sources should
> be fine as its compiler and library parts should agree.

Doesn't stage 2 take it's configuration settings from stage 1 though?  (IIRC,
at for at least some of those settings depend on whether we have pre-generated
C files or not.)


More information about the developers mailing list