Hi,
Neither the reference nor the current build includes later fixes for
zero_padding.cc file, in particular:
> commit 3a41229f92022bfb388911854d597721fce76714
> Author: Tomasz Kamiński <tkaminsk(a)redhat.com>
> Date: Thu Mar 5 08:57:24 2026 +0100
>
> libstdc++: Fix atomic/cons/zero_padding.cc test for arm-none-eabi
[PR124124]
>
> The test uses dg-require-atomic-cmpxchg-word that checks if atomic
compare
> exchange is available for pointer sized integers, and then test types
that
> are eight bytes in size. This causes issue for targets for which
pointers
> are four byte and libatomic is not present, like arm-none-eabi.
> commit f3ba5ad088cebe117f857329a35b95d18d97a808
> Author: Tomasz Kamiński <tkaminsk(a)redhat.com>
> Date: Tue Feb 17 13:35:39 2026 +0100
>
> libstdc++: Correct requirements for atomic/cons/zero_padding.cc tests
again [PR124124]
>
> The requirements introduced in previous patch r16-7548-g060d7c2a9c1fe1,
> were not sufficient for types of size bigger than 64B (Ctor or long
double),
> as dg-add-options of libatomic, links libatomic only if it is required
to
> handle atomics of 64B types or pointers.
Are issue still present on thunk build?
On Mon, Apr 20, 2026 at 10:28 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.
>
> In arm-eabi cortex-m55 hard, after:
> | commit gcc-16-7460-g682c95b80872
> | Author: Tomasz Kamiński <tkaminsk(a)redhat.com>
> | Date: Wed Feb 11 15:05:00 2026 +0100
> |
> | libstdc++: Add test for atomic with padding on heap [PR123875]
> |
> | C++26 makes the values of uninitialized stack object erroneous,
> | de-facto requiring their initialization, so adding a test for
> | variable on heap.
> | ... 8 lines of the commit log omitted.
>
>
> Used configuration :
> *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb
> -march=armv8.1-m.main+mve.fp+fp.dp -mtune=cortex-m55 -mfloat-abi=hard
> -mfpu=auto
> *configure and test flags:* --target arm-eabi --disable-multilib
> --with-mode=thumb --with-arch=armv8.1-m.main+mve.fp+fp.dp --with-float=hard
> --target_board=-mthumb/-march=armv8.1-m.main+mve.fp+fp.dp/-mtune=cortex-m55/-mfloat-abi=hard/-mfpu=auto
> qemu-cpu=cortex-m55
>
> We track this bug report under
> https://linaro.atlassian.net/browse/GNU-1877. Please let us know if you
> have a fix.
>
> If you have any questions regarding this report, please ask on
> linaro-toolchain(a)lists.linaro.org mailing list.
>
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways
> to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h…
> The full lists of regressions and improvements as well as configure and
> make commands are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h…
> The list of [ignored] baseline and flaky failures are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h…
>
> Current build :
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h…
> Reference build :
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h…
>
> Instruction to reproduce the build :
> https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s…
>
> Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git
>
ci_notify(a)linaro.org writes:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In armv8l-unknown-linux-gnueabihf native, after:
> | gcc patch https://patchwork.sourceware.org/patch/133402
> | Author: Rainer Orth <ro(a)CeBiTec.Uni-Bielefeld.DE>
> | Date: Mon Apr 20 18:29:40 2026 +0200
> |
> | [PATCH] testsuite: Check configured assembler in gcc.misc-tests/options.exp
> |
> | When I recently dropped --with-gnu-as from my builds which had become
> | unnecessary, several tests started to FAIL, e.g.
> |
> | ... 45 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 416fe77efb4 d: Fix ICE in must_pass_in_stack_var_size_or_pad with D enums [PR123411]
It's good to see you're running pre-commit checks. However, this report
is particularly confusing in its current form: while the Subject states
"no pregression/no fix on arm", the report starts with
Our automatic CI has detected problems related to your patch(es). Please find some details below.
^^^^^^^^^^^^^^^^^^^^^
That sent me looking for regressions, but I couldn't find any. At first
I thought I was beeing particularly stupid, but it seems that your CI
found no issues at all with the patch.
So please say so *prominently* in the body of the message, rather than
confusing contributors and wasting their time.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
Hello there,
According to the list of regressions below, all the failing tests are
for the C compiler. I am at a bit of a loss to know how to proceed
since the patch that you have fingered applies exclusively to fortran.
Best regards
Paul
---------- Forwarded message ---------
From: <ci_notify(a)linaro.org>
Date: Sun, 19 Apr 2026 at 23:05
Subject: [Linaro-TCWG-CI] gcc patch #133364: 113 regressions on aarch64
To: <paul.richard.thomas(a)gmail.com>
Cc: <pault(a)gcc.gnu.org>
Dear contributor,
Our automatic CI has detected problems related to your patch(es).
Please find some details below.
In aarch64 native, after:
| gcc patch https://patchwork.sourceware.org/patch/133364
| Author: Paul Thomas <pault(a)gcc.gnu.org>
| Date: Sun Apr 19 15:00:14 2026 +0100
|
| [PATCH] Fortran: ICE due to allocatable component in hidden
type [PR117077]
|
| 2026-03-19 Paul Thomas <pault(a)gcc.gnu.org>
|
| gcc/fortran
| ... 8 lines of the commit log omitted.
| ... applied on top of baseline commit:
| 68920b1f14d cse: Validate subreg replacements [PR124643]
Produces 113 regressions:
|
| regressions.sum:
| Running g++:g++.target/aarch64/aarch64.exp ...
| FAIL: g++.target/aarch64/pr117048.C scan-assembler
\\txar\\tv[0-9]+\\.2d, v[0-9]+\\.2d, v[0-9]+\\.2d, 32\\n
| Running g++:g++.target/aarch64/sme2/aarch64-sme2-acle-asm.exp ...
| FAIL: gcc.target/aarch64/sme2/acle-asm/svluti4_zt_1.c -std=c++11
-O0 -g -DTEST_FULL (test for excess errors)
| FAIL: gcc.target/aarch64/sme2/acle-asm/svluti4_zt_1.c -std=c++11
-O0 -g -DTEST_OVERLOADS (test for excess errors)
| ... and 120 more
Used configuration :
*CI config* tcwg_gcc_check aarch64-linux-gnu
*configure and test flags:* none, autodetected on
aarch64-unknown-linux-gnu--disable-multilib
--enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419
--with-arch=armv8-a
If you have any questions regarding this report, please ask on
linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the
ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
The full lists of regressions and improvements as well as configure
and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
Current build :
http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
Reference build :
http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
Warning: we do not enable maintainer-mode nor automatically update
generated files, which may lead to failures if the patch modifies the
master files.
This test failure is pre-existing on master and is not introduced by this
series. I verified that vanilla master (commit d3e7d81adc8, the baseline
cited by the CI report) produces identical output to the patched build for
the Egypt walk in test_egypt() — the diff is empty.
The test's hardcoded expected output expects ambiguous local_info results
at certain EEST→EET fall-back transitions (2003, 2005, 2007, 2009, 2010),
but the current master code produces two consecutive
unique EET intervals instead (a 1-hour interval followed by the long winter
interval, same offset/save/abbrev). This looks like a pre-existing
consequence of the merge block in _M_get_sys_info being #if 0'd out.
--Álvaro.
On Sun, Apr 12, 2026 at 1:40 AM <ci_notify(a)linaro.org> wrote:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please
> find some details below.
>
> In armv8l-unknown-linux-gnueabihf native, after:
> | 5 patches in gcc
> | Patchwork URL: https://patchwork.sourceware.org/patch/132945
> | 9c1142da97d [PATCH 5/5] libstdc++: Implement zic writezone merge
> optimization [PR 124854]
> | 4647ebca332 [PATCH 4/5] libstdc++: Cascade wall-time saves in lazy
> expansion seeding [PR 124853]
> | f5a3c3c82e2 [PATCH 3/5] libstdc++: Resolve named-rule UNTIL save
> adjustment [PR116110]
> | e31e5de33bb [PATCH 2/5] libstdc++: Support ON-format DAY in Zone UNTIL
> field [PR 124852]
> | a607854b476 [PATCH 1/5] libstdc++: Fix numeric save offset on Zone
> lines [PR 124851]
> | ... applied on top of baseline commit:
> | d3e7d81adc8 Daily bump.
>
> Produces 1 regression:
> |
> | regressions.sum:
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL: std/time/time_zone/get_info_local.cc -std=gnu++20 execution test
>
> Used configuration :
> *CI config* tcwg_gcc_check armv8l-unknown-linux-gnueabihf
> *configure and test flags:* none, autodetected on
> armv8l-unknown-linux-gnueabihf--disable-multilib --with-float=hard
> --with-mode=thumb --with-tune=cortex-a9 --with-arch=armv7-a
> --with-fpu=neon-fp-armv8
>
> If you have any questions regarding this report, please ask on
> linaro-toolchain(a)lists.linaro.org mailing list.
>
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways
> to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-precommit/builds/…
> The full lists of regressions and improvements as well as configure and
> make commands are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-precommit/builds/…
> The list of [ignored] baseline and flaky failures are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-precommit/builds/…
>
> Current build :
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-precommit/builds/…
> Reference build :
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1008…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
On Sun, Apr 19, 2026 at 9:16 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.
>
> In glibc_check master-arm, after:
> | glibc patch https://patchwork.sourceware.org/patch/133360
> | Author: H.J. Lu <hjl.tools(a)gmail.com>
> | Date: Mon Apr 13 08:23:05 2026 +0800
> |
> | [PATCH v4] elf: Support THP segment load with madvise enabled THP
> |
> | The current THP segment load approach works only when THP is enabled
> | with always in the kernel. If THP is enabled with madvise in the
> | kernel, to enable THP segment load in an application, madvise should
> | ... 36 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 0664c8e2761 localedata: Consistently use one space after 'category'
>
> Produces 4 regressions:
> |
> | regressions.sum:
> | Running glibc:elf ...
> | FAIL: elf/tst-thp-1-no-s-code-pde
> | FAIL: elf/tst-thp-1-no-s-code-static
> | FAIL: elf/tst-thp-1-pde
> | FAIL: elf/tst-thp-1-static
What do they report, like in elf/tst-thp-1-pde.out? What is in
/sys/kernel/mm/transparent_hugepage/hpage_pmd_size?
> Used configuration :
> *CI config* tcwg_glibc_check master-arm
> *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> * http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-precommit/build…
> The full lists of regressions and improvements as well as configure and make commands are in
> * http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-precommit/build…
> The list of [ignored] baseline and flaky failures are in
> * http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-precommit/build…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-precommit/build…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
--
H.J.
On Fri, 17 Apr 2026 at 06:03, <ci_notify(a)linaro.org> wrote:
>
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In aarch64 native, after:
> | gcc patch https://patchwork.sourceware.org/patch/133193
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Thu Apr 16 15:21:49 2026 +0100
> |
> | [PATCH v2] libstdc++: Add module initialization functions to the library [PR124268]
> |
> | This tries to ensure that the module init functions are present in
> | libstdc++.so and libstdc++.a, so that users of the std and std.compat
> | modules don't need to manually link to std.o and/or std.compat.o in
> | ... 32 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 20230911fca Daily bump.
>
> Produces 3 regressions:
> |
> | regressions.sum:
> | Running libstdc++:libstdc++-prettyprinters/prettyprinters.exp ...
> | FAIL: libstdc++-prettyprinters/debug.cc print redirected
> | FAIL: libstdc++-prettyprinters/simple.cc print redirected
> | FAIL: libstdc++-prettyprinters/simple11.cc print redirected
>
> Used configuration :
> *CI config* tcwg_gcc_check aarch64-linux-gnu
> *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu--disable-multilib --enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
I don't understand how these failures can possibly be caused by the
patch, and I don't see them on cfarm185 (Ampere eMAG
aarch64-linux-gnu, almalinux 8.10) or on any other *-*-linux-gnu
targets, nor solaris.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
> The full lists of regressions and improvements as well as configure and make commands are in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
> The list of [ignored] baseline and flaky failures are in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
The test fails on arm-eabi when testing with the following settings:
-mlittle-endian -mfloat-abi=hard -mcpu=cortex-a9 -mfpu=vfpv3
It only fails in the following torture option set:
-O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions
It also fails on numerous other 32-bit targets, but it depends on how
the memcpy-like loop gets vectorized and unrolled.
I hope we can live with the XPASSes.
On Apr 11, 2026, ci_notify(a)linaro.org wrote:
> Dear contributor,
> Our automatic CI has detected problems related to your
> patch(es). Please find some details below.
> In arm-eabi thumb v8-a hard, after:
> | commit gcc-16-6952-g14cd2833b27a
> | Author: Alexandre Oliva <oliva(a)adacore.com>
> | Date: Wed Jan 21 00:30:24 2026 -0300
> |
> | testsuite: tolerate bogus warning in pr113026-1.c [PR113524]
> |
> | The bogus warning in pr113026-1.c is issued at some optimization
> | levels on various 32-bit targets.
> |
> | ... 6 lines of the commit log omitted.
> Produces 7 regressions:
> |
> | regressions.sum:
> | Running gcc:gcc.dg/torture/dg-torture.exp ...
> | XPASS: gcc.dg/torture/pr113026-1.c -O0 PR118504 (test for bogus messages, line 12)
> | XPASS: gcc.dg/torture/pr113026-1.c -O1 PR118504 (test for bogus messages, line 12)
> | XPASS: gcc.dg/torture/pr113026-1.c -O2 PR118504 (test for bogus messages, line 12)
> | XPASS: gcc.dg/torture/pr113026-1.c -O2 -flto
> | -fno-use-linker-plugin -flto-partition=none PR118504 (test for
> | bogus messages, line 12)
> | ... and 3 more
> Used configuration :
> *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb
> -march=armv8-a+simd -mfpu=auto -mfloat-abi=hard
> *configure and test flags:* --target arm-eabi --disable-multilib
> --with-mode=thumb --with-arch=armv8-a+simd
> --with-fpu=crypto-neon-fp-armv8 --with-float=hard
> --target_board=-mthumb/-march=armv8-a+simd/-mfpu=auto/-mfloat-abi=hard
> qemu_cpu=any
> We track this bug report under
> https://linaro.atlassian.net/browse/GNU-1870. Please let us know if
> you have a fix.
> If you have any questions regarding this report, please ask on
> linaro-toolchain(a)lists.linaro.org mailing list.
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below contains the details of the failures, and the
> ways to reproduce a debug environment:
> You can find the failure logs in *.log.1.xz files in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_v8a_h…
> The full lists of regressions and improvements as well as configure
> and make commands are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_v8a_h…
> The list of [ignored] baseline and flaky failures are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_v8a_h…
> Current build :
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_v8a_h…
> Reference build :
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_v8a_h…
> Instruction to reproduce the build :
> https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s…
> Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git
--
Alexandre Oliva, happy hacker https://blog.lx.oliva.nom.br/
Free Software Activist FSFLA co-founder GNU Toolchain Engineer
More tolerance and less prejudice are key for inclusion and diversity.
Excluding neuro-others for not behaving ""normal"" is *not* inclusive!
Hi!
On 4/3/26 08:06, ci_notify--- via Gcc-regression wrote:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In aarch64 native, after:
> | commit gcc-16-8401-g71033b1dfbd1
> | Author: Roger Sayle <roger(a)nextmovesoftware.com>
> | Date: Wed Apr 1 23:54:50 2026 +0100
> |
> | PR target/123238: VCOND_MASK regression on aarch64.
> |
> | This patch fixes the regression PR target/123238 on aarch64, using the
> | changes to aarch64's aarch64_rtx_costs proposed by Tamar Christina.
> |
> | ... 38 lines of the commit log omitted.
>
> Produces 1 regression:
> |
> | regressions.sum:
> | Running gcc:gcc.target/aarch64/aarch64.exp ...
> | FAIL: gcc.target/aarch64/pr123238.c scan-assembler-not not
>
This was fixed by Andrew in:
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=9c694b3ecd0eb5308e85a0eac69c4…
Thanks,
Christophe
> Used configuration :
> *CI config* tcwg_gcc_check aarch64-linux-gnu
> *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu--disable-multilib --enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1868. Please let us know if you have a fix.
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
> The full lists of regressions and improvements as well as configure and make commands are in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
> The list of [ignored] baseline and flaky failures are in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s…
>
> Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git
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.
Hi,
Probably these errors are false detections caused by precision errors in floating-point arithmetic. Please ignore the mail. We'll update the tests.
I apologize for the false detection.
Best regards,
Yasuyuki Ohno
Software Development Div.,
Advanced Technology Development Unit,
Fujitsu Research, Fujitsu Limited, JAPAN.
________________________________
差出人: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
送信: 2026 年 4 月 12 日 (日曜日) 17:45
宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com>
Cc: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>; a.bataev(a)outlook.com <a.bataev(a)outlook.com>
件名: [Linaro-TCWG-CI] llvmorg-23-init-11166-g8ac9461e48e0: 1 regression 1 fix on aarch64
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In tcwg_flang_test/main-aarch64-Ofast-sve_vls-lto-lld, after:
| commit llvmorg-23-init-11166-g8ac9461e48e0
| Author: Alexey Bataev <a.bataev(a)outlook.com>
| Date: Sat Apr 11 08:18:36 2026 -0400
|
| [SLP] Reject 2-element vectorization when vector inst count exceeds scalar
|
| The LLVM cost model uses integer-valued throughput costs which cannot
| represent fractional costs. For 2-element vectors, this rounding can
| make vectorization appear profitable when it actually produces more
| ... 15 lines of the commit log omitted.
Produces 1 regression 1 fix:
|
| regressions.sum:
| Running test-suite:Fujitsu/C/0121 ...
| FAIL: test-suite :: Fujitsu/C/0121/Fujitsu-C-0121_0259.test
| # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
|
| fixes.sum:
| Running test-suite:Fujitsu/Fortran/0640 ...
| FAIL: test-suite :: Fujitsu/Fortran/0640/Fujitsu-Fortran-0640_0216.test
| # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld
* Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH}
cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-2210. Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/…
Full commit : https://github.com/llvm/llvm-project/commit/8ac9461e48e024448a2b6493b7c5b50…