- linaro-toolchain - lists.linaro.org

clang-cmake-armv7-selfhost build failure

by John McCall

There’s been an ongoing failure on the clang-cmake-armv8-selfhost builder for the last day or so; see e.g.: http://lab.llvm.org:8011/builders/clang-cmake-armv7-selfhost/builds/2827/ This list is recorded as the contact information for that builder. It is apparently crashing in a tblgen backend that I just added: ``` Stack dump: 0. Program arguments: /home/buildslave/buildslave/clang-cmake-armv7-selfhost/stage1/bin/clang-tblgen -gen-clang-type-writer -I /home/buildslave/buildslave/clang-cmake-armv7-selfhost/llvm/clang/include -I /home/buildslave/buildslave/clang-cmake-armv7-selfhost/llvm/clang/include/clang/AST -I /home/buildslave/buildslave/clang-cmake-armv7-selfhost/llvm/llvm/include /home/buildslave/buildslave/clang-cmake-armv7-selfhost/llvm/clang/include/clang/AST/TypeProperties.td --write-if-changed -o /home/buildslave/buildslave/clang-cmake-armv7-selfhost/stage1/tools/clang/include/clang/AST/AbstractTypeWriter.inc Segmentation fault (core dumped) ``` I would like to fix this, but I have no ability to reproduce it, and the crash information in the log is quite minimal. Is there a way I can get a shell on a system that can reproduce this, or at the very least get a line number for where exactly it is crashing? John.

6 years, 4 months

2
7
0 0

[ANNOUNCE] Arm provided GNU 9.2-2019.12 A-profile cross-toolchain release

by Ashok Bhat

The Arm GNU Toolchain for the A-profile Architecture ===================================================== We are pleased to announce the Arm release of the pre-built GNU cross-toolchain for the A-profile cores: GCC 9.2-2019.12. Further information about the GNU Arm toolchain and the release packages is available at Arm Developer site https://developer.arm.com/open-source/gnu-toolchain/gnu-a/downloads Features ======== * Based on GCC 9.2 (See https://gcc.gnu.org/gcc-9/changes.html for details). Supported targets ================= * On Windows(x86_64): - AArch64 (bare-metal and Linux) - AArch32 (bare-metal and Linux hard-float) * On Linux(x86_64): - AArch64 (bare-metal, Linux and Linux big-endian) - AArch32 (bare-metal and Linux hard-float) * On Linux(AArch64) - AArch64 (bare-metal) - AArch32 (bare-metal and Linux hard-float) Changes since Arm release GCC 8.3-2019.03 ========================================= * Additional AArch64 hosted cross-toolchains for AArch64 (bare-metal) and AArch32 (bare-metal and Linux hard-float) * Additional Windows hosted cross-toolchains for AArch64 (Linux) and AArch32 (Linux hard-float) * Retired Linux(x86_64) toolchain for AArch64 (big-endian bare-metal) and AArch32 (Linux soft-float) * Changed toolchain naming convention to match standard target triplet naming convention, with vendor name being none. For example, arm-eabi is now arm-none-eabi. * Fixed the Windows toolchain convention to correctly include mingw-w64 instead of mingw32 Host Requirements ================== * x86-64 Linux: Ubuntu 16.04 LTS or later, or RHEL 7 or later * AArch64 Linux: Ubuntu 18.04 LTS or later, or RHEL 8 * x86 Windows: Windows 10 Package Versions ================= * GCC 9.2.1 * glibc 2.30 * binutils 2.33.1 * GDB 8.3.0 * libexpat 2.2.5 * Linux Kernel v4.20.13 * libgmp 4.3.2 * libisl 0.15 * libmpfr 3.1.6 * libmpc 1.0.3 * libiconv 1.15 Contact Arm =========== For any questions, please use the Arm Communities forums at: https://community.arm.com/tools/ Please report any bugs via the Linaro Bugzilla at: https://bugs.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.

6 years, 4 months

1
1
0 0

[ACTIVITY] Week 50

by Yvan Roux

* One day off o LLVM: * Couple of failures with the bots * Machine Outliner: - Completed testcases - Validation before re-submission o Misc * Various meetings and discussions.

6 years, 4 months

1
0
0 0

[ACTIVITY] week ending 15 Dec 2019

by Richard Henderson

