- linaro-toolchain - lists.linaro.org

[ACTIVITY] 5 - 9 March 2018

by Prathamesh Kulkarni

== This Week == * Code hoisting/TCWG-1234 (4/10) - Continuing with cost model approach * Connect slides (4/10) * Misc (2/10) - Meetings - Experimenting with ipa-dse == Next Week == - Continue ongoing tasks

7 years, 3 months

1
0
0 0

[ACTIVITY] Week 10

by Yvan Roux

== Progress == o LLVM * Benchmarking job * Buildbots babysitting o Misc * Various meetings and discussions. * Preparing Connect

7 years, 3 months

1
0
0 0

[ACTIVITY] 5-9 March 2018

by Christophe Lyon

== Progress == * GCC - FDPIC - reworking/cleaning binutils patches * GCC upstream validation: * Infrastructure: - TCWG-1335: updated builder dockerfiles with postfix config, pending review ABE patch merged. contrib/test_summary patch pending review. - Enabling use of Linaro binary release on old distro: not worth the effort needed to do this cleanly - bug #3344: fixed gdbserver build in Linaro releases * misc (conf-calls, meetings, emails, ....) == Next == * GCC/FDPIC * GCC upstream validation

7 years, 3 months

1
0
0 0

libpython2.7.so missing

by Pukitis, Martins

Hi. gdb doesn't run due to there is no libpython2.7.so on the system. $ ./gdb/gdb --version ./gdb/gdb: error while loading shared libraries: libpython2.7.so: cannot open shared object file: No such file or directory There is only static python library available. Is there a way to build gdb with static python library? Regards, Martins

7 years, 3 months

2
1
0 0

[ACTIVITY] Week 09

by Yvan Roux

== Progress == o LLVM * Benchmarking job * Buildbots babysitting o Misc * Various meetings and discussions. * Preparing Connect

7 years, 4 months

1
0
0 0

[ACTIVITY] 26 February-2 March 2018

by Christophe Lyon

== Progress == * GCC - FDPIC - reworking/cleaning binutils patches * GCC upstream validation: * Infrastructure: - TCWG-1335: updated builder dockerfiles with postfix config. ABE patch under review to send test results. Sent a patch for contrib/test_summary script. - Enabling use of Linaro binary release on old distro: unsuccessful experiment with LD_PRELOAD so far. * misc (conf-calls, meetings, emails, ....) == Next == * GCC/FDPIC * GCC upstream validation

7 years, 4 months

1
0
0 0

[ACTIVITY] 26 Feb - 02 March

by Yao Qi

* Off on Friday afternoon. # Progress # * Fix non-gdbserver issue and GDB buildbot issue. Intel people committed a patch breaks every non-x86 gdbserver. Test with GDBserver is slowed down from 20~40 minutes to 6~12 hours. The fix is pushed in, requested upstream GDB buildbot maintainer to get rid of pending builds until the fix. # Plan # * Review Alan H.'s patches. -- Yao Qi

7 years, 4 months

1
0
0 0

[ACTIVITY] 19 - 23 Feb 2018

by Prathamesh Kulkarni

== This Week == * Coremark regression (TCWG-1234) (6/10) - Working on defining a cost model for hoisting. * Public Holiday (2/10) * Misc (2/10) - Meetings - Slides == Next Week == - Continue ongoing tasks.

7 years, 4 months

1
0
0 0

[ACTIVITY] Week 08

by Yvan Roux

== Progress == o LLVM * Benchmarking job * Buildbots babysitting * Python scripts reviews o Misc * Various meetings and discussions. * Preparing Connect presentations

7 years, 4 months

1
0
0 0

[ACTIVITY] Weekly report for week 8

by Thomas Preudhomme

Note: working for Linaro every other week * start looking at fix for PR34170 / TCWG1137 (cannot select truncate in ARMv7 backend): + inline asm with >=64bit floating-point output is not handled + wrote a tentative patch which crashes later in the code, need to investigate * Start slides for technical talk in TCWG room @ Linaro connect: + bswap done, started to refamiliarize myself with store merging pass and its latest improvement * Merge the two patches for TCWG-1308 (missing pseudo expansion + crash in instruction selection of vector load/store with register writeback) === Plan for next Linaro week (week 10) === * finish fix for PR34170 / TCWG1137 (cannot select truncate in ARMv7 backend) * finish slides for bswap/store merging passes presentation in hacker room at Connect HK2018

7 years, 4 months

1
0
0 0

[ACTIVITY] 19 - 23 Feb

by Yao Qi

* Off on Monday [1/5] # Progress # * GDB is confused by the line table generated by GCC with -gcolumn-info PR 22531. [2/5] Preparatory patches v2 are posted. * Merge my patches on removing MAX_REGISTER_SIZE. Done. [2/5] # Plan # * PR 22531, * Upstream patches review. -- Yao Qi

7 years, 4 months

1
0
0 0

[ACTIVITY] 19-23 February 2018

by Christophe Lyon

== Progress == * GCC - FDPIC - reworking/cleaning binutils patches * GCC upstream validation: - no regression to report this week :-) * Infrastructure: - tcwg-buildapp + lava now triggered daily, to check lava/lab reliability. - updated builder dockerfiles with postfix config. Patch under review - some progress on enabling use of Linaro binary release on old distro. My proposal was rejected, but the discussion moved forward. - fixed toolchain build not to ship 'runtest' anymore, and moved gdbserver from bin/ to sysroot dir * misc (conf-calls, meetings, emails, ....) == Next == * GCC/FDPIC * GCC upstream validation

7 years, 4 months

1
0
0 0

[ACTIVITY] 12 - 16 Feb

by Yao Qi

# Progress # * GDB is confused by the line table generated by GCC with -gcolumn-info PR 22531. [2/5] Tested one patch again, committed. Keep going on the rest of them. * Fix one GDB issue with OpenOCD, which is a long standing issue. [2/5] Commit patch to both GDB master and 8.1 branch. Done. * Misc, patches review, meeting. [1/5] # Plan # * One day off on Monday, * PR 22531, * Resume my pending patches on removing MAX_REGISTER_SIZE. -- Yao Qi

7 years, 4 months

1
0
0 0

[ACTIVITY] 12-16 February 2018

by Christophe Lyon

== Progress == * GCC - FDPIC - rebased GCC and GDB patches on top of recent master branches. - adjusted some of the GDB (gdbserver) patches to cope with gcc-8 complaints. - adjusted CI testsuite to cope with gcc-8 * GCC upstream validation: - no regression to report this week :-) - still checking go/libgo random results on some tests * Infrastructure: - improved tcwg-buildapp (Using Lava, thanks to Remi). Now retries lava job several times if needed. - managed to configure postfix to send emails from our build containers (thanks Ben). Once this is properly configured/deployed, we'll finally be able to send GCC validation results to the appropriate list - resurrected my old work to force use of the old memcpy version such that our binary toolchains work on older distros (such as RHEL6...) * misc (conf-calls, meetings, emails, ....) == Next == * GCC/FDPIC * GCC upstream validation

7 years, 4 months

1
0
0 0

[ACTIVITY] 5 - 9 February 2018

by Prathamesh Kulkarni

== This Week == * Code hoisting (TCWG-1234) (6/10) - Working on approach to add basic block info to ANTIC sets * GCC bugs (3/10) - Extend sincos to handle sin 2x (PR83661): Patch completed. * Misc (1/10) - Meetings

7 years, 4 months

1
0
0 0

[ACTIVITY] 05 - 09 Feb

by Yao Qi

# Progress # * GDB is confused by the line table generated by GCC with -gcolumn-info PR 22531. [2/5] Override operator new/delete, patch is OK'ed but Tom still believes classes must be is_trivially_destructible. * Resume my pending patches on removing MAX_REGISTER_SIZE. [2/5] Patches v2 are updated and posted. * Fix one GDB issue with OpenOCD, which is a long standing issue. [1/5] Patch is tested, but not committed yet. # Plan # * PR 22531, * Resume my pending patches on removing MAX_REGISTER_SIZE. * More patches review, -- Yao Qi

7 years, 4 months

1
0
0 0

[ACTIVITY] 5-9 February 2018

by Christophe Lyon

== Progress == * GCC - FDPIC - updated binutils ref results in CI. There are a couple of new failures to investigate - started GCC upgrade: rebased the FDPIC GCC pile of patches on top of trunk. - debugging ICE while building libgcc * GCC upstream validation: - helped reproduce a bugzilla on armeb - reported random go/libgo test failures. Intel confirmed they also see similar random results. * Infrastructure: - improved tcwg-buildapp script/job to actually boot arm/arm64 boards after building a kernel with a given toolchain. (Using Lava, thanks to Remi) * misc (conf-calls, meetings, emails, ....) == Next == * GCC/FDPIC * GCC upstream validation

7 years, 4 months

1
0
0 0

[ACTIVITY] 29 January - 2 February 2018

by Prathamesh Kulkarni

== This Week == * Code hoisting (TCWG-1234) (6/10) - Working on patch with feedback from Thomas. * GCC bugs (3/10) - Extend sincos to handle sin 2x (PR83661): WIP patch * Misc (1/10) - Meetings == Next Week == - TCWG-1234 - GCC bugs

7 years, 4 months

1
0
0 0

[ACTIVITY] Week 05

by Yvan Roux

== Progress == o LLVM * "unpredictable" handling: - Bugzilla 33011: Fix committed - Working on unpredictable cases when using PC as operand. * Buildbots failures: - Analyzed regressions, due to D42574 - Tested and reviewed proposed tix * 6.0.0 release test failure: - Investigate Bug 35996 (asan_rt_conflict_test segfaults) - Issue due to hardcoded filename;s lenght is too short - Validating a fix * Got commit after approval access granted o Misc * Various meetings and discussions.

7 years, 4 months

1
0
0 0

[ACTIVITY] 29/01 -- 02/02

by Yao Qi

# Progress # * gfortran 7.2 vs 8.0 debug information difference. [2/5] Open GCC bug to get more attention, PR debug/84131. It is a GCC 8 regression. Jakub fixed it two hours after I opened the bug. Now, there is no gdb.fortran test fails with truk gcc. * GDB is confused by the line table generated by GCC with -gcolumn-info PR 22531. [2/5] Patches are done, to be posted for review. Investigate how to override new/delete operator in C++. * Resume my pending patches on removing MAX_REGISTER_SIZE. [1/5] Update patch series v2 per reviewers' comments. # Plan # * GDB 8.1 is released! Bump up GDB version in Linaro toolchain. * PR 22531, * Resume my pending patches on removing MAX_REGISTER_SIZE. -- Yao Qi

7 years, 4 months

1
0
0 0

[ACTIVITY] 29 January-2 February 2018

by Christophe Lyon

== Progress == * GCC - FDPIC - debugged CI loop - analyzing new failures * GCC upstream validation: - reported a few regressions - contributed to jenkins jobs * Infrastructure: - looking at configuring email relay in our builders to send validation results * misc (conf-calls, meetings, emails, ....) == Next == * GCC/FDPIC * GCC upstream validation

7 years, 5 months

1
0
0 0

[ACTIVITY] 22 - 26 Jan 2018

by Prathamesh Kulkarni

== This Week == * GCC bugs (5/10) a) Extend malloc_candidate_p to handle multiple phi's (TCWG-1331): Fixed testsuite regressions b) Extend sincos to handle sin 2x (PR83661): Started working on patch. * TCWG-1234 (2/10) - A one liner patch that pessimizes hoisting by requiring an expression to be in AVAIL blocks of all immediate successors works for improving the regression. - Working to make the patch more general to avoid pessimizing hoisting. * Public holiday (2/10) * Misc (1/10) - Meetings

7 years, 5 months

1
0
0 0

[ACTIVITY] Week 04

by Yvan Roux

== Progress == o Linaro GCC/Validation * 2018.01 snapshots deployed * 2018.02 release candidates will be done when CVE mitigation will be contributed upstream. o LLVM * "unpredictable" handling (Bugzilla 33011, ...): on-going * Investigated OOM issue further... without much success. * Python scripts reviews o Misc * Various meetings and discussions. * Preparing Connect presentations

7 years, 5 months

1
0
0 0

[ACTIVITY] Weekly report for week 4

by Thomas Preudhomme

Note: working for Linaro every other week == Progress == * PR35157 / TCWG-1308 (crash in ARM backend for VST1d64TPseudoWB_fixed instruction): + after 2 attempts got now a clean patch with no testsuite regression + need to add testcase and it will be good to go upstream * Track down why xdg-open launches libreoffice for .dot files and opened Launchpad LP#1744953. * Misc meetings == Plan == * submit fix for PR35157 (crash in ARM backend for VST1d64TPseudoWB_fixed instruction) * fix for PR34170 / TCWG1137 (cannot select truncate in ARMv7 backend) * start preparing slide for bswap/store merging passes presentation in hacker room at Connect HK2018

7 years, 5 months

1
0
0 0

[ACTIVITY] 22 - 26 Jan

by Yao Qi

# Progress # * GDB is confused by the line table generated by GCC with -gcolumn-info PR 22531. [2/5] My preparatory patches are reviewed, mostly on C++, get encouraged to use more fancy C++ features. * gfortran 7.2 vs 8.0 debug information difference. [2/5] Many gdb.fortran test fails with gfortran 8 but gfotran 7.2 is OK. I 'git bisect' gcc and find the commit causing the debug info change, it is like a bug to me, but my compiler/fortran knowledge is too few to claim it is a 7.2 -> 8.0 regression. Posted my analysis to gcc@ and fortran@ mail list. * TCWG-1040, SVE patches review. [1/5] Review Alan's patches. # Plan # * PR 22531, upstream preparatory patches, * Write patch series v2 for TCWG-1292. -- Yao Qi

7 years, 5 months

1
0
0 0

Linaro aarch64-none-elf builds on Cygwin

by Tim Ozimek

Hello, I'm attempting an aarch64-none-elf build on Cygwin. Has this been done? Any obvious things that will prevent such an attempt? Thanks, Tim

7 years, 5 months

1
0
0 0

[ACTIVITY] 22-26 January 2018

by Christophe Lyon

== Progress == * GCC - FDPIC - debugging CI loop * GCC upstream validation: - reported a few regressions - contributed to jenkins jobs * Infrastructure: - looking at how to use lava to boot boards in gcc validation (with Remi) * misc (conf-calls, meetings, emails, ....) == Next == * GCC/FDPIC * GCC upstream validation

7 years, 5 months

1
0
0 0

arm-eabi-g++: -isystem option handle header as c linkage

by Kaul, Martin

Hi, given the following code: -- isystem_test.cpp ------------- #include < isystem_test.h> bool dummy_function( void ) { return false; } ----------------------------------------- -- isystem_test.h ------------------ template <class _CS_cT> class allocator { }; ----------------------------------------- and g++ version: arm-eabi-g++.exe (Linaro GCC 7.2-2017.11) 1. compiling with "arm-eabi-g++ -I . -g -c isystem_test.cpp" --> OK 2. compiling with " arm-eabi-g++ -isystem . -g -c isystem_test.cpp " --> output error: In file included from isystem_test.cpp:3:0: ./isystem_test.h:3:1: error: template with C linkage template <class _CS_cT> ^~~~~~~~ It seams that the option -isystem changes the include of isystems_test.h into a C include, i.e. the header content seems to be handled as C-Code Same error behavior with arm-eabi Linaro GCC 6.4-2017.11, Linaro GCC 6.3-2017.05 ----------------- Testing the same with the mingw msys g++ compiler outputs no error: g++.exe (Rev2, Built by MSYS2 project) 7.2.0 Copyright (C) 2017 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. --------------- Also no errors for: arm-linux-gnueabihf-g++.exe (Linaro GCC 6.3-2017.05) --------------- Is there a special behavior for arm-eabi g++ compiler? Best regards Martin Kaul

7 years, 5 months

2
1
0 0

[ANNOUNCE] Linaro GCC 6 and 7 2018.01 source snapshots

by Mark Murray

The Linaro Toolchain Working Group (TCWG) is pleased to announce the 2018.01 snapshot of Linaro GCC 6 and 7 source packages. o The GCC 7 series introduced an ABI change for ARM targets by fixing a bug (present since GCC 5, see link below) that affects conformance to the procedure call standard (AAPCS). The bug affects some C++ code where class objects are passed by value to functions and could result in incorrect or inconsistent code being generated. If the option -Wpsabi is enabled (on by default) the compiler will emit a diagnostic note for code that might be affected by this ABI change. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77728 For an explanation of the changes please see the following website: https://gcc.gnu.org/gcc-7/changes.html o Linaro GCC 7 monthly snapshot[1] is based on FSF GCC 7.2+svn254792 and includes performance improvements and bug fixes backported from mainline GCC. The contents of this snapshot will be part of the 2018.02 stable[2] quarterly release. This snapshot tarball is available on: http://snapshots.linaro.org/components/toolchain/gcc-linaro/7.2-2018.01/ Interesting changes in this GCC source package snapshot include: * Updates to GCC 7.2+svn256695 o Linaro GCC 6 monthly snapshot[1] is based on FSF GCC 6.4+svn254791 and includes performance improvements and bug fixes backported from mainline GCC. This snapshot contents will be part of the next maintenance release. This snapshot tarball is available on: http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.4-2018.01/ Interesting changes in this GCC source package snapshot include: * Updates to GCC 6.4+svn256699 o 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 * Interested in commercial support? inquire at "Linaro support": mailto:support@linaro.org [1]. Source package snapshots are defined when the compiler is only put through unit-testing and full validation is not performed. [2]. Stable source package releases are defined as releases where the full Linaro Toolchain validation plan is executed. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

7 years, 5 months

1
0
0 0

[ACTIVITY] 15 - 19 January 2018

by Prathamesh Kulkarni

== This Week == * GCC bugs (4/10) a) Extend malloc_candidate_p to handle multiple phi's (TCWG-1331) - Created patch b) CSE erf/erfc pair (PR83750) - Created patch * TCWG-1234 (5/10) - WIP patch on second approach * Misc (1/10) - Meetings == Next Week == - GCC bugs - TCWG-1234

7 years, 5 months

1
0
0 0

[ACTIVITY] 8 - 12 January 2018

by Prathamesh Kulkarni

== This Week == * GCC bugs (4/10) a) TCWG-1331 - Created patch b) PR83750 - Created patch * TCWG-1234 (5/10) - WIP patch on second approach * Misc (1/10) - Meetings == Next Week == - GCC bugs - TCWG-1234

7 years, 5 months

1
1
0 0

[ACTIVITY] Week 03

by Yvan Roux

== Progress == o LLVM * Bugzilla 33011 (MVN instruction "Upredictable" bit patterns incorrect): - Working on upstream comments * Working on more unpredictable handling in Tablegen * Fixing an issue with registers class in peephole optimization (exhibited by unpredictable patches). * Buildbots babysitting: investigated OOM issue, offending patch reverted. o Misc * Various meetings and discussions.

7 years, 5 months

1
0
0 0

[ACTIVITY] 15 - 19 Jan

by Yao Qi

# Progress # * GDB is confused by the line table generated by GCC with -gcolumn-info PR 22531. [2/5] Chat with other two people who are changing the same file, and they are OK to get my changes first. Commit one obvious patch, and testing one patch series for refactor. * TCWG-181, GDB compile feature. [2/5] Many new test failures in gdb.compile, because it is not supported on arm and aarch64, but we have no way to disable them. Commit two fixes to get test better, but still many fails on arm-linux. I think I still need a patch to disable the test form arm-linux. * TCWG-1040, SVE patches review. [1/5] Review Alan's patches. # Plan # * PR 22531, upstream preparatory patches, * Answer questions to my pending patch series, TCWG-1292. -- Yao Qi

7 years, 5 months

1
0
0 0

[ACTIVITY] 15-19 January 2018

by Christophe Lyon

== Progress == * GCC - FDPIC - fixed crash during program startup (self-relocation) - CI loop now almost green * GCC upstream validation: - reported a few of regressions - committed a few minor testsuite fixes * Infrastructure: * misc (conf-calls, meetings, emails, ....) == Next == * GCC/FDPIC * GCC upstream validation

7 years, 5 months

1
0
0 0

[update]: Does linaro toolchain support c++11 ??

by zhangwentao (M)

Hi, all I have updated my test case: Compile passed but failed while linking. wentao@ubuntu:~/test/lamda$ cat a.cc #include <iostream> using namespace std; int main() { auto f = [=]() { cout <<"Hello world"<<endl; }; f(); return 0; } wentao@ubuntu:~/test/lamda$ arm-eabi-g++ --std=gnu++11 a.cc -o arm32 /home/wentao/TeeOS/tools/gcc-linaro-6.3.1-2017.05-x86_64_arm-eabi/bin/../lib/gcc/arm-eabi/6.3.1/../../../../arm-eabi/lib/libstdc++.a(locale.o): In function `get_locale_cache_mutex': /home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/arm-eabi/snapshots/gcc.git~linaro-6.3-2017.05/libstdc++-v3/src/c++98/locale.cc:36: undefined reference to `__sync_synchronize' /home/wentao/TeeOS/tools/gcc-linaro-6.3.1-2017.05-x86_64_arm-eabi/bin/../lib/gcc/arm-eabi/6.3.1/../../../../arm-eabi/lib/libstdc++.a(future.o): In function `__future_category_instance': /home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/arm-eabi/snapshots/gcc.git~linaro-6.3-2017.05/libstdc++-v3/src/c++11/future.cc:64: undefined reference to `__sync_synchronize' /home/wentao/TeeOS/tools/gcc-linaro-6.3.1-2017.05-x86_64_arm-eabi/bin/../lib/gcc/arm-eabi/6.3.1/../../../../arm-eabi/lib/libstdc++.a(locale_init.o): In function `(anonymous namespace)::get_locale_mutex()': /home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/arm-eabi/snapshots/gcc.git~linaro-6.3-2017.05/libstdc++-v3/src/c++98/locale_init.cc:66: undefined reference to `__sync_synchronize' collect2: error: ld returned 1 exit status wentao@ubuntu:~/test/lamda$ ��: zhangwentao (M) ��ʱ��: 2018��1��10�� 10:22 �ռ��: 'linaro-toolchain(a)lists.linaro.org' ��: Huangqiang (H); Lizefan; leijitang ��: Does linaro toolchain support c++11 ?? Hi all, I wonder if my compiler supports C++11? If not, where could I found the compiler supports c++11 (both 32bit and 64bit arm). THANKS a lot~~~ My compiler information is as below: wentao@ubuntu:~/test/lamda$ arm-eabi-g++ -v Using built-in specs. COLLECT_GCC=arm-eabi-g++ COLLECT_LTO_WRAPPER=/home/wentao/TeeOS/tools/gcc-linaro-6.3.1-2017.05-x86_64_arm-eabi/bin/../libexec/gcc/arm-eabi/6.3.1/lto-wrapper Target: arm-eabi Configured with: '/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/arm-eabi/snapshots/gcc.git~linaro-6.3-2017.05/configure' SHELL=/bin/bash --with-mpc=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/arm-eabi/_build/builds/destdir/x86_64-unknown-linux-gnu --with-mpfr=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/arm-eabi/_build/builds/destdir/x86_64-unknown-linux-gnu --with-gmp=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/arm-eabi/_build/builds/destdir/x86_64-unknown-linux-gnu --with-gnu-as --with-gnu-ld --disable-libmudflap --enable-lto --enable-shared --without-included-gettext --enable-nls --disable-sjlj-exceptions --enable-gnu-unique-object --enable-linker-build-id --disable-libstdcxx-pch --enable-c99 --enable-clocale=gnu --enable-libstdcxx-debug --enable-long-long --with-cloog=no --with-ppl=no --with-isl=no --enable-multilib --with-multilib-list=aprofile --enable-threads=no --disable-multiarch --with-newlib --with-build-sysroot=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/arm-eabi/_build/sysroots/arm-eabi --with-sysroot=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/arm-eabi/_build/builds/destdir/x86_64-unknown-linux-gnu/arm-eabi/libc --enable-checking=release --disable-bootstrap --enable-languages=c,c++,lto --build=x86_64-unknown-linux-gnu --host=x86_64-unknown-linux-gnu --target=arm-eabi --prefix=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/arm-eabi/_build/builds/destdir/x86_64-unknown-linux-gnu Thread model: single gcc version 6.3.1 20170404 (Linaro GCC 6.3-2017.05) wentao@ubuntu:~/test/lamda$ ===> And more, I wrote a ��hello-world�� program using c++11, it could work with host g++, but when I change to ��arm-eabi-g++��, it does not work. Information as below: wentao@ubuntu:~/test/lamda$ cat a.cc #include <iostream> using namespace std; typedef void(*Func)(); int main() { Func f = [=]() { cout <<"Hello world"<<endl; }; f(); return 0; } wentao@ubuntu:~/test/lamda$ g++ a.cc -o host a.cc: In function ��int main()��: a.cc:10:2: warning: lambda expressions only available with -std=c++11 or -std=gnu++11 [enabled by default] }; ^ wentao@ubuntu:~/test/lamda$ ./host Hello world wentao@ubuntu:~/test/lamda$ arm-eabi-g++ a.cc -o arm32 a.cc: In function ��int main()��: a.cc:10:2: error: cannot convert ��main()::<lambda()>�� to ��Func {aka void (*)()}�� in initialization }; ^ wentao@ubuntu:~/test/lamda$ arm-eabi-g++ --std=gnu++11 a.cc -o arm32 # if gives �Cstd=c++11 , the error is the same. a.cc: In function ��int main()��: a.cc:10:2: error: cannot convert ��main()::<lambda()>�� to ��Func {aka void (*)()}�� in initialization }; ^ wentao@ubuntu:~/test/lamda$

7 years, 5 months

2
5
0 0

[ACTIVITY] Weekly report for week 1 & 2

by Thomas Preudhomme

Hi everyone, Note 1: Working on Linaro 50% time. Note 2: had afternoons off for the first 2 weeks of January == Progress == * Week 1 (2/1 -> 5/1) working for Arm * Fix poor screen resolution issue * Onboarding process: + read all docs, setup accounts (gmail, octopus, ...) * PR35157 / TCWG-1308 (Crash in ARM backend for VST1d64TPseudoWB_fixed instruction): + reproduce in llc under gdb, start investigating == Plan == * PR35157 / TCWG-1308 (Crash in ARM backend for VST1d64TPseudoWB_fixed instruction)

7 years, 5 months

1
0
0 0

[ACTIVITY] 08 - - 12 Jan 2018

by Yao Qi

# Progress # * GDB 8.1 release. 8.1 RC was created. 8.1 will be released soon, I think. * GDB is confused by the line table generated by GCC with -gcolumn-info PR 22531. [3/5] Get a working patch, but need to upstream my refactoring first. Other two people from upstream are also changing the same file, need to cooperate. * Upstream patches review, [2/5] ** Review changes to dwarf2read.c, ** Review one ARMv8 OpenOCD patch, # Plan # * PR 22531, * Resume my pending patches on removing MAX_REGISTER_SIZE. -- Yao Qi

7 years, 5 months

1
0
0 0

[ACTIVITY] Week 02

by Yvan Roux

== Progress == o LLVM * TCWG-1324 (failures of Clang::atomic_ops.c and frem.ll on armv8l host): - Fix committed in mainline as r322098 * Bugzilla 33011 (MVN instruction "Upredictable" bit patterns incorrect): - Fix submitted upstream * Buildbots babysitting. * LLVM scripts reviews o Misc * Various meetings and discussions.

7 years, 5 months

1
0
0 0

[ACTIVITY] 8 - 12 January 2018

by Prathamesh Kulkarni

== This Week == * GCC bugs (8/10) - PR81703: Committed to trunk, restricted test-case to x86_64 for now. - PR83514: Committed to trunk. - PR82665: Upstream iteration and approved for next stage-1. - PR83648: Upstream iteration and approved for next stage-1. - TCWG-1329: Created patch. - PR83570: Work in progress patch. * libgo regression (1/10) - Individual tests failing with makechan size out of range - Sent patch to add failing tests to unstable-tests.txt * Misc (1/10) - libgo regressions - Meetings == Next Week == - TCWG-1234 - GCC bugs

7 years, 5 months

1
0
0 0

[ACTIVITY] 8-12 January 2018

by Christophe Lyon

== Progress == * GCC - FDPIC - understood crash during program startup (self-relocation): self-relocated data is set read-only by the dynamic linker. * GCC upstream validation: - reported a couple of regressions - helped validating a couple of patches before they are committed * Infrastructure: * misc (conf-calls, meetings, emails, ....) == Next == * GCC/FDPIC * GCC upstream validation

7 years, 5 months

1
0
0 0

Does linaro toolchain support c++11 ??

by zhangwentao (M)

Hi all, I wonder if my compiler supports C++11? If not, where could I found the compiler supports c++11 (both 32bit and 64bit arm). THANKS a lot~~~ My compiler information is as below: wentao@ubuntu:~/test/lamda$ arm-eabi-g++ -v Using built-in specs. COLLECT_GCC=arm-eabi-g++ COLLECT_LTO_WRAPPER=/home/wentao/TeeOS/tools/gcc-linaro-6.3.1-2017.05-x86_64_arm-eabi/bin/../libexec/gcc/arm-eabi/6.3.1/lto-wrapper Target: arm-eabi Configured with: '/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/arm-eabi/snapshots/gcc.git~linaro-6.3-2017.05/configure' SHELL=/bin/bash --with-mpc=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/arm-eabi/_build/builds/destdir/x86_64-unknown-linux-gnu --with-mpfr=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/arm-eabi/_build/builds/destdir/x86_64-unknown-linux-gnu --with-gmp=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/arm-eabi/_build/builds/destdir/x86_64-unknown-linux-gnu --with-gnu-as --with-gnu-ld --disable-libmudflap --enable-lto --enable-shared --without-included-gettext --enable-nls --disable-sjlj-exceptions --enable-gnu-unique-object --enable-linker-build-id --disable-libstdcxx-pch --enable-c99 --enable-clocale=gnu --enable-libstdcxx-debug --enable-long-long --with-cloog=no --with-ppl=no --with-isl=no --enable-multilib --with-multilib-list=aprofile --enable-threads=no --disable-multiarch --with-newlib --with-build-sysroot=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/arm-eabi/_build/sysroots/arm-eabi --with-sysroot=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/arm-eabi/_build/builds/destdir/x86_64-unknown-linux-gnu/arm-eabi/libc --enable-checking=release --disable-bootstrap --enable-languages=c,c++,lto --build=x86_64-unknown-linux-gnu --host=x86_64-unknown-linux-gnu --target=arm-eabi --prefix=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/arm-eabi/_build/builds/destdir/x86_64-unknown-linux-gnu Thread model: single gcc version 6.3.1 20170404 (Linaro GCC 6.3-2017.05) wentao@ubuntu:~/test/lamda$ ===> And more, I wrote a "hello-world" program using c++11, it could work with host g++, but when I change to "arm-eabi-g++", it does not work. Information as below: wentao@ubuntu:~/test/lamda$ cat a.cc #include <iostream> using namespace std; typedef void(*Func)(); int main() { Func f = [=]() { cout <<"Hello world"<<endl; }; f(); return 0; } wentao@ubuntu:~/test/lamda$ g++ a.cc -o host a.cc: In function 'int main()': a.cc:10:2: warning: lambda expressions only available with -std=c++11 or -std=gnu++11 [enabled by default] }; ^ wentao@ubuntu:~/test/lamda$ ./host Hello world wentao@ubuntu:~/test/lamda$ arm-eabi-g++ a.cc -o arm32 a.cc: In function 'int main()': a.cc:10:2: error: cannot convert 'main()::<lambda()>' to 'Func {aka void (*)()}' in initialization }; ^ wentao@ubuntu:~/test/lamda$ arm-eabi-g++ --std=gnu++11 a.cc -o arm32 # if gives -std=c++11 , the error is the same. a.cc: In function 'int main()': a.cc:10:2: error: cannot convert 'main()::<lambda()>' to 'Func {aka void (*)()}' in initialization }; ^ wentao@ubuntu:~/test/lamda$

