From mboxrd@z Thu Jan  1 00:00:00 1970
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
Date: Fri, 25 Mar 2016 07:43:09 +0100
Subject: [U-Boot] [PATCH 5/5] lib: Enable private libgcc by default
In-Reply-To: <20160325073725.0a7d3b03@lilith>
References: <1458490534-5537-1-git-send-email-marex@denx.de>
 <1458490534-5537-5-git-send-email-marex@denx.de>
 <20160323135335.5fbe01ae@lilith>
 <20160323132238.GA23166@bill-the-cat>
 <20160323180845.4bbc1035@lilith>
 <20160323213617.GE23166@bill-the-cat>
 <20160324085003.61b54390@lilith>
 <20160325004942.GX23166@bill-the-cat>
 <20160325073725.0a7d3b03@lilith>
Message-ID: <20160325074309.06bcb2a9@lilith>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On Fri, 25 Mar 2016 07:37:25 +0100, Albert ARIBAUD
<albert.u.boot@aribaud.net> wrote:
> Hello Tom,

> That way,
> 
> 0) U-Boot gets the stable and controlled AEABI support you want;
> 
> 1) GCC keeps its somewhat stable but uncontrolled internal "generated
>    code / libgcc" interface;
> 
> 2) U-Boot won't interfere with non-aeabi-related stuff in GCC+libgcc,
>    i.e. whatever ibgcc-related but non-AEABI-related changes occur in
>    a GCC release, we won't break them changes in non-AEABI ;
> 
> 3) GCC+libgcc won't interfere with AEABI any more, i.e. whatever AEABI
>    breakages happen in a given GCC toolchain will not break U-Boot.
> 
> 4) This design works with any ARM toolchain -- which is kind of evident
>    since it separates generic ARM EABI support from specific toolchain
>    support.

Addition: this does not mean we should get rid of the private libgcc
support: it can be useful in case of an issue with the non-aeabi part
of libgcc.

Amicalement,
-- 
Albert.