== Progress ==
3 day week 21 August unwell and 23-August leave.
* Libssp support for AArch64 TCWG 23:
Sent RFC patch for review.
http://sourceware.org/ml/libc-ports/2013-08/msg00044.html
workign on cross testing eglibc from host.
* Backport 201406 to linaro branch. Waiting for review.
==
Kugan,
> * Back-porting
> - Back ported all the assigned one
> - There are some make check failures for thread related test cases with
> qemu; investigating it
This are known qemu threading issues, don't spend time on it ;)
___
linaro-toolchai
On 26/08/13 17:21, Yvan Roux wrote:
Kugan,
* Back-porting
- Back ported all the assigned one
- There are some make check failures for thread related test cases with
qemu; investigating it
This are known qemu threading issues, don't spend time on it ;)
Thanks Yvan. I had a suspici
== Progress ==
* Got Cbuildv2 building native on Odroid and Wandboard via Jenkins
using the LAVA build farm.
* Improved support for native builds in Cbuildv2.
* Added building binary tarballs for releases.
* Looked at two patches for multilib support.
* Reviewed a bunch of wiki
Hi all,
There has been interest from LEG members to ensure that optimal library
routines are used on their platforms. My understanding is that the
"correct" way of doing this these days is to use ifuncs to select the
best implementation for a given system.
I see that glibc 2.18 contains an ifunc
I think a better way of doing some of these functions is using ifunc with a
vdso. So the glibc does not have to be updated; only the kernel.
Thanks,
Andrew
Sent from my iPad
On Aug 26, 2013, at 8:17 PM, "Michael Hudson-Doyle"
wrote:
> Hi all,
>
> There has been interest from LEG members to
Hi,
Apologies in advance for any chinese whispers effects that happen, but
colleagues at Canonical are attempting to backport this change:
https://sourceware.org/git/?p=glibc.git;a=commit;h=ae65139d140ac85808c0666c363
to the (e)glibc in current versions of Ubuntu, 2.17, but are
encountering