7 years, 5 months

1
0
0 0

[ACTIVITY] Week 01

by Yvan Roux

o 3 days off == Progress == o LLVM * TCWG-1317 (lencod miscompilation on clang-native-arm-lnt-perf bot): - Can't reproduce the miscompilation on the builder at a revision where it should - Issue fixed on the bot * TCWG-1324 (failures of Clang::atomic_ops.c and frem.ll on armv8l host): - Built the toolchains and start to investigate * Buildbots babysitting: - Investigate and reported upstream regressions o Misc * Catch-up after vacations

7 years, 5 months

1
0
0 0

[ACTIVITY] 2 - 5 January 2018

by Prathamesh Kulkarni

== This Week == * GCC bugs (8/10) a) PR83501 - Committed to trunk. b) PR82665 - Upstream iteration, waiting for final approval. c) PR83648 - Upstream iteration. d) PR81703 - Created a fix. e) PR83661 - Work in progress patch. * Public Holiday (2/10) == Next Week == - Continue ongoing tasks

7 years, 5 months

1
0
0 0

[ACTIVITY] 2-5 January 2018

by Christophe Lyon

* 1 day off (Monday) == Progress == * GCC - FDPIC - debugging crash during program startup (self-relocation) - fixed linker assert when using -static * GCC upstream validation: - reported a couple of regressions - incremental improvements for more robustness, and easier configuration of validations * Infrastructure: * misc (conf-calls, meetings, emails, ....) == Next == * GCC/FDPIC * GCC upstream validation

7 years, 5 months

1
0
0 0

[ACTIVITY] 02 - - 05 Jan 2018

by Yao Qi

* New year holiday # Progress # * GDB 8.1 release. 8.1 branch is created. Fix GDB and GDBserver build failure in release mode. Patches are posted. Looking at several test fails caused by new GCC emitting multiple line entries for the same line but with different columns, like, i = 1; j = 2; GDB can't step over the whole source line, and program stops at the middle of the source line. # Plan # * GDB 8.1 release. * Resume my pending patches on removing MAX_REGISTER_SIZE. -- Yao Qi

7 years, 5 months

1
0
0 0

Regarding license manifest for Linaro toolchain packages

by Ronak Desai

Hi, I am using the following linaro toolchain and need to create a license manifest in terms what are the packages are there, what license they use. https://releases.linaro.org/components/toolchain/binaries/ 5.2-2015.11-2/aarch64-linux-gnu/ I don't see any such manifest in the release archive nor in the toolchain archive. If such manifest is available then would you please point me to it. -- *Ronak A Desai*

7 years, 6 months

1
0
0 0

ACTIVITY] 18-22 December 2017

by Christophe Lyon

1 day off (Friday) == Progress == * GCC - FDPIC - debugging crash during program startup (self-relocation), and linker assert when using -static * GCC upstream validation: - reported a couple of regressions, tested a couple of patches for upstream - incremental improvements for more robustness, and easier configuration of validations * Infrastructure: * misc (conf-calls, meetings, emails, ....) == Next == Holidays until Jan 2nd, 2018 Merry Christmas and happy new year!

7 years, 6 months

1
0
0 0

[ACTIVITY] 11 - 15 Dec 2017

by Prathamesh Kulkarni

== This Week == * alloc_size propagation (6/10) - Prototype patch done * Sick leave (4/10) - Cough and Viral fevers == Next Week == - Continue ongoing tasks

7 years, 6 months

1
0
0 0

[ACTIVITY] 11th -- 15th Dec

by Yao Qi

# Progress # * GDB 8.1 release. [2/10] Triage regressions on aarch64 and arm. * PR 21698. [3/10] During the patch review, I doubt the patch fixes an invalid python use in gdb. The GDB doc is quite unclear on how that python api should be used. Ask the python api owner to clarify. * Misc, [5/10] Two days travel to Manchester. # Plan # * GDB 8.1 release. Fix regressions. -- Yao Qi

7 years, 6 months

1
0
0 0

[ACTIVITY] 11-15 December 2017

by Christophe Lyon

== Progress == * GCC - FDPIC - debugging crash during program startup (self-relocation) * GCC upstream validation: - reported a couple of regressions, tested a couple of patches for upstream - incremental improvements for more robustness, and easier configuration of validations * Infrastructure: - updated Jenkins job for GCC upstream monitoring * misc (conf-calls, meetings, emails, ....) == Next == * GCC/FDPIC * GCC upstream validation

7 years, 6 months

1
0
0 0

[ACTIVITY] 4th -- 8th Dec

by Yao Qi

# Progress # * TCWG-1125, ARMv8 tagged address support in GDB. Finish v3, and committed. Done. [5/10] * TCWG-1040, Update my patches to remove the last use of MAX_REGISTER_SIZE. No response, people are busy on release. * GDB 8.1 release. [2/10] PR gdb/21698. It is a regression. Fixed. * Misc, [3/10] # Plan # * GDB 8.1 release, testing for ARM and AArch64. -- Yao Qi

7 years, 6 months

1
0
0 0

[ACTIVITY] Week 49

by Yvan Roux

== Progress == o Linaro GCC/Validation * 6.4 an 7.2 2017.11 snapshots deployed. o LLVM ramp-up * Buildbots babysitting: - Investigate and reported upstream regressions * Patch benchmarking job (TCWG-1306): - Start to look at it * Upstream BZ 32999: - Still on-going o Misc * Various meetings and discussions.

7 years, 6 months

1
0
0 0

[ACTIVITY] 4-8 December 2017

by Christophe Lyon

== Progress == * GCC - FDPIC - debugged linker assert while building gcc target libs - now debugging crash during program startup (self-relocation) * GCC upstream validation: - reported a couple of regressions - a few more improvements to handle random infrastructure problems - experimenting with new builders * Infrastructure: - updated Jenkins job for GCC upstream monitoring * misc (conf-calls, meetings, emails, ....) == Next == * GCC/FDPIC * GCC upstream validation

7 years, 6 months

1
0
0 0

[ANNOUNCE] Linaro GCC 6 and 7 2017.11 source snapshots

by Mark Murray

The Linaro Toolchain Working Group (TCWG) is pleased to announce the 2017.11 snapshot of Linaro GCC 6 and 7 source packages. o The GCC 7 series introduced an ABI change for ARM targets by fixing a bug (present since GCC 5, see link below) that affects conformance to the procedure call standard (AAPCS). The bug affects some C++ code where class objects are passed by value to functions and could result in incorrect or inconsistent code being generated. If the option -Wpsabi is enabled (on by default) the compiler will emit a diagnostic note for code that might be affected by this ABI change. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77728 For an explanation of the changes please see the following website: https://gcc.gnu.org/gcc-7/changes.html o Linaro GCC 7 monthly snapshot[1] is based on FSF GCC 7.2+svn254792 and includes performance improvements and bug fixes backported from mainline GCC. The contents of this snapshot will be part of the 2018.02 stable[2] quarterly release. This snapshot tarball is available on: http://snapshots.linaro.org/components/toolchain/gcc-linaro/7.2-2017.11/ Interesting changes in this GCC source package snapshot include: * Updates to GCC 7.2+svn254792 o Linaro GCC 6 monthly snapshot[1] is based on FSF GCC 6.4+svn254791 and includes performance improvements and bug fixes backported from mainline GCC. This snapshot contents will be part of the next maintenance release. This snapshot tarball is available on: http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.4-2017.11/ Interesting changes in this GCC source package snapshot include: * Updates to GCC 6.4+svn254791 o 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 * Interested in commercial support? inquire at "Linaro support": mailto:support@linaro.org [1]. Source package snapshots are defined when the compiler is only put through unit-testing and full validation is not performed. [2]. Stable source package releases are defined as releases where the full Linaro Toolchain validation plan is executed. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

7 years, 6 months

1
0
0 0

[ACTIVITY] 27 November - 1 December 2017

by Prathamesh Kulkarni

== This Week == * TCWG-1234 (6/10) - WIP patch * Public Holiday (2/10) * Misc (2/10) - PR83142 - Meetings == Next Week == - Continue ongoing tasks

7 years, 7 months

1
0
0 0

[ACTIVITY] Week 48

by Yvan Roux

* One day off * One day sick and half one in the snow == Progress == o Linaro GCC/Validation * GCC 6.4 and 7.2 binary releases deployed * 2017.11 snapshots: - 6.4 and 7.2 ready to be deployed o LLVM ramp-up * Upstream BZ 32999: - Struggled to construct the testcases which produce the DAGs needed for a good coverage - Re-working sub-vectors indexes logic to handle these testcases. o Misc * Various meetings and discussions.

7 years, 7 months

1
0
0 0

[ACTIVITY] 27th Nov -- 1st Dec

by Yao Qi

# Progress # * TCWG-1040, [6/10] Update my patches to remove the last use of MAX_REGISTER_SIZE. Post the whole patch series as an RFC. There are 15 patches, but I rewrote them in seven times. This version is quite satisfying. Targeting to GDB 8.2. One patch can't be merged until 8.1 is branched. * TCWG-1125, ARMv8 tagged address support in GDB. Writing v3. [2/10] * Misc, [2/10] # Plan # * TCWG-1125, * GDB 8.1 release. Testing for ARM and AArch64. -- Yao Qi

7 years, 7 months

1
0
0 0

[ACTIVITY] 27 November - 1 December 2017

by Christophe Lyon

== Progress == * GCC - FDPIC:debugging linker assert while building gcc target libs * GCC upstream validation: - reported a couple of regressions * Infrastructure: * misc (conf-calls, meetings, emails, ....) == Next == * GCC/FDPIC * GCC upstream validation

7 years, 7 months

1
0
0 0

[ACTIVITY] 20 - 24 November 2017

by Prathamesh Kulkarni

== This Week == * TCWG-1234 (6/10) - Using dfs to compute bb dist - Reading through rest of PRE/SCCVN to better understand the infrastructure * PR82808 (2/10) - Trying to find an approach to pass parm_type from all callers. - Martin posted a patch to address the parm_type issue. * Misc (2/10) - Meetings - Filed PR83194, browsing through other PR's. == Next Week == - Continue ongoing tasks

7 years, 7 months

1
0
0 0

[ANNOUNCE] Linaro Binary Toolchain Release GCC 7.2-2017.11

by Mark Murray

The Linaro Binary Toolchain ============================ The Linaro GCC 7.2-2017.11 Release is now available. *Notice*: GCC 7.1 ABI change for arm*-*-* targets, and note for aarch64*-*-* targets From GCC 7.1 release notes: On ARM targets (arm*-*-*), a bug introduced in GCC 5 that affects conformance to the procedure call standard (AAPCS) has been fixed. The bug affects some C++ code where class objects are passed by value to functions and could result in incorrect or inconsistent code being generated. This is an ABI change. If the option -Wpsabi is enabled (on by default) the compiler will emit a diagnostic note for code that might be affected. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77728 GCC 5 and GCC 6 releases will continue to be affected by the ABI bug, since changing ABI in these releases is not practical. A warning enabled by -Wpsabi option was added to GCC 5 and GCC 6 toolchains to diagnose codebases that might be affected by the ABI bug. Additionally, this same bug was present in AArch64 backend in development versions of GCC 7. There was no releases of GCC with this bug present in AArch64 backend, therefore the release notes does not mention this. However, be advised that any code bases built with development versions of GCC 7 need to be recompiled with released version of GCC 7 to conform to ABI. For an explanation of GCC 7 series changes please see the following website: https://gcc.gnu.org/gcc-7/changes.html For help in porting to GCC 7 please see the following explanation: https://gcc.gnu.org/gcc-7/porting_to.html Download release packages from: (sources) http://releases.linaro.org/components/toolchain/gcc-linaro/7.2-2017.11/ (binaries) http://releases.linaro.org/components/toolchain/binaries/7.2-2017.11/ Previous snapshots and release-candidates are at: http://snapshots.linaro.org/components/toolchain/binaries/ Previous releases are at: http://releases.linaro.org/components/toolchain/binaries/ A description of the arm and AArch64 target triples can be found at: https://collaborate.linaro.org/display/TCWGPUB/ARM+and+AArch64+Target+Tripl… Host Requirements ================== Linaro officially supports the current and previous Ubuntu LTS releases (as of the time of this release). This does not mean that the toolchain will not work on other/older Linux distributions. See the following for the life-time of Ubuntu LTS releases. https://wiki.ubuntu.com/Releases The host system upon which the cross-compiler will run requires a minimum of glibc 2.14, because of API changes to glibc's memcpy API. https://bugs.linaro.org/show_bug.cgi?id=1869 Package Versions ================= Linaro GCC 7.2-2017.11 http://releases.linaro.org/components/toolchain/gcc-linaro/7.2-2017.11/ FSF glibc 2.25 (release/2.25) https://lists.gnu.org/archive/html/info-gnu/2017-02/msg00002.html Newlib 2.5 (newlib-2_5_0 tag) https://sourceware.org/ml/newlib/2016/msg01191.html GNU Binutils 2.28 (users/linaro/binutils-2_28-branch) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=bin… FSF GDB 8.0 (gdb-8.0-branch) https://sourceware.org/ml/gdb-announce/2017/msg00003.html Linaro toolchain package git branches are hosted at: http://git.linaro.org/toolchain NEWS for GCC 7 (as of Linaro GCC 7.2-2017.11) ============================================== * The Linaro GCC 7.2-2017.09 snapshot added float and integer moves improvement for AArch64 targets. * The Linaro GCC 7.1-2017.07 snapshot added prefetching configuration improvement for AArch64 targets and laid groundwork to enabling prefetching in more cases. * Previous MinGW hosted version of Linaro GCC C preprocessor failed to convert character set used for string, character constants, etc. This is fixed in this release. Linaro bugzilla #3040 : CC1 and cc1plus cannot convert UTF-8. https://bugs.linaro.org/show_bug.cgi?id=3040 * Performance related backports from the following snapshots have been included: Linaro GCC 7.1-2017.05, Linaro GCC 7.1-2017.06, Linaro GCC 7.1-2017.07, Linaro GCC 7.2-2017.08, Linaro GCC 7.2-2017.09 and Linaro GCC 7.2-2017.10. See the following Linaro GCC snapshots: http://snapshots.linaro.org/components/toolchain/gcc-linaro/7.1-2017.05/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/7.1-2017.06/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/7.1-2017.07/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/7.2-2017.08/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/7.2-2017.09/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/7.2-2017.10/ Contact Linaro =============== File bugs at http://bugs.linaro.org For Linaro member support see http://support.linaro.org For Linaro community support email linaro-toolchain(a)lists.linaro.org IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

7 years, 7 months

1
0
0 0

[ANNOUNCE] Linaro Binary Toolchain Release GCC 6.4-2017.11

by Mark Murray

