[ACTIVITY] Week 17
o 4 days week. o LLVM * Machine outliner: - Reduced CTMark issue, still working on it. o Misc * Various meetings and discussions. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] Week 17
o 1 day off (2/10) == Progress == o Extended validation (2/10) * Extended validation now operational, reporting enhancements investigations. * Looked at gdb/guality unstable results. * Reviewed some jobs. o Linaro GCC (2/10) * Scripted new Linaro development branch process. o Upstream GCC (1/10) * Digging in libatomic code. o Misc (3/10) * Various meetings and discussions. == Plan == o 2 days off (Thu/Fri) o Continue on validation and upstream work. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: [Activity] Week 17
On 27 April 2015 at 03:17, Prathamesh Kulkarni prathamesh.kulka...@linaro.org wrote: == This Week == * TCWG-619: * abe sysroot/libc issue While building chromium with development build of toolchain on arm-linux-gnueabihf, I get the following error: undefined reference to clock_gettime() Builds fine with release toolchain build. Symlinking libc in toolchain install directory to sysroots/arm-linux-gnueabihf appears to work (which is what --tarbin did). * PR65778 - v8 fails to build with LTO - Resolved Invalid * PR65837 - target specific builtin not available - created a reduced test case - There's a weird issue: looks like for lto1, translation unit command line options, precede the default ones rather than overriding them. Assume test.c contains a neon intrinsic: arm-linux-gnueabihf-gcc -flto -c test.c -mfpu=neon arm-linux-gnueabihf-gcc -flto test.o results in target specific builtin not available, because both -mfpu=neon and -mfpu=vfpv3-d16 is passed and -mfpu=vfpv3-d16 overrides earlier -mfpu=neon Passing -mfpu=neon at link time correctly overrides -mfpu=vfpv3-d16. * PR6778 - ICE in varpool_node::get_constructor. s/PR6778/PR65858 - Looks like PR65776 appears due to same issue as well. - It appears error_mark_node gets streamed that causes ICE. - Triage went wrong, thought it was an error in typeck2.c:check_narrowing(). * PR49551 - The C front-end c/c-decl.c:merge_decls still incorrectly marks the variable as 'common' for the test-case: int x = 5; int x; However it's not reproducible anymore on trunk (maybe latent?) - I have an untested patch that resolves the issue in merge_decls(). * Issues - abe built native gcc on x8_64-unknown-linux-gnu fails to build code when passed -m32 option (bug 1508). * Misc - exams on 20th and 24th april. * Next week - Continue working on PR65837, PR65778 - Test patch for PR49551 ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] Week 17
Short week, Easter Monday + child care (3/10) == Issues == * Toolchain64 disk still full every 2 days == Progress == * Linaro GCC 4.9 2014.04 release (3/10) - Branch merge with FSF 4.9.1 - Release tarball available on releases.linaro.org - Announcement will follow * Launchpad bugs: (2/10) o LP #1169164 : including signal.h exposes various PSR_MODE #defines - Discussed and implemented a fix - Validation on-going * Misc: o Cbuildv1 baby-sitting (1/10) o Various meetings (1/10). o Resolved cards : - TCWG-343. Make LRA the default for the ARM backend - TCWG-422. LP-bug 1296676 : ICE in assign_by_spills building linux btrfs module == Next == - One day off (Labor day) - Submit patch for LP #1169164 - TCWG-345. Analyse performance of LRA for ARM ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] Week 17
== Progress== TCWG-435 needless busy-wait in lowlevellock.c (3/10) * Patches ready, testing a bit slow fiddly TCWG-156 cortex-strings memset (3/10) * Worried about noisy benchmarks * Learned to use Lava * Found some helpful internal docs * Managed to tweak the code slightly == Misc == Meetings/mail/etc 2/10 (Public) holiday 2/10 == Plan == Stop worrying and follow the general curve of the noisy benchmarks (But also try to convince Maxim's spec scripts + lava to generate some less noisy results) Another public holiday next Monday ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] Week 17
== Issue == * None == Progress == * More tests on shrink-wrap changes (TCWG-133, 6/10). - Cortex-m3 tests exposes a data flow issue: New BB created after dfinit does not have correct df_lr info. - Collect Spec2k benchmarks on X86-64 and ARM. * Linaro 4.9 binaries release (2/10). - Update Linaro crosstool-ng config and samples to support 4.9. - Disable parallel build for gcc manual (pdf html). - Prebuild binaries for aarch64: http://cbuild.validation.linaro.org/binaries/4.9-prerelease-2014.04 * Ping aarch64 fcel patch. But still no comments. * Fix a trunk build fail issue @r209556. * One day off (2/10). == Plans == * Send the shrink-wrap related patches for review. * PING the pending patches. * Investigate move-loop-invariants heuristics. == Planed leaves == * May 1-3: Labour day holiday. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] Week 17
== Issues == * None == Progress == * Libunwind AArch64 support: - Fixed signal frame issue. - Sent patch upstream for review. - Delivered patch to OE team for early testing. * LRA on ARM and AArch64: - Start to look at what is missing. == Plan == * 3 days off next week * Continue on LRA. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] Week 17
Summary: * Enhance Linaro crosstool-ng. Details: 1. Work with Bero to release 4.8 binary build. 2. Update Linaro crosstool-ng to use ISL/CLooG for 4.8 build (lp:1172595). 3. Rebase conditional compare experimental codes to lp:gcc-linaro/4.8. Plan: * Investigate the impact of conditional compare on optimizations. Planned leaves: * 29 April - 1 May: Labor Day's holiday. Best Regards! -Zhenqiang ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] Week 17
== Progress == * Submitted binutils patch for testsuite failure on precise. * Updated glibc memcpy patch based on feedback. * Updated binutils IFUNC patch based on feedback. * Started working on AArch64 IFUNC. * Submitted a couple of cleanup patches for AArch64 binutils. == Issues == * 2 cards blocked on upstream review, 1 blocked on Android team. == Plan == * Should get binutils IFUNC patch committed Monday. * Need to ping other patches again. * More work on AArch64 IFUNC. -- Will Newton Toolchain Working Group, Linaro ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: [Activity] Week 17
On 28 April 2012 21:34, Zhenqiang Chen zhenqiang.c...@linaro.org wrote: Summary: * Linaro binary toolchain 2012.04 release. * Code size benchmark analysis. Details: 1. Validate and bug fix for linaro binary toolchain 2012.04 release. 2. Investigate code size regressions in 4.7 Find more regression cases due to loop invariant hoisting, and tests should we can reduce some codesize with option -fno-move-loop-invariants. Some regressions are due to pass_reorder_blocks, which is disabled for -Os in 4.7. For some cases, ivopt will introduce to more codes and function inline might lead to more spilling. We also try linaro 2012.04 baremetal build. But there is a few bytes regression compared with 4.7 trunk. 3. Setup the qemu env following Michael’s instructions (https://wiki.linaro.org/MichaelHope/Sandbox/QEMUCrossTest) and tests show it work. 4. Try to build gcc-linaro-2012.04 configured with --with-fpu=neon --with-float=hard based on a precise sysroot (precise-sysroot-armhf-r0.tar.bz2) from http://people.linaro.org/~michaelh/incoming * Linux build is OK without any change. * Mingw32 build reports error. After removing the code, the build PASS. [ERROR] .../libc/usr/include/arm-linux-gnueabihf/sys/types.h:117:19: error: two or more data types in declaration specifiers See the oneiric sysroot patch. This needs to be brought forward for Precise on mingw. -- Michael ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
[Activity] Week 17
Summary: * Linaro binary toolchain 2012.04 release. * Code size benchmark analysis. Details: 1. Validate and bug fix for linaro binary toolchain 2012.04 release. 2. Investigate code size regressions in 4.7 Find more regression cases due to loop invariant hoisting, and tests should we can reduce some codesize with option -fno-move-loop-invariants. Some regressions are due to pass_reorder_blocks, which is disabled for -Os in 4.7. For some cases, ivopt will introduce to more codes and function inline might lead to more spilling. We also try linaro 2012.04 baremetal build. But there is a few bytes regression compared with 4.7 trunk. 3. Setup the qemu env following Michael’s instructions (https://wiki.linaro.org/MichaelHope/Sandbox/QEMUCrossTest) and tests show it work. 4. Try to build gcc-linaro-2012.04 configured with --with-fpu=neon --with-float=hard based on a precise sysroot (precise-sysroot-armhf-r0.tar.bz2) from http://people.linaro.org/~michaelh/incoming * Linux build is OK without any change. * Mingw32 build reports error. After removing the code, the build PASS. [ERROR] .../libc/usr/include/arm-linux-gnueabihf/sys/types.h:117:19: error: two or more data types in declaration specifiers Plans: * Investigate other code size regressions in 4.7. Planed leaves: * Labor Day holiday: April 30 and May 1. Best regards! -Zhenqiang ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
