[ANNOUNCE] Linaro GCC 4.9 2014.10 released
The Linaro Toolchain Working Group (TCWG) is pleased to announce the 2014.10 release of the Linaro GCC 4.9 source package. Linaro GCC 4.9 2014.10 is the seventh Linaro GCC source package release. It is based on FSF GCC 4.9.2-pre+svn216130 and includes performance improvements and bug fixes. With the imminent release of ARMv8 hardware and the recent release of the GCC 4.9 compiler the Linaro TCWG will be focusing on stabilization and performance of the compiler as the FSF GCC compiler. The Linaro TCWG provides stable[1] quarterly releases and monthly enginering[2] releases. Interesting changes in this GCC source package release include * Updates to GCC 4.9.2-pre+svn216130 * Backport of [AArch64] Define TARGET_FLAGS_REGNUM * Backport of PR target/61565 * Backport of [AArch64] libitm: Improve _ITM_beginTransaction * Backport of [AArch64] Fix *extr_insv_lower_reg pattern * Backport of [AArch64] Use CC_Z and CC_NZ with csinc and similar instructions * Backport of [AArch32] Implement and vectorize lceil, lfloor, lround optabs with new ARMv8-A instructions * Backport of [AArch64] Improve epilogue unwind info rth * Backport of [AArch64] Add a mode to operand 1 of sibcall_value_insn * Backport of [AArch64] Add a builtin for rbit(q?)_p8; add intrinsics and tests * Backport of [AArch32/AArch64] Schedule alu_ext for Cortex-A53 * Backport of [AArch64] Remove varargs from aarch64_simd_expand_args * Backport of [AArch64] Tidy: remove unused qualifier_const_pointer * Backport of [AArch32/AArch64] Add scheduling info for ARMv8-A FPU new instructions in Cortex-A53 * Backport of [AArch32] Convert FP mnemonics to UAL. * Backport of [AArch32] Enable auto-vectorization for copysignf * Backport of [AArch32][tests] Make input and output arrays 128-bit aligned in vectorisation tests * Backport of [AArch64] Add crtfastmath * Backport of PR target/56846 libstdc++ * Backport of PR target/63209 * Backport of [Ree] Ensure inserted copy don't change the number of hard registers * Backport of [AArch64] Fix force_simd macro in vdup_lane_2 * Backport of [AArch32] Disallow -mfpu=neon for unsuitable architectures * Backport of [AArch32] movmisalign_neon_load * Backport of [AArch64] Add constraint letter for stack_protect_test pattern * Backport of [AArch64] Auto-generate the "BUILTIN_" macros Feedback and Support Subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro development. ** Linaro Toolchain Development "mailing list": http://lists.linaro.org/mailman/listinfo/linaro-toolchain ** Linaro Toolchain IRC channel on irc.freenode.net at @#linaro-tcwg@ * Bug reports should be filed in bugzilla against GCC product: http://bugs.linaro.org/enter_bug.cgi?product=GCC * Questions? "ask Linaro": http://ask.linaro.org/. * Interested in commercial support? inquire at "Linaro support":mailto: supp...@linaro.org [1] Stable source package releases are defined as releases where the full Linaro Toolchain validation plan is executed. [2] Engineering source package releases are defined as releases where the compiler is only put through unit-testing and full validation is not performed. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] Week 42
== Progress == * Linux Plumbers (6/10) - Attended conference, Android/Tools/LLVM tracks - Presented 2 talks (GCC+LLVM and LLVM+ARM) * Buildbots (TCWG-76 2/10) - Made the Compiler-RT bot green! Now on to the libc++ one * Background (2/10) - Code review, meetings, discussions, etc. - Internet upgrade, re-wiring the house, building works == Plan == * Add libc++abi buildbot * Follow up on the fpu issues on Clang/asm ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Q about using AArch64 gdb with target running in AArch32 state
Hi, I start to use Linary AArch64 toolchain recently and just joined this maillist. I went through some of the archived threads but didn't read all of them. So bear me if I'm asking dumb question or old question which had been answered before. For our use case, we are running the gdb client at early state of boot. So the ARMv8 target might be running into any EL and into either AArch64 or AArch32 state. My questions are: 1) Is the aarch64-none-elf-gdb.exe good for both AArch64 and AArch32 or I have to run the arm-none-eabi-gdb.exe if the target running in AArch32 state? 2) If the target is in AArch64 state, can I use the aarch64-none-elf-gdb.exe to load binary built for AArch32 to the target? I'm really appreciated if anybody can help me on these two questions. Thanks in advance, StrongQ ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] 13 - 17 October 2014
== Progress == * Respin of malloc single-thread optimizations (4/10, TCWG-436) - Create a generic header, include AArch64 in series * Further work on malloc app benchmark framework (4/10, TCWG-441) - Cleaned up, improved reliability, added comments - Committed to cortex-malloc.git * Email, meetings, etc. (1/10) * Upstream work (1/10, CARD-341) - glibc patch review and pings - Look into some bug reports and testsuite failures == Issues == * Electricians and gas engineers turning off power/heating at various points == Plan == * Hopefully get some resolution of single thread atomic stuff for glibc -- Will Newton Toolchain Working Group, Linaro ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] 13-17 October 2014
== Progress == * GCC trunk/4.9 validation (CARD-647) (3/10) - committed testsuite patch to test if -shared is supported - forcing -mword-relocations flags when compiling testglue works on my Ubuntu machines, but does not in the Compute Farm RHEL5 servers. - investigating why, all the more as it made me incorrectly report failures in the 4.9 branch * Validation (2/10) - compared cbuild2 schroot-test branch and master the results of this manual run does not seem to match Jenkins results * Neon intrinsics tests (1/10) - fixed .exp harness to support parallelization - looking at how to pre-support fp16, will probably skip it for now, and add dedicated tests later * AArch64 sanitizer (1/10) - GCC trunk seems to need to cherry pick a sanitizer patch when building using recent kernel headers - tried to use Jenkins to build trunk and trunk+cherry-pick, but the results are not consistent needs more investigation * Misc (3/10) - calls, meetings, irc == Next == * GCC trunk/4.9 cross-validation - fix -mword-relocations support - investigate abi_check test * AArch64 sanitizer * Neon intrisics tests update * cbuild2: - analyze previous results (mostly check the logs) - look at backport-test script + logs Short next week: off Wednesday/Thursday ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
