[ACTIVITY] 19 - 23 August 2013
== 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. == Plan == * Post RFC patch for Libssp support for AArch64 in GCC * Continue testing the patch for Libssp support for AArch64 in GCC and glibc TCWG-23 * Backport 201411 201624 201666 from trunk == Issues == * LTO/PGO work stopped now since libssp support priority is more. * Waiting for Marcus feedback for Matt comments on gprof patches TCWG-20. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: [ACTIVITY] 19 - 23 August 2013
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-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: [ACTIVITY] 19 - 23 August 2013
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 suspicion and now you have confirmed it. Kugan. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] Aug 18-23
== 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 pages, updated some, deleted some, some were ok as is and still useful. * Registered for LCU13. * Ordered Odroid XU & U2 boards. * Put out 2 lightning caused wildland fires. * Ran weekend music festival fund raiser for a local non-profit. == Plan == * Review more wiki pages. * Improve binary tarball support in Cbuildv2. * Add 'make check' to Jenkins builds. * Get Jenkins to do automated builds on LAVA build farm. * Get lava-tool working. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Any plans for "ifunc-ing" more glibc routines?
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-ed version of memcpy. Does the TCWG have a hit list of other functions that might get the same treatment? If so, does it have a plan and the resources to implement them? If it's a matter of resources, I think LEG might be able to help there. Cheers, mwh ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Any plans for "ifunc-ing" more glibc routines?
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 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-ed version of memcpy. Does the > TCWG have a hit list of other functions that might get the same > treatment? If so, does it have a plan and the resources to implement > them? If it's a matter of resources, I think LEG might be able to help > there. > > Cheers, > mwh > > ___ > linaro-toolchain mailing list > linaro-toolchain@lists.linaro.org > http://lists.linaro.org/mailman/listinfo/linaro-toolchain > ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
backport of memcpy ifunc work to 2.17
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 mysterious segfaults when building. These are the additional patches being used: arm/define-sfi_breg-and-PC_OFS.patch arm/Add-Cortex-A15-optimized-NEON-and-VFP-memcpy-rou.patch arm/Make-multiarch-memcpy-always-use-NEON-when-compi.patch arm/Clean-up-__libc_ifunc_impl_list.patch arm/Make-armv7-memcpy-implementations-SFI-friendly.patch arm/Use-push-pop-mnemonics.patch arm/Support-avoiding-pc-as-destination-register.patch arm/BX_ALIGN_LOG2.patch arm/Pass-dl_hwcap-to-IFUNC-resolver-functions.patch -- all grabbed from glibc git. Are we missing something obvious? :) Cheers, mwh ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
