- linaro-toolchain - lists.linaro.org

[ACTIVITY] week ending 1 July 2018

by Richard Henderson

[VIRT-198 # QEMU: SVE Emulation Support ] Full aarch64-linux-user patch set merged. [VIRT-214 # SVE System Registers ] Implemented ID_AA64PFR0_EL1, ID_AA64ZFR0_EL1. [VIRT-249 # SVE System Mode ] Fixed sve disabled exception routing. A booted kernel recognizes sve is present, according to /proc/cpuinfo. However, the kernel crashes as soon as the first sve insn is executed. Task for next week is to find out why. r~

7 years, 5 months

1
0
0 0

[ACTIVITY] week ending Jul. 1 2018

by Alex Bennée

SVE Support ([VIRT-198]) ======================== - posted {PATCH v3 0/5} support reading some CPUID/CNT registers from user-space Message-Id: <20180625160009.17437-1-alex.bennee(a)linaro.org> - needed for the HPC guys in their test setups - pm has grabbed the CNT patches, the rest need rework, not this cycle [VIRT-198] https://projects.linaro.org/browse/VIRT-198 RISU Support for SVE ([VIRT-199]) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - posted {RISU PATCH v4 00/22} ARM SVE support for RISU Message-Id: <20180622141205.16306-1-alex.bennee(a)linaro.org> - support load/store memory instructions from ASL :todo - awaiting legal clearance from ARM to publish script - generated more traces at different VQ's - VQ3 (found one error, actually x86 SIGFPE issue) - VQ16 (still generating :-/) [VIRT-199] https://projects.linaro.org/browse/VIRT-199 [iteration of SVE series] https://github.com/stsquad/risu/tree/add-sve-support-v3 SVE Reviews ~~~~~~~~~~~ - reviewed {Qemu-devel} {PATCH v5 00/35} target/arm SVE patches Message-Id: <20180621015359.12018-1-richard.henderson(a)linaro.org> Upstream Work ([VIRT-109]) ========================== - posted {PATCH v1 00/10} Travis updates and code coverage tweaks Message-Id: <20180625111935.26108-1-alex.bennee(a)linaro.org> - spent some time looking at getting xtensa system test stuff done - posted {PATCH v2 00/21} Travis, Code Coverage and Cross Build updates Message-Id: <20180629205232.27190-1-alex.bennee(a)linaro.org> [VIRT-109] https://projects.linaro.org/browse/VIRT-109 [hacky fix] https://github.com/stsquad/qemu/commit/a15577f8a6629f9924d2671a82f0b9801351… KVM CI Loop ([VIRT-2]) ====================== - need to sync-up on the current state of this work :todo - spoke with LAVA team about build status and build button - now have a qa-reports account to submit LAVA jobs via [VIRT-2] https://projects.linaro.org/browse/VIRT-2 [our wiki] https://wiki.linaro.org/Core/Virtualization Other Tasks =========== [arm64 story a bit more desktopy] https://github.com/stsquad/gentoo/tree/arm-keywords-so-far Completed Reviews [1/1] ======================= {PATCH v2 00/13} iommu: support txattrs, support TCG execution, implement TZ MPC Message-Id: <20180604152941.20374-10-peter.maydell(a)linaro.org> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - CLOSING NOTE [2018-06-14 Thu 19:27] Looks good. {PATCH 0/8} Docker improvements Message-Id: <20180628164643.9668-1-f4bug(a)amsat.org> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - CLOSING NOTE [2018-06-29 Fri 21:38] Grabbed some patches, commented on others {Qemu-arm} {PATCH v6 00/35} target/arm SVE patches Message-Id: <20180627043328.11531-1-richard.henderson(a)linaro.org> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - CLOSING NOTE [2018-06-29 Fri 21:39] Looks good {Qemu-devel} {PATCH v5 00/35} target/arm SVE patches Message-Id: <20180621015359.12018-1-richard.henderson(a)linaro.org> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - CLOSING NOTE [2018-06-29 Fri 21:39] Looking good, stopped to move to v6 {PATCH 0/4} KVM: arm64: FPSIMD/SVE fixes for 4.17 Message-Id: <1528976039-25826-1-git-send-email-Dave.Martin(a)arm.com> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - CLOSING NOTE [2018-06-29 Fri 21:40] Seems sane to me. Absences ======== - YVR18 Connect (17th-21st September 2018) - KVM Forum 2018 (24th-26th October 2018) Current Review Queue ==================== * {PATCH v4 00/19} reverse debugging Message-Id: <20180528071332.9424.27343.stgit@pasha-VirtualBox> * {RFC PATCH 00/12} tests/tcg: Add TriCore tests Message-Id: <20180501142222.19154-1-kbastian(a)mail.uni-paderborn.de> * {PATCH 0/4} tests/vm: various trivial fixes Message-Id: <20180628153535.1411-1-f4bug(a)amsat.org> * {PATCH 0/6} docker: Port to Python 3 Message-Id: <20180627021423.18404-1-ehabkost(a)redhat.com> * {PATCH v4 00/14} fp-test + hardfloat Message-Id: <1528768140-17894-1-git-send-email-cota(a)braap.org> * {RFC PATCH 00/16} KVM: arm64: Initial support for SVE guests Message-Id: <1529593060-542-1-git-send-email-Dave.Martin(a)arm.com> -- Alex Bennée

7 years, 5 months

1
0
0 0

[ACTIVITY] report week ending 29 June

by Peter Smith

[TCWG-1424] Investigation into profile and size optimisations - Completed the pass and got it working on both the old and new pass managers - Spent quite a bit of time trying to understand how llvm classifies hot and cold functions, a lot of the details are not documented well or at all. - Found another problem with --pgo and lnt when the exec-multisample option is used. I've applied a local fix to stop the extra runs from triggering profile collection - Upstream lnt doesn't seem to collect code size information for a benchmarks-only run, wrote a script to measure and inject it back. - Got some benchmark figures on the pass. Difficult to interpret as I suspect that too many of the benchmarks are too small to give useful results. There seemed to be some huge regressions when a critical function stopped getting inlined, but overall performance was comparable. I need to find some better benchmarks and learn how to make sense of results. [TCWG-1368] Buildbot failure investigation Decided to take a look as an exercise in using the packet.net machines. Some libfuzzer tests are hanging or taking an extremely long time to run on aarch64. Reproduced on one of TCWGs packet.net machines. At early stage of investigation right now as there doesn't seem to be any obvious answers or easily available diagnostics.

7 years, 5 months

1
0
0 0

[ACTIVITY] report week ending 29 Jun

by Peter Maydell

Progress: * VIRT-65 [QEMU upstream maintainership] + code review in preparation for 3.0 softfreeze next week: - PMU emulation improvements - last round of SVE patches - i.mx minor code cleanups - put 'address' annotations into DTB node names - virtualization extension support in GICv2 emulation + sent two target-arm pull requests + bug investigation: the small-MPU-regions patchset had a bug which broke an m68k test image + handling lots of pull requests from everybody else thanks -- PMM

7 years, 5 months

1
0
0 0

[ACTIVITY] Weekly report for week 26

by Thomas Preudhomme

=== Work done during this 2.5day week === * 2.5 day off to take care of my sick son * stack-protector failure on GCC ARM: more testing needed + submitted CVE ID request -> will be known as CVE-2018-12886 once published + start testing * Continue work on DSGHACK-25 (Support arithmetic on FileCheck regex variable) * Misc improvement to Linaro TCWG infrastructure === Plan for week 27 === * finish testing of stack protector bug fix and submit patch for review * DSGHACK-25 (Support arithmetic on FileCheck regex variable): finish patch

7 years, 5 months

1
0
0 0

[ACTIVITY] Week 25

by Yvan Roux

o GNU releases * 6.4 and 7.3 2018.05 deployed o LLVM * First prototype implemented for ARM mode * Working on more cases to handle * Investigating potential issues w/r to pass ordering o Misc * Various meetings and discussions.

7 years, 5 months

1
0
0 0

[ACTIVITY] week ending 24 June 2018

by Richard Henderson

[VIRT-198 # QEMU: SVE Emulation Support ] Implemented FCADD, FCMLA, SDOT, UDOT. Posted v5 patch set. [VIRT-210 # SVE first-fault and no-fault loads ] Implemented for user-only. Posted an RFC for using a rwlock instead of a mutex to protect from mmap changes. Emilio Cota wants perf numbers. Rebased previous glibc sve string patches to align with the cortex-strings work reviewed by Richard Sandiford. Found that strrchr fails with glibc's testsuite even though it didn't work cortex-strings' testsuite. Found that it would *really* help to have a gdb that understands the new sve registers, especially predicates. Found that some sve support is now upstream in gdb. Added some support to the qemu gdbstub, but so far it just crashes gdb. [Upstream] Patch review; the big tickets being SVE RISU and nanoMIPS. r~

7 years, 5 months

1
0
0 0

[ACTIVITY] 18-22 June 2018

by Christophe Lyon

== Progress == * FDPIC - GCC patch series: updating patches.. - uclibc-ng: checking other test results beyond GCC testsuite. Noticed a problem with some libc.a symbols not being weak (eg. write()) * GCC upstream validation: - looking at some random noise in testing - reported a couple of regressions * GCC upstream - ACLE preprocessor defines: cleanup patch committed * Infrastructure: - patch reviews - cleanup/improvements * misc (conf-calls, meetings, emails, ....) == Next == * FDPIC: uclibc-ng, GCC * GCC upstream validation

7 years, 5 months

1
0
0 0

[ACTIVITY] week ending Jun. 24 2018

by Alex Bennée

SVE Support ([VIRT-198]) ======================== - spin next version of CNT{VCT|FRQ}_EL0 from user-space Message-Id: <20180518114424.18054-1-alex.bennee(a)linaro.org> with ID regs :todo - the HPC guys hit this in their test setups [VIRT-198] https://projects.linaro.org/browse/VIRT-198 RISU Support for SVE ([VIRT-199]) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - Investigated some weirdness in SVE traces - didn't figure out what was happening :-/ - but did generate a new "clean" set of tests that pass repeat runs - posted {RISU PATCH v4 00/22} ARM SVE support for RISU Message-Id: <20180622141205.16306-1-alex.bennee(a)linaro.org> - support load/store memory instructions from ASL :todo - awaiting legal clearance from ARM to publish script [VIRT-199] https://projects.linaro.org/browse/VIRT-199 SVE Reviews ~~~~~~~~~~~ Upstream Work ([VIRT-109]) ========================== - posted {RFC PATCH 0/5} Tweak code coverage reporting Message-Id: <20180620132032.12952-1-alex.bennee(a)linaro.org> - found a bug with gcov + linux-user - build a [hacky fix] will include in next patch series [VIRT-109] https://projects.linaro.org/browse/VIRT-109 [hacky fix] https://github.com/stsquad/qemu/commit/a15577f8a6629f9924d2671a82f0b9801351… Fixing up tests/tcg ~~~~~~~~~~~~~~~~~~~ - sent {PULL 00/56} add check-tcg and associated machinery Message-Id: <20180619154435.18898-1-alex.bennee(a)linaro.org> - sent {PULL v2 00/57} add check-tcg and associated machinery Message-Id: <20180621062605.941-1-alex.bennee(a)linaro.org> - spent some time digging into build failures in pm215's merge tests KVM CI Loop ([VIRT-2]) ====================== - need to sync-up on the current state of this work :todo - spoke with LAVA team about build status and build button - now have a qa-reports account to submit LAVA jobs via [VIRT-2] https://projects.linaro.org/browse/VIRT-2 [our wiki] https://wiki.linaro.org/Core/Virtualization Completed Reviews [1/1] ======================= {PATCH v2 00/13} iommu: support txattrs, support TCG execution, implement TZ MPC Message-Id: <20180604152941.20374-10-peter.maydell(a)linaro.org> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - CLOSING NOTE [2018-06-14 Thu 19:27] Looks good. Absences ======== - YVR18 Connect (17th-21st September 2018) - KVM Forum 2018 (24th-26th October 2018) Current Review Queue ==================== * {Qemu-devel} {PATCH v5 00/35} target/arm SVE patches Message-Id: <20180621015359.12018-1-richard.henderson(a)linaro.org> * {PATCH v4 00/14} fp-test + hardfloat Message-Id: <1528768140-17894-1-git-send-email-cota(a)braap.org> * {PATCH 0/4} KVM: arm64: FPSIMD/SVE fixes for 4.17 Message-Id: <1528976039-25826-1-git-send-email-Dave.Martin(a)arm.com> * {RFC PATCH 00/12} tests/tcg: Add TriCore tests Message-Id: <20180501142222.19154-1-kbastian(a)mail.uni-paderborn.de> * {PATCH v4 00/19} reverse debugging Message-Id: <20180528071332.9424.27343.stgit@pasha-VirtualBox> * {RFC PATCH 00/16} KVM: arm64: Initial support for SVE guests Message-Id: <1529593060-542-1-git-send-email-Dave.Martin(a)arm.com> -- Alex Bennée

7 years, 5 months

1
0
0 0

[ACTIVITY] report week ending 22 June

by Peter Maydell

Progress: * VIRT-65 [QEMU upstream maintainership] + lots of code review (including patchsets supporting up to 512 CPUs and lots of PCI devices for KVM virt) + put together another target-arm pullreq * VIRT-164 [improve Cortex-M emulation] + Got small-MPU-regions working for read/write; patches sent for review + MPC support patchset is now in master Lots of meetings this week; clearly the stars have aligned. thanks -- PMM

7 years, 5 months

1
0
0 0

[ACTIVITY] Weekly report for week 25

by Peter Smith

[TCWG-1424] Profile guided information code size investigation. - Wrote up initial findings in Jira - Have written a pass that works with both the new and old pass manager that I can use to selectively add size optimisation attributes to functions. - Spent way too much time trying to work out where to put the pass in both the old and new pass manager. -- I now understand why the new pass manager is required to get the most benefits of profile feedback. -- I now understand a bit better some of the frustrations of the old pass manager. -- I can see why the new pass manager isn't quite ready yet. - Fixed up, I think, -fprofile-instr-generate in the new pass manager. I didn't realise that were two separate instrumentation methods as -fprofile-generate is subtly different. Misc: - Updated state of sanitizer tests on Arm and AArch64 to enable a PR to be closed.

7 years, 5 months

1
0
0 0

[ACTIVITY] Weekly report for week 25

by Thomas Preudhomme

=== Work done during this week === * stack-protector failure on GCC ARM: more testing needed + rework to introduce new standard pattern including guard's address computation and make pattern opaque until after register allocation + fill in form for new CVE ID and ask feedback on CVE description * Resume work on extending FileCheck to allow variable with arithmetic expression + created TCWG-1428 to track this work * Tried to fix LD_LIBRARY_PATH issue with depot build of GNU Arm Embedded Toolchain -> need to talk to someone who know better depot module recipes * Misc: + Arm meetings + Linaro syncs + 1.5 day spent on IT issue (personal investigation to help IT, blocked on broken system after some IT attempts to solve it) -> issue finally fully resolved === Plan for Linaro week 26 === * Do extended testing of stack protector bug fix * TCWG-1428 (Support arithmetic on FileCheck regex variable): finish patch

7 years, 5 months

1
0
0 0

[TCWG] BOLT - Binary optimization and layout tool

by Prathamesh Kulkarni

Just came across Facebook's announcement of open-sourcing BOLT, a tool for optimising instruction cache and TLB misses. Looks interesting. They claim to get 2-15% perf improvement in their services with BOLT and have a port for aarch64: https://code.facebook.com/posts/605721433136474/accelerate-large-scale-appl… Regards, Prathamesh

7 years, 5 months

2
2
0 0

[ANNOUNCE] Linaro Binary Toolchain Release GCC 7.3-2018.05

by Mark Murray

The Linaro Binary Toolchain ============================ The Linaro GCC 7.3-2018.05 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.3-2018.05/ (binaries) http://releases.linaro.org/components/toolchain/binaries/7.3-2018.05/ 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.3-2018.05 http://releases.linaro.org/components/toolchain/gcc-linaro/7.3-2018.05/ 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.1 (gdb-8.1-branch) https://lists.gnu.org/archive/html/info-gnu/2018-01/msg00016.html Linaro toolchain package git branches are hosted at: http://git.linaro.org/toolchain NEWS for GCC 7 (as of Linaro GCC 7.3-2018.05) ============================================== * Runtest and gdbserver are no longer installed in the toolchain bin/ directory. Binary releases no longer include runtest at all, and gdbserver is a target tool; it is now shipped in the sysroot under usr/bin/. LDTS case #2211: gdbserver and runtest in GCC binary release are in the wrong place or have the wrong name * Gdbserver is no longer linked statically, because this is currently unsupported. Linaro bugzilla #3344: gdbserver broken in Linaro 2017.02 https://bugs.linaro.org/show_bug.cgi?id=3344 * 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, Linaro GCC 7.2-2017.10 and Linaro GCC 7.2-2018.04. 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/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/7.2-2018.04/ 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 Mark Murray Staff Software Engineer | Arm . . . . . . . . . . . . . . . . . . . . . . . . . . . p: +44 1223 405082 arm.com <http://www.arm.com> 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

[ANNOUNCE] Linaro Binary Toolchain Release GCC 6.4-2018.05

by Mark Murray

The Linaro Binary Toolchain ============================ The Linaro GCC 6.4-2018.05 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-2018.05/ (binaries) http://releases.linaro.org/components/toolchain/binaries/6.4-2018.05/ 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-2018.05 http://releases.linaro.org/components/toolchain/gcc-linaro/6.4-2018.05/ 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.1 (gdb-8.1-branch) https://lists.gnu.org/archive/html/info-gnu/2018-01/msg00016.html Linaro toolchain package git branches are hosted at: http://git.linaro.org/toolchain NEWS for GCC 6 (as of Linaro GCC 6.4-2018.05) ============================================== * Runtest and gdbserver are no longer installed in the toolchain bin/ directory. Binary releases no longer include runtest at all, and gdbserver is a target tool; it is now shipped in the sysroot under usr/bin/. LDTS case #2211: gdbserver and runtest in GCC binary release are in the wrong place or have the wrong name * Gdbserver is no longer linked statically, because this is currently unsupported. Linaro bugzilla #3344: gdbserver broken in Linaro 2017.02 https://bugs.linaro.org/show_bug.cgi?id=3344 * 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 to 8.1. * 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, Linaro GCC 6.4-2017.10 and Linaro GCC 6.4-2018.04. 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/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.4-2018.04/ 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 Mark Murray Staff Software Engineer | Arm . . . . . . . . . . . . . . . . . . . . . . . . . . . p: +44 1223 405082 arm.com <http://www.arm.com> 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

SVE routines for cortex-strings

by Richard Henderson

I spoke with Ramana about these at HKG18, and I'm finally getting back to these. I have routines for -rw-rw-r--. 1 rth rth 2538 May 30 19:12 memchr.S -rw-rw-r--. 1 rth rth 2405 May 30 20:49 memcmp.S -rw-rw-r--. 1 rth rth 2385 May 30 19:12 rawmemchr.S -rw-rw-r--. 1 rth rth 2470 May 30 19:12 strchrnul.S -rw-rw-r--. 1 rth rth 2588 May 30 19:12 strchr.S -rw-rw-r--. 1 rth rth 2370 May 30 19:12 strcmp.S -rw-rw-r--. 1 rth rth 2403 May 30 19:12 strcpy.S -rw-rw-r--. 1 rth rth 2263 May 30 19:12 strlen.S -rw-rw-r--. 1 rth rth 2595 May 30 19:12 strncmp.S -rw-rw-r--. 1 rth rth 2344 May 30 19:12 strnlen.S -rw-rw-r--. 1 rth rth 3105 May 30 19:12 strrchr.S The tests pass when run under Foundation Platform 11.3. What is the best way to submit these for review and upstreaming? There's nothing in the git README about an upstream mailing list... FWIW, my code is at https://github.com/rth7680/cortex-strings/tree/rth/sve r~

7 years, 5 months

7
17
0 0

[ACTIVITY] Week 24

by Yvan Roux

o LLVM * Some fixes in LLVM patch benchmarking job. * Some experiments with LLVM (Thin)LTO * Start to look at Outliner for ARM o Misc * Various meetings and discussions.

7 years, 5 months

1
0
0 0

[ACTIVITY] Week ending 17 Jun 2018

by Richard Henderson

Progress: [VIRT-198 # QEMU: SVE Emulation Support ] Another round of patches merged. About 25 remaing. Implemented MOVPRFX, for which I had plans but forgot to actually implement. Discovered that the advance planning that I have added for this isn't really sufficient. For the purposes of initial upstreaming, I'll emulate them as plain moves. With MOVPRFX done, feedback from Ori.Chalak(a)Huawei.com: > Thank you so much for the quick resolution. > I have run successfully 466 tests of the OpenBLAS benchmark suite on > the branch tag of Qemu you sent me, with SVE instructions compiled > from C using ARM Compiler and Gnu linker. > All pass without any failure. > Did not verify functional correctness, just that all instructions > are run by your Qemu branch in user mode and Qemu completes the job > without a crash. [Upstream] Third iteration on splitting do_syscall. Patch review; pull request for Cota's tb_lock patch set. Tracked down a TB offset overflow affecting a softmmu NEON test case. [GCC] Sent some patches for MOVPRFX to Richard Sandiford. He offered to test them over the weekend before posting them to gcc-patches.

7 years, 6 months

1
0
0 0

[ACTIVITY] 11-15 June 2018

by Christophe Lyon

* 2 days of training == Progress == * FDPIC - GCC patch series: received some feedback. Will have to iterate. - Rebased uclibc patches on top of uclibc-ng. Patch set passes the GCC testsuite * GCC upstream validation: - looking at some random noise in testing * GCC upstream - posted a small patch to use ACLE preprocessor defines. Will have to enhance it * Infrastructure: - patch reviews - cleanup/improvements * misc (conf-calls, meetings, emails, ....) == Next == * FDPIC: uclibc-ng, GCC * GCC upstream validation

7 years, 6 months

1
0
0 0

[ACTIVITY] week ending Jun. 17 2018

by Alex Bennée

SVE Support ([VIRT-198]) ======================== - spin next version of CNT{VCT|FRQ}_EL0 from user-space Message-Id: <20180518114424.18054-1-alex.bennee(a)linaro.org> with ID regs :todo - the HPC guys hit this in their test setups [VIRT-198] https://projects.linaro.org/browse/VIRT-198 RISU Support for SVE ([VIRT-199]) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - worked on next [iteration of SVE series] - added variable size reginfo for backwards compatibility - various unrelated build clean-ups and tweaks - posted {RISU PATCH v3 00/22} SVE support and various misc fixes Message-Id: <20180613125601.14371-1-alex.bennee(a)linaro.org> - Generating full SVE test set from ASL - coded up some "heuristics" to add RISU constraints in patterns - left model generating test sequences over the weekend - handle load/store memory instructions :todo [VIRT-199] https://projects.linaro.org/browse/VIRT-199 [iteration of SVE series] https://github.com/stsquad/risu/tree/add-sve-support-v3 SVE Reviews ~~~~~~~~~~~ - start kicking tires of rth's patches with new test suite :todo Upstream Work ([VIRT-109]) ========================== - started reviewing {PATCH v4 00/19} reverse debugging Message-Id: <20180528071332.9424.27343.stgit@pasha-VirtualBox> - ran into some issues, need clearer understanding of snapshots - posted {RFC PATCH 0/3} Better docker dependency checking Message-Id: <20180608160432.8734-1-alex.bennee(a)linaro.org> - posted {PATCH v1 0/3} Current Travis Patches Message-Id: <20180614125337.24950-1-alex.bennee(a)linaro.org> - posted {PULL 0/3} Travis updates Message-Id: <20180615110903.29674-1-alex.bennee(a)linaro.org> [VIRT-109] https://projects.linaro.org/browse/VIRT-109 Fixing up tests/tcg ~~~~~~~~~~~~~~~~~~~ - finished working on test/tcg series - posted {PATCH v7 00/54} fix building of tests/tcg - last chance to review! Message-Id: <20180615194705.28019-1-alex.bennee(a)linaro.org> - sending the pull req next week :todo KVM CI Loop ([VIRT-2]) ====================== - need to sync-up on the current state of this work :todo [VIRT-2] https://projects.linaro.org/browse/VIRT-2 [our wiki] https://wiki.linaro.org/Core/Virtualization Completed Reviews [1/1] ======================= {PATCH v2 00/13} iommu: support txattrs, support TCG execution, implement TZ MPC Message-Id: <20180604152941.20374-10-peter.maydell(a)linaro.org> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - CLOSING NOTE [2018-06-14 Thu 19:27] Looks good. Absences ======== - YVR18 Connect (17th-21st September 2018) - KVM Forum 2018 (24th-26th October 2018) Current Review Queue ==================== * {Qemu-devel} {PATCH v4b 00/18} target/arm: SVE instructions, part 2 Message-Id: <20180613015641.5667-1-richard.henderson(a)linaro.org> * {PATCH 0/4} KVM: arm64: FPSIMD/SVE fixes for 4.17 Message-Id: <1528976039-25826-1-git-send-email-Dave.Martin(a)arm.com> * {PATCH v4 00/14} fp-test + hardfloat Message-Id: <1528768140-17894-1-git-send-email-cota(a)braap.org> * {RFC PATCH 00/12} tests/tcg: Add TriCore tests Message-Id: <20180501142222.19154-1-kbastian(a)mail.uni-paderborn.de> * {PATCH v4 00/19} reverse debugging Message-Id: <20180528071332.9424.27343.stgit@pasha-VirtualBox> * {Qemu-devel} {RFC PATCH v2 0/7} QEMU binary instrumentation prototype Message-Id: <152819515565.30857.16834004920507717324.stgit@pasha-ThinkPad-T60> -- Alex Bennée

7 years, 6 months

1
0
0 0

[ACTIVITY] report week ending 15 June

by Peter Maydell

Progress: * VIRT-65 [QEMU upstream maintainership] + code review + put together another target-arm pullreq (including more SVE patches) * VIRT-164 [improve Cortex-M emulation] + I have a half-working prototype of small-MPU-regions + sent patches for various preparatory and cleanup work for that + MPC support patchset has been reviewed and needs some minor fixes NB: have shifted next week's non-working day from Weds to Mon due to a meeting on Weds; sorry about the short notice. thanks -- PMM

7 years, 6 months

1
0
0 0

[ACTIVITY] week ending 15th June 2018

by Peter Smith

TCWG-1319 ICF support in clang and lld - Reviewed LLD patches TCWG-1424 Investigate profile information for code-size - Spent some time tracking down problem with using perf=profile and run_under simultaneously. Posted patch upstream. - Investigated how llvm makes use of profile information and found an analysis pass that can be adapted to get the information I'm likely to need. Other - Worked on side-project for tiny-code model. Got it passing the test-suite modulo TLS and one test that was too large for the code model. - Have a good idea of what I'll need to do for TLS, will need to start with assembler support. - Landed https://reviews.llvm.org/D45959 one step closer to removing MCSubargetInfo from assembler backend.

7 years, 6 months

1
0
0 0

Question About Trusted Application (.ta)

by Yin Liu

Hello, I'm learning the Trusted application that can be run in the TEE. I was wondering whether there are some ways to check the .ta file's instructions, just like using objdump or readelf on ELF. I'm also interested how does the .ta be protected? What's the difference between the .ta and normal executable? Would it be possible to give me some information about that? Thanks in advance! Brs, YL

7 years, 6 months

2
1
0 0

Aarch64 Toolchain - aarch64-elf-gcc.exe: error: CreateProcess: No such file or directory - additional info

by Glen Verran

Hi there I apologize for posting this again as I was not subscribed to the mailing list on posting my first message, so if the first message made to the list without me being a subscriber, I apologize. I added some more info as to my issue below. I need to cross-compile an application written in C for ARM v8 (aarch64) and found the toolchain on your website. I am running Windows 10 using Cygwin 32-bit as I am already compiling for arm6, arm7 and Linux (x86 and x64) successfully. I downloaded https://releases.linaro.org/components/toolchain/binaries/latest/aarch64-el… and deployed it into my Cygwin installation with no issues. When I ran my script, I get the following error message: aarch64-elf-gcc.exe: error: CreateProcess: No such file or directory I enabled verbose mode on the GCC and the result is below. My Cygwin's default GCC version is 4.8.3, but I am running 7.2.1 for this. I also tried 4.9.4 as well using a different Cygwin instance. Can you please advise how I can get around this error? I am able to cross-compile using the 100% exact script with all other architectures with the only difference being the toolchain and architecture. I also found references to C:\cygwin\bin in the logs (note the backslashes instead of forward slashes) below which I'd imagine would cause the issue I am experiencing as I have no way to alter the -iprefix in the COLLECT_GCC_OPTIONS as I am not setting this parameter - seems the GCC compiler is injecting this in. I also realised that I needed to use the linux-gnu version of the toolchain and not the ELF version which I did, but got the same results. Cygwin DLL version (just in case). I called: cygcheck -p cygwin1.dll |grep "cygwin:" And it returned: cygwin-2.10.0-1 - cygwin: The UNIX emulation engine cygwin-2.8.2-1 - cygwin: The UNIX emulation engine cygwin-2.9.0-3 - cygwin: The UNIX emulation engine 7.2.1 Using built-in specs. COLLECT_GCC=C:\cygwin\bin\aarch64-elf-gcc.exe Target: aarch64-elf Configured with: '/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/aarch64-elf/snapshots/gcc.git~linaro-7.2-2017.11/configure' SHELL=/bin/bash --with-mpc=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/aarch64-elf/_build/builds/destdir/i686-w64-mingw32 --with-mpfr=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/aarch64-elf/_build/builds/destdir/i686-w64-mingw32 --with-gmp=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/aarch64-elf/_build/builds/destdir/i686-w64-mingw32 --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 --enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a --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/aarch64-elf/_build/sysroots/aarch64-elf --with-sysroot=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/aarch64-elf/_build/builds/destdir/i686-w64-mingw32/aarch64-elf/libc --enable-checking=release --disable-bootstrap --enable-languages=c,c++,lto --with-libiconv-prefix=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/aarch64-elf/_build/builds/destdir/i686-w64-mingw32/usr --build=x86_64-unknown-linux-gnu --host=i686-w64-mingw32 --target=aarch64-elf --prefix=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/aarch64-elf/_build/builds/destdir/i686-w64-mingw32 Thread model: single gcc version 7.2.1 20171011 (Linaro GCC 7.2-2017.11) COLLECT_GCC_OPTIONS='-std=c99' '-Wall' '-I' 'C:/Users/username/git/repo/appvm/vm/src/c/java/include' '-I' 'C:/Users/username/git/repo/appvm/vm/src/c/java/include/linux' '-D' '_POSIX_SOURCE' '-D' '_BSD_SOURCE' '-o' 'C:/Users/username/git/repo/appvm/target/vm/aarch64/app_vm' '-v' '-march=armv8-a' '-mlittle-endian' '-mabi=lp64' cc1 -quiet -v -I C:/Users/username/git/repo/appvm/vm/src/c/java/include -I C:/Users/username/git/repo/appvm/vm/src/c/java/include/linux -iprefix c:\cygwin\bin\../lib/gcc/aarch64-elf/7.2.1/ -D _POSIX_SOURCE -D _BSD_SOURCE C:/Users/username/git/repo/appvm/vm/src/c/main.c -quiet -dumpbase main.c -march=armv8-a -mlittle-endian -mabi=lp64 -auxbase main -Wall -std=c99 -version -o C:\cygwin\tmp\ccXFqWeJ.s aarch64-elf-gcc.exe: error: CreateProcess: No such file or directory 4.9.4 Using built-in specs. COLLECT_GCC=C:\cygwin\bin\aarch64-elf-gcc.exe Target: aarch64-elf Configured with: /home/tcwg-buildslave/workspace/tcwg-make-release/label/docker-trusty-amd64-tcwg-build/target/aarch64-elf/snapshots/gcc-linaro-4.9-2017.01/configure SHELL=/bin/bash --with-mpc=/home/tcwg-buildslave/workspace/tcwg-make-release/label/docker-trusty-amd64-tcwg-build/target/aarch64-elf/_build/builds/destdir/i686-w64-mingw32 --with-mpfr=/home/tcwg-buildslave/workspace/tcwg-make-release/label/docker-trusty-amd64-tcwg-build/target/aarch64-elf/_build/builds/destdir/i686-w64-mingw32 --with-gmp=/home/tcwg-buildslave/workspace/tcwg-make-release/label/docker-trusty-amd64-tcwg-build/target/aarch64-elf/_build/builds/destdir/i686-w64-mingw32 --with-gnu-as --with-gnu-ld --disable-libmudflap --enable-lto --enable-objc-gc --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 --enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a --enable-threads=no --disable-multiarch --with-newlib --with-build-sysroot=/home/tcwg-buildslave/workspace/tcwg-make-release/label/docker-trusty-amd64-tcwg-build/target/aarch64-elf/_build/sysroots/aarch64-elf --with-sysroot=/home/tcwg-buildslave/workspace/tcwg-make-release/label/docker-trusty-amd64-tcwg-build/target/aarch64-elf/_build/builds/destdir/i686-w64-mingw32/aarch64-elf/libc --enable-checking=release --disable-bootstrap --enable-languages=c,c++,lto --build=x86_64-unknown-linux-gnu --host=i686-w64-mingw32 --target=aarch64-elf --prefix=/home/tcwg-buildslave/workspace/tcwg-make-release/label/docker-trusty-amd64-tcwg-build/target/aarch64-elf/_build/builds/destdir/i686-w64-mingw32 Thread model: single gcc version 4.9.4 (Linaro GCC 4.9-2017.01) COLLECT_GCC_OPTIONS='-std=c99' '-Wall' '-I' 'c:/Users/username/git/repo/appvm/vm/src/c/java/include' '-I' 'c:/Users/username/git/repo/appvm/vm/src/c/java/include/linux' '-D' '_POSIX_SOURCE' '-D' '_BSD_SOURCE' '-o' 'c:/Users/username/git/repo/appvm/target/vm/aarch64/app_vm' '-v' '-mlittle-endian' '-mabi=lp64' cc1 -quiet -v -I c:/Users/username/git/repo/appvm/vm/src/c/java/include -I c:/Users/username/git/repo/appvm/vm/src/c/java/include/linux -iprefix c:\cygwin\bin\../lib/gcc/aarch64-elf/4.9.4/ -D _POSIX_SOURCE -D _BSD_SOURCE c:/Users/username/git/repo/appvm/vm/src/c/main.c -quiet -dumpbase main.c -mlittle-endian -mabi=lp64 -auxbase main -Wall -std=c99 -version -o C:\cygwin\tmp\ccXoLYc6.s aarch64-elf-gcc.exe: error: CreateProcess: No such file or directory ~Glen

7 years, 6 months

1
0
0 0

[ACTIVITY] week ending 10 Jun 2018

by Richard Henderson

Progress: [VIRT-198 # QEMU: SVE Emulation Support ] Some rebasing based on review. [Upstream] Two iterations of splitting do_syscall. r~

7 years, 6 months

1
0
0 0

Aarch64 Toolchain - aarch64-elf-gcc.exe: error: CreateProcess: No such file or directory

by Glen Verran

Hi there I need to cross-compile an application written in C for ARM v8 (aarch64) and found the toolchain on your website. I am running Windows 10 using Cygwin 32-bit as I am already compiling for arm6, arm7 and Linux (x86 and x64) successfully. I downloaded https://releases.linaro.org/components/toolchain/binaries/latest/aarch64-el… and deployed it into my Cygwin installation with no issues. When I ran my script, I get the following error message: aarch64-elf-gcc.exe: error: CreateProcess: No such file or directory I enabled verbose mode on the GCC and the result is below. My Cygwin's default GCC version is 4.8.3, but I am running 7.2.1 for this. I also tried 4.9.4 as well using a different Cygwin instance. Can you please advise how I can get around this error? I am able to cross-compile using the 100% exact script with all other architectures with the only difference being the toolchain and architecture. Cygwin DLL version (just in case). I called: cygcheck -p cygwin1.dll |grep "cygwin:" And it returned: cygwin-2.10.0-1 - cygwin: The UNIX emulation engine cygwin-2.8.2-1 - cygwin: The UNIX emulation engine cygwin-2.9.0-3 - cygwin: The UNIX emulation engine 7.2.1 Using built-in specs. COLLECT_GCC=C:\cygwin\bin\aarch64-elf-gcc.exe Target: aarch64-elf Configured with: '/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/aarch64-elf/snapshots/gcc.git~linaro-7.2-2017.11/configure' SHELL=/bin/bash --with-mpc=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/aarch64-elf/_build/builds/destdir/i686-w64-mingw32 --with-mpfr=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/aarch64-elf/_build/builds/destdir/i686-w64-mingw32 --with-gmp=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/aarch64-elf/_build/builds/destdir/i686-w64-mingw32 --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 --enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a --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/aarch64-elf/_build/sysroots/aarch64-elf --with-sysroot=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/aarch64-elf/_build/builds/destdir/i686-w64-mingw32/aarch64-elf/libc --enable-checking=release --disable-bootstrap --enable-languages=c,c++,lto --with-libiconv-prefix=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/aarch64-elf/_build/builds/destdir/i686-w64-mingw32/usr --build=x86_64-unknown-linux-gnu --host=i686-w64-mingw32 --target=aarch64-elf --prefix=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/aarch64-elf/_build/builds/destdir/i686-w64-mingw32 Thread model: single gcc version 7.2.1 20171011 (Linaro GCC 7.2-2017.11) COLLECT_GCC_OPTIONS='-std=c99' '-Wall' '-I' 'C:/Users/username/git/repo/appvm/vm/src/c/java/include' '-I' 'C:/Users/username/git/repo/appvm/vm/src/c/java/include/linux' '-D' '_POSIX_SOURCE' '-D' '_BSD_SOURCE' '-o' 'C:/Users/username/git/repo/appvm/target/vm/aarch64/app_vm' '-v' '-march=armv8-a' '-mlittle-endian' '-mabi=lp64' cc1 -quiet -v -I C:/Users/username/git/repo/appvm/vm/src/c/java/include -I C:/Users/username/git/repo/appvm/vm/src/c/java/include/linux -iprefix c:\cygwin\bin\../lib/gcc/aarch64-elf/7.2.1/ -D _POSIX_SOURCE -D _BSD_SOURCE C:/Users/username/git/repo/appvm/vm/src/c/main.c -quiet -dumpbase main.c -march=armv8-a -mlittle-endian -mabi=lp64 -auxbase main -Wall -std=c99 -version -o C:\cygwin\tmp\ccXFqWeJ.s aarch64-elf-gcc.exe: error: CreateProcess: No such file or directory 4.9.4 Using built-in specs. COLLECT_GCC=C:\cygwin\bin\aarch64-elf-gcc.exe Target: aarch64-elf Configured with: /home/tcwg-buildslave/workspace/tcwg-make-release/label/docker-trusty-amd64-tcwg-build/target/aarch64-elf/snapshots/gcc-linaro-4.9-2017.01/configure SHELL=/bin/bash --with-mpc=/home/tcwg-buildslave/workspace/tcwg-make-release/label/docker-trusty-amd64-tcwg-build/target/aarch64-elf/_build/builds/destdir/i686-w64-mingw32 --with-mpfr=/home/tcwg-buildslave/workspace/tcwg-make-release/label/docker-trusty-amd64-tcwg-build/target/aarch64-elf/_build/builds/destdir/i686-w64-mingw32 --with-gmp=/home/tcwg-buildslave/workspace/tcwg-make-release/label/docker-trusty-amd64-tcwg-build/target/aarch64-elf/_build/builds/destdir/i686-w64-mingw32 --with-gnu-as --with-gnu-ld --disable-libmudflap --enable-lto --enable-objc-gc --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 --enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a --enable-threads=no --disable-multiarch --with-newlib --with-build-sysroot=/home/tcwg-buildslave/workspace/tcwg-make-release/label/docker-trusty-amd64-tcwg-build/target/aarch64-elf/_build/sysroots/aarch64-elf --with-sysroot=/home/tcwg-buildslave/workspace/tcwg-make-release/label/docker-trusty-amd64-tcwg-build/target/aarch64-elf/_build/builds/destdir/i686-w64-mingw32/aarch64-elf/libc --enable-checking=release --disable-bootstrap --enable-languages=c,c++,lto --build=x86_64-unknown-linux-gnu --host=i686-w64-mingw32 --target=aarch64-elf --prefix=/home/tcwg-buildslave/workspace/tcwg-make-release/label/docker-trusty-amd64-tcwg-build/target/aarch64-elf/_build/builds/destdir/i686-w64-mingw32 Thread model: single gcc version 4.9.4 (Linaro GCC 4.9-2017.01) COLLECT_GCC_OPTIONS='-std=c99' '-Wall' '-I' 'c:/Users/username/git/repo/appvm/vm/src/c/java/include' '-I' 'c:/Users/username/git/repo/appvm/vm/src/c/java/include/linux' '-D' '_POSIX_SOURCE' '-D' '_BSD_SOURCE' '-o' 'c:/Users/username/git/repo/appvm/target/vm/aarch64/app_vm' '-v' '-mlittle-endian' '-mabi=lp64' cc1 -quiet -v -I c:/Users/username/git/repo/appvm/vm/src/c/java/include -I c:/Users/username/git/repo/appvm/vm/src/c/java/include/linux -iprefix c:\cygwin\bin\../lib/gcc/aarch64-elf/4.9.4/ -D _POSIX_SOURCE -D _BSD_SOURCE c:/Users/username/git/repo/appvm/vm/src/c/main.c -quiet -dumpbase main.c -mlittle-endian -mabi=lp64 -auxbase main -Wall -std=c99 -version -o C:\cygwin\tmp\ccXoLYc6.s aarch64-elf-gcc.exe: error: CreateProcess: No such file or directory ~Glen

7 years, 6 months

1
0
0 0

[ACTIVITY] Week 23

by Yvan Roux

o GNU releases * Gave support to Mark. o LLVM * Deployed LLVM patch benchmarking job o Misc * Various meetings and discussions.

7 years, 6 months

1
0
0 0

[ACTIVITY] week ending Jun. 10 2018

by Alex Bennée

SVE Support ([VIRT-198]) ======================== [VIRT-198] https://projects.linaro.org/browse/VIRT-198 RISU Support for SVE ([VIRT-199]) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - started work on next [iteration of SVE series] - added variable size reginfo for backwards compatibility - various unrelated build clean-ups and tweaks - left model generating the testcases over the weekend - post patches to list :todo [VIRT-199] https://projects.linaro.org/browse/VIRT-199 [iteration of SVE series] https://github.com/stsquad/risu/tree/add-sve-support-v3 Upstream Work ([VIRT-109]) ========================== - started reviewing {PATCH v4 00/19} reverse debugging Message-Id: <20180528071332.9424.27343.stgit@pasha-VirtualBox> - ran into some issues, need clearer understanding of snapshots - posted {PATCH v1 0/7} updates for Docker Message-Id: <20180604145109.30498-1-alex.bennee(a)linaro.org> - posted {PULL 0/6} Some docker updates Message-Id: <20180605160541.10664-1-alex.bennee(a)linaro.org> - posted {RFC PATCH 0/3} Better docker dependency checking Message-Id: <20180608160432.8734-1-alex.bennee(a)linaro.org> [VIRT-109] https://projects.linaro.org/browse/VIRT-109 [v4 of the tb_lock removal patches] https://github.com/cota/qemu/tree/tb-lock-removal-redux-v4 Fixing up tests/tcg ~~~~~~~~~~~~~~~~~~~ - worked on v6 of tests/tcg - --enable-debug threw up a crash in sh4-linux-user/testthread and gusa handling - fun and games with dependencies for building docker images from makefiles - posted {PATCH v6 00/49} fix building of tests/tcg Message-Id: <20180608123307.24773-1-alex.bennee(a)linaro.org> KVM CI Loop ([VIRT-2]) ====================== - need to sync-up on the current state of this work :todo [VIRT-2] https://projects.linaro.org/browse/VIRT-2 [our wiki] https://wiki.linaro.org/Core/Virtualization Completed Reviews [2/2] ======================= {PATCH v3 00/17} tcg: tb_lock removal redux v3 Message-Id: <1526945967-9687-1-git-send-email-cota(a)braap.org> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - CLOSING NOTE [2018-06-04 Mon 13:21] v4 was posted, tested ok. {PATCH v3 00/19} reverse debugging Message-Id: <20180523064941.26016.74274.stgit@pasha-VirtualBox> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - CLOSING NOTE [2018-06-04 Mon 16:32] v4 posted Absences ======== - YVR18 Connect (17th-21st September 2018) - KVM Forum 2018 (24th-26th October 2018) Current Review Queue ==================== * {RFC PATCH 00/12} tests/tcg: Add TriCore tests Message-Id: <20180501142222.19154-1-kbastian(a)mail.uni-paderborn.de> * {PATCH v4 00/19} reverse debugging Message-Id: <20180528071332.9424.27343.stgit@pasha-VirtualBox> * {Qemu-devel} {RFC PATCH v2 0/7} QEMU binary instrumentation prototype Message-Id: <152819515565.30857.16834004920507717324.stgit@pasha-ThinkPad-T60> * {Qemu-devel} {PATCH v3b 00/18} target/arm: SVE instructions, part 2 Message-Id: <20180530180120.13355-1-richard.henderson(a)linaro.org> * {Qemu-devel} {PATCH v3 0/5} Acceptance/functional tests Message-Id: <20180529193730.9204-1-crosa(a)redhat.com> * {PATCH v3 00/15} fp-test + hardfloat Message-Id: <1522883475-27858-1-git-send-email-cota(a)braap.org> -- Alex Bennée

7 years, 6 months

1
0
0 0

[ACTIVITY] report week ending 8 June

by Peter Smith

[ACTIVITY] - Landed D44928, we should pass the subtarget through to fixups and relaxation now. The only remaining use of the subtarget in the assembler backend is for writeNop(). Patches to fix that are upstream but I'm not hopeful that anyone will want to review them due to the cost/benefit. - Wrote up some thoughts on Maxim's idea to use pgo to optimize hot code for time, but cold code for size in an attempt to retain as much as performance as possible while reducing code-size. - Some investigation into the --pgo option of lnt. There seem to be some pre-requisites and some interactions that have made it difficult to get results: -- Needs compiler-rt, duh! But it didn't tell me until after I'd waited for everything to compile. -- Failed when I enabled perf and pgo, looks to be a configuration problem where profile-generate and profile-use are set simultaneously. Probably a cmake problem. - Some work on side-project to implement the tiny code model -- Have something working on small examples, much more testing needed. -- Need to decide what to do about TLS. Peter

7 years, 6 months

1
0
0 0

[ACTIVITY] report week ending 8 June

by Peter Maydell

Progress: * VIRT-65 [QEMU upstream maintainership] + reviewed the next chunk of rth's SVE patches + various other misc code review + updated windows cross-build environment to handle impending bump in our minimum supported glib version * VIRT-164 [improve Cortex-M emulation] + revised and sent out v2 of the iommu/MPC emulation patchset + started looking at implementation of small-MPU-regions thanks -- PMM

7 years, 6 months

1
0
0 0

[ACTIVITY] 4-8 June 2018

by Christophe Lyon

== Progress == * GCC - FDPIC patch series: received some feedback. Will have to iterate. - Rebased uclibc patches on top of uclibc-ng, now debugging build problems * GCC upstream validation: - looking at some random noise in testing * Infrastructure: - patch reviews - cleanup/improvements * misc (conf-calls, meetings, emails, ....) == Next == * FDPIC: uclibc * GCC upstream validation * Training Wed/Thu

7 years, 6 months

1
0
0 0

[ACTIVITY] Week 22

by Yvan Roux

o LLVM * Thumbv8 bot failures [TCWG-1400]: - Fix committed upstream - Thumbv8 bots now green * Updated staging bots docker images o Misc * Various meetings and discussions.

7 years, 6 months

1
0
0 0

[ACTIVITY] week ending 3 Jun 2018

by Richard Henderson

Progress: [VIRT-198 # QEMU: SVE Emulation Support ] Part 2 posted. [Upstream] Review of tb_lock removal; it's failing it's own asserts. :-/ Respin interp_dirfd patchset, now with host fd protection. Posted an RFC for splitting up the ~5000 line do_syscall function. [Cortex Strings] Found two bugs in my sve string implementations. Submitted the results to cortex-strings. (This is the mechanism by which I plan to test the first-fault load implementation within qemu; the testsuite tries string operations near a page boundary.) Beginning to incorporate feedback from Richard Sandiford. So far strlen, strcmp, strcpy updated, but not yet reposted. r~

7 years, 6 months

1
0
0 0

[ACTIVITY] week ending Jun. 3 2018

by Alex Bennée

Upstream Work ([VIRT-109]) ========================== - catch-up on review queue :todo - posted {PATCH v1 0/8} Travis stability and a few docker patches Message-Id: <20180530110655.22022-1-alex.bennee(a)linaro.org> - posted {PULL 0/7} Travis updates Message-Id: <20180601162101.895-1-alex.bennee(a)linaro.org> - reviewing {PATCH v3 00/17} tcg: tb_lock removal redux v3 Message-Id: <1526945967-9687-1-git-send-email-cota(a)braap.org> - getting good results with cpu_get_tb_cpu_state at the top now - investigating difference with rth's experience on aarch64 - can replicate the coldfire crash though [VIRT-109] https://projects.linaro.org/browse/VIRT-109 Fixing up tests/tcg ~~~~~~~~~~~~~~~~~~~ - working on v6 of tests/tcg - --enable-debug threw up a crash in sh4-linux-user/testthread and gusa handling KVM CI Loop ([VIRT-2]) ====================== - need to sync-up on the current state of this work :todo [VIRT-2] https://projects.linaro.org/browse/VIRT-2 [our wiki] https://wiki.linaro.org/Core/Virtualization Other Tasks =========== - SyncQuacer DevBox now booting Gentoo \o/ - been making Gentoo's [arm64 story a bit more desktopy] - testing fwupdate mechanism for fwupdate - Messing around with virtio-pci - got -nic and networking on PCI working nicely - however virtio-scsi seems broken and not sure why [arm64 story a bit more desktopy] https://github.com/stsquad/gentoo/tree/arm-keywords-so-far Completed Reviews [0/0] ======================= Absences ======== - Short week from holidays/bank-holidays - VNC18 Connect (17th-21st September 2018) - KVM Forum 2018 (24th-26th October 2018) Current Review Queue ==================== * {PATCH v3 00/17} tcg: tb_lock removal redux v3 Message-Id: <1526945967-9687-1-git-send-email-cota(a)braap.org> * {RFC PATCH 00/12} tests/tcg: Add TriCore tests Message-Id: <20180501142222.19154-1-kbastian(a)mail.uni-paderborn.de> * {Qemu-devel} {PATCH v3 0/5} Acceptance/functional tests Message-Id: <20180529193730.9204-1-crosa(a)redhat.com> * {PATCH v4 00/19} reverse debugging Message-Id: <20180528071332.9424.27343.stgit@pasha-VirtualBox> * {PATCH v3 00/15} fp-test + hardfloat Message-Id: <1522883475-27858-1-git-send-email-cota(a)braap.org> * {PATCH v3 00/19} reverse debugging Message-Id: <20180523064941.26016.74274.stgit@pasha-VirtualBox> -- Alex Bennée

7 years, 6 months

1
0
0 0

[ACTIVITY] report week ending 1 Jun

by Peter Smith

[ACTIVITY] Upstream reviews for LLD. Trying to be more proactive here now that there are fewer maintainers. [TCWG-1420] Initial investigation into some proposed linker enhancements for embedded systems - Mostly features already implemented in proprietary linkers such as AT and an equivalent to .any. - Completed initial investigation with links to TI/IAR documentation, binutils discussions. - Some thoughts on which of the features might be implemented cleanly enough to be upstreamed. Pinged llvm-mc subtarget reviews (no response) Spent some more time investigating a tiny-code model for AArch64 in an attempt to teach myself more about LLVM.

7 years, 6 months

1
0
0 0

[ACTIVITY] report week ending 1 Jun

by Peter Maydell

Progress: [short week, 3 days] * VIRT-65 [QEMU upstream maintainership] + code review + some more conversions of devices using 'old_mmio' + looking at trying to fix non-migrated RAM regions in various devices * VIRT-164 [improve Cortex-M emulation] + wrote some minor cleanup patches (including giving a helpful error message for attempts to use an M-profile CPU without an NVIC, rather than crashing) + reviewing first few patches from the micro:bit emulation GSoC students + reviewed and added comments on Stefan's list of tasks for Cortex-M0 emulation Absences: * Aug 27 -- Sep 14: holiday * Sep 17 -- 21: Linaro Connect (Vancouver) * Oct 22 -- 26: KVM Forum (Edinburgh; unconfirmed) * NB: I work a 4 day week, excluding Wednesdays thanks -- PMM

7 years, 6 months

1
0
0 0

[ACTIVITY] 28 May-1 June 2018

by Christophe Lyon

== Progress == * GCC - FDPIC patch series: received a bit of feedback. Noticed problems with v8m and libssp, should be easy to fix - Started rebasing uclibc patches on top of uclibc-ng * GCC upstream validation: - reported a few failures/regressions - looking at some random noise in testing * Infrastructure: - patch reviews - cleanup/improvements * misc (conf-calls, meetings, emails, ....) == Next == * FDPIC: uclibc * GCC upstream validation * Training Mon/Tue

7 years, 6 months

1
0
0 0

[ACTIVITY] Week 21

by Yvan Roux

== Progress == o GNU release transition * 6.4 and 7.3 2018.05 RC1 deployed o LLVM * Thumbv8 bot failures [TCWG-1400]: - Testing fix on arm, armhf, armv7 and armv8. o Misc * Various meetings and discussions.

7 years, 6 months

1
0
0 0

[ACTIVITY] 21 - 25 May 2018

by Prathamesh Kulkarni

== This Week == * TCWG-1234: Code hoisting and register pressure (8/10) - Created patches for restricting hoisting out of blocks on loop exit but that was false alarm. - Investigating interaction of forwprop, code hoisting and register pressure. - Started upstream discussion. * GCC bugs (1/10) - TCWG-125: static_cast not working on ARM hardfp: Asked upstream on libvolk list for help to reproduce. - PR85787: Created patch, investigating regressions caused due to it. * Misc (1/10) - Meetings == Next Week == - TCWG-1234 - GCC bugs

7 years, 6 months

1
0
0 0

[ACTIVITY] report week ending 25 May

by Peter Maydell

Progress: * VIRT-65 [QEMU upstream maintainership] + sent patch for minor bug where FRECPX was not honouring FPCR.FZ + looking at migration failure for TCG VMs using Secure mode. I know what the bug is, but need to figure out how to fix it without breaking migration compatibility for TCG VMs which don't use Secure mode... + various miscellaneous minor bug fixing and code review * VIRT-164 [improve Cortex-M emulation] + MPC emulation: - sent out first version of patchset that implements the required IOMMU core code features and the MPC device that uses them; fielded various code review discussions on it thanks -- PMM

7 years, 6 months

1
0
0 0

[ACTIVITY] week ending May. 27 2018

by Alex Bennée

Upstream Work ([VIRT-109]) ========================== - catch-up on review queue :todo Fixing up tests/tcg ~~~~~~~~~~~~~~~~~~~ - posted {PATCH v5 00/49} fix buildings of tests/tcg Message-Id: <20180525141915.6497-1-alex.bennee(a)linaro.org> KVM CI Loop ([VIRT-2]) ====================== - need to sync-up on the current state of this work :todo Other Tasks =========== - SyncQuacer DevBox now booting Gentoo \o/ Completed Reviews [10/10] ========================= {Qemu-devel} {PATCH 0/9} Honor CPU_DUMP_FPU Message-Id: <20180511035240.4016-1-richard.henderson(a)linaro.org> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - CLOSING NOTE [2018-05-21 Mon 14:11] Merged already {PATCH 00/27} iommu: support txattrs, support TCG execution, implement TZ MPC Message-Id: <20180521140402.23318-1-peter.maydell(a)linaro.org> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - CLOSING NOTE [2018-05-23 Wed 12:41] Plumbing looks pretty good, only minor comments. Didn't delve too deeply into the MPC behaviour itself. {PATCH v10 00/18} KVM: arm64: Optimise FPSIMD context switching Message-Id: <1527005119-6842-1-git-send-email-Dave.Martin(a)arm.com> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - CLOSING NOTE [2018-05-24 Thu 16:09] Brings back memories ;-) Absences ======== - Bank Holiday Monday (28th May) - VNC18 Connect (17th-21st September 2018) - KVM Forum 2018 (24th-26th October 2018) Current Review Queue ==================== * {RFC PATCH 00/12} tests/tcg: Add TriCore tests Message-Id: <20180501142222.19154-1-kbastian(a)mail.uni-paderborn.de> * {PATCH v3 00/17} tcg: tb_lock removal redux v3 Message-Id: <1526945967-9687-1-git-send-email-cota(a)braap.org> * {PATCH v3 00/15} fp-test + hardfloat Message-Id: <1522883475-27858-1-git-send-email-cota(a)braap.org> * {PATCH v3 00/19} reverse debugging Message-Id: <20180523064941.26016.74274.stgit@pasha-VirtualBox> * {PATCH} tests/boot-serial: Do not delete the output file in case of errors Message-Id: <1526977831-31129-1-git-send-email-thuth(a)redhat.com> * {Qemu-arm} {PATCH v3-a 00/27} target/arm: Scalable Vector Extension Message-Id: <20180516223007.10256-1-richard.henderson(a)linaro.org> -- Alex Bennée

7 years, 6 months

1
0
0 0

[ACTIVITY] 21-25 May 2018

by Christophe Lyon

== Progress == * GCC - FDPIC patch series sent upstream * GCC upstream validation: - reported a few failures/regressions - looking at some random noise in testing * Infrastructure: - patch reviews - cleanup/improvements * misc (conf-calls, meetings, emails, ....) == Next == * FDPIC: uclibc * GCC upstream validation

7 years, 6 months

1
0
0 0

[ACTIVITY] Week ending 24th May

by Peter Smith

Half of the week spent investigating identical code folding -icf=safe. Turns out that upstream have a proposal that is much further along so shifted focus on to doing as much as I can to help it along. Found out that for some use cases of AArch64 PIC the small code model is inappropriate as the code segments may not be 4k aligned. Started looking into what it would take to implement the tiny code model in LLVM (supports only small and large at the moment). Built a small prototype to handle the easiest absolute addressing case, much more work needed to handle PIC and TLS. Not a lot of tangible progress, but I think I have learned a bit more about LLVM. Planned Absences - Friday 25th May (holiday). - Monday 28th May (UK public holiday)

7 years, 6 months

1
0
0 0

Re: LINARO GCC 5.5 Differences in the manifest file

by Andrej.Gantvorg＠wago.com

> > > Hello, > > > > > > I just noticed that the manifest file of the Linaro gcc-5.5-2017.10 release under > > http://releases.linaro.org/components/toolchain/gcc-linaro/5.5- > 2017.10/x86_64.arm- > > linux-gnueabihf-gcc-linaro-5.5-2017.10-manifest.txt from January, 13th 2018 > differs > > from the original version from October 2017: the binutils, gdb and abe versions > are > > different. > > > > > > Could you please tell me the reason for the changes? > > > > > > Thank you very much! > > > > > > Hi Andrej, > > > > I don't fully understand. Could you provide both original and new versions of > the > > manifest? > > Hello Maxim, > > I am sorry for the delayed answer but I was AFK for quite a long period of time. > > Please find attached a diff between a manifest version I archived on October, 28th 2017 and > the one currently available for download. Sorry again, the attachment seems to have been removed. Here is the diff: =================================== --- x86_64.arm-linux-gnueabihf-gcc-linaro-5.5-2017.10-manifest.old.txt 2018-05-24 10:59:23.758376365 +0200 +++ x86_64.arm-linux-gnueabihf-gcc-linaro-5.5-2017.10-manifest.new.txt 2018-01-13 10:36:52.000000000 +0100 @@ -63,11 +63,11 @@ # Component data for binutils binutils_url=http://git.linaro.org/git/toolchain -binutils_branch=users/linaro/binutils-2_25-branch -binutils_revision=f7897e0c6bb3803f2603f5ebabeaffdd49b1ab77 +binutils_branch=linaro_binutils-2_25-branch +binutils_revision=331ccedd381918185634a0f6c864eea4e2d7c960 binutils_filespec=binutils-gdb.git binutils_mingw_only="no" -binutils_configure="--enable-lto --enable-plugins --disable-werror CPPFLAGS=-UFORTIFY_SOURCE --with-pkgversion=Linaro_Binutils-2017.10 --disable-gdb --disable-sim --disable-libdecnumber --disable-readline --with-sysroot=${sysroots}" +binutils_configure="--enable-lto --enable-plugins --disable-werror CPPFLAGS=-UFORTIFY_SOURCE --with-pkgversion=Linaro_Binutils-2017.11.08 --disable-gdb --disable-sim --disable-libdecnumber --disable-readline --with-sysroot=${sysroots}" binutils_staticlink="yes" # Component data for gcc @@ -81,7 +81,7 @@ gcc_mingw_extraconf="--with-libiconv-prefix=${local_builds}/destdir/${host}/usr" gcc_staticlink="no" gcc_stage1_flags="--with-mpc=${local_builds}/destdir/${host} --with-mpfr=${local_builds}/destdir/${host} --with-gmp=${local_builds}/destdir/${host} --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 --disable-multilib --with-float=hard --with-fpu=vfpv3-d16 --with-mode=thumb --with-tune=cortex-a9 --with-arch=armv7-a --enable-threads=posix --enable-multiarch --enable-libstdcxx-time=yes --disable-libssp --disable-libquadmath --disable-threads --without-headers --with-newlib --disable-libmudflap --disable-bootstrap --disable-decimal-float --disable-libgomp --disable-libatomic --disable-libsanitizer --disable-plugins --disable-libitm --enable-languages=c --with-sysroot=${local_builds}/sysroot-arm-linux-gnueabihf --disable-shared --with-glibc-version=2.18" -gcc_stage2_flags="--with-mpc=${local_builds}/destdir/${host} --with-mpfr=${local_builds}/destdir/${host} --with-gmp=${local_builds}/destdir/${host} --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 --disable-multilib --with-float=hard --with-fpu=vfpv3-d16 --with-mode=thumb --with-tune=cortex-a9 --with-arch=armv7-a --enable-threads=posix --enable-multiarch --enable-libstdcxx-time=yes --with-build-sysroot=${sysroots} --with-sysroot=${local_builds}/destdir/${host}/arm-linux-gnueabihf/libc --enable-checking=release --disable-bootstrap --enable-languages=c,c++,fortran,lto" +gcc_stage2_flags="--with-mpc=${local_builds}/destdir/${host} --with-mpfr=${local_builds}/destdir/${host} --with-gmp=${local_builds}/destdir/${host} --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 --disable-multilib --with-float=hard --with-fpu=vfpv3-d16 --with-mode=thumb --with-tune=cortex-a9 --with-arch=armv7-a --enable-threads=posix --enable-multiarch --enable-libstdcxx-time=yes --with-build-sysroot=${sysroots} --with-sysroot=${local_builds}/destdir/${host}/arm-linux-gnueabihf/libc --enable-checking=yes --disable-bootstrap --enable-languages=c,c++,fortran,lto" # Component data for glibc glibc_url=http://git.linaro.org/git/toolchain @@ -95,17 +95,17 @@ # Component data for gdb gdb_url=http://git.linaro.org/git/toolchain gdb_branch=gdb-8.0-branch -gdb_revision=0edf338067489d3d9c8599ebc2e3ff1398afac44 +gdb_revision=24c10fa29a033d9c6033645cee9327d380b1f411 gdb_filespec=binutils-gdb.git gdb_mingw_only="no" -gdb_configure="--with-gnu-ld --enable-plugins --enable-tui --with-pkgversion=Linaro_GDB-2017.10 --disable-gas --disable-binutils --disable-ld --disable-gold --disable-gprof --with-python=yes" +gdb_configure="--with-gnu-ld --enable-plugins --enable-tui --with-pkgversion=Linaro_GDB-2017.11.08 --disable-gas --disable-binutils --disable-ld --disable-gold --disable-gprof --with-python=yes" gdb_mingw_extraconf="--disable-tui --with-python=${local_snapshots}/python-2.7.4-mingw32 CFLAGS=-I${local_builds}/destdir/${host}/usr/include LDFLAGS=-L${local_builds}/destdir/${host}/usr/lib" gdb_staticlink="yes" # Component data for gdbserver gdbserver_url=http://git.linaro.org/git/toolchain gdbserver_branch=gdb-8.0-branch -gdbserver_revision=0edf338067489d3d9c8599ebc2e3ff1398afac44 +gdbserver_revision=24c10fa29a033d9c6033645cee9327d380b1f411 gdbserver_filespec=binutils-gdb.git gdbserver_mingw_only="no" gdbserver_configure="LDFLAGS=-static CPPFLAGS=--sysroot=${sysroots} CFLAGS=--sysroot=${sysroots} CXXFLAGS=--sysroot=${sysroots}" @@ -114,7 +114,7 @@ clibrary=glibc target=arm-linux-gnueabihf -manifestid=b5618ef7ab78715b9d0116deda80608ae3fe2d53 +manifestid=681cc3860bd43b0df639ca30dbf8a0a2ad5ce659 ############################################################################## # Everything below this line is only for informational purposes for developers @@ -124,21 +124,21 @@ build: linux host: x86_64-unknown-linux-gnu kernel: 4.4.0-45-generic -hostname: 5b2ef4f080c5 +hostname: a87b0fddd62a distribution: trusty host_gcc: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) # These aren't used in the repeat build. just a sanity check for developers -build directory: /home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/arm-linux-gnueabihf/_build/builds -sysroot directory: /home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/arm-linux-gnueabihf/_build/sysroots/arm-linux-gnueabihf -snapshots directory: /home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/arm-linux-gnueabihf/snapshots +build directory: /home/tcwg-buildslave/workspace/tcwg-buildfarm/arm-linux-gnueabihf/_build/builds +sysroot directory: /home/tcwg-buildslave/workspace/tcwg-buildfarm/arm-linux-gnueabihf/_build/sysroots/arm-linux-gnueabihf +snapshots directory: /home/tcwg-buildslave/workspace/tcwg-buildfarm/arm-linux-gnueabihf/snapshots git reference directory: /home/tcwg-buildslave/snapshots-ref abe_url=https://git-us.linaro.org/toolchain abe_branch=branch= -abe_revision=333add3ae07b35815672a8a1d03eb443e5ea87fe +abe_revision=a64e7b393c1181cfad5e9a30f75b83bbc317838b abe_filespec=abe.git -abe_configure="--with-local-snapshots=${local_snapshots} --with-git-reference-dir=/home/tcwg-buildslave/snapshots-ref" +abe_configure="--with-local-snapshots=${local_snapshots} --with-git-reference-dir=/home/tcwg-buildslave/snapshots-ref --with-languages=default --enable-schroot-test" --------------------- gcc ---------------------- commit be42a8fd29c966d67ad17329dcafca50c9826c4f @@ -151,23 +151,12 @@ * LINARO-VERSION: Update. --------------------- binutils ---------------------- -commit f7897e0c6bb3803f2603f5ebabeaffdd49b1ab77 -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. - - PR gas/20364 - * config/tc-aarch64.c (s_ltorg): Change the mapping state after - aligning the frag. - (aarch64_init): Treat rs_align frags in code sections as - containing code, not data. - * testsuite/gas/aarch64/pr20364.s: New test. - * testsuite/gas/aarch64/pr20364.d: New test driver. - - Cherry-pick of 7ea12e5c3ad54da440c08f32da09534e63e515ca - - Change-Id: I6bb37f33419cbf54e52c8d54ef0d1c18fdc85878 +commit 331ccedd381918185634a0f6c864eea4e2d7c960 +Merge: 441de95 8f2db47 +Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> +Date: Thu Oct 20 13:04:11 2016 -0200 + + Merge branch 'binutils-2_25-branch' into linaro_binutils-2_25-branch --------------------- glibc ---------------------- commit a67ffcfae3a020e70ef70d5f9f975e54354fb5e0 @@ -197,11 +186,11 @@ * io/ftwtest-sh: Also trap on exit to remove temporary files. --------------------- abe ---------------------- -commit 333add3ae07b35815672a8a1d03eb443e5ea87fe -Author: Yvan Roux <yvan.roux(a)linaro.org> -Date: Thu Nov 9 14:57:03 2017 +0100 +commit a64e7b393c1181cfad5e9a30f75b83bbc317838b +Author: Christophe Lyon <christophe.lyon(a)linaro.org> +Date: Tue Sep 12 11:57:45 2017 +0000 - config/gcc[567]/binutils.conf: Switch to upstream users/linaro branches. + Cleanup: remove unused references to makeversion/MAKEVERSION. - Change-Id: I47d4c82b02ffad83191f70e8e226e301e8eb0b60 + Change-Id: I207bf298cdeb812ab1e0e1dacdbb3bcd515f0332

7 years, 6 months

1
0
0 0

WG: Linaro Test

by Andrej.Gantvorg＠wago.com

Hello, I just noticed that the manifest file of the Linaro gcc-5.5-2017.10 release under http://releases.linaro.org/components/toolchain/gcc-linaro/5.5-2017.10/x86_… from January, 13th 2018 differs from the original version from October 2017: the binutils, gdb and abe versions are different. Could you please tell me the reason for the changes? Thank you very much! Andrej Gantvorg

7 years, 6 months

2
2
0 0

[ANNOUNCE] Linaro Binary Toolchain Release-Candidate GCC 7.3-2018.05-rc1

by Mark Murray

The Linaro Binary Toolchain ============================ The Linaro GCC 7.3-2018.05-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.3-2018.05-rc1/ (binaries) http://snapshots.linaro.org/components/toolchain/binaries/7.3-2018.05-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.3-2018.05-rc1 http://snapshots.linaro.org/components/toolchain/gcc-linaro/7.3-2018.05-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 (users/linaro/binutils-2_28-branch) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=bin… FSF GDB 8.1 (gdb-8.1-branch) https://lists.gnu.org/archive/html/info-gnu/2018-01/msg00016.html Linaro toolchain package git branches are hosted at: http://git.linaro.org/toolchain NEWS for GCC 7 (as of Linaro GCC 7.3-2018.05-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, Linaro GCC 7.2-2017.10 and Linaro GCC 7.2-2018.04. 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/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/7.2-2018.04/ 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, 6 months

1
0
0 0

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

by Mark Murray

The Linaro Binary Toolchain ============================ The Linaro GCC 6.4-2018.05-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-2018.05-rc1/ (binaries) http://snapshots.linaro.org/components/toolchain/binaries/6.4-2018.05-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-2018.05-rc1 http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.4-2018.05-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 (users/linaro/binutils-2_27-branch) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=bin… Linaro GDB 8.1 (gdb-8.1-branch) https://lists.gnu.org/archive/html/info-gnu/2018-01/msg00016.html Linaro toolchain package git branches are hosted at: http://git.linaro.org/toolchain NEWS for GCC 6 (as of Linaro GCC 6.4-2018.05-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 to 8.1. * 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, Linaro GCC 6.4-2017.10 and Linaro GCC 6.4-2018.04. 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/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.4-2018.04/ 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, 6 months

1
0
0 0

[ACTIVITY] week ending 20 May 2018

by Richard Henderson

[VIRT-198 # QEMU: SVE Emulation Support ] All softfp prerequisites merged upstream. First 25 of 70 patches of SVE decode merged upstream. [Upstream] Review and testing of Alex's check-tcg revival. [STOP] r~

7 years, 6 months

1
0
0 0

[ACTIVITY] Week 20

by Yvan Roux

== Progress == o GNU release transition * Provided support to handle infra issues * Meetings on GCC 8 o LLVM * Benchmarking effort with HPC team [HPC-183/184] - Added OpenMP support to LLVM scripts and jobs - Generate toolchain tarballs as job artifact. * Thumbv8 bot failures [TCWG-1400]: - Needs a deeper cleanup of LIT configuration. o Misc * Various meetings and discussions.

7 years, 6 months

1
0
0 0

[ACTIVITY] 14 - 18 May 2018

by Prathamesh Kulkarni

== This Week == * GCC bugs (8/10) a) Committed patches for: i) TCWG-1413 / PR83648: missing -Wsuggest-attribute=malloc on a trivial malloc-like function ii) TCWG-1414 / PR85817: ICE in expand_call at gcc/calls.c:4291 iii) TCWG-1415 / PR85734: --suggest-attribute=malloc misdiagnoses static functions b) Work in progress for: i) TCWG-125: static cast from float to int not working on ARM hardfp ii) TCWG-1416 / PR85787: malloc_candidate_p fails to detect malloc attribute on nested phis * TCWG-1234: Code hoisting and register pressure (1/10) i) Looking into Bin Cheng's patches for computing register pressure on GIMPLE * Misc (1/10) - Meetings - Gerrit reviews 25367 and 25371 == Next Week == - Continue with GCC bugs - TCWG-1234

7 years, 6 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain