From mint-bounce@lists.fishpool.fi  Fri Jan 15 11:08:41 2010
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:sender:message-id:date:from
         :user-agent:mime-version:to:subject:references:in-reply-to
         :content-type:content-transfer-encoding;
        bh=25XV5ApYvCbBRTf3PCNTyFXk4DSsS91Yitxvh3IkqpY=;
        b=WZKoe+gnuHKKgqxJCPyij83mVnRODdjQKbml68MQ60tOWZhssyvG7UD6SDiZgXiUpk
         XgE8f4KOFwgvhle+3Z/K9w4pWTmtnOaq06dBWk+zMjXD9KlC4oQgGktc6uLyzEjsEsCJ
         uRbW+SA0V4JoYm6kKvRjvRkqLf05ForZqbmiU=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=sender:message-id:date:from:user-agent:mime-version:to:subject
         :references:in-reply-to:content-type:content-transfer-encoding;
        b=xuSg6HOs9ixa8zedMJbNOuPkx3YG7ZJcZoKcLKgsSw9Yk9/KKdapujQGfk9YNICtWz
         lS9m2/IFjGpfNNVWD2ohQGLzPiMn96ECKQBJ7sy33le0Msb4Pz2+wT/q+z0lddpc9Fu5
         B+bGuzps5nEoBarIM/g3eaCfjcWsjy15AJRkw=
Message-ID: <4B509237.3060000@freesbee.fr>
Date: Fri, 15 Jan 2010 17:05:11 +0100
From: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= <vincent.riviere@freesbee.fr>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: MiNT Mailing List <mint@lists.fishpool.fi>
Subject: Re: [MiNT] gcc 68000 vs 68020-60 vs 68060 comparison
References: <c6533ef61001150424na19f697u2036f9a5942109ad@mail.gmail.com>	 <4B508C6E.9040507@freesbee.fr> <c6533ef61001150752u15990a13o605cb52268659dd@mail.gmail.com>
In-Reply-To: <c6533ef61001150752u15990a13o605cb52268659dd@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-to: mint-bounce@lists.fishpool.fi
X-original-sender: vincent.riviere@freesbee.fr
Precedence: bulk
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
List-Id: <mint.lists.fishpool.fi>
X-List-ID: <mint.lists.fishpool.fi>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>

Miro Kropacek a écrit :
> But we are talking about native builds then, right? And since your step 
> by step tutorial and my Makefile are for cross compiler only... it 
> shouldn't be needed. Maybe for some stuff while building cross compiler? 
> What would be really strange, native build using cross compiler needs no 
> libm but cross compiler building on i686 does ;-) 

This look strange... did you recompile the C++ compiler ?
I think the problem was only with the C++ libraries.
I will try to remember (with my full email history).

> That's interesting. What is needed for 32-bit compiler with 32-bit 
> aligns but respecting original TOS structures? Some changes to 
> mint/osbind.h and friends?

There are several things to do to enable 32-bit aligment:
- The C compler must be configured to keep the stack and the structure 
members aligned (in the internal GCC config file. Easy.).
- The OS Malloc() must return an aligned pointer (seems good already).
- The C malloc() must return an aligned pointer.
- The current binutils are ready to respect alignment on global variables.

Then the public OS structures must be protected with the right pragma 
pack alignments. I made some tests recently, and unfortunately I didn't 
manage to get what I wanted... but we should make tests with a compiler 
already configured for 32-bit alignment.

-- 
Vincent Rivière