The Linaro Binary Toolchain ============================ The Linaro GCC 6.4-2017.11 Release is now available. The GCC 6 Release series has significant changes from the GCC 5 release series. For an explanation of the changes please see the following website: https://gcc.gnu.org/gcc-6/changes.html For help in porting to GCC 6 please see the following explanation: https://gcc.gnu.org/gcc-6/porting_to.html Download release packages from: (sources) http://releases.linaro.org/components/toolchain/gcc-linaro/6.4-2017.11/ (binaries) http://releases.linaro.org/components/toolchain/binaries/6.4-2017.11/ Previous snapshots and release-candidates are at: http://snapshots.linaro.org/components/toolchain/binaries/ Previous releases are at: http://releases.linaro.org/components/toolchain/binaries/ A description of the arm and AArch64 target triples can be found at: https://collaborate.linaro.org/display/TCWGPUB/ARM+and+AArch64+Target+Tripl… Host Requirements ================== Linaro officially supports the current and previous Ubuntu LTS releases (as of the time of this release). This does not mean that the toolchain will not work on other/older Linux distributions. See the following for the life-time of Ubuntu LTS releases. https://wiki.ubuntu.com/Releases The host system upon which the cross-compiler will run requires a minimum of glibc 2.14, because of API changes to glibc's memcpy API. https://bugs.linaro.org/show_bug.cgi?id=1869 Package Versions ================= Linaro GCC 6.4-2017.11 http://releases.linaro.org/components/toolchain/gcc-linaro/6.4-2017.11/ Linaro glibc 2.23 (linaro/2.23/master) https://lists.gnu.org/archive/html/info-gnu/2016-02/msg00009.html Linaro newlib 2.4-2016.03 (linaro_2.4-branch) https://sourceware.org/ml/newlib/2016/msg00370.html Linaro binutils 2.27 (users/linaro/binutils-2_27-branch) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=bin… Linaro GDB 8.0 (gdb-8.0-branch) https://lists.gnu.org/archive/html/info-gnu/2016-10/msg00007.html Linaro toolchain package git branches are hosted at: http://git.linaro.org/toolchain NEWS for GCC 6 (as of Linaro GCC 6.4-2017.11) ============================================== * Previous MinGW hosted version of Linaro GCC C preprocessor failed to convert character set used for string, character constants, etc. This is fixed in this release. Linaro bugzilla #3040 : CC1 and cc1plus cannot convert UTF-8. https://bugs.linaro.org/show_bug.cgi?id=3040 * The Linaro GCC 6.3-2017.05 snapshot added support for -mpure-code option to ARMv7-M and ARMv8-M targets. This option ensures functions are put into sections that contain only code and no data. * The GDB version was upgraded from GDB 8.0. * Previous versions of the Linaro GCC 6 toolchain, when -static -E/—dynamic-list are passed to the linker, might create executables with dynamic sections which aren’t supported by run-time. This was exhibited in Perf Tools build system and has been fixed upstream and backported into Linaro Binutils 2.27 branch. Linaro bugzilla #2926 : Perf tools compiled statically for AArch64 with Linaro release 6.1 and later ones was not statically linked. https://bugs.linaro.org/show_bug.cgi?id=2926 * The Linaro GCC 6.3-2017.03 snapshot fixed some ILP32 issues (TLS, exception handling, …) and these have been incorporated into this release. * Previous versions of the Linaro GCC 6 toolchain were incorrectly generating floating-point code for soft-float Linux targets (arm-linux-gnueabi, and armeb-linux-gnueabi). This escaped detection until recently because the soft-float targeted toolchains were configured to use general-purpose registers for passing floating-point values (which is what you would expect for soft-float toolchains) and the intra-routine floating-code was not noticed. The issue would only show up on targets that were run on hardware that truly didn't have floating-point hardware where the kernel did not trap and emulate floating-point routines. This has been solved in Linaro GCC 6.3-2017.02-rc2 by configuring the toolchain (using --with-float=soft) to generate code without any floating-point instructions at all (-mfloat-abi=soft). https://review.linaro.org/#/c/16968/2 This change should not break compatibility between existing binaries compiled with these toolchains since the float-point parameter passing ABI is still the same. * A bug/regression in the compiler has been identified whereby the target function that is invoked when calling a "weak" function directly is the "strong" override, whereas when calling the function via a pointer the "weak" implementation is used. This would be noticed as inconsistent function invocation when invoking directly vs. invoking via function pointer. This issue only affected 32-bit arm targets. This regression has been fixed upstream and backported into Linaro GCC 6.3-2017.02-rc2. GCC PR target/78253: [5/6/7 Regression] [ARM] call weak function instead of strong when called through pointer. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78253 Linaro bugzilla #2562: ARM GCC 5.2 call weak function instead of strong when called through pointer https://bugs.linaro.org/show_bug.cgi?id=2562 * MS Windows does not support symlinks and the MS Windows archive extractor does not properly deep copy the symlink target files/directories into the symlinked directory structure when unpacking the toolchain archive. This causes problems with missing dependencies when using the Linaro mingw toolchains, as identified in the following bugs: https://bugs.linaro.org/show_bug.cgi?id=2684 https://bugs.linaro.org/show_bug.cgi?id=2192 https://bugs.linaro.org/show_bug.cgi?id=2762 This has been solved by copying files rather than using symlinks when the mingw targetted toolchain archives are created. https://review.linaro.org/#/c/16415/ * Users of Linaro's toolchain have encountered problems when building projects with Autotools (specifically libtool): https://bugs.linaro.org/show_bug.cgi?id=2764 The Linaro binary toolchain release contained files with a .la suffix as artifacts of the toolchain build process. These .la files are helper files for libtool, but unlike a gcc install tree, they are not position independent and contain full paths. Since these artifacts contain absolute paths they can actually mislead user invocation of libtool into not finding required libraries (because they reference the build tree, not the install location) and hence breaking Autotools builds. These *.la file artifacts have been removed from Linaro toolchain binaries because they are unnecessary for users. * The Linaro GCC 6.3-2017.01 snapshot added further enablement for ARMv8-M and these have been incorporated into this release. * Compiling and statically linking some SPEC2006int tests against tcmalloc have been failing due to a problem with glibc's memory allocator function overrides. This was fixed upstream: https://sourceware.org/bugzilla/show_bug.cgi?id=20432 Backported into Linaro glibc 2.23: commit 058b5a41d56b9a8860dede14d97dd443792d064b Author: Florian Weimer <fweimer(a)redhat.com> Date: Fri Aug 26 22:40:27 2016 +0200 malloc: Simplify static malloc interposition [BZ #20432] * Host binaries for x86_64 linux hosts now have symbols and debug information stripped in order to reduce the size of the toolchain binary archives. This reduces the archive size from 1.5G to 600M for aarch64-linux-gnu target with the gcc-6-branch. * The GDB version was upgraded from GDB 7.11 in the Linaro GCC 6.1-2016.08 release to GDB 7.12 in the Linaro GCC 6.2-2016.11 release. * The Linaro GCC 6.2-2016.10 snapshot added AArch32 support for ARMv8.2 and ARMv8m, as well as some AArch64 fixes for ARMv8.2, and bug fixes merged from FSF GCC 6.2. This is available in the binary toolchain as of Linaro GCC 6.2-2016.11. * Basic tuning support for the Qualcomm qdf24xx was added to the Linaro GCC 6.2-2016.10 snapshot and is available in the binary toolchain as of Linaro GCC 6.2-2016.11. * IFUNC was disabled for baremetal targets, as it was causing test-suite failures, and is presently a Linux only feature. * The gold linker was added to this binary release. * Backported malloc_lock fix into Linaro newlib 2.4. commit 2665915cfc46aa6403bb2efd473c523d3167e0cb Author: Andre Vieira (lists) <Andre.SimoesDiasVieira(a)arm.com> Date: Thu Jun 16 12:23:51 2016 +0100 Re-enable malloc_lock for newlib-nano * Backported rawmemchr patch into Linaro newlib 2.4. commit e7b1ee2ea6aa3ee1da41976407410e6202a098c5 Author: Wilco Dijkstra <Wilco.Dijkstra(a)arm.com> Date: Thu May 12 16:16:58 2016 +0000 Add rawmemchr * Backported strlen fix when using Thumb-2 and -Os -marm into Linaro newlib 2.4. commit 5c02bcc086a96b174e1b9e1445a4a1770070107a Author: Thomas Preud'homme <thomas.preudhomme(a)arm.com> Date: Wed May 11 17:18:48 2016 -0400 Fix strlen using Thumb-2 with -Os -marm * Backported fix for semihosting ARM when heapinfo not provided by debugger into Linaro newlib 2.4. commit 5c9403eaf40951f8a4f55ed65f661b485ff44be7 Author: David Hoover <spm2(a)dangerous.li> Date: Thu Apr 21 07:12:24 2016 +0200 Fixed semihosting for ARM when heapinfo not provided by debugger. * Merged latest FSF glibc release/2.23/master into Linaro glibc 2.23. * Backported __ASSUME_REQUEUE_PI check Linaro glibc 2.23 branch. commit 2d20c3bf918cd94ebd4106693adb3a5c9272baba Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> Date: Tue May 17 10:16:39 2016 -0300 Add runtime check for __ASSUME_REQUEUE_PI (BZ# 18463) * Backported removal of __ASSUME_SET_ROBUST_LIST from Linaro glibc 2.23 branch. commit bb8f09d72756186a3d82a1f7b2adcf8bc1fbaed1 Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> Date: Mon May 16 19:01:10 2016 -0300 Remove __ASSUME_SET_ROBUST_LIST * Backported removal of __ASSUME_FUTEX_LOCK_PI from Linaro glibc 2.23 branch. commit e48b4e7fed0de06dd7832ead48bea8ebc813a204 Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> Date: Mon May 16 10:35:25 2016 -0300 Remove __ASSUME_FUTEX_LOCK_PI * Merged latest FSF binutils-2_27-branch into linaro_binutils-2_27-branch. * The libwinpthread DLL is now copied into the host bin directory to satisfy mingw package dependencies. * Backported GNU Linker fix. commit fbc6c6763e70cb2376e2de990c7fc54c0ee44a59 Author: Nick Clifton <nickc(a)redhat.com> Date: Tue Aug 23 09:45:11 2016 +0100 Fix seg-fault in ARM linker when trying to parse a binary file. * Backported GNU Assembler fix for PR 20364 commit 5fe7ebe5ab43750abf8f490b785d99a1e598e7fd Author: Nick Clifton <nickc(a)redhat.com> Date: Fri Aug 5 10:37:57 2016 +0100 Fix the generation of alignment frags in code sections for AArch64. https://sourceware.org/bugzilla/show_bug.cgi?id=20364 * Performance related backports from the following snapshots have been included: Linaro GCC 6.1-2016.06, Linaro GCC 6.1-2016.07, Linaro GCC 6.1-2016.08, Linaro GCC 6.2-2016.09, Linaro GCC 6.2-2016.10, Linaro GCC 6.2-2016.11, Linaro GCC 6.2-2016.12, Linaro GCC 6.3-2017.01, Linaro GCC 6.3-2017.02, Linaro GCC 6.3-2017.03, Linaro GCC 6.3-2017.04, Linaro GCC 6.3-2017.05, Linaro GCC 6.3-2017.06, Linaro GCC 6.4-2017.07, Linaro GCC 6.4-2017.08, Linaro GCC 6.4-2017.09 and Linaro GCC 6.4-2017.10 . See the following Linaro GCC snapshots: http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.1-2016.06/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.1-2016.07/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.1-2016.08/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.2-2016.09/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.2-2016.10/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.2-2016.11/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.2-2016.12/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.3-2017.01/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.3-2017.02/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.3-2017.03/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.3-2017.04/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.3-2017.05/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.3-2017.06/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.4-2017.07/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.4-2017.08/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.4-2017.09/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.4-2017.10/ Contact Linaro =============== File bugs at http://bugs.linaro.org For Linaro member support see http://support.linaro.org For Linaro community support email linaro-toolchain(a)lists.linaro.org IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

7 years, 7 months

1
0
0 0

[ACTIVITY] Week 47

by Yvan Roux

* 2 days off (Internal Training) == Progress == o Linaro GCC/Validation * Final GCC 5.5 release deployed and announced * GCC 6.4 and 7.2 deployed * 2017.11 snapshots on-going (branch merges done) o LLVM ramp-up * Upstream BZ 32999: - Addressing upstream comments. * Upstream BZ 35272: - Analysed and commented upstream. o Misc * Various meetings and discussions. == Plan == o Continue on on-going LLVM Bugs. o Wednesday off

7 years, 7 months

1
0
0 0

[ACTIVITY] 20-24 Nov

by Yao Qi

# Progress # * TCWG-1040, [4/10] Update my patches to remove the last use of MAX_REGISTER_SIZE. Commit my 1/6 patch series. Prepare 2/6 patch series. Need to be sync'ed with GDB 8.1 release. * TCWG-1159, [4/10] GDB flexible target description conversion. Commit patch for tic6x, and ready to post patches for nios2. * Run GDB testsuite with CLANG. [1/10] Commit my patches, but leave some controversial patches in my tree. Now, I get some reasonable GDB test result with clang. * Upstream patches review. [1/10] Approved four Alan's patches. # Plan # * ARMv8 tagged pointer support in GDB. * Update my patches to remove the last use of MAX_REGISTER_SIZE. -- Yao Qi

7 years, 7 months

1
0
0 0

[ACTIVITY] 20-24 November 2017

by Christophe Lyon

== Progress == * GCC - FDPIC: hitting a linker assert while building gcc target libs * GCC upstream validation: - reported a few regressions, fixed a couple of obvious errors - struggling with ST-internal infrastructure difficulties * Infrastructure: - looking at ABE & building a native toolchain from a manifest * misc (conf-calls, meetings, emails, ....) - became 1 year older :) == Next == * GCC/FDPIC * GCC upstream validation

7 years, 7 months

1
0
0 0

[ANNOUNCE] Linaro Binary Toolchain Final Release GCC 5.5-2017.10

by Mark Murray

The Linaro Binary Toolchain ============================ The Linaro GCC 5.5-2017.10 Final Release is now available. Notice: All Linaro GCC 5 series toolchain users should migrate to the latest version of the Linaro GCC 5 toolchain in order to mitigate potential security exposure to CVE-2015-7547. See the NEWS section below for details. Download release packages from: (sources) http://releases.linaro.org/components/toolchain/gcc-linaro/5.5-2017.10/ (binaries) http://releases.linaro.org/components/toolchain/binaries/5.5-2017.10/ Previous snapshots and release-candidates are at: http://snapshots.linaro.org/components/toolchain/binaries/ Previous releases are at: http://releases.linaro.org/components/toolchain/binaries/ A description of the arm and AArch64 target triples can be found at: https://collaborate.linaro.org/display/TCWGPUB/ARM+and+AArch64+Target+Tripl… Host Requirements ================== Linaro officially supports the current and previous Ubuntu LTS releases (as of the time of this release). This does not mean that the toolchain will not work on other/older Linux distributions. See the following for the life-time of Ubuntu LTS releases. https://wiki.ubuntu.com/Releases The host system upon which the cross-compiler will run requires a minimum of glibc 2.14, because of API changes to glibc's memcpy API. https://bugs.linaro.org/show_bug.cgi?id=1869 Package Versions ================= Linaro GCC 5.5-2017.10 http://releases.linaro.org/components/toolchain/gcc-linaro/5.5-2017.10/ Linaro glibc 2.21 (linaro/2.21) https://lists.gnu.org/archive/html/info-gnu/2015-02/msg00001.html Linaro newlib 2.1.0-2014.09 (linaro_newlib-branch) https://sourceware.org/ml/newlib/2013/msg01128.html Linaro binutils 2.25 (users/linaro/binutils-2_25-branch) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=bin… FSF GDB 8.0 (gdb-8.0-branch) https://sourceware.org/ml/gdb-announce/2017/msg00001.html Linaro toolchain package git branches are hosted at: http://git.linaro.org/toolchain NEWS for GCC 5 (as of Linaro GCC 5.5-2017.10) ============================================== * Include Binutils fix for bugzilla #20364: Data-based padding causes current address evaluation to be non-constant on aarch64 https://sourceware.org/bugzilla/show_bug.cgi?id=20364 * Include GCC fix for Linaro bugzilla #2575: ICE: declaration and definition of function with __attribute__((target("thumb"))) and inlined assembler, with debug symbols enabled https://bugs.linaro.org/show_bug.cgi?id=2575 * Include GCC fix for Linaro bugzilla #2575: Internal compiler error using -mtune=cortex-a57.cortex-a53. https://bugs.linaro.org/show_bug.cgi?id=2785 * The soft-float targeted toolchains have now been configured to generate code using -mfloat-abi=soft. This makes arm-linux-gnueabi and armeb-linux-gnueabi toolchains use the “soft” FP ABI instead of “softfp”. Historically, TCWG’s toolchains provided both “soft” and “softfp” multilibs, but when switching from crosstool-ng to cbuildv2/abe (which support a single multilib) “softfp” multilib was choosen. Using “-mfloat-abi=soft” is a better choice for a gnueabi toolchain, since it doesn’t require cores to have a floating-point unit. This change should not break compatibility for toolchain users since the ABI will stay the same. The compiler and glibc libraries will not refernce FP instructions. * Include GCC fix for Linaro bugzilla #2562: ARM GCC 5.2 call weak function instead of strong when called through pointer https://bugs.linaro.org/show_bug.cgi?id=2562 * Include GCC fix for Linaro bugzilla #1925: [regression] FAIL: libgomp.fortran/retval1.f90 -O1 execution test https://bugs.linaro.org/show_bug.cgi?id=1925 * Include GCC fix for Linaro bugzilla #2185: aarch64-linux-gnu-g++ internal compiler error: in curr_insn_transform https://bugs.linaro.org/show_bug.cgi?id=2185 * Backported glibc patch to simplify static malloc interposition [BZ #20432] to correct user identified issue. commit 058b5a41d56b9a8860dede14d97dd443792d064b Author: Florian Weimer Date: Fri Aug 26 22:40:27 2016 +0200 malloc: Simplify static malloc interposition [BZ #20432] * Host binaries for x86_64 linux hosts now have symbols and debug information stripped in order to reduce the size of the toolchain binary archives. This reduces the archive size from 1.1G to 580M for aarch64-linux-gnu target with the gcc-5-branch. * Removed .la files from binary toolchain archive as these files break autotools builds. https://bugs.linaro.org/show_bug.cgi?id=2764 * The mingw toolchains are now archived using the rsync -L option in order to avoid problems with Windows extractors and symbolic links. https://review.linaro.org/#/c/16415/ This resolves the following user bugs: https://bugs.linaro.org/show_bug.cgi?id=2684 https://bugs.linaro.org/show_bug.cgi?id=2192 https://bugs.linaro.org/show_bug.cgi?id=2762 * Copy the libwinpthread DLL into the bin directories so it gets into the tmp directory before tar is run. https://review.linaro.org/#/c/13723/ * Increment binutils release date to 2016_02 to reflect the most recent commit: commit ef90a4718f535cbe6345b4e7168baea7b1972abf Author: Matthew Wahab <matthew.wahab(a)arm.com> Date: Tue Jan 12 16:35:30 2016 +0000 [ARM] Support ARMv8.2 RAS extension. * Baremetal sysroot names now contain 'newlib' rather than 'glibc'. * Manifests now contain relative paths rather than absolute paths. * Now generating proper manifest files. * Fixed pi requeue support in glibc 2.21 while allowing the existing 2.21 minimum kernel default setting. This was checked into the linaro/2.21/master branch. commit a68cafa11c500d8a49a3014c43c5152859d037ae Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> Date: Tue May 17 10:16:39 2016 -0300 Add runtime check for __ASSUME_REQUEUE_PI (BZ# 18463) commit 6e5cb616b5b442ce8b2664ad673c0acf42a490ac Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> Date: Mon May 16 19:01:10 2016 -0300 Remove __ASSUME_SET_ROBUST_LIST commit 9ac61c0047295696cbcdbc26bdc174c7bd25a3c8 Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> Date: Mon May 16 10:35:25 2016 -0300 Remove __ASSUME_FUTEX_LOCK_PI * Backported support into GCC for Cortex-A32, Cortex-A35, and Cortex-R8. * Applied fix for CVE-2015-7547 - A stack-based buffer overflow in glibc's getaddrinfo() was corrected in glibc 2.23 and backported into glibc 2.21. https://sourceware.org/ml/libc-alpha/2016-02/msg00416.html * ARMv8.1 Instruction Support - ARMv8.1 instructions support was checked into GCC and binutils. It has been backported into Linaro GCC 5.3 and Linaro binutils 2.25. * Backported -Bsymbolic-functions into Linaro binutils 2.25. * Performance related backports from Linaro GCC 5.2-2015.11, Linaro GCC 5.2-2015.12, and Linaro GCC 5.3-2016.01-1, Linaro GCC 5.3-2016.02, Linaro GCC 5.3-2016.03, Linaro GCC 5.3-2016.04, Linaro GCC 5.4-2016.06, Linaro GCC 5.4-2016.10, Linaro GCC 5.4-2016.12, Linaro GCC 5.4-2017.02, GCC 5.4-2017.04 and Linaro GCC 5.5-2017.10 have been included. See the following Linaro GCC snapshots: http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.2-2015.11/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2015.12/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.01-1/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.02 http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.03 http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.04 http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.4-2016.06 http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.4-2016.10 http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.4-2016.12 http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.4-2017.02 http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.4-2017.04 http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.5-2017.10 Contact Linaro =============== File bugs at http://bugs.linaro.org For Linaro member support see http://support.linaro.org For Linaro community support email linaro-toolchain(a)lists.linaro.org IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

7 years, 7 months

1
0
0 0

[ACTIVITY] 13 - 17 November 2017

by Prathamesh Kulkarni

== This Week == * PR82665 (3/10) - Submitted patch upstream - Blocked on POINTER_DIFF_EXPR patch by Marc Glisse. * PR82808 (1/10) - Submitted another fix but was rejected by Richard. * TCWG-1234 (4/10) - Tried tweaking with register allocator, but to no effect - Trying to think about possible approaches for stage-3 fixes. * Misc (2/10) - Meetings - Managed to get autofdo working == Next Week == - Continue ongoing tasks

7 years, 7 months

1
0
0 0

[ACTIVITY] 13-17 November 2017

by Christophe Lyon

== Progress == * GCC - FDPIC: rebased binutils patches, debugging CI loop. * GCC upstream validation: - iterating on qemu/sanitizers problems. Found a bug in arm sanitizer libs, already fixed upstream. Requested a new merge in GCC. - reported a few regressions * Infrastructure: - looking at ABE & building a native toolchain from a manifest * misc (conf-calls, meetings, emails, ....) - started looking at hcqc == Next == * GCC/FDPIC * GCC upstream validation

7 years, 7 months

1
0
0 0

[ACTIVITY] Nov 13 -- Nov 17

by Yao Qi

# Progress # * TCWG-1040, [4/10] Update my patches to remove the last use of MAX_REGISTER_SIZE. Get everything in shape. Post my 1/6 patch series. * TCWG-1159, [4/10] GDB flexible target description conversion. Post patch for tic6x, and write the patch for nios2. * ILP32 GDB. [1/10] Chat with Maxim, triage some test failures. * Open GCC PR 83010. AArch64 GCC doesn't generate DW_AT_location for TLS variable. It causes some GDB test failures. CLANG+GOLD can correctly generate DW_AT_location. * Run GDB testsuite with CLANG. [1/10] Post three patches to GDB testsuite to compile test cases with CLANG. # Plan # * TCWG-1125, ARMv8 tagged address support in GDB. -- Yao Qi

7 years, 7 months

1
0
0 0

arm-eabi toolchain memcpy using hard float causing unaligned access

by Yupeng Chang

Hi Linaro Team, I'm currently using toolchain gcc-linaro-7.1.1-2017.08-x86_64_arm-eabi.tar.xz <https://releases.linaro.org/components/toolchain/binaries/latest/arm-eabi/g…> to develop my bera-metal programs. My compile option is "-marm -march=armv7-a -mtune=cortex-a9 -mlittle-endian -mfloat-abi=hard -mfpu=neon" I found an issue, when I use memcpy, and if the DEST or SOURCE address is not 4 bytes aligned, the system hangs. It seems that this toolchain doesn't support using hard float and NEON ? My question is does this toolchain support hard float and NEON in the newlib C library? If I want to use hard float and NEON, how can I do that? Your reply is more appreciated!!

7 years, 7 months

2
3
0 0

ILP32 toolchain status update

by Maxim Kuvyrkov

Over the last couple of months arm64 community and us have tested various aspects of ILP32 toolchain and, while most of toolchain works as expected, several features are still missing. Most of the work left is on GDB side, especially using LP64 GDB to debug ILP32 applications. 1. [GCC] GCC sanitizers (ASAN, UBSAN) are not supported for ILP32. -- TCWG is working on implementing sanitizer support for ILP32. 2. [GLIBC] LP64 glibc libthread_db does not support ILP32. This causes failures when LP64 GDB is trying to debug ILP32 threaded application. It is expected by users to be able to use LP64 GDB to debug ILP32 applications (LP64 AArch64 GDB can successfully debug AArch32 applications already!). -- Steve, do you plan to work on adding libthread_db support for ILP32? 3. [GDB] Handle ILP32 siginfo layout. Kernel siginfo layout is different between LP64 and ILP32. 4. [GDB] Inferior call passing pointer argument. GDB may need update to handle 32-bit pointer vs 64-bit pointer. 5. Handle shared libraries. GDB needs to read a linked list out of the inferior, and that list is about the libraries loaded already. LP64 and ILP32 may have different layouts. 6. [GDB] GDB resolves ifunc functions, needs to read auxv (HWCAP) from the inferior. auxv is different on LP64 and ILP32. 7. [GDB] Gdbserver support for ILP32. -- Maxim Kuvyrkov www.linaro.org

7 years, 7 months

4
10
0 0

[ACTIVITY] 6 - 10 November 2017

by Prathamesh Kulkarni

== This Week == * TCWG-1234 (2/10) - Came up with another fix which works on my test-case but not on actual regression * PR82808 (2/10) - Modified patch based on upstream suggestions. * PR82665 (4/10) - Untested fix * Misc (2/10) - Meetings - Reading ipa mod/ref paper - Looked at autofdo == Next Week == - Continue ongoing tasks

7 years, 7 months

1
0
0 0

[ACTIVITY] Week 45

by Yvan Roux

== Progress == o Linaro GCC/Validation * GCC 6 and 7 2017.11 RC1 deployed * Fixed Binutils branch used for 5.5 release * Investigate and fixed Python3 issues in release notes script (patch under review) o LLVM ramp-up * Upstream bug 32999: - Still tracking corner cases * Looking at zero/sign-extension elimination status o Misc == Plan == o Release handover o LLVM tasks (Bug 32999, sign-extension)

7 years, 7 months

1
0
0 0

ILP32 sysroot image

by Adhemerval Zanella

Hi all, I just upload an sysroot image for ILP32 meant to be used on both testing and development on dev-01.tcwglab [1]. It is based on out current ILP32 GCC 7 sysroot plus some tools and it is meant to easier development and testing. It should have all native required tools for GNU development: glibc 2.27 (arm/ilp32 branch) gcc 7.2.1 (linaro/gcc-7-branch) binutils 2.28.2 (linaro_binutils-2_28-branch) gmp 6.1.2 mpfr 3.1.6 mpc 1.0.3 coreutils 8.28 bash 4.4.12 gnumake 4.2 (plus a patch to fix glob usage on glibc 2.27) gawk 4.2 perl 5.26.1 textinfo 6.5 bison 3.0.3 m4 1.4.18 libtool 2.4.5 flex 2.6.4 tcl 8.6.7 expect 5.45.3 dejagnu 1.6 sed 4.4 diffutils 3.6 tar 1.29 gzip 1.8 finutils 4.6.0 I could build and check glibc and binutils and bootstrap gcc. The binutils and gcc tests are working (dejagnu/expect/tcl is installed). To actually get a working VMs to run ILP32 you need a kernel built with different branch than either canonical Linus tree or linux stable. Easier way is to use Maxim's automated script to start a qemu aarch64 instance on r1-a7: $ WORKSPACE=`pwd` bash -x ~maxim.kuvyrkov/src/jenkins-scripts/start-container-qemu.sh \ --weight 2 --node r1-a7 --arch arm64 --distro xenial --task test --prefix ilp32_ \ --kernel_url https://people.linaro.org/~maxim.kuvyrkov/norov-Image --initrd_url \ https://cloud-images.ubuntu.com/releases/16.04/release/unpacked/ubuntu-16.0… \ --session-name ilp32-$USER --newuser $USER --cp_file ~/.ssh/authorized_keys You can then log in the machine as usual ('ssh -P r1-a7.aus-colo') and download the sysroot from dev-01.tcwglab. Just uncompress it and issue the usual chroot command: $ mkdir aarch64-linux-gnu_ilp32/proc; sudo mount -t proc proc aarch64-linux-gnu_ilp32/proc $ mkdir aarch64-linux-gnu_ilp32/sys; sudo mount -t sysfs sys aarch64-linux-gnu_ilp32/sys $ mkdir aarch64-linux-gnu_ilp32/dev; sudo mount -o bind /dev aarch64-linux-gnu_ilp32/dev $ sudo chroot aarch64-linux-gnu_ilp32 A useful package missing is GDB and python, I plan to get them built and I will update the image on dev-01.tcwglab during this week. [1] /home/tcwg-buildslave/public_html/images/ilp32/aarch64-linux-gnu_ilp32.tar.bz2

7 years, 7 months

1
0
0 0

[ACTIVITY] 6-10 November 2017

by Christophe Lyon