[VIRT-327 # Richard's upstream QEMU work ] Following up on the feedback from last week on VHE and PAN, posted a patch set eliminating MMU_MODE*_SUFFIX, and the current limit of NB_MMU_IDX <= 12 that went with that. Some patch review. r~

6 years, 4 months

1
0
0 0

[ACTIVITY] week ending Dec. 15 2019

by Alex Bennée

QEMU Tooling ([VIRT-252]) ========================= Extend gdbstub for SVE ([VIRT-281]) - posted [PATCH v3 00/20] gdbstub refactor and SVE support (+check-tcg tweaks) Message-Id: <20191211170520.7747-1-alex.bennee(a)linaro.org> GSoC Mentoring Afermath ([VIRT-348]) - started working on re-base of [TCG code quality tracking] - bit of a re-factor rethink required [TCG code quality tracking] <https://github.com/stsquad/qemu/tree/tcg/tbstats-and-perf-v10> Upstream Work ([VIRT-109]) ========================== - posted [PATCH] target/arm: ensure we use current exception state after SCR update Message-Id: <20191209143723.6368-1-alex.bennee(a)linaro.org> - posted [PATCH v2] target/arm: ensure we use current exception state after SCR update Message-Id: <20191212114734.6962-1-alex.bennee(a)linaro.org> - did and initial tyre kicking of rth's mmu_idx clean-up patches Completed Reviews [3/3] ======================= [PATCH] target/arm: Display helpful message when hflags mismatch Message-Id: <20191209134552.27733-1-philmd(a)redhat.com> [PATCH v2 0/2] gdbstub: allow sending packet of arbitrary length Message-Id: <20191211160514.58373-1-damien.hedde(a)greensocs.com> [PATCH 0/2] tests/acceptance: Add boot vmlinux test Message-Id: <20191206140012.15517-3-wainersm(a)redhat.com> Absences ======== - Christmas and New Year holidays Current Review Queue ==================== * {PATCH} Semihost SYS_READC implementation (v6) Message-Id: <20191104204230.12249-1-keithp(a)keithp.com> Added: <2019-12-06 Fri> * [RFC PATCH v3 000/132] Proof of concept for Meson integration Message-Id: <1576155176-2464-1-git-send-email-pbonzini(a)redhat.com> Added: <2019-12-12 Thu> * {PATCH 0/2} tests/acceptance: Add boot vmlinux test Message-Id: <20191206140012.15517-1-wainersm(a)redhat.com> Added: <2019-12-06 Fri> * {RFC PATCH 00/10} hw/avr: Introduce the Arduino board Message-Id: <20191128015030.27543-1-f4bug(a)amsat.org> Added: <2019-11-28 Thu> -- Alex Bennée

6 years, 4 months

1
0
0 0

[ACTIVITY] 9-13 Dec 2019

by Christophe Lyon

== Progress == * GCC: - -mpure-code on v6m: waiting for approval, pinged again. * BFD Linker: - GNU-629: non-contiguous memory support: Looking at how to handle the case where input sections change size during the linker iterations. * GCC upstream validation: - reported/checked a few issues * misc: - infra fixes / troubleshooting / reviews == Next == * GCC: pure-code/v6m, handle feedback * Binutils: GNU-629: support non-contiguous memory regions in linker == Future == Holidays: Dec 23rd-Jan 2nd

6 years, 4 months

1
0
0 0

[ACTIVITY] Week ending 13th December 2019

by Peter Smith

Morello: - Updated clang driver to use lld with --image-base rather than a linker script. - LLD changes merged. - Fixed up a few problems spotted by CI and a test on the examples. - Thoughts on code sequences for an experimental descriptor based ABI. LLD: - Committed changes to fix branch patch and thunks interaction in instrumented Chromium build - Discussion about deploying BTI in large programs like Chromium with pre-compiled objects and lots of assembler files. Planned absences On holiday for the rest of the decade. First day back in the office 6th January

6 years, 4 months

1
0
0 0

[ACTIVITY] week ending Dec. 8 2019

by Alex Bennée

QEMU Tooling ([VIRT-252]) ========================= Extend gdbstub for SVE ([VIRT-281]) - worked on [v3 rebase] - added a new test case and discovered a bug in upstream gdbserver - raised [GNU-647] to track it [v3 rebase] https://github.com/stsquad/qemu/tree/sve-registers-v3 [GNU-647] https://projects.linaro.org/browse/GNU-647 QEMU ARMv8.1 VHE ([VIRT_263]) ============================= - bunch of review and testing of rth's v4 series [VIRT_263] https://projects.linaro.org/browse/VIRT-263 Upstream Work ([VIRT-109]) ========================== - posted {PATCH v2 0/6} linux-user mmap debug cleanup Message-Id: <20191206110354.GA775461(a)stefanha-x1.localdomain> Completed Reviews [8/8] ======================= {PATCH 0/3} iotests: Check for the possibility to create large files Message-Id: <20191202101631.10003-1-thuth(a)redhat.com> - CLOSING NOTE [2019-12-03 Tue 10:14] Preparatory for the multiarch Travis tests. Added: <2019-12-02 Mon> {PATCH v2 0/2} Run tcg tests with tci on Travis Message-Id: <20191128153525.2646-1-thuth(a)redhat.com> - CLOSING NOTE [2019-12-03 Tue 10:21] will take v3 with --disable-kvm and sparc tweaks Added: <2019-11-28 Thu> {PATCH 0/2} flush CPU TB cache in breakpoint_invalidate Message-Id: <20191127220602.10827-1-jcmvbkbc(a)gmail.com> - CLOSING NOTE [2019-12-03 Tue 11:20] Needs a slightly neater solution than always flushing everything. Added: <2019-11-28 Thu> {PATCH 0/1} tests/vm: Allow to set path to qemu-img Message-Id: <20191114134246.12073-1-wainersm(a)redhat.com> - CLOSING NOTE [2019-12-03 Tue 11:37] Queued to my tree Added: <2019-11-14 Thu> {PATCH 0/4} docker: Update Travis-CI image to run acceptance tests Message-Id: <20190818231827.27573-1-philmd(a)redhat.com> - CLOSING NOTE [2019-12-03 Tue 16:03] Will wait for next iteration. {PATCH 0/4} python/qemu: New accel module and improvements Message-Id: <20191115180829.10275-1-wainersm(a)redhat.com> - CLOSING NOTE [2019-12-03 Tue 17:00] All looks good. I assume will be merged with another series that uses the new features. Added: <2019-11-28 Thu> {PATCH v7 0/8} Acceptance test: Add "boot_linux" acceptance test Message-Id: <20191104151323.9883-1-crosa(a)redhat.com> - CLOSING NOTE [2019-12-03 Tue 19:20] Broken for me with load_module failure Added: <2019-11-04 Mon> {PATCH v4 00/40} target/arm: Implement ARMv8.1-VHE Message-Id: <20191203022937.1474-1-richard.henderson(a)linaro.org> - CLOSING NOTE [2019-12-06 Fri 18:35] Reviewed about half the patch set, will do the remainder on v5 once Peter's comments are addressed. Added: <2019-12-03 Tue> Current Review Queue ==================== * {PATCH} Semihost SYS_READC implementation (v6) Message-Id: <20191104204230.12249-1-keithp(a)keithp.com> Added: <2019-12-06 Fri> * {PATCH 0/2} tests/acceptance: Add boot vmlinux test Message-Id: <20191206140012.15517-1-wainersm(a)redhat.com> Added: <2019-12-06 Fri> * {RFC PATCH 00/10} hw/avr: Introduce the Arduino board Message-Id: <20191128015030.27543-1-f4bug(a)amsat.org> Added: <2019-11-28 Thu> * {RFC 0/3} tests/vhost-user-fs-test: add vhost-user-fs test case Message-Id: <20191025100152.6638-1-stefanha(a)redhat.com> Added: <2019-10-25 Fri> -- Alex Bennée

6 years, 4 months

1
0
0 0

[ACTIVITY] 3x3 for week ending 6th December 2019

by Peter Smith

Morello: - Static linking patches committed to merge branch. - Dynamic linking patches up for review. - Agreed definition of what LLD for stage-1 looks like. - Discussions on what linker and ABI work is likely to be needed for stage-2. Linaro: Some LLD thunk/patch generation problems https://bugs.llvm.org/show_bug.cgi?id=44071 for a gigantic build of Chromium > 260 Mb .text section on AArch64. Diagnosed problems but will need to fix next week. Some support for ClangBuiltLinux with respect to some integrated assembler compatibility with GNU as. Buildbot duty. Pretty quiet, attempted to reproduce some timeouts seen on the LNT generate cmake. 3 minutes on an lightly loaded machine, exceeding 20 minutes in some cases on the heavily loaded buildbot host. Seems to have resolved itself with the latest container update. - Some changes to BTI for the Android team. All committed upstream. -- Adding PT_GNU_PROPERTY support. -- Increasing alignment of .note.gnu.property section to 8. Holiday - On holiday from Monday 16th to 3rd January inclusive. Back in office January 6th.

6 years, 4 months

1
0
0 0

[ACTIVITY] report week ending 6 Dec

by Peter Maydell

Progress: * VIRT-65 [QEMU upstream maintainership] - code review (have had a go at cutting down the backlog; down to six patchsets in my queue...): + reviewed the 'clock framework API' patchset; this is looking good, the only major question to sort out is what the right internal representation for the clock frq/period is + Paolo's series to add kernel-doc support to our Sphinx setup (which is a mashup of something I hacked together ages ago and more recent work from him) + RAS memory error support for KVM guests (mostly reviewing the easy bits and noting that others have provided code review comments on the rest) + reviewed RTH's MemTag emulation series + reviewed the bits of RTH's VHE series that Alex hadn't got to + tested an arm/acpi patchset from Huawei from March which had unfortunately fallen through the cracks. It failed 'make check' so they'll need to fix and resubmit :-( - release work: + we needed an rc4 + and it looks like we'll need an rc5 for one last important bugfix; I'm hoping we can do an rc and then actual release a few days later, though thanks -- PMM

6 years, 4 months

1
0
0 0

[ACTIVITY] 2-6 Dec 2019

by Christophe Lyon

== Progress == * GCC: - -mpure-code on v6m: waiting for approval, pinged again. * BFD Linker: - GNU-629: non-contiguous memory support: received some feedback. Looking at how to handle the case where input sections change size during the linker iterations. * GCC upstream validation: - reported/checked a few issues * misc: - infra fixes / troubleshooting / reviews == Next == * GCC: pure-code/v6m, handle feedback * Binutils: GNU-629: support non-contiguous memory regions in linker

6 years, 4 months

1
0
0 0

[ACTIVITY] 2 - 6 December 2019

by Diana Picus

== Progress == * LLVM 9.0.1 - Trying to bisect the arm failures * Triaging check-lldb failures on AArch64 [LLVM-512] - Finished with the unexpected failures - There are still some unexpected passes, but Omair has agreed to look into them * Morello - Managed to build android and lldb-server, currently trying to see if I can get them to work together

6 years, 4 months

1
0
0 0

coresight drivers access from syscall interface

by zied guermazi

hi,I started implementing GDB process record and replay with ARM CoreSight as described in the rfc published early this year. Current implementation of coresight tracing in Perf is based on the sysfs interface, by accessing /sys/bus/event_source/devices/cs_etm ... file. GDB implementation of bts and ipt is based on the syscall "sys_perf_event_open".it would be nice to use the similar mechanism for realizing similar functionalities. therefore I would like to know if linux kernel (with coresight deivers) is exposing coresight drivers through the syscall sys_perf_event_open and if this is the case how shall I configure the perf_event_attr to use it. thanks Zied Guermazi

6 years, 5 months

2
1
0 0

[ANNOUNCE] Linaro Binary Toolchain Release GCC 7.5-2019.12

by Maxim Kuvyrkov

The Linaro Binary Toolchain ============================ The Linaro GCC 7.5-2019.12 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.5-2019.12/ (binaries) http://releases.linaro.org/components/toolchain/binaries/7.5-2019.12/ 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.5-2019.12 http://releases.linaro.org/components/toolchain/gcc-linaro/7.5-2019.12/ 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.3 (gdb-8.3-branch) https://lists.gnu.org/archive/html/info-gnu/2019-05/msg00007.html Linaro toolchain package git branches are hosted at: http://git.linaro.org/toolchain NEWS for GCC 7 (as of Linaro GCC 7.5-2019.12) ============================================== * 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.4-2019.01 snapshot added a fix for Linaro bug 4007: "Internal compiler error with -mcpu=thunderx2t99". * 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, Linaro GCC 7.2-2018.04, Linaro GCC 7.4-2019.01 and Linaro GCC 7.5-2019.11. 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/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/7.4-2019.01/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/7.5-2019.11/ 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 -- Maxim Kuvyrkov https://www.linaro.org

6 years, 5 months

1
0
0 0

[ANNOUNCE] Linaro Binary Toolchain Release-Candidate GCC 7.5-2019.12-rc1

by Maxim Kuvyrkov

The Linaro Binary Toolchain ============================ The Linaro GCC 7.5-2019.12-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.5-2019.12-rc1/ (binaries) http://snapshots.linaro.org/components/toolchain/binaries/7.5-2019.12-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.5-2019.12-rc1 http://snapshots.linaro.org/components/toolchain/gcc-linaro/7.5-2019.12-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.3 (gdb-8.3-branch) https://lists.gnu.org/archive/html/info-gnu/2019-05/msg00007.html Linaro toolchain package git branches are hosted at: http://git.linaro.org/toolchain NEWS for GCC 7 (as of Linaro GCC 7.5-2019.12-rc1) ================================================== * 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.4-2019.01 snapshot added a fix for Linaro bug 4007: "Internal compiler error with -mcpu=thunderx2t99". * 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, Linaro GCC 7.2-2018.04, Linaro GCC 7.4-2019.01 and Linaro GCC 7.5-2019.11. 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/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/7.4-2019.01/ http://snapshots.linaro.org/components/toolchain/gcc-linaro/7.5-2019.11/ 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 -- Maxim Kuvyrkov https://www.linaro.org

6 years, 5 months

1
0
0 0

[Activity] Nov 25th ~ Nov 29nd 2019

by Luis Machado

# Progress # o Upstream GDB * ARM sim build failure with -fno-common - Sent a patch to gdb-patches. Going through rounds of reviews. * Patch reviewing and answering community questions. o GDB * GNU-644 - [GDB, AArch64] gdb.base/step-over-syscalls.exp failures - Spent some more time with this in the hopes of understanding the various failure modes. Still not clear if the kernel is doing the right thing. It may be hard to adjust things on GDB's side, but i have a couple patches solving some of the problems. o Misc * Updated personal information in the HR system. # Plan # o Upstream GDB * Get approval for the fix to -fno-common build issues with ARM sim. o GDB * GNU-644 - [GDB, AArch64] gdb.base/step-over-syscalls.exp failures - Engage with kernel folks for better understanding of signal delivery scheme. Polish current fixes and submit for review.

6 years, 5 months

1
0
0 0

[ACTIVITY] Week 48

by Yvan Roux

o LLVM: * Machine Outliner: - Disabled asm statements. - Added Helium LD/ST instructions support - Adding testcases o Misc * Various meetings and discussions.

6 years, 5 months

1
0
0 0

[ACTIVITY] 2 weeks ending 1 Dec 2019

by Richard Henderson

7 working days, then Thanksgiving. [VIRT-262 # ARMv8.1-PAN Privileged Access Never] Finished, still need to post. [VIRT-273 # ARMv8.2-ATS1E1, AT S1E1R and AT S1E1W instruction variants ] Finished, still need to post. [VIRT-276 # ARMv8.2-UAO, PSTATE override of Unprivileged Load/Store ] Finished, still need to post. [VIRT-263 # ARMv8.1-VHE Virtual Host Extensions ] FIXED! Welsh sprint with AJB; found and fixed two bugs. Final bug causing guest kernel crash while booting fixed upstream by Marc Zyngier vs ptrauth. Will do some more thorough testing during rc4 and post once the development phase opens up again. [VIRT-327 # Richard's upstream QEMU work ] Review of target/hexagon skeleton. Review of arm dcpop patch set for beata. Fixed a couple of arm translator bug for clyon. Some investigation into a reported hppa-linux-user bug. While I can reproduce locally, so far I have not tracked down anything that I can prove is a translation bug. r~

6 years, 5 months

1
0
0 0

[ACTIVITY] week ending Dec. 1 2019

by Alex Bennée

QEMU Tooling ([VIRT-252]) ========================= Extend gdbstub for SVE ([VIRT-281]) - worked on [v2 rebase addressing comments] - posted {PATCH v2 00/14} gdbstub refactor and SVE support Message-Id: <20191130084602.10818-1-alex.bennee(a)linaro.org> [VIRT-281] https://projects.linaro.org/browse/VIRT-281 [working prototype] https://github.com/stsquad/qemu/tree/gdbstub/sve-registers [v2 rebase addressing comments] https://github.com/stsquad/qemu/tree/gdbstub/sve-registers-v2 QEMU ARMv8.1 VHE ([VIRT_263]) ============================= - inaugural Welsh code sprint with rth - found some new bugs, squashed some old bugs - together with recent upstream fixes SUCCESS! - can now boot a guest from a VHE enabled kernel :-) [VIRT_263] https://projects.linaro.org/browse/VIRT-263 Upstream Work ([VIRT-109]) ========================== - posted {PULL for 4.2 0/3} a few vm-test fixes Message-Id: <20191126120339.18059-1-alex.bennee(a)linaro.org> - there are still niggling netbsd failures - posted {PATCH for 4.2?} .travis.yml: drop xcode9.4 from build matrix Message-Id: <20191127132430.3681-1-alex.bennee(a)linaro.org> - investigation into [ARM HPC compiler triggered linux-user bug] - may be 64k page related as couldn't reproduce on Ubuntu - posted {PATCH v1 0/5} linux-user mmap debug cleanup Message-Id: <20191128194603.24818-1-alex.bennee(a)linaro.org> [ARM HPC compiler triggered linux-user bug] https://bugs.launchpad.net/qemu/+bug/1853826 Other Activities ================ - published [QEMU Summit and KVM Forum trip report] [QEMU Summit and KVM Forum trip report] https://collaborate.linaro.org/display/CR/20191030+QEMU+Summit+and+KVM+Foru… Absences ======== - 2nd Dec Holiday Current Review Queue ==================== * {PATCH 0/4} python/qemu: New accel module and improvements Message-Id: <20191115180829.10275-1-wainersm(a)redhat.com> Added: <2019-11-28 Thu> * {PATCH v2 0/2} Run tcg tests with tci on Travis Message-Id: <20191128153525.2646-1-thuth(a)redhat.com> Added: <2019-11-28 Thu> * {PATCH 0/2} flush CPU TB cache in breakpoint_invalidate Message-Id: <20191127220602.10827-1-jcmvbkbc(a)gmail.com> Added: <2019-11-28 Thu> * {RFC PATCH 00/10} hw/avr: Introduce the Arduino board Message-Id: <20191128015030.27543-1-f4bug(a)amsat.org> Added: <2019-11-28 Thu> -- Alex Bennée

6 years, 5 months

1
0
0 0

[weekly][dsg-models][linaro] report week ending 29 Nov

by Peter Maydell

Progress: * VIRT-65 [QEMU upstream maintainership] - code review: + finally got back to the reset-refactoring patchset and gave review on v5 of that. This is very nearly ready. + reviewed and got into 4.2 rc3 some patches from Marc Z fixing some missing emulation/bugs that newer Linux guest kernels trip over + rc3 out of the door; we will need an rc4, though - more time consumed by office-move thanks -- PMM

6 years, 5 months

1
0
0 0

[ACTIVITY] Week ending 29th November 2019

by Peter Smith

[Morello] Rebase of LLD against September CUCL update complete - Painful due to LLD changing address layout (every test expected value shifted), and a naming convention change. - No functional changes needed to patch. - Submitted static linking patches for review. Will send the dynamic ones after all static linking has been merged. Wrote up notes of Linaro Tech-leads Morello Q&A. Misc: Upstream LLD reviews

6 years, 5 months

1
0
0 0

[ACTIVITY] 25-29 Nov 2019

by Christophe Lyon

== Progress == * GCC: - -mpure-code on v6m: waiting for approval, pinged again. * BFD Linker: - GNU-629: non-contiguous memory support: RFC patch sent. * GCC upstream validation: - only a minor testcase issue to fix this week * misc: - infra fixes / troubleshooting / reviews == Next == * GCC: pure-code/v6m, handle feedback * Binutils: GNU-629: support non-contiguous memory regions in linker

6 years, 5 months

1
0
0 0

[ACTIVITY] 25 - 29 November 2019

by Diana Picus

== Progress == * Out of office on Thursday * LLVM 9.0.1 - Uploaded ARM & AArch64 binaries for rc1 - ARM: opened 2 bug reports (asan and cfi tests failing) * Triaging check-lldb failures on AArch64 [LLVM-512] - Opened a few more bug reports - Got one nasty failure that I want to look into a bit more before committing a patch XFAIL-ing everything so far * Morello - Got a VM working, built the toolchain, currently trying to build android - Setting up all sorts of gerrit accounts and other minutiae == Plan == * More of the same

6 years, 5 months

1
0
0 0

Help understanding "VFP magic dust" in cortex-strings memcpy

by Alexander Monakov

Hi! I've attempted to study the implementation of memcpy for 32-bit Arm cores in Glibc (which is also found in arm-optimized-routines and first appeared in Linaro's cortex-strings project), and I came across a peculiar snippet: #ifdef USE_VFP /* Magic dust alert! Force VFP on Cortex-A9. Experiments show that the FP pipeline is much better at streaming loads and stores. This is outside the critical loop. */ vmov.f32 s0, s0 #endif This seems to imply that this NOP-like instruction affects CPU state and makes the vldr/vstr instructions that follow use different datapaths that they might otherwise? Can anyone shed more light on this, please? I was able to trace history of this code back to revision 100 in cortex-strings repository, where it appeared as part of a large rewrite by Will Newton: https://bazaar.launchpad.net/~linaro-toolchain-dev/cortex-strings/trunk/rev… The entire memcpy.S file in Arm optimized-routines repo can be found here: https://github.com/ARM-software/optimized-routines/blob/master/string/arm/m… Thanks! Alexander

6 years, 5 months

2
1
0 0

High stack usage due ftree-ch

by Adhemerval Zanella

Hi Arnd, I took a look on the stack usage issue in the kernel snippet you provided [1], and as you have noted the most impact indeed come from -ftree-ch optimization. It is enabled in all optimization levels besides -Os (since besides possible increasing the stack usage it also might increase code side). I am still fulling grasping what free-ch optimization does, but my understanding so far is it tries to reorganize the loop for later loop optimization phases. More specifically, what it ends up doing on the specific snippet is create extra stack variables for the internal membber access in the inner loop (which in its turns increase stack usage). This is also why adding the compiler barrier inhibits the optimization, since it prevents the ftree-ch to optimize the internal loop reorganization and it is passed as is to later optimizations phases. It is also a generic pass that affects all architecture, albeit the resulting stack will depend on later passes. With GCC 9.2.1 I see the resulting stack usage using -fstack-usage along with -O2: arm 632 aarch64 448 powerpc 912 powerpc64le 560 s390 600 s390x 632 i386 1376 x86_64 784 Also, -fconserve-stack does not really help with this pass since ftree-ch does not check the flag usage. The fconserve-stack currently only seems to effect the inliner by setting both large-stack-frame and large-stack-frame-growth to some conservative values. The straightforward change I am checking is just to disable tree-ch optimization if fconserve-stack is also enabled: diff --git a/gcc/tree-ssa-loop-ch.c b/gcc/tree-ssa-loop-ch.c index b894a7e0918..b14dd66257c 100644 --- a/gcc/tree-ssa-loop-ch.c +++ b/gcc/tree-ssa-loop-ch.c @@ -291,7 +291,8 @@ public: {} /* opt_pass methods: */ - virtual bool gate (function *) { return flag_tree_ch != 0; } + virtual bool gate (function *) { return flag_tree_ch != 0 + && flag_conserve_stack == 0; } /* Initialize and finalize loop structures, copying headers inbetween. */ virtual unsigned int execute (function *); On powerpc64le with gcc master: $ /home/azanella/gcc/gcc-git-build/gcc/xgcc -B /home/azanella/gcc/gcc-git-build/gcc -O2 ../stack_usage.c -c -fstack-usage && cat stack_usage.su ../stack_usage.c:157:6:mlx5e_grp_sw_update_stats 496 static $ /home/azanella/gcc/gcc-git-build/gcc/xgcc -B /home/azanella/gcc/gcc-git-build/gcc -O2 ../stack_usage.c -c -fstack-usage -fconserve-stack && cat stack_usage.su ../stack_usage.c:157:6:mlx5e_grp_sw_update_stats 176 static The reference for minimal stack usage is with -Os: $ /home/azanella/gcc/gcc-git-build/gcc/xgcc -B /home/azanella/gcc/gcc-git-build/gcc -Os ../stack_usage.c -c -fstack-usage && cat stack_usage.su ../stack_usage.c:157:6:mlx5e_grp_sw_update_stats 32 static I will try to check if also enable the same test for -fgcse and -free-ter do make sense. [1] https://godbolt.org/z/WKa-Bd

6 years, 5 months

3
8
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain