Hello,
In our company we are using following version of Linaro compilers. I want to know if these versions are officially supported. If these versions are NOT supported, please let me know what is the version we may need to move to take advantage of support
* LINARO-GCC - AARCH64 4.9.4
* LINARO-GCC - AARCH64 6.3.1
* LINARO-GCC 4.9 2016.2
Thanks for your help
Regards/Anand
Series:
- Cleaned QEMU device model API abuses
- Suggest new "wiring" step in QEMU device model
- Add new qemu-system binary to experiment:
- single binary
- dynamic machine
- heterogeneous emulation
Started wiki document to share work:
https://wiki.qemu.org/Dynamic_machine_and_heterogeneous_emulation_roadmap
Progress:
- Refactor ICH9 device to fix another QDev IRQ abuse
Usual reviews
- Peter's MP3R new board
Progress:
* UM-2 [QEMU upstream maintainership]
- code review and pullrequest wrangling
+ RTH's MTE fixes patchset
+ Some cleanup patches from Philippe
+ various other smaller things
- sent out some minor patches:
+ avoid some warnings being printed during 'make check'
+ fix an assertion failure trying to vmsave/vmload for M-profile
- a little gardening of the bug tracker
* QEMU-598 [Model the MPS3-AN536 dual-Cortex-R52 FPGA image]
- Finished off the loose ends and sent patchset out for review
-- PMM
Hi,
The regression was introduced after we added a new test (rev16_2.c) in https://github.com/gcc-mirror/gcc/commit/bad991a1c5960e90c4686a9362a1258ef2….
The generated code is functionally correct, but the optimization is disabled when -mthumb is equivalent to Thumb1.
The fix would not be suitable for stage 4. Instead, I opened a Jira ticket on our side to track the issue and prioritize it.
In the meantime, I am going to publish a patch to mark the test as XFAIL when used with thumb1.
Regards,
Matthieu
-----Original Message-----
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: Thursday, February 1, 2024 5:10 PM
To: Richard Earnshaw <Richard.Earnshaw(a)arm.com>
Cc: gcc-regression(a)gcc.gnu.org; Matthieu Longo <Matthieu.Longo(a)arm.com>
Subject: [Linaro-TCWG-CI] gcc-14-8499-gbad991a1c59: FAIL: 1 regressions on master-thumb_m0_eabi
Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
We track this report status in https://linaro.atlassian.net/browse/GNU-1141 , please let us know if you are looking at the problem and/or when you have a fix.
In arm-eabi cortex-m0 soft after:
| commit gcc-14-8499-gbad991a1c59
| Author: Matthieu Longo <matthieu.longo(a)arm.com>
| Date: Mon Jan 29 15:54:35 2024 +0000
|
| arm: Add pattern for bswap + rotate -> rev16 [Bug 108933]
|
| The rev16 pattern was not recognised anymore as a change in the bswap
| tree pass was introducing a new GIMPLE form, not recognized by the
| assembly final transformation pass.
|
| Also, fix the output patterns for arm_rev16si_alt[12] to correctly
| ... 18 lines of the commit log omitted.
FAIL: 1 regressions
regressions.sum:
=== gcc tests ===
Running gcc:gcc.target/arm/arm.exp ...
FAIL: gcc.target/arm/rev16_2.c scan-assembler-times rev16\\tr[0-9]+, r[0-9]+ 2
You can find the failure logs in *.log.1.xz files in
- https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu…
The full lists of regressions and progressions as well as configure and make commands are in
- https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu…
The list of [ignored] baseline and flaky failures are in
- https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu…
The configuration of this build is:
CI config tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv6s-m -mtune=cortex-m0 -mfloat-abi=soft -mfpu=auto
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu…
Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu…
Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
Full commit : https://github.com/gcc-mirror/gcc/commit/bad991a1c5960e90c4686a9362a1258ef2…
List of configurations that regressed due to this commit :
* tcwg_gnu_embed_check_gcc
** master-thumb_m0_eabi
*** FAIL: 1 regressions
*** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
*** https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu…
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.
Progress:
* UM-2 [QEMU upstream maintainership]
- more code review and pullreq wrangling
* QEMU-598 [Model the MPS3-AN536 dual-Cortex-R52 FPGA image]
- Wrote code to create the CPUs and the GIC and the UARTs.
(Decided in the end not to try to create an a15mpcore-style
wrapper device for the CPUs and GIC, because the need to
have per-CPU RAM and UARTs makes that a bit awkward.)
- Got to a working implementation which can boot the selftest
binary and run those parts of the selftest which we expect
to work. Also will boot a Linux kernel (support for R52 is
not upstream but there are public mailing list patches).
- Started on tidying up the patchset and finishing off the
loose ends to get it into a state where it can be sent out:
hope to be able to do that first half of next week.
-- PMM
Hi All,
This is a false positive, obviously. We do our best to filter out flaky tests, but in this case "gdb.threads/staticthreads.exp: up 10" PASSed twice in the previous run, and then FAILed twice in the next run. Sneaky!
Re. the FAIL, the testcase expects to be " in main .*" after "up 10", but ends up in pthread_join() instead:
===
up 10
#4 0x0001b864 in pthread_join ()
(gdb) FAIL: gdb.threads/staticthreads.exp: up 10
===
See [1] for details.
[1] https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/752/artifact/art… .
Hi Thiago,
Would you please investigate whether ending up in pthread_join() is expected/reasonable for 32-bit ARM? In other words, whether we have a GDB bug exposed by staticthreads.exp or the testcase needs to be generalized a bit.
Thank you,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Jan 31, 2024, at 01:30, ci_notify(a)linaro.org wrote:
>
> Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> We track this report status in https://linaro.atlassian.net/browse/GNU-1137 , please let us know if you are looking at the problem and/or when you have a fix.
>
> In gdb_check master-arm after:
>
> | commit gdb-14-branchpoint-1426-gb960445a459
> | Author: GDB Administrator <gdbadmin(a)sourceware.org>
> | Date: Tue Jan 30 00:00:26 2024 +0000
> |
> | Automatic date update in version.in
>
> FAIL: 1 regressions
>
> regressions.sum:
> === gdb tests ===
>
> Running gdb:gdb.threads/staticthreads.exp ...
> FAIL: gdb.threads/staticthreads.exp: up 10
>
>
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/752/artifact/art…
> The full lists of regressions and progressions as well as configure and make commands are in
> - https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/752/artifact/art…
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/752/artifact/art…
>
> The configuration of this build is:
> CI config tcwg_gdb_check master-arm
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/752/artifact/art…
> Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/751/artifact/art…
>
> Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sh…
>
> Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=b960445a45981…
>
> List of configurations that regressed due to this commit :
> * tcwg_gdb_check
> ** master-arm
> *** FAIL: 1 regressions
> *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sh…
> *** https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/752/artifact/art…
On Tue, Jan 30, 2024 at 5:45 PM <ci_notify(a)linaro.org> wrote:
>
> Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> In gcc_check master-aarch64 after:
>
> | gcc patch https://patchwork.sourceware.org/patch/85019
> | Author: H.J. Lu <hjl.tools(a)gmail.com>
> | Date: Tue Jan 30 04:56:44 2024 -0800
> |
> | Handle private COMDAT function symbol reference in readonly data section
> |
> | For a private COMDAT function symbol reference in readonly data section,
> | instead of putting it in .data.rel.ro or .rodata.cst section, call
> | function_rodata_section to get the read-only or relocated read-only
> | data section associated with the function DECL so that the COMDAT
> | section will be used for the private COMDAT function symbol.
> | ... 14 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | f2061b2a964 c++: avoid -Wdangling-reference for std::span-like classes [PR110358]
>
> FAIL: 29 regressions
>
> regressions.sum:
> === gcc tests ===
>
> Running gcc:gcc.c-torture/execute/execute.exp ...
> FAIL: gcc.c-torture/execute/pr79286.c -Os (internal compiler error: Segmentation fault)
> FAIL: gcc.c-torture/execute/pr79286.c -Os (test for excess errors)
> UNRESOLVED: gcc.c-torture/execute/pr79286.c -Os compilation failed to produce executable
>
> Running gcc:gcc.dg/torture/dg-torture.exp ...
> FAIL: gcc.dg/torture/pr67109.c -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (internal compiler error: Segmentation fault)
> FAIL: gcc.dg/torture/pr67109.c -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess errors)
> ... and 25 more entries
I can't reproduce it with a cross compiler on x86-64 configured with
--target=aarch64-linux
But I sent out the v2 patch:
https://patchwork.sourceware.org/project/gcc/list/?series=30393
to check decl non-null before dereferencing it.
--
H.J.
This patch has been superseded.
On Fri, Jan 26, 2024 at 2:01 PM <ci_notify(a)linaro.org> wrote:
>
> Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> In binutils_check master-arm after:
>
> | binutils patch https://patchwork.sourceware.org/patch/84803
> | Author: H.J. Lu <hjl.tools(a)gmail.com>
> | Date: Fri Jan 26 10:09:48 2024 -0800
> |
> | ld: Turn on --error-execstack/--error-rwx-segments
> |
> | Since --fatal-warnings always turns a warning to an error, turn on
> | --error-execstack for --warn-execstack and --error-rwx-segments for
> | --warn-rwx-segments if --fatal-warnings is used, overriding
> | --no-error-execstack and --no-error-rwx-segments.
> |
> | ... 8 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 91cdbed4d7b gas: scfi: untraceable control flow should be a hard error
>
> FAIL: 1 regressions
>
> regressions.sum:
> === ld tests ===
>
> Running ld:ld-elf/elf.exp ...
> FAIL: PR ld/31299 (error about absent .note.GNU-stack)
>
> === Results Summary ===
>
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_binutils_check--master-arm-precommit/1003/ar… .
> The full lists of regressions and progressions are in
> - https://ci.linaro.org/job/tcwg_binutils_check--master-arm-precommit/1003/ar… .
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_binutils_check--master-arm-precommit/1003/ar… .
>
> The configuration of this build is:
> CI config tcwg_binutils_check master-arm
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_binutils_check--master-arm-precommit/1003/ar…
> Reference build : https://ci.linaro.org/job/tcwg_binutils_check--master-arm-build/696/artifac…
--
H.J.