== Progress == * GCC - FDPIC: rebasing binutils, looking at ACI loop * GCC upstream validation: - iterating on qemu bug report (sanitizer's stoptheworld is not supported by qemu) - restarted upstream validations - not decided yet how to proceed wrt to sanitizers & validation under qemu: - disable sanitizers - switch to umeq instead of qemu - carry local gcc patches to disable lsan * Infrastructure: * misc (conf-calls, meetings, emails, ....) - started looking at hcqc == Next == * GCC/FDPIC * GCC upstream validation

7 years, 7 months

1
0
0 0

[FYI] HCQC(HPC compiler quality checker) on GitHub

by Masaki Arai

Hi, I put HCQC(HPC compiler quality checker) on GitHub. URL: https://github.com/Linaro/hcqc Any comments or suggestions are very welcome. I am going to improve README.md overall and to add more test programs. I will also report the analysis results using HCQC on hpc-sig-devel. The attached PDF file was used to explain HCQC at HPC-SIG SC meeting(11/7). I think you can reproduce the results on this slide if you modify the following part of the configuration file: hcqc/config/clang-config.json "COMMAND" : "/usr/bin/clang", "VERSION" : "4.0.1", hcqc/config/gcc-config.json "COMMAND" : "/usr/bin/gcc-7", "VERSION" : "7.1.1", which you need to fix to suit your environment. [image: https://ssl.gstatic.com/ui/v1/icons/mail/images/cleardot.gif] Best regards, -- -------------------------------------- Masaki Arai

7 years, 7 months

4
9
0 0

[ANNOUNCE] Linaro Binary Toolchain Release-Candidate GCC 7.2-2017.11-rc1

by Przemyslaw Wirkus

The Linaro Binary Toolchain ============================ The Linaro GCC 7.2-2017.11-rc1 Release-Candidate is now available. *Notice*: GCC 7.1 ABI change for arm*-*-* targets, and note for aarch64*-*-* targets >From GCC 7.1 release notes: On ARM targets (arm*-*-*), a bug introduced in GCC 5 that affects conformance to the procedure call standard (AAPCS) has been fixed. The bug affects some C++ code where class objects are passed by value to functions and could result in incorrect or inconsistent code being generated. This is an ABI change. If the option -Wpsabi is enabled (on by default) the compiler will emit a diagnostic note for code that might be affected. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77728 GCC 5 and GCC 6 releases will continue to be affected by the ABI bug, since changing ABI in these releases is not practical. A warning enabled by -Wpsabi option was added to GCC 5 and GCC 6 toolchains to diagnose codebases that might be affected by the ABI bug. Additionally, this same bug was present in AArch64 backend in development versions of GCC 7. There was no releases of GCC with this bug present in AArch64 backend, therefore the release notes does not mention this. However, be advised that any code bases built with development versions of GCC 7 need to be recompiled with released version of GCC 7 to conform to ABI. For an explanation of GCC 7 series changes please see the following website: https://gcc.gnu.org/gcc-7/changes.html For help in porting to GCC 7 please see the following explanation: https://gcc.gnu.org/gcc-7/porting_to.html Download release-candidate packages from: (sources) http://snapshots.linaro.org/components/toolchain/gcc-linaro/7.2-2017.11-rc1/ (binaries) http://snapshots.linaro.org/components/toolchain/binaries/7.2-2017.11-rc1/ Previous snapshots and release-candidates are at: http://snapshots.linaro.org/components/toolchain/binaries/ Previous releases are at: http://releases.linaro.org/components/toolchain/binaries/ A description of the arm and AArch64 target triples can be found at: https://collaborate.linaro.org/display/TCWGPUB/ARM+and+AArch64+Target+Tripl… Host Requirements ================== Linaro officially supports the current and previous Ubuntu LTS releases (as of the time of this release). This does not mean that the toolchain will not work on other/older Linux distributions. See the following for the life-time of Ubuntu LTS releases. https://wiki.ubuntu.com/Releases The host system upon which the cross-compiler will run requires a minimum of glibc 2.14, because of API changes to glibc's memcpy API. https://bugs.linaro.org/show_bug.cgi?id=1869 Package Versions ================= Linaro GCC 7.2-2017.11-rc1 http://snapshots.linaro.org/components/toolchain/gcc-linaro/7.2-2017.11-rc1/ FSF glibc 2.25 (release/2.25) https://lists.gnu.org/archive/html/info-gnu/2017-02/msg00002.html Newlib 2.5 (newlib-2_5_0 tag) https://sourceware.org/ml/newlib/2016/msg01191.html GNU Binutils 2.28 (linaro-local/linaro_binutils-2_28-branch) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=bin… FSF GDB 8.0 (gdb-8.0-branch) https://sourceware.org/ml/gdb-announce/2017/msg00003.html Linaro toolchain package git branches are hosted at: http://git.linaro.org/toolchain NEWS for GCC 7 (as of Linaro GCC 7.2-2017.11-rc1) ================================================== * The Linaro GCC 7.2-2017.09 snapshot added float and integer moves improvement for AArch64 targets. * The Linaro GCC 7.1-2017.07 snapshot added prefetching configuration improvement for AArch64 targets and laid groundwork to enabling prefetching in more cases. * Previous MinGW hosted version of Linaro GCC C preprocessor failed to convert character set used for string, character constants, etc. This is fixed in this release. Linaro bugzilla #3040 : CC1 and cc1plus cannot convert UTF-8. https://bugs.linaro.org/show_bug.cgi?id=3040 * Performance related backports from the following snapshots have been included: Linaro GCC 7.1-2017.05, Linaro GCC 7.1-2017.06, Linaro GCC 7.1-2017.07, Linaro GCC 7.2-2017.08, Linaro GCC 7.2-2017.09 and Linaro GCC 7.2-2017.10. See the following Linaro GCC snapshots: http://snapshots.linaro.org/components/toolchain/gcc-linaro/7.1-2017.05/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/7.1-2017.06/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/7.1-2017.07/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/7.2-2017.08/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/7.2-2017.09/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/7.2-2017.10/ Contact Linaro =============== File bugs at http://bugs.linaro.org For Linaro member support see http://support.linaro.org For Linaro community support email linaro-toolchain(a)lists.linaro.org

7 years, 7 months

1
0
0 0

[ANNOUNCE] Linaro Binary Toolchain Release-Candidate GCC 6.4-2017.11-rc1

by Przemyslaw Wirkus

The Linaro Binary Toolchain ============================ The Linaro GCC 6.4-2017.11-rc1 Release-Candidate is now available. The GCC 6 Release series has significant changes from the GCC 5 release series. For an explanation of the changes please see the following website: https://gcc.gnu.org/gcc-6/changes.html For help in porting to GCC 6 please see the following explanation: https://gcc.gnu.org/gcc-6/porting_to.html Download release-candidate packages from: (sources) http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.4-2017.11-rc1/ (binaries) http://snapshots.linaro.org/components/toolchain/binaries/6.4-2017.11-rc1/ Previous snapshots and release-candidates are at: http://snapshots.linaro.org/components/toolchain/binaries/ Previous releases are at: http://releases.linaro.org/components/toolchain/binaries/ A description of the arm and AArch64 target triples can be found at: https://collaborate.linaro.org/display/TCWGPUB/ARM+and+AArch64+Target+Tripl… Host Requirements ================== Linaro officially supports the current and previous Ubuntu LTS releases (as of the time of this release). This does not mean that the toolchain will not work on other/older Linux distributions. See the following for the life-time of Ubuntu LTS releases. https://wiki.ubuntu.com/Releases The host system upon which the cross-compiler will run requires a minimum of glibc 2.14, because of API changes to glibc's memcpy API. https://bugs.linaro.org/show_bug.cgi?id=1869 Package Versions ================= Linaro GCC 6.4-2017.11-rc1 http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.4-2017.11-rc1/ Linaro glibc 2.23 (linaro/2.23/master) https://lists.gnu.org/archive/html/info-gnu/2016-02/msg00009.html Linaro newlib 2.4-2016.03 (linaro_2.4-branch) https://sourceware.org/ml/newlib/2016/msg00370.html Linaro binutils 2.27 (linaro-local/linaro_binutils-2_27-branch) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=bin… Linaro GDB 8.0 (gdb-8.0-branch) https://lists.gnu.org/archive/html/info-gnu/2016-10/msg00007.html Linaro toolchain package git branches are hosted at: http://git.linaro.org/toolchain NEWS for GCC 6 (as of Linaro GCC 6.4-2017.11-rc1) ================================================== * Previous MinGW hosted version of Linaro GCC C preprocessor failed to convert character set used for string, character constants, etc. This is fixed in this release. Linaro bugzilla #3040 : CC1 and cc1plus cannot convert UTF-8. https://bugs.linaro.org/show_bug.cgi?id=3040 * The Linaro GCC 6.3-2017.05 snapshot added support for -mpure-code option to ARMv7-M and ARMv8-M targets. This option ensures functions are put into sections that contain only code and no data. * The GDB version was upgraded from GDB 8.0. * Previous versions of the Linaro GCC 6 toolchain, when -static -E/—dynamic-list are passed to the linker, might create executables with dynamic sections which aren’t supported by run-time. This was exhibited in Perf Tools build system and has been fixed upstream and backported into Linaro Binutils 2.27 branch. Linaro bugzilla #2926 : Perf tools compiled statically for AArch64 with Linaro release 6.1 and later ones was not statically linked. https://bugs.linaro.org/show_bug.cgi?id=2926 * The Linaro GCC 6.3-2017.03 snapshot fixed some ILP32 issues (TLS, exception handling, …) and these have been incorporated into this release. * Previous versions of the Linaro GCC 6 toolchain were incorrectly generating floating-point code for soft-float Linux targets (arm-linux-gnueabi, and armeb-linux-gnueabi). This escaped detection until recently because the soft-float targeted toolchains were configured to use general-purpose registers for passing floating-point values (which is what you would expect for soft-float toolchains) and the intra-routine floating-code was not noticed. The issue would only show up on targets that were run on hardware that truly didn't have floating-point hardware where the kernel did not trap and emulate floating-point routines. This has been solved in Linaro GCC 6.3-2017.02-rc2 by configuring the toolchain (using --with-float=soft) to generate code without any floating-point instructions at all (-mfloat-abi=soft). https://review.linaro.org/#/c/16968/2 This change should not break compatibility between existing binaries compiled with these toolchains since the float-point parameter passing ABI is still the same. * A bug/regression in the compiler has been identified whereby the target function that is invoked when calling a "weak" function directly is the "strong" override, whereas when calling the function via a pointer the "weak" implementation is used. This would be noticed as inconsistent function invocation when invoking directly vs. invoking via function pointer. This issue only affected 32-bit arm targets. This regression has been fixed upstream and backported into Linaro GCC 6.3-2017.02-rc2. GCC PR target/78253: [5/6/7 Regression] [ARM] call weak function instead of strong when called through pointer. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78253 Linaro bugzilla #2562: ARM GCC 5.2 call weak function instead of strong when called through pointer https://bugs.linaro.org/show_bug.cgi?id=2562 * MS Windows does not support symlinks and the MS Windows archive extractor does not properly deep copy the symlink target files/directories into the symlinked directory structure when unpacking the toolchain archive. This causes problems with missing dependencies when using the Linaro mingw toolchains, as identified in the following bugs: https://bugs.linaro.org/show_bug.cgi?id=2684 https://bugs.linaro.org/show_bug.cgi?id=2192 https://bugs.linaro.org/show_bug.cgi?id=2762 This has been solved by copying files rather than using symlinks when the mingw targetted toolchain archives are created. https://review.linaro.org/#/c/16415/ * Users of Linaro's toolchain have encountered problems when building projects with Autotools (specifically libtool): https://bugs.linaro.org/show_bug.cgi?id=2764 The Linaro binary toolchain release contained files with a .la suffix as artifacts of the toolchain build process. These .la files are helper files for libtool, but unlike a gcc install tree, they are not position independent and contain full paths. Since these artifacts contain absolute paths they can actually mislead user invocation of libtool into not finding required libraries (because they reference the build tree, not the install location) and hence breaking Autotools builds. These *.la file artifacts have been removed from Linaro toolchain binaries because they are unnecessary for users. * The Linaro GCC 6.3-2017.01 snapshot added further enablement for ARMv8-M and these have been incorporated into this release. * Compiling and statically linking some SPEC2006int tests against tcmalloc have been failing due to a problem with glibc's memory allocator function overrides. This was fixed upstream: https://sourceware.org/bugzilla/show_bug.cgi?id=20432 Backported into Linaro glibc 2.23: commit 058b5a41d56b9a8860dede14d97dd443792d064b Author: Florian Weimer <fweimer(a)redhat.com> Date: Fri Aug 26 22:40:27 2016 +0200 malloc: Simplify static malloc interposition [BZ #20432] * Host binaries for x86_64 linux hosts now have symbols and debug information stripped in order to reduce the size of the toolchain binary archives. This reduces the archive size from 1.5G to 600M for aarch64-linux-gnu target with the gcc-6-branch. * The GDB version was upgraded from GDB 7.11 in the Linaro GCC 6.1-2016.08 release to GDB 7.12 in the Linaro GCC 6.2-2016.11 release. * The Linaro GCC 6.2-2016.10 snapshot added AArch32 support for ARMv8.2 and ARMv8m, as well as some AArch64 fixes for ARMv8.2, and bug fixes merged from FSF GCC 6.2. This is available in the binary toolchain as of Linaro GCC 6.2-2016.11. * Basic tuning support for the Qualcomm qdf24xx was added to the Linaro GCC 6.2-2016.10 snapshot and is available in the binary toolchain as of Linaro GCC 6.2-2016.11. * IFUNC was disabled for baremetal targets, as it was causing test-suite failures, and is presently a Linux only feature. * The gold linker was added to this binary release. * Backported malloc_lock fix into Linaro newlib 2.4. commit 2665915cfc46aa6403bb2efd473c523d3167e0cb Author: Andre Vieira (lists) <Andre.SimoesDiasVieira(a)arm.com> Date: Thu Jun 16 12:23:51 2016 +0100 Re-enable malloc_lock for newlib-nano * Backported rawmemchr patch into Linaro newlib 2.4. commit e7b1ee2ea6aa3ee1da41976407410e6202a098c5 Author: Wilco Dijkstra <Wilco.Dijkstra(a)arm.com> Date: Thu May 12 16:16:58 2016 +0000 Add rawmemchr * Backported strlen fix when using Thumb-2 and -Os -marm into Linaro newlib 2.4. commit 5c02bcc086a96b174e1b9e1445a4a1770070107a Author: Thomas Preud'homme <thomas.preudhomme(a)arm.com> Date: Wed May 11 17:18:48 2016 -0400 Fix strlen using Thumb-2 with -Os -marm * Backported fix for semihosting ARM when heapinfo not provided by debugger into Linaro newlib 2.4. commit 5c9403eaf40951f8a4f55ed65f661b485ff44be7 Author: David Hoover <spm2(a)dangerous.li> Date: Thu Apr 21 07:12:24 2016 +0200 Fixed semihosting for ARM when heapinfo not provided by debugger. * Merged latest FSF glibc release/2.23/master into Linaro glibc 2.23. * Backported __ASSUME_REQUEUE_PI check Linaro glibc 2.23 branch. commit 2d20c3bf918cd94ebd4106693adb3a5c9272baba Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> Date: Tue May 17 10:16:39 2016 -0300 Add runtime check for __ASSUME_REQUEUE_PI (BZ# 18463) * Backported removal of __ASSUME_SET_ROBUST_LIST from Linaro glibc 2.23 branch. commit bb8f09d72756186a3d82a1f7b2adcf8bc1fbaed1 Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> Date: Mon May 16 19:01:10 2016 -0300 Remove __ASSUME_SET_ROBUST_LIST * Backported removal of __ASSUME_FUTEX_LOCK_PI from Linaro glibc 2.23 branch. commit e48b4e7fed0de06dd7832ead48bea8ebc813a204 Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> Date: Mon May 16 10:35:25 2016 -0300 Remove __ASSUME_FUTEX_LOCK_PI * Merged latest FSF binutils-2_27-branch into linaro_binutils-2_27-branch. * The libwinpthread DLL is now copied into the host bin directory to satisfy mingw package dependencies. * Backported GNU Linker fix. commit fbc6c6763e70cb2376e2de990c7fc54c0ee44a59 Author: Nick Clifton <nickc(a)redhat.com> Date: Tue Aug 23 09:45:11 2016 +0100 Fix seg-fault in ARM linker when trying to parse a binary file. * Backported GNU Assembler fix for PR 20364 commit 5fe7ebe5ab43750abf8f490b785d99a1e598e7fd Author: Nick Clifton <nickc(a)redhat.com> Date: Fri Aug 5 10:37:57 2016 +0100 Fix the generation of alignment frags in code sections for AArch64. https://sourceware.org/bugzilla/show_bug.cgi?id=20364 * Performance related backports from the following snapshots have been included: Linaro GCC 6.1-2016.06, Linaro GCC 6.1-2016.07, Linaro GCC 6.1-2016.08, Linaro GCC 6.2-2016.09, Linaro GCC 6.2-2016.10, Linaro GCC 6.2-2016.11, Linaro GCC 6.2-2016.12, Linaro GCC 6.3-2017.01, Linaro GCC 6.3-2017.02, Linaro GCC 6.3-2017.03, Linaro GCC 6.3-2017.04, Linaro GCC 6.3-2017.05, Linaro GCC 6.3-2017.06, Linaro GCC 6.4-2017.07, Linaro GCC 6.4-2017.08, Linaro GCC 6.4-2017.09 and Linaro GCC 6.4-2017.10 . See the following Linaro GCC snapshots: http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.1-2016.06/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.1-2016.07/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.1-2016.08/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.2-2016.09/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.2-2016.10/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.2-2016.11/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.2-2016.12/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.3-2017.01/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.3-2017.02/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.3-2017.03/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.3-2017.04/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.3-2017.05/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.3-2017.06/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.4-2017.07/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.4-2017.08/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.4-2017.09/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.4-2017.10/ Contact Linaro =============== File bugs at http://bugs.linaro.org For Linaro member support see http://support.linaro.org For Linaro community support email linaro-toolchain(a)lists.linaro.org

7 years, 7 months

1
0
0 0

Linux kernel compiling with LTO

by Yury Norov

Hi Maxim, all, Alex Matveev and I try to enable LTO optimization for Linux kernel on ARM64. The work is based on patches from Andi Kleen, and is not complete yet. Maxim recommended to work tightly with toolchain group to understand how to fix problems better - on kernel or compiler side. Links: My unfinished branch: https://github.com/norov/linux/tree/lto Andi Kleen tree: https://github.com/andikleen/linux-misc/tree/lto-411-1 Sami Tolvanen's recent work for clang: https://lkml.org/lkml/2017/11/3/606 Question we have for now: There's mrs_s/msr_s macro that doesn't work with LTO - linker complains very loudly that macro is either not declared, or declared multiple times. (To reproduce - try to build my kernel branch w/o last patch). The same (?) problem is observed with clang, and people there considered it as feature, not a bug. https://bugs.llvm.org/show_bug.cgi?id=19749 We have the fix for both clang and gcc, but it looks hacky. Maybe it worth to fix mrs/msr issue on toolchain side? Thanks, Yury

7 years, 7 months

1
0
0 0

[ACTIVITY] 30 October - 3 November 2017

by Prathamesh Kulkarni

== This Week == * PR82808 (4/10) - Submitted patch upstream * TCWG-1234 (4/10) - Experimenting with unhoisting approach - Working through ICE's * TCWG-319 (1/10) - Rebased and locally validated patch * Misc (1/10) - Meetings == Next Week == - Continue ongoing tasks

7 years, 7 months

1
0
0 0

Linaro GCC CrossCompiler for ARMv8 - Weak Linkage issue

by Veena & Deepak Ramaswamy

All, Using the tool chain that comes with the FVP package that I downloaded last month (Oct 2017), I'm trying to compile the Splash2 benchmark to execute on the latest FVP platform and seeing a compilation issue that goes like this (please see below) To reproduce: 1. download the benchmark from here and follow _all_ the instructions in the homepage: http://www.capsl.udel.edu/splash/Download.html 2. edit the makefile.config under /splash2/codes to use linaro toolchain and choose POSIX_BARRIER for the MACROS section (I've pasted my makefile.config here as well - you will have to modify the toolchain paths to suit your setup) 3. cd to splash2/codes/apps/ocean/contiguous_partitions 4. make (and you will see the problem) Please help. Thanks. ------------------------------------------ /local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu-gcc jacobcalc.o jacobcalc2.o laplacalc.o linkup.o main.o multi.o slave1.o slave2.o subblock.o -v -O3 -pthread -D_POSIX_C_SOURCE=200112 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wredundant-decls -Wdisabled-optimization -Wpadded -Winline -Wpointer-arith -Wsign-compare -Wendif-labels -lgcc -lc -lm -static -o OCEAN -lm -lc -lgcc -static Using built-in specs. COLLECT_GCC=/local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu-gcc COLLECT_LTO_WRAPPER=/local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../libexec/gcc/aarch64-linux-gnu/6.2.1/lto-wrapper Target: aarch64-linux-gnu Configured with: /home/tcwg-buildslave/workspace/tcwg-make-release/label/docker-trusty-amd64-tcwg-build/target/aarch64-linux-gnu/snapshots/gcc-linaro-6.2-2016.11/configure SHELL=/bin/bash --with-mpc=/home/tcwg-buildslave/workspace/tcwg-make-release/label/docker-trusty-amd64-tcwg-build/target/aarch64-linux-gnu/_build/builds/destdir/x86_64-unknown-linux-gnu --with-mpfr=/home/tcwg-buildslave/workspace/tcwg-make-release/label/docker-trusty-amd64-tcwg-build/target/aarch64-linux-gnu/_build/builds/destdir/x86_64-unknown-linux-gnu --with-gmp=/home/tcwg-buildslave/workspace/tcwg-make-release/label/docker-trusty-amd64-tcwg-build/target/aarch64-linux-gnu/_build/builds/destdir/x86_64-unknown-linux-gnu --with-gnu-as --with-gnu-ld --disable-libstdcxx-pch --disable-libmudflap --with-cloog=no --with-ppl=no --with-isl=no --disable-nls --enable-c99 --enable-gnu-indirect-function --disable-multilib --with-arch=armv8-a --enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419 --enable-multiarch --with-build-sysroot=/home/tcwg-buildslave/workspace/tcwg-make-release/label/docker-trusty-amd64-tcwg-build/target/aarch64-linux-gnu/_build/sysroots/aarch64-linux-gnu --enable-lto --enable-linker-build-id --enable-long-long --enable-shared --with-sysroot=/home/tcwg-buildslave/workspace/tcwg-make-release/label/docker-trusty-amd64-tcwg-build/target/aarch64-linux-gnu/_build/builds/destdir/x86_64-unknown-linux-gnu/aarch64-linux-gnu/libc --enable-languages=c,c++,fortran,lto --enable-checking=release --disable-bootstrap --build=x86_64-unknown-linux-gnu --host=x86_64-unknown-linux-gnu --target=aarch64-linux-gnu --prefix=/home/tcwg-buildslave/workspace/tcwg-make-release/label/docker-trusty-amd64-tcwg-build/target/aarch64-linux-gnu/_build/builds/destdir/x86_64-unknown-linux-gnu Thread model: posix gcc version 6.2.1 20161016 (Linaro GCC 6.2-2016.11) COMPILER_PATH=/local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../libexec/gcc/aarch64-linux-gnu/6.2.1/:/local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../libexec/gcc/aarch64-linux-gnu/:/local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../libexec/gcc/:/local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../lib/gcc/aarch64-linux-gnu/6.2.1/../../../../aarch64-linux-gnu/bin/ LIBRARY_PATH=/local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../lib/gcc/aarch64-linux-gnu/6.2.1/:/local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../lib/gcc/aarch64-linux-gnu/:/local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../lib/gcc/:/local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../lib/gcc/aarch64-linux-gnu/6.2.1/../../../../aarch64-linux-gnu/lib/../lib64/:/local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../lib/gcc/aarch64-linux-gnu/6.2.1/../../../../aarch64-linux-gnu/lib/:/local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../aarch64-linux-gnu/libc/lib/:/local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../aarch64-linux-gnu/libc/usr/lib/ COLLECT_GCC_OPTIONS='-v' '-O3' '-pthread' '-D' '_POSIX_C_SOURCE=200112' '-Wall' '-Wextra' '-Wmissing-prototypes' '-Wmissing-declarations' '-Wredundant-decls' '-Wdisabled-optimization' '-Wpadded' '-Winline' '-Wpointer-arith' '-Wsign-compare' '-Wendif-labels' '-static' '-o' 'OCEAN' '-static' '-march=armv8-a' '-mlittle-endian' '-mabi=lp64' /local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../libexec/gcc/aarch64-linux-gnu/6.2.1/collect2 -plugin /local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../libexec/gcc/aarch64-linux-gnu/6.2.1/liblto_plugin.so -plugin-opt=/local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../libexec/gcc/aarch64-linux-gnu/6.2.1/lto-wrapper -plugin-opt=-fresolution=/tmp/ccwD6OY1.res -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_eh -plugin-opt=-pass-through=-lpthread -plugin-opt=-pass-through=-lc --sysroot=/local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../aarch64-linux-gnu/libc --build-id -Bstatic -X -EL -maarch64linux --fix-cortex-a53-835769 --fix-cortex-a53-843419 -o OCEAN /local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../aarch64-linux-gnu/libc/usr/lib/crt1.o /local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../aarch64-linux-gnu/libc/usr/lib/crti.o /local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../lib/gcc/aarch64-linux-gnu/6.2.1/crtbeginT.o -L/local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../lib/gcc/aarch64-linux-gnu/6.2.1 -L/local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../lib/gcc/aarch64-linux-gnu -L/local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../lib/gcc -L/local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../lib/gcc/aarch64-linux-gnu/6.2.1/../../../../aarch64-linux-gnu/lib/../lib64 -L/local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../lib/gcc/aarch64-linux-gnu/6.2.1/../../../../aarch64-linux-gnu/lib -L/local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../aarch64-linux-gnu/libc/lib -L/local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../aarch64-linux-gnu/libc/usr/lib jacobcalc.o jacobcalc2.o laplacalc.o linkup.o main.o multi.o slave1.o slave2.o subblock.o -lgcc -lc -lm -lm -lc -lgcc --start-group -lgcc -lgcc_eh -lpthread -lc --end-group /local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../lib/gcc/aarch64-linux-gnu/6.2.1/crtend.o /local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../aarch64-linux-gnu/libc/usr/lib/crtn.o /local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../aarch64-linux-gnu/libc/usr/lib/libpthread.a(lowlevellock.o): In function `__lll_lock_wait_private': /home/tcwg-buildslave/workspace/tcwg-make-release/label/docker-trusty-amd64-tcwg-build/target/aarch64-linux-gnu/snapshots/glibc.git~linaro~2.23~master/nptl/lowlevellock.c:29: multiple definition of `__lll_lock_wait_private' /local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/../aarch64-linux-gnu/libc/usr/lib/libc.a(libc-lowlevellock.o):/home/tcwg-buildslave/workspace/tcwg-make-release/label/docker-trusty-amd64-tcwg-build/target/aarch64-linux-gnu/snapshots/glibc.git~linaro~2.23~master/nptl/./lowlevellock.c:29: first defined here collect2: error: ld returned 1 exit status make: *** [OCEAN] Error 1 ----------------------------------------- Makefile.config ----------------------------------------- #CC := /local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-gcc CC := /local/mnt/workspace/linaro/tools/gcc/gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu-gcc CFLAGS := -v -O3 -pthread -D_POSIX_C_SOURCE=200112 #CFLAGS := -g3 -pthread -D_POSIX_C_SOURCE=200112 CFLAGS := $(CFLAGS) -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wredundant-decls -Wdisabled-optimization CFLAGS := $(CFLAGS) -Wpadded -Winline -Wpointer-arith -Wsign-compare -Wendif-labels CFLAGS := $(CFLAGS) -lgcc -lc -lm -static LDFLAGS := -lm -lc -lgcc -static BASEDIR := /net/dramaswa-linux/local/mnt/workspace/MT/splash2/codes MACROS := $(BASEDIR)/null_macros/c.m4.null.POSIX_BARRIER M4 := m4 -s -Ulen -Uindex x = * $(TARGET): $(OBJS) $(CC) $(OBJS) $(CFLAGS) -o $(TARGET) $(LDFLAGS) clean: rm -rf *.c *.h *.o $(TARGET) .SUFFIXES: .SUFFIXES: .o .c .C .h .H .H.h: $(M4) $(MACROS) $*.H > $*.h .C.c: $(M4) $(MACROS) $*.C > $*.c .c.o: $(CC) -c $(CFLAGS) $*.c .C.o: $(M4) $(MACROS) $*.C > $*.c $(CC) -c $(CFLAGS) $*.c

7 years, 7 months

2
5
0 0

[ACTIVITY] 30 October-3 November 2017

by Christophe Lyon

Short week (off Wed/Thu/Fri) == Progress == * GCC - FDPIC: looking at patch stacks * GCC upstream validation: - got feedback from upstream about qemu and asan interaction since recent merge: need to disable LSAN on arm. - using qemu-2.7 again enables to workaround the timeout issues observed last week - worked on improving timeout handling - restarted validations, but.... - validations on-hold since Nov 1st because of an ST-internal infrastructure problem * Infrastructure: * misc (conf-calls, meetings, emails, ....) == Next == * GCC upstream validation * GCC/ubsan * GCC/FDPIC

7 years, 7 months

1
0
0 0

[ACTIVITY] Week 44

by Yvan Roux

* 3 days off == Progress == o Linaro GCC/Validation o LLVM * Continue ramp-up * Upstream bug 32999: - Reworked the fix and validate it - Ready to be submitted upstream * Start to look at sign-extension elimination status o Misc == Plan == o Release handover (5 release, 6 and 7 RCs) o LLVM tasks (Bug 32999, sign-extension)

7 years, 7 months

1
0
0 0

[ACTIVITY] Oct 27 -- Nov 03

by Yao Qi

# Progress # * TCWG-1040, [6/10] Update my patches to remove the last use of MAX_REGISTER_SIZE. Commit clean up and refactor patches. Find more clean up patches in my tree. Keep upstreaming them. The design and implementation of removing MAX_REGISTER_SIZE becomes more and more clear. * TCWG-1125, [2/10] ARMv8 tagged address support in GDB. v2 patches were posted. No comments yet. * aarch64: PR 19806: watchpoints: false negatives + PR 20207 contiguous ones. Patch review. [1/10] * Think about the TODOs for GDB ILP32 support, write them down, and send it to Maxim. [1/10] # Plan # * TCWG-1040, TCWG-1125. -- Yao Qi

7 years, 8 months

1
0
0 0

aarch64 toolchain support NEON and vfp features

by Joy Deng

Hi , I am a SW engineer that use Linaro-toolchain to build images, Recently, I encounter some issue about enable NEON features on ARMv8 processor platform. I cat cpuinfo, can not find neon and vfp feature enable in list, the image was build with aarch-64 toolchian; While, the image built by armv7l toolchain can list "neon and vfp" in cpuinfo. I want to verify from your side, 1. if the toolchain of aarch64 version already enable" neon and vfp " in default, Because I do not find some build items that related with "neon", 2. If not supported defaultly, can you give some suggestion to enable it. Thanks & B.R. Joy Deng

7 years, 8 months

2
4
0 0

[ACTIVITY] 23 October - 27 October 2017

by Prathamesh Kulkarni

== This Week == * TCWG-1005 (4/10) - Iteration on upstream feedback and validated patch - Committed to trunk in r254140. * Reverse of TCWG-1253 transform (3/10) - Adding reverse transform for div pattern in expand * TCWG-1234 (2/10) - Experimenting with "unhoisting" approach * Misc (1/10) - Meetings == Next Week == - Continue ongoing and backlog tasks from JIRA - Go through IPA mod/ref paper

7 years, 8 months

1
0
0 0

[ACTIVITY] Week 43

by Yvan Roux

* One day off == Progress == o Linaro GCC/Validation * Releases handover - GCC 5.5 source snapshot and RC1 deployed - GCC 6 and 7 RCs under construction o LLVM * Continue ramp-up * Upstream bug 32999: - Validating a fix o Misc * Various meetings and discussions. == Plan == o Continue release handover and LLVM ramp-up

7 years, 8 months

1
0
0 0

[ACTIVITY] 23-27 October 2017

by Christophe Lyon

== Progress == * GCC - FDPIC: started reading docs and looking at patches - Neon intrinsics PR71233: duplicates will be removed from the next doc update * GCC upstream validation: - since ubsan merge with upstream, validation of arm targets is now broken. Switching back to qemu-2.7 seems to avoid qemu deadlocks, but there are still new asan test failures after the merge. - reduced the dejagnu timeout to avoid global 'make check' timeouts, but this caused some testcases to become zombies, in turn causing problems in the ST compute farm. - validation on-hold until next so that I can experiment a bit more with workarounds - reported another qemu bug - reported a couple of regressions/breakages in binutils * Infrastructure: * misc (conf-calls, meetings, emails, ....) == Next == * GCC upstream validation * GCC/ubsan * GCC/FDPIC * Short week (off Wed/Thu/Fri)

7 years, 8 months

1
0
0 0

[ACTIVITY] Oct 23 - 27

by Yao Qi

* TCWG-1040, [4/10] Update my patches to remove the last use of MAX_REGISTER_SIZE. Post the clean up and refactor patches. * TCWG-1125, [4/10] ARMv8 tagged address support in GDB. v2 patches are posted. Take care of breakpoint and watchpoint on tagged address carefully. * ILP32 GDB branch. [1/10] Branch is created! Done. * Misc, meeting, [1/10] # Plan # * Update my patches to remove the last use of MAX_REGISTER_SIZE. * GDB flexible target description conversion. Upstream patches. -- Yao Qi

7 years, 8 months

1
0
0 0

[ANNOUNCE] Linaro Binary Toolchain Release-Candidate GCC 5.5-2017.10-rc1

by Mark Murray

[ANNOUNCE] Linaro Binary Toolchain Release-Candidate GCC 5.5-2017.10-rc1 The Linaro Binary Toolchain ============================ The Linaro GCC 5.5-2017.10-rc1 Release-Candidate is now available. Notice: All Linaro GCC 5 series toolchain users should migrate to the latest version of the Linaro GCC 5 toolchain in order to mitigate potential security exposure to CVE-2015-7547. See the NEWS section below for details. Download release-candidate packages from: (sources) http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.5-2017.10-rc1/ (binaries) http://snapshots.linaro.org/components/toolchain/binaries/5.5-2017.10-rc1/ Previous snapshots and release-candidates are at: http://snapshots.linaro.org/components/toolchain/binaries/ Previous releases are at: http://releases.linaro.org/components/toolchain/binaries/ A description of the arm and AArch64 target triples can be found at: https://collaborate.linaro.org/display/TCWGPUB/ARM+and+AArch64+Target+Tripl… Host Requirements ================== Linaro officially supports the current and previous Ubuntu LTS releases (as of the time of this release). This does not mean that the toolchain will not work on other/older Linux distributions. See the following for the life-time of Ubuntu LTS releases. https://wiki.ubuntu.com/Releases The host system upon which the cross-compiler will run requires a minimum of glibc 2.14, because of API changes to glibc's memcpy API. https://bugs.linaro.org/show_bug.cgi?id=1869 Package Versions ================= Linaro GCC 5.5-2017.10-rc1 http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.5-2017.10-rc1/ Linaro glibc 2.21 (linaro/2.21) https://lists.gnu.org/archive/html/info-gnu/2015-02/msg00001.html Linaro newlib 2.1.0-2014.09 (linaro_newlib-branch) https://sourceware.org/ml/newlib/2013/msg01128.html Linaro binutils 2.25 (linaro_binutils-2_25-branch) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=bin… FSF GDB 7.12 (gdb-7.12-branch) https://lists.gnu.org/archive/html/info-gnu/2016-10/msg00007.html Linaro toolchain package git branches are hosted at: http://git.linaro.org/toolchain NEWS for GCC 5 (as of Linaro GCC 5.5-2017.10-rc1) ================================================== * Include GCC fix for Linaro bugzilla #2575: ICE: declaration and definition of function with __attribute__((target("thumb"))) and inlined assembler, with debug symbols enabled https://bugs.linaro.org/show_bug.cgi?id=2575 * Include GCC fix for Linaro bugzilla #2575: Internal compiler error using -mtune=cortex-a57.cortex-a53. https://bugs.linaro.org/show_bug.cgi?id=2785 * The soft-float targeted toolchains have now been configured to generate code using -mfloat-abi=soft. This makes arm-linux-gnueabi and armeb-linux-gnueabi toolchains use the “soft” FP ABI instead of “softfp”. Historically, TCWG’s toolchains provided both “soft” and “softfp” multilibs, but when switching from crosstool-ng to cbuildv2/abe (which support a single multilib) “softfp” multilib was choosen. Using “-mfloat-abi=soft” is a better choice for a gnueabi toolchain, since it doesn’t require cores to have a floating-point unit. This change should not break compatibility for toolchain users since the ABI will stay the same. The compiler and glibc libraries will not refernce FP instructions. * Include GCC fix for Linaro bugzilla #2562: ARM GCC 5.2 call weak function instead of strong when called through pointer https://bugs.linaro.org/show_bug.cgi?id=2562 * Include GCC fix for Linaro bugzilla #1925: [regression] FAIL: libgomp.fortran/retval1.f90 -O1 execution test https://bugs.linaro.org/show_bug.cgi?id=1925 * Include GCC fix for Linaro bugzilla #2185: aarch64-linux-gnu-g++ internal compiler error: in curr_insn_transform https://bugs.linaro.org/show_bug.cgi?id=2185 * Backported glibc patch to simplify static malloc interposition [BZ #20432] to correct user identified issue. commit 058b5a41d56b9a8860dede14d97dd443792d064b Author: Florian Weimer Date: Fri Aug 26 22:40:27 2016 +0200 malloc: Simplify static malloc interposition [BZ #20432] * Host binaries for x86_64 linux hosts now have symbols and debug information stripped in order to reduce the size of the toolchain binary archives. This reduces the archive size from 1.1G to 580M for aarch64-linux-gnu target with the gcc-5-branch. * Removed .la files from binary toolchain archive as these files break autotools builds. https://bugs.linaro.org/show_bug.cgi?id=2764 * The mingw toolchains are now archived using the rsync -L option in order to avoid problems with Windows extractors and symbolic links. https://review.linaro.org/#/c/16415/ This resolves the following user bugs: https://bugs.linaro.org/show_bug.cgi?id=2684 https://bugs.linaro.org/show_bug.cgi?id=2192 https://bugs.linaro.org/show_bug.cgi?id=2762 * Copy the libwinpthread DLL into the bin directories so it gets into the tmp directory before tar is run. https://review.linaro.org/#/c/13723/ * Increment binutils release date to 2016_02 to reflect the most recent commit: commit ef90a4718f535cbe6345b4e7168baea7b1972abf Author: Matthew Wahab <matthew.wahab(a)arm.com> Date: Tue Jan 12 16:35:30 2016 +0000 [ARM] Support ARMv8.2 RAS extension. * Baremetal sysroot names now contain 'newlib' rather than 'glibc'. * Manifests now contain relative paths rather than absolute paths. * Now generating proper manifest files. * Fixed pi requeue support in glibc 2.21 while allowing the existing 2.21 minimum kernel default setting. This was checked into the linaro/2.21/master branch. commit a68cafa11c500d8a49a3014c43c5152859d037ae Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> Date: Tue May 17 10:16:39 2016 -0300 Add runtime check for __ASSUME_REQUEUE_PI (BZ# 18463) commit 6e5cb616b5b442ce8b2664ad673c0acf42a490ac Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> Date: Mon May 16 19:01:10 2016 -0300 Remove __ASSUME_SET_ROBUST_LIST commit 9ac61c0047295696cbcdbc26bdc174c7bd25a3c8 Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> Date: Mon May 16 10:35:25 2016 -0300 Remove __ASSUME_FUTEX_LOCK_PI * Backported support into GCC for Cortex-A32, Cortex-A35, and Cortex-R8. * Applied fix for CVE-2015-7547 - A stack-based buffer overflow in glibc's getaddrinfo() was corrected in glibc 2.23 and backported into glibc 2.21. https://sourceware.org/ml/libc-alpha/2016-02/msg00416.html * ARMv8.1 Instruction Support - ARMv8.1 instructions support was checked into GCC and binutils. It has been backported into Linaro GCC 5.3 and Linaro binutils 2.25. * Backported -Bsymbolic-functions into Linaro binutils 2.25. * Performance related backports from Linaro GCC 5.2-2015.11, Linaro GCC 5.2-2015.12, and Linaro GCC 5.3-2016.01-1, Linaro GCC 5.3-2016.02, Linaro GCC 5.3-2016.03, Linaro GCC 5.3-2016.04, Linaro GCC 5.4-2016.06, Linaro GCC 5.4-2016.10, Linaro GCC 5.4-2016.12, Linaro GCC 5.4-2017.02, GCC 5.4-2017.04 and Linaro GCC 5.5-2017.10 have been included. See the following Linaro GCC snapshots: http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.2-2015.11/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2015.12/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.01-1/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.02 http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.03 http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.04 http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.4-2016.06 http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.4-2016.10 http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.4-2016.12 http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.4-2017.02 http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.4-2017.04 http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.5-2017.10 Contact Linaro =============== File bugs at http://bugs.linaro.org For Linaro member support see http://support.linaro.org For Linaro community support email linaro-toolchain(a)lists.linaro.org

7 years, 8 months

1
0
0 0

Does Linaro GCC 5.4 fully support ARMv8.2-A

by Vincent Chen

Hi, We are evaluating LInaro GCC5.4 readiness for ARMv8.2-A extension support but can't find direct answer if all the features has been supported/backported. Can you point me to the answer? Thanks, Vincent ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -----------------------------------------------------------------------------------

7 years, 8 months

2
6
0 0

[ACTIVITY] Week 42

by Yvan Roux

== Progress == o Linaro GCC/Validation * Releases handover - Monthly snapshots for GCC 6 and 7 deployed - GCC 5 final release handled by Mark * Branch merge done * Tarball and release ready to be deployed * RC1 planned for w43 o LLVM * Continue ramp-up * Working on upstream bug 32999: [ARM] Missed vpadd combine opportunity o Misc * Various meetings and discussions. == Plan == o Continue release handover and LLVM ramp-up

7 years, 8 months

1
0
0 0

[ACTIVITY] 16 - 20 October 2017

by Prathamesh Kulkarni

== This Week == * TCWG-1234 (4/10) - Patch inhibits if-conversion for couple of tests. * TCWG-1253 (3/10) - Fixed regressions with the patch * Took Monday off for recovering from travel (2/10) * Misc (1/10) - Meetings == Next Week == - TCWG-1234, TCWG-1253, TCWG-319

7 years, 8 months

1
0
0 0

[ACTIVITY] Oct. 16 -- Oct 20

by Yao Qi

# Progress # * TCWG-1040, [4/10] Update my patches to remove the last use of MAX_REGISTER_SIZE. Before I send them upstream, I find some bits that I can improve, but finally, many things are changed. Need to get them in shape, and think about the design again. * TCWG-1125, [4/10] ARMv8 tagged address support in GDB. GDB/GDBserver needs to remove the top one byte of virtual address before pass it to kernel. Patch v1 was reviewed, and GDB internal caching needs updated for tagged address, because tagged address and non-tagged address should be mapped to the same cache entry in GDB. * GDB flexible target description conversion [1/10] Finished the conversion for tic6x and nios2. To be posted. * ILP32 GDB branch. [1/10] Got Steve Ellcey's patches, one bfd patch and one gdb patch. No GDBserver patches. Will create branch with them. # Plan # * ILP32 GDB branch. * ARMv8 tagged address support in GDB. * Update my patches to remove the last use of MAX_REGISTER_SIZE. -- Yao Qi

7 years, 8 months

1
0
0 0

[ACTIVITY] 16-20 October 2017

by Christophe Lyon

== Progress == * GCC - FDPIC: started reading docs - testsuite cleanup * GCC upstream validation: - reported 2 bugs in qemu-armeb - noise reduction: polishing dejagnu local patches - since ubsan merge with upstream, validation of arm targets is now much longer (typically 1h30 to 6h), leading to timeouts most of the time * Infrastructure: - improved GCC bisect job/scripts - updated ABE to allow overriding cpu/fpu/tune/arch etc... * misc (conf-calls, meetings, emails, ....) == Next == * GCC upstream validation * GCC/ubsan * GCC/FDPIC

7 years, 8 months

1
0
0 0

[ANNOUNCE] Linaro GCC 6 and 7 2017.10 source snapshots

by Mark Murray

The Linaro Toolchain Working Group (TCWG) is pleased to announce the 2017.10 snapshot of Linaro GCC 6 and 7 source packages. o The GCC 7 series introduced an ABI change for ARM targets by fixing a bug (present since GCC 5, see link below) that affects conformance to the procedure call standard (AAPCS). The bug affects some C++ code where class objects are passed by value to functions and could result in incorrect or inconsistent code being generated. If the option -Wpsabi is enabled (on by default) the compiler will emit a diagnostic note for code that might be affected by this ABI change. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77728 For an explanation of the changes please see the following website: https://gcc.gnu.org/gcc-7/changes.html o Linaro GCC 7 monthly snapshot[1] is based on FSF GCC 7.2+svn253626 and includes performance improvements and bug fixes backported from mainline GCC. The contents of this snapshot will be part of the 2017.11 stable[2] quarterly release. This snapshot tarball is available on: http://snapshots.linaro.org/components/toolchain/gcc-linaro/7.2-2017.10/ Interesting changes in this GCC source package snapshot include: * Updates to GCC 7.2+svn253626 o Linaro GCC 6 monthly snapshot[1] is based on FSF GCC 6.4+svn253668 and includes performance improvements and bug fixes backported from mainline GCC. This snapshot contents will be part of the next maintenance release. This snapshot tarball is available on: http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.4-2017.10/ Interesting changes in this GCC source package snapshot include: * Updates to GCC 6.4+svn253668 o 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 * Interested in commercial support? inquire at "Linaro support": mailto:support@linaro.org [1]. Source package snapshots are defined when the compiler is only put through unit-testing and full validation is not performed. [2]. Stable source package releases are defined as releases where the full Linaro Toolchain validation plan is executed.

7 years, 8 months

1
0
0 0

[ACTIVITY] Week 41

by Yvan Roux

== Progress == o Linaro GCC/Validation * Continue releases handover - Branch merges done - Monthly snapshots about to be deployed o LLVM * Jira cards review * Checked/updated cards related to upstream BZ * Continue ramp-up o Misc * Various meetings and discussions. == Plan == o Continue release handover and LLVM ramp-up

7 years, 8 months

1
0
0 0

[ACTIVITY] 9 - 13 October 2017

by Prathamesh Kulkarni

== This Week == * TCWG-1234 (5/10) - Posted analysis upstream with a test-case. - Have a workaround that disables hoisting when only single stmt is to be hoisted. - Investigating solution to limit distance between hoisted def. and it's uses. * TCWG-1005 (2/10) - Did changes based on upstream feedback from Honza, validated patch. - Waiting for final approval from Honza before committing. * Sick leave (2/10) * Misc (1/10) - Meetings == Next Week == - TCWG-1234, TCWG-1005

7 years, 8 months

1
0
0 0

[ACTIVITY] 9-13 October 2017

by Christophe Lyon

== Progress == * GCC - sent final patch for deprecated IT blocks - updated PR 71233 (missing AdvSIMD intrinsics) * GCC upstream validation: - reported a couple of regressions/new failures, found bugs in qemu (need to report them) - noise reduction: will report randomly killed processes as "untested" making it easier to ignore them - buildbot discussion * Infrastructure: - improved GCC bisect job/scripts * misc (conf-calls, meetings, emails, ....) - Connect feedback (internal) == Next == * GCC upstream validation * GCC/ubsan

7 years, 8 months

1
0
0 0

[ACTIVITY] Week 40

by Yvan Roux

* One day off after Connect == Progress == o Linaro GCC/Validation * Handover releases to ARM on-going. o LLVM * Continue ramp-up o Misc * Various meetings and discussions. * Debrief Connect inside ST == Plan == o Continue release handover o LLVM Jira card: cleanup and find first tasks to do

7 years, 8 months

1
0
0 0

[ACTIVITY] 2nd Oct - 6th Oct 2017

by Prathamesh Kulkarni

== This Week == * TCWG-1234: code-hoisting regression (3/10) - Have a workaround that fixes the particular regression (but may introduce another) - Trying to cross build benchmarks - Investigating PRE and code-hoisting optimizations * TCWG-1005: malloc attr propagation (3/10) - Iteration based on upstream feedback. * TCWG-1253 (1/10) - Committed patch last week to add patterns for div and cmp against 0. - Patch to transform rshift and cmp against 0 to cmp between operands in upstream review. * Public Holiday (2/10) * Misc (1/10) - Meetings == Next Week == - TCWG-1234, TCWG-1005

7 years, 8 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain