Hi,
* catching up with emails
* rebased against current OE-core
* OE is planning a release in april (following the yocto schedule)
* noticed the libc of our binary toolchain is lacking i18n
* caused a packaging issue for meta-linaro but easy to workaround
* contents of the i18n folder
On 23 April 2012 00:54, Ken Werner wrote:
> Hi,
>
> * catching up with emails
> * rebased against current OE-core
> * OE is planning a release in april (following the yocto schedule)
> * noticed the libc of our binary toolchain is lacking i18n
> * caused a packaging issue for meta-linaro bu
On 21 April 2012 09:10, Jon Masters wrote:
> Hey everyone,
>
> Following up here. Where do we stand? We need to have upstream patches
> before we can pull them into the distro - is that piece done?
Hi Jon. I've been away, sorry. I've just sent the GCC patch and
Carlos is on the hook for the GLI
On 20 April 2012 22:26, Felipe Contreras wrote:
> Hi,
>
> I have been using CodeSourcery tool-chains since forever, and I
> decided to try Linaro's tool-chain. So far I haven't had any issues,
> except one:
>
> libgcc_s.so.1 is located in arm-linux-gnueabi/lib, which is not
> available from arm-li
On 04/22/2012 06:06 PM, Michael Hope wrote:
> On 21 April 2012 09:10, Jon Masters wrote:
>> Hey everyone,
>>
>> Following up here. Where do we stand? We need to have upstream patches
>> before we can pull them into the distro - is that piece done?
>
> Hi Jon. I've been away, sorry. I've just se
Summary:
* Code size benchmark analysis.
* Linaro binary toolchain 2012.04 release.
Details:
1. Tuning the heuristic to assign register for copies.
* Take the CONFLICT_HARD_REGS and HARD_REG_COSTS of copies into
account when conflict_costs is NULL in
update_conflict_hard_regno_costs, which handl
