From mint-bounce@lists.fishpool.fi  Mon Jun 21 05:17:33 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=6LpVGP6otuzla0TH0KlPoBn8NocYuOhWqVZkFs4FQNs=;
        b=J3vy34wLkbHM+nA02peqMz0FkjSI3qktGbdBxiLoDF2I5HVL35BsbNVpcIPMtxPNJi
         BHk1nhbEX4gBl4TSrPUovaf1F00jPxYRaVAcqkmPQxKi0qhq/Gu/FZzX68g5DFt2FwDc
         iCRKArhvdtZjcxb8uAhmGyMd/ab0PzrznxO6A=
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=WxjZUoxgsyATExbTEnVl/ASgKehDmtNpjnw9mrS+t8gtjhKuebn6lk850/F/vulQZV
         w50/YLtZJBz86jXoHa9G3+pV0DbhbONrnIqRZTEPeDCCpf+cxuxZMSQ1VDljuf9FEp3Q
         fo/P0L88fWQYciQRmvoq0NQhY2Sj/9zeHd73I=
Message-ID: <4C1F2DB9.6050701@freesbee.fr>
Date: Mon, 21 Jun 2010 11:15:37 +0200
From: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= <vincent.riviere@freesbee.fr>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: mint@lists.fishpool.fi
Subject: Re: [MiNT] Still don't get it - difference between 68020 and 68020-60
References: <729ec3d897ff67cb50ea2269d3c5d33c-EhVcX1lFRQVaRwYcDTpQCEFddQZLVF5dQUBFBDBTXF5bVkYJXldoA1VcMl5dRkMKX1hZQFA=-webmailer2@server05.webmailer.hosteurope.de>	<AANLkTilYGU_w-mINXvhpuz4CFcgrFHaueGtLLdBosLmB@mail.gmail.com>	<Pine.GSO.4.63.1006181724120.2220@saltmine.radix.net>	<20100619122903.672ba2e2.mandin.patrice@orange.fr>	<4C1CAEC6.8070907@freesbee.fr>	<1277027272.10907.455.camel@jetpack.demon.co.uk>	<Pine.GSO.4.63.1006201452500.5137@saltmine.radix.net>	<1277070265.10907.478.camel@jetpack.demon.co.uk>	<AANLkTinvv7OnfSKg01n1sgIqhVFKY9JY9Ksh4nDuIOs-@mail.gmail.com>	<1277109553.10907.480.camel@jetpack.demon.co.uk> <AANLkTikkAdNNZ1yiTOO1DJXrq4gk7pRfE0JQ4vqAErLd@mail.gmail.com>
In-Reply-To: <AANLkTikkAdNNZ1yiTOO1DJXrq4gk7pRfE0JQ4vqAErLd@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 wrote:
>> And we need -mshort for all targets because the kernel requires -mshort.
> Does it? I thought kernel needs libgcc only in 68000 version because
> of long mul/div emulation.

I think you are right here, by chance.
The most used stuff in libgcc is mul/div emulation. Since the kernel 
does not use floats, libgcc is probably not linked (to be verified with 
-Wl,-t). But if some other libgcc function was used, it would be linked 
with the wrong libgcc.
There is also the __main() function in libgcc, used to call the C++ 
constructors of global variables and nonstandard C code using that 
feature. This function is automatically called from main(), I don't know 
if FreeMiNT has a main() function (EmuTOS has not).

So in any case, libgcc must be provided for every multilib supported by 
the compiler, including mshort, or we are going to face big troubles 
some day.

-- 
Vincent Rivière