[Buildroot] how to tune powerpc e500v2 cpus in BR

[Buildroot] how to tune powerpc e500v2 cpus in BR

[raymond zhao]

Hi,
I am using freescale's p1020 CPU. It is a e500v2 core. How could I
config the build root to tune the tool chain for the following
options:

-mcpu=8548 -mspe=yes -mabi=spe -mhard-float -mfloat-gprs=double

From the menuconfig, I can only select CPU as 8540.

Thanks,

Raymond

[Buildroot] how to tune powerpc e500v2 cpus in BR

[Matias Garcia]

Hi Raymond,

You can put those in the BR2_TARGET_OPTIMIZATIONS setting under the 
Toolchain page e.g.

(-mcpu=8548 -mspe=yes -mabi=spe -mhard-float -mfloat-gprs=double)  
Target Optimizations

I selected a generic powerpc target because I didn't need the -mtune 
when I was specifying -mcpu already. As far as I know, 8548 and 8540 
work out to the same code.

I switched to the external CodeSourcery build tools for two reasons: (1) 
it allowed us to compile our application with -O3 (which we need) while 
the standard GNU toolchain caused some errors, and (2) they're supported 
by the Freescale/Mentor/CodeSourcery relationship, and not all of the 
patches get applied to mainline (particularly for newer processors). I 
had to add an option to the external wrapper so that it would call the 
toolchain with '-te500v2' which is a shortcut for the optimizations you 
list below. In that case, you can build your own applications without 
calling any options explicitly.

Cheers,
Matias

On 11-06-24 10:27 AM, raymond zhao wrote:
> Hi,
> I am using freescale's p1020 CPU. It is a e500v2 core. How could I
> config the build root to tune the tool chain for the following
> options:
>
> -mcpu=8548 -mspe=yes -mabi=spe -mhard-float -mfloat-gprs=double
>
>  From the menuconfig, I can only select CPU as 8540.
>
> Thanks,
>
> Raymond
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

[Buildroot] how to tune powerpc e500v2 cpus in BR

[raymond zhao]

Thanks, Matias
After looked into the scripts. I believe you are right. But somehow I have
problem with building target gdb server when I put this flags there. I am
keep digging now.

thanks

raymond
On Fri, Jun 24, 2011 at 1:31 PM, Matias Garcia <mgarcia@rossvideo.com>wrote:

> Hi Raymond,
>
> You can put those in the BR2_TARGET_OPTIMIZATIONS setting under the
> Toolchain page e.g.
>
> (-mcpu=8548 -mspe=yes -mabi=spe -mhard-float -mfloat-gprs=double)  Target
> Optimizations
>
> I selected a generic powerpc target because I didn't need the -mtune when I
> was specifying -mcpu already. As far as I know, 8548 and 8540 work out to
> the same code.
>
> I switched to the external CodeSourcery build tools for two reasons: (1) it
> allowed us to compile our application with -O3 (which we need) while the
> standard GNU toolchain caused some errors, and (2) they're supported by the
> Freescale/Mentor/CodeSourcery relationship, and not all of the patches get
> applied to mainline (particularly for newer processors). I had to add an
> option to the external wrapper so that it would call the toolchain with
> '-te500v2' which is a shortcut for the optimizations you list below. In that
> case, you can build your own applications without calling any options
> explicitly.
>
> Cheers,
> Matias
>
>
> On 11-06-24 10:27 AM, raymond zhao wrote:
>
>> Hi,
>> I am using freescale's p1020 CPU. It is a e500v2 core. How could I
>> config the build root to tune the tool chain for the following
>> options:
>>
>> -mcpu=8548 -mspe=yes -mabi=spe -mhard-float -mfloat-gprs=double
>>
>>  From the menuconfig, I can only select CPU as 8540.
>>
>> Thanks,
>>
>> Raymond
>> ______________________________**_________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/**mailman/listinfo/buildroot<http://lists.busybox.net/mailman/listinfo/buildroot>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110624/9bd90154/attachment.html>

[Buildroot] how to tune powerpc e500v2 cpus in BR

[raymond zhao]

The error caused by the option "-mabi=spe"
The cross compiler report: cc1: error: not configured for ABI: 'spe'.
So, there must be some option need to be past when we compile the GCC.
Anyone has any idea?

thanks,

Raymond

On Fri, Jun 24, 2011 at 5:14 PM, raymond zhao <raymond.zhao.ml@gmail.com> wrote:
>
> Thanks, Matias
> After looked into the scripts. I believe you are right. But somehow I have
> problem with building target gdb server when I put this flags there. I am
> keep digging now.
>
> thanks
>
> raymond
> On Fri, Jun 24, 2011 at 1:31 PM, Matias Garcia <mgarcia@rossvideo.com>
> wrote:
>>
>> Hi Raymond,
>>
>> You can put those in the BR2_TARGET_OPTIMIZATIONS setting under the
>> Toolchain page e.g.
>>
>> (-mcpu=8548 -mspe=yes -mabi=spe -mhard-float -mfloat-gprs=double) ?Target
>> Optimizations
>>
>> I selected a generic powerpc target because I didn't need the -mtune when
>> I was specifying -mcpu already. As far as I know, 8548 and 8540 work out to
>> the same code.
>>
>> I switched to the external CodeSourcery build tools for two reasons: (1)
>> it allowed us to compile our application with -O3 (which we need) while the
>> standard GNU toolchain caused some errors, and (2) they're supported by the
>> Freescale/Mentor/CodeSourcery relationship, and not all of the patches get
>> applied to mainline (particularly for newer processors). I had to add an
>> option to the external wrapper so that it would call the toolchain with
>> '-te500v2' which is a shortcut for the optimizations you list below. In that
>> case, you can build your own applications without calling any options
>> explicitly.
>>
>> Cheers,
>> Matias
>>
>> On 11-06-24 10:27 AM, raymond zhao wrote:
>>>
>>> Hi,
>>> I am using freescale's p1020 CPU. It is a e500v2 core. How could I
>>> config the build root to tune the tool chain for the following
>>> options:
>>>
>>> -mcpu=8548 -mspe=yes -mabi=spe -mhard-float -mfloat-gprs=double
>>>
>>> ?From the menuconfig, I can only select CPU as 8540.
>>>
>>> Thanks,
>>>
>>> Raymond
>>> _______________________________________________
>>> buildroot mailing list
>>> buildroot at busybox.net
>>> http://lists.busybox.net/mailman/listinfo/buildroot
>
>

[Buildroot] how to tune powerpc e500v2 cpus in BR

[Bryan Hundven]

On Fri, Jun 24, 2011 at 2:41 PM, raymond zhao <raymond.zhao.ml@gmail.com> wrote:
> The error caused by the option "-mabi=spe"
> The cross compiler report: cc1: error: not configured for ABI: 'spe'.
> So, there must be some option need to be past when we compile the GCC.
> Anyone has any idea?

What version of gcc are you using?

> thanks,
>
> Raymond
>
> On Fri, Jun 24, 2011 at 5:14 PM, raymond zhao <raymond.zhao.ml@gmail.com> wrote:
>>
>> Thanks, Matias
>> After looked into the scripts. I believe you are right. But somehow I have
>> problem with building target gdb server when I put this flags there. I am
>> keep digging now.
>>
>> thanks
>>
>> raymond
>> On Fri, Jun 24, 2011 at 1:31 PM, Matias Garcia <mgarcia@rossvideo.com>
>> wrote:
>>>
>>> Hi Raymond,
>>>
>>> You can put those in the BR2_TARGET_OPTIMIZATIONS setting under the
>>> Toolchain page e.g.
>>>
>>> (-mcpu=8548 -mspe=yes -mabi=spe -mhard-float -mfloat-gprs=double) ?Target
>>> Optimizations
>>>
>>> I selected a generic powerpc target because I didn't need the -mtune when
>>> I was specifying -mcpu already. As far as I know, 8548 and 8540 work out to
>>> the same code.
>>>
>>> I switched to the external CodeSourcery build tools for two reasons: (1)
>>> it allowed us to compile our application with -O3 (which we need) while the
>>> standard GNU toolchain caused some errors, and (2) they're supported by the
>>> Freescale/Mentor/CodeSourcery relationship, and not all of the patches get
>>> applied to mainline (particularly for newer processors). I had to add an
>>> option to the external wrapper so that it would call the toolchain with
>>> '-te500v2' which is a shortcut for the optimizations you list below. In that
>>> case, you can build your own applications without calling any options
>>> explicitly.
>>>
>>> Cheers,
>>> Matias
>>>
>>> On 11-06-24 10:27 AM, raymond zhao wrote:
>>>>
>>>> Hi,
>>>> I am using freescale's p1020 CPU. It is a e500v2 core. How could I
>>>> config the build root to tune the tool chain for the following
>>>> options:
>>>>
>>>> -mcpu=8548 -mspe=yes -mabi=spe -mhard-float -mfloat-gprs=double
>>>>
>>>> ?From the menuconfig, I can only select CPU as 8540.
>>>>
>>>> Thanks,
>>>>
>>>> Raymond
>>>> _______________________________________________
>>>> buildroot mailing list
>>>> buildroot at busybox.net
>>>> http://lists.busybox.net/mailman/listinfo/buildroot
>>
>>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>

[Buildroot] how to tune powerpc e500v2 cpus in BR

[raymond zhao]

buildroot: gcc 4.6.x,
in .config:
CT_CC="gcc"
CT_CC_VERSION="4.6.0"
CT_CC_gcc=y
CT_CC_GCC_SHOW_LINARO=y
# CT_CC_V_linaro_4_6_2011_04_0 is not set

My development machine is ubuntu 10.04, with gcc 4.4.3

thanks
raymond

On Fri, Jun 24, 2011 at 5:44 PM, Bryan Hundven <bryanhundven@gmail.com> wrote:
> On Fri, Jun 24, 2011 at 2:41 PM, raymond zhao <raymond.zhao.ml@gmail.com> wrote:
>> The error caused by the option "-mabi=spe"
>> The cross compiler report: cc1: error: not configured for ABI: 'spe'.
>> So, there must be some option need to be past when we compile the GCC.
>> Anyone has any idea?
>
> What version of gcc are you using?
>
>> thanks,
>>
>> Raymond
>>
>> On Fri, Jun 24, 2011 at 5:14 PM, raymond zhao <raymond.zhao.ml@gmail.com> wrote:
>>>
>>> Thanks, Matias
>>> After looked into the scripts. I believe you are right. But somehow I have
>>> problem with building target gdb server when I put this flags there. I am
>>> keep digging now.
>>>
>>> thanks
>>>
>>> raymond
>>> On Fri, Jun 24, 2011 at 1:31 PM, Matias Garcia <mgarcia@rossvideo.com>
>>> wrote:
>>>>
>>>> Hi Raymond,
>>>>
>>>> You can put those in the BR2_TARGET_OPTIMIZATIONS setting under the
>>>> Toolchain page e.g.
>>>>
>>>> (-mcpu=8548 -mspe=yes -mabi=spe -mhard-float -mfloat-gprs=double) ?Target
>>>> Optimizations
>>>>
>>>> I selected a generic powerpc target because I didn't need the -mtune when
>>>> I was specifying -mcpu already. As far as I know, 8548 and 8540 work out to
>>>> the same code.
>>>>
>>>> I switched to the external CodeSourcery build tools for two reasons: (1)
>>>> it allowed us to compile our application with -O3 (which we need) while the
>>>> standard GNU toolchain caused some errors, and (2) they're supported by the
>>>> Freescale/Mentor/CodeSourcery relationship, and not all of the patches get
>>>> applied to mainline (particularly for newer processors). I had to add an
>>>> option to the external wrapper so that it would call the toolchain with
>>>> '-te500v2' which is a shortcut for the optimizations you list below. In that
>>>> case, you can build your own applications without calling any options
>>>> explicitly.
>>>>
>>>> Cheers,
>>>> Matias
>>>>
>>>> On 11-06-24 10:27 AM, raymond zhao wrote:
>>>>>
>>>>> Hi,
>>>>> I am using freescale's p1020 CPU. It is a e500v2 core. How could I
>>>>> config the build root to tune the tool chain for the following
>>>>> options:
>>>>>
>>>>> -mcpu=8548 -mspe=yes -mabi=spe -mhard-float -mfloat-gprs=double
>>>>>
>>>>> ?From the menuconfig, I can only select CPU as 8540.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Raymond
>>>>> _______________________________________________
>>>>> buildroot mailing list
>>>>> buildroot at busybox.net
>>>>> http://lists.busybox.net/mailman/listinfo/buildroot
>>>
>>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
>>
>

[Buildroot] how to tune powerpc e500v2 cpus in BR

[Bryan Hundven]

On Fri, Jun 24, 2011 at 3:04 PM, raymond zhao <raymond.zhao.ml@gmail.com> wrote:
> buildroot: gcc 4.6.x,
> in .config:
> CT_CC="gcc"
> CT_CC_VERSION="4.6.0"
> CT_CC_gcc=y
> CT_CC_GCC_SHOW_LINARO=y
> # CT_CC_V_linaro_4_6_2011_04_0 is not set
>
> My development machine is ubuntu 10.04, with gcc 4.4.3
>
> thanks
> raymond

It would be helpful if you could post your config and build log
somewhere, but please don't email it to the mailing list.

Also, could you avoid top posting in your emails?

> On Fri, Jun 24, 2011 at 5:44 PM, Bryan Hundven <bryanhundven@gmail.com> wrote:
>> On Fri, Jun 24, 2011 at 2:41 PM, raymond zhao <raymond.zhao.ml@gmail.com> wrote:
>>> The error caused by the option "-mabi=spe"
>>> The cross compiler report: cc1: error: not configured for ABI: 'spe'.
>>> So, there must be some option need to be past when we compile the GCC.
>>> Anyone has any idea?
>>
>> What version of gcc are you using?
>>
>>> thanks,
>>>
>>> Raymond
>>>
>>> On Fri, Jun 24, 2011 at 5:14 PM, raymond zhao <raymond.zhao.ml@gmail.com> wrote:
>>>>
>>>> Thanks, Matias
>>>> After looked into the scripts. I believe you are right. But somehow I have
>>>> problem with building target gdb server when I put this flags there. I am
>>>> keep digging now.
>>>>
>>>> thanks
>>>>
>>>> raymond
>>>> On Fri, Jun 24, 2011 at 1:31 PM, Matias Garcia <mgarcia@rossvideo.com>
>>>> wrote:
>>>>>
>>>>> Hi Raymond,
>>>>>
>>>>> You can put those in the BR2_TARGET_OPTIMIZATIONS setting under the
>>>>> Toolchain page e.g.
>>>>>
>>>>> (-mcpu=8548 -mspe=yes -mabi=spe -mhard-float -mfloat-gprs=double) ?Target
>>>>> Optimizations
>>>>>
>>>>> I selected a generic powerpc target because I didn't need the -mtune when
>>>>> I was specifying -mcpu already. As far as I know, 8548 and 8540 work out to
>>>>> the same code.
>>>>>
>>>>> I switched to the external CodeSourcery build tools for two reasons: (1)
>>>>> it allowed us to compile our application with -O3 (which we need) while the
>>>>> standard GNU toolchain caused some errors, and (2) they're supported by the
>>>>> Freescale/Mentor/CodeSourcery relationship, and not all of the patches get
>>>>> applied to mainline (particularly for newer processors). I had to add an
>>>>> option to the external wrapper so that it would call the toolchain with
>>>>> '-te500v2' which is a shortcut for the optimizations you list below. In that
>>>>> case, you can build your own applications without calling any options
>>>>> explicitly.
>>>>>
>>>>> Cheers,
>>>>> Matias
>>>>>
>>>>> On 11-06-24 10:27 AM, raymond zhao wrote:
>>>>>>
>>>>>> Hi,
>>>>>> I am using freescale's p1020 CPU. It is a e500v2 core. How could I
>>>>>> config the build root to tune the tool chain for the following
>>>>>> options:
>>>>>>
>>>>>> -mcpu=8548 -mspe=yes -mabi=spe -mhard-float -mfloat-gprs=double
>>>>>>
>>>>>> ?From the menuconfig, I can only select CPU as 8540.
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Raymond
>>>>>> _______________________________________________
>>>>>> buildroot mailing list
>>>>>> buildroot at busybox.net
>>>>>> http://lists.busybox.net/mailman/listinfo/buildroot
>>>>
>>>>
>>> _______________________________________________
>>> buildroot mailing list
>>> buildroot at busybox.net
>>> http://lists.busybox.net/mailman/listinfo/buildroot
>>>
>>
>

Thanks,

-Bryan

[Buildroot] how to tune powerpc e500v2 cpus in BR

[Baruch Siach]

Hi Raymond, Matias,

On Fri, Jun 24, 2011 at 01:31:26PM -0400, Matias Garcia wrote:
> You can put those in the BR2_TARGET_OPTIMIZATIONS setting under the
> Toolchain page e.g.
> 
> (-mcpu=8548 -mspe=yes -mabi=spe -mhard-float -mfloat-gprs=double)
> Target Optimizations
> 
> I selected a generic powerpc target because I didn't need the -mtune
> when I was specifying -mcpu already. As far as I know, 8548 and 8540
> work out to the same code.
> 
> I switched to the external CodeSourcery build tools for two reasons:
> (1) it allowed us to compile our application with -O3 (which we
> need) while the standard GNU toolchain caused some errors, and (2)
> they're supported by the Freescale/Mentor/CodeSourcery relationship,
> and not all of the patches get applied to mainline (particularly for
> newer processors). I had to add an option to the external wrapper so
> that it would call the toolchain with '-te500v2' which is a shortcut
> for the optimizations you list below. In that case, you can build
> your own applications without calling any options explicitly.

I'm also using the CodeSourcery toolchain for the e500v2 target (P1011), and I 
figured out that I must pass -te500v2 to gcc at link time as well. Since there 
is no generic way to add LDFLAGS options in Buildroot, I've posted the patch 
at http://lists.busybox.net/pipermail/buildroot/2011-June/043668.html. Did you 
find a better solution?

baruch

> On 11-06-24 10:27 AM, raymond zhao wrote:
> >Hi,
> >I am using freescale's p1020 CPU. It is a e500v2 core. How could I
> >config the build root to tune the tool chain for the following
> >options:
> >
> >-mcpu=8548 -mspe=yes -mabi=spe -mhard-float -mfloat-gprs=double
> >
> > From the menuconfig, I can only select CPU as 8540.

-- 
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

[Buildroot] how to tune powerpc e500v2 cpus in BR

[raymond zhao]

On Sun, Jun 26, 2011 at 11:59 PM, Baruch Siach <baruch@tkos.co.il> wrote:
> Hi Raymond, Matias,
>
> On Fri, Jun 24, 2011 at 01:31:26PM -0400, Matias Garcia wrote:
>> You can put those in the BR2_TARGET_OPTIMIZATIONS setting under the
>> Toolchain page e.g.
>>
>> (-mcpu=8548 -mspe=yes -mabi=spe -mhard-float -mfloat-gprs=double)
>> Target Optimizations
>>
>> I selected a generic powerpc target because I didn't need the -mtune
>> when I was specifying -mcpu already. As far as I know, 8548 and 8540
>> work out to the same code.
>>
>> I switched to the external CodeSourcery build tools for two reasons:
>> (1) it allowed us to compile our application with -O3 (which we
>> need) while the standard GNU toolchain caused some errors, and (2)
>> they're supported by the Freescale/Mentor/CodeSourcery relationship,
>> and not all of the patches get applied to mainline (particularly for
>> newer processors). I had to add an option to the external wrapper so
>> that it would call the toolchain with '-te500v2' which is a shortcut
>> for the optimizations you list below. In that case, you can build
>> your own applications without calling any options explicitly.
>
> I'm also using the CodeSourcery toolchain for the e500v2 target (P1011), and I
> figured out that I must pass -te500v2 to gcc at link time as well. Since there
> is no generic way to add LDFLAGS options in Buildroot, I've posted the patch
> at http://lists.busybox.net/pipermail/buildroot/2011-June/043668.html. Did you
> find a better solution?
>
> baruch
>
>> On 11-06-24 10:27 AM, raymond zhao wrote:
>> >Hi,
>> >I am using freescale's p1020 CPU. It is a e500v2 core. How could I
>> >config the build root to tune the tool chain for the following
>> >options:
>> >
>> >-mcpu=8548 -mspe=yes -mabi=spe -mhard-float -mfloat-gprs=double
>> >
>> > From the menuconfig, I can only select CPU as 8540.
>
> --
> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ~. .~ ? Tk Open Systems
> =}------------------------------------------------ooO--U--Ooo------------{=
> ? - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
>

Hi, Baruch
I took a look at the CodeSourcery. Looks it doesn't support uCLibc.
Best regards,
changbing

[Buildroot] how to tune powerpc e500v2 cpus in BR

[Matias Garcia]

On 11-06-27 04:10 PM, raymond zhao wrote:
> On Sun, Jun 26, 2011 at 11:59 PM, Baruch Siach<baruch@tkos.co.il>  wrote:
>> Hi Raymond, Matias,
>> I'm also using the CodeSourcery toolchain for the e500v2 target (P1011), and I
>> figured out that I must pass -te500v2 to gcc at link time as well. Since there
>> is no generic way to add LDFLAGS options in Buildroot, I've posted the patch
>> at http://lists.busybox.net/pipermail/buildroot/2011-June/043668.html. Did you
>> find a better solution?
>>
>> baruch
> Hi, Baruch
> I took a look at the CodeSourcery. Looks it doesn't support uCLibc.
> Best regards,
> changbing
changbing: That's correct. You may find an older toolchain from them 
that uses uClibc, but you'll have to specify it yourself in the 
Buildroot config. I found a very small difference in size (<2MB) between 
uclibc and eglibc filesystems, but I'm using 32MB of flash just for the 
OS, so small is relative.

Baruch: I use the external toolchain wrapper introduced just before 
2011.05, but I had to patch it to add arbitrary options. I posted a 
couple of patches here, one that introduces a new option for selecting 
the sysroot when compiling the external wrapper, and another that simply 
passes the BR2_TARGET_OPTIMIZATIONS to the external wrapper, but they 
didn't get much attention.

I prefer the first method (new config option) because you can choose not 
to pass the optimizations@some later point for whatever reason, and 
thus use the wrapper only to select your sysroot.

Cheers,
Matias

[Buildroot] how to tune powerpc e500v2 cpus in BR

[Baruch Siach]

Hi Matias, raymod,
On Mon, Jun 27, 2011 at 04:23:55PM -0400, Matias Garcia wrote:
> On 11-06-27 04:10 PM, raymond zhao wrote:
> >On Sun, Jun 26, 2011 at 11:59 PM, Baruch Siach<baruch@tkos.co.il>  wrote:
> >>Hi Raymond, Matias,
> >>I'm also using the CodeSourcery toolchain for the e500v2 target (P1011), and I
> >>figured out that I must pass -te500v2 to gcc at link time as well. Since there
> >>is no generic way to add LDFLAGS options in Buildroot, I've posted the patch
> >>at http://lists.busybox.net/pipermail/buildroot/2011-June/043668.html. Did you
> >>find a better solution?
> >>
> >I took a look at the CodeSourcery. Looks it doesn't support uCLibc.

Yes. I'm also trying to build a uClibc toolchain using crosstool-ng. No luck 
yet. You may try the Aboriginal Linux toolchain 
(http://landley.net/aboriginal/downloads/binaries/), although it's based on an 
old gcc version (4.2.1).

> changbing: That's correct. You may find an older toolchain from them
> that uses uClibc, but you'll have to specify it yourself in the
> Buildroot config. I found a very small difference in size (<2MB)
> between uclibc and eglibc filesystems, but I'm using 32MB of flash
> just for the OS, so small is relative.

The greatest advantage of uClibc is that it behaves better when doing static 
linking. I use it to generate Busybox based initramfs, and for this use case 
the 2MB size reduction is a big difference.

> Baruch: I use the external toolchain wrapper introduced just before
> 2011.05, but I had to patch it to add arbitrary options. I posted a
> couple of patches here, one that introduces a new option for
> selecting the sysroot when compiling the external wrapper, and
> another that simply passes the BR2_TARGET_OPTIMIZATIONS to the
> external wrapper, but they didn't get much attention.

Can this solve the link time -te500v2 issue? I'll look into this.

baruch

> I prefer the first method (new config option) because you can choose
> not to pass the optimizations at some later point for whatever
> reason, and thus use the wrapper only to select your sysroot.
> 
> Cheers,
> Matias

-- 
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -