Has the bisect somehow failed in this? It's highly unlikely that a test
macro would cause an ICE, unless it somehow exposed a latent bug, which
also seems very unlikely in this context.
Sid
On 2025-01-28 20:48, 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 gcc_check master-arm, after:
> | gcc patch https://patchwork.sourceware.org/patch/105574
> | Author: Siddhesh Poyarekar <siddhesh(a)gotplt.org>
> | Date: Tue Jan 28 12:43:50 2025 -0500
> |
> | [PATCH v3] testsuite/118127: Pass fortran tests on ppc64le for IEEE128 long doubles
> |
> | Denormal behaviour is well defined for IEEE128 long doubles, so don't
> | XFAIL some gfortran tests on ppc64le when configured with the IEEE128
> | long double ABI.
> | ... 13 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 2abc555a80b Daily bump.
>
> Produces 1 regressions 1 improvements:
> |
> | regressions.sum:
> | Running gcc:gcc.dg/dg.exp ...
> | FAIL: gcc.dg/pr41123.c (internal compiler error: in gen_movsf, at config/arm/arm.md:7450)
> |
> | improvements.sum:
> | Running gcc:gcc.dg/dg.exp ...
> | FAIL: gcc.dg/pr41123.c (internal compiler error: in gen_movsf, at /home/tcwg-buildslave/workspace/tcwg_gnu_2/abe/snapshots/gcc.git~master/gcc/config/arm/arm.md:7450)
>
> Used configuration :
> *CI config* tcwg_gcc_check master-arm
> *configure and test flags:* --target arm-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
> * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/10965/artifa…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/10965/artifa…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/10965/artifa…
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/10965/artifa…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3358/artifact/ar…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
[AMD Official Use Only - AMD Internal Distribution Only]
Thanks for bringing this to my notice. I have opened upstream issue https://github.com/llvm/llvm-project/issues/123960 to track this. I am working on a fix and will update when a PR is opened.
Thanks
Abid
________________________________
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: Wednesday, January 22, 2025 6:43 AM
To: ohno.yasuyuki(a)fujitsu.com <ohno.yasuyuki(a)fujitsu.com>; itou.tetsuya(a)fujitsu.com <itou.tetsuya(a)fujitsu.com>; t-kawashima(a)fujitsu.com <t-kawashima(a)fujitsu.com>
Cc: Qadeer, Hafiz Abid <HafizAbid.Qadeer(a)amd.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>
Subject: [Linaro-TCWG-CI] llvmorg-20-init-18360-gaf91372b7561: 1 regressions on aarch64
Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In tcwg_flang_test/main-aarch64-O0-debug, after:
| commit llvmorg-20-init-18360-gaf91372b7561
| Author: Abid Qadeer <haqadeer(a)amd.com>
| Date: Mon Jan 20 12:03:59 2025 +0000
|
| [flang][debug] Improve handling of cyclic derived types. (#122770)
|
| When `RecordType` is converted to corresponding `DIType`, we cache the
| information to avoid doing the conversion again.
|
| ... 66 lines of the commit log omitted.
Produces 1 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0394 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0394/Fujitsu-Fortran-0394_0031.test
| # "NOEXE" means : the test program cannot be compiled
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;openmp;clang-tools-extra" -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/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O0 -g" -DCMAKE_CXX_FLAGS_RELEASE="-O0 -g" -DCMAKE_Fortran_FLAGS_RELEASE="-O0 -g" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-1528. 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
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/383/…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/383/…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/383/…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/383/…
Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/382/…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…
Full commit : https://github.com/llvm/llvm-project/commit/af91372b75613d5654e68d393477e86…
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In master-aarch64, after:
| commit binutils-2_41-release-5490-g50505c486ed
| Author: Nick Clifton <nickc(a)redhat.com>
| Date: Tue Jan 21 10:48:02 2025 +0000
|
| More updated translations
Produces Failure:
| Results changed to
| # reset_artifacts:
| -10
| # true:
| 0
| # build_abe binutils:
| 1
| # build_abe gcc:
| # FAILED
| # build_abe linux:
| # build_abe glibc:
| # build_abe gdb:
| # First few build errors in logs:
| # 00:36:56 make[2]: [Makefile:1835: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored)
| # 00:36:56 make[2]: [Makefile:1836: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored)
| # 00:47:24 make[7]: [Makefile:850: stamp-modules-bits] Error 1 (ignored)
| # 02:07:45 make[2]: [/home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/gcc/ada/gcc-interface/Make-lang.in:995: gnat-install-tools] Error 1 (ignored)
|
| From
| # reset_artifacts:
| -10
| # true:
| 0
| # build_abe binutils:
| 1
| # build_abe gcc:
| 2
| # build_abe linux:
| 4
| # build_abe glibc:
| 5
| # build_abe gdb:
| 6
Used configuration :
*CI config* tcwg_gnu_native_build master-aarch64
*configure and test flags:* --target aarch64-linux-gnu
We track this bug report under https://linaro.atlassian.net/browse/GNU-1505. 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
* https://ci.linaro.org/job/tcwg_gnu_native_build--master-aarch64-build/928/a…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_gnu_native_build--master-aarch64-build/928/a…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_gnu_native_build--master-aarch64-build/928/a…
Current build : https://ci.linaro.org/job/tcwg_gnu_native_build--master-aarch64-build/928/a…
Reference build : https://ci.linaro.org/job/tcwg_gnu_native_build--master-aarch64-build/927/a…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti…
Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=50505c486ed26…
Hi; I'm wondering if anybody is using QEMU's iwmmxt/xscale emulation
for toolchain testing. (My suspicion is the answer is "no".)
This emulation isn't enabled by default, so to use it you would have
to explicitly select an iwmmxt capable CPU (with -cpu or the QEMU_CPU
environment variable). The relevant CPU types are anything beginning
"pxa" (pxa250, pxa255, pxa260, pxa261, pxa262, pxa270-a0, pxa270-a1,
pxa270, pxa270-b0, pxa270-b1, pxa270-c0, pxa270-c5).
The context for this is that I'm considering deprecate-and-drop
for this emulation. (We already dropped all the system emulation
of boards that use these CPUs, so the only thing remaining is their
support via QEMU's user-mode emulation.) If there's still somebody
using this then I'm OK keeping it in QEMU a bit longer, but if
as I suspect it's all entirely unused then we might as well start
the process of dropping it.
(I'm aware that GCC is in the process of dropping its iwmmxt
codegen support. I also didn't find anything particularly with
a web search with examples of users using it.)
thanks
-- PMM
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In master-arm, after:
| commit glibc-2.40.9000-770-gc36fc507819
| Author: Malte Skarupke <malteskarupke(a)fastmail.fm>
| Date: Wed Dec 4 07:56:38 2024 -0500
|
| nptl: Remove g_refs from condition variables
|
| This variable used to be needed to wait in group switching until all sleepers
| have confirmed that they have woken. This is no longer needed. Nothing waits
| on this variable so there is no need to track how many threads are currently
| ... 4 lines of the commit log omitted.
Produces 189 regressions:
|
| regressions.sum:
| Running g++:g++.dg/analyzer/analyzer.exp ...
| FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-default.C -std=c++14 at line 12 (test for warnings, line 11)
| FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-default.C -std=c++14 at line 17 (test for warnings, line 10)
| FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-default.C -std=c++14 at line 18 (test for warnings, line 11)
| FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-default.C -std=c++14 at line 19 (test for warnings, line 11)
| ... and 192 more
Used configuration :
*CI config* tcwg_gnu_native_check_gcc master-arm
*configure and test flags:* --target arm-linux-gnueabihf
We track this bug report under https://linaro.atlassian.net/browse/GNU-1504. 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
* https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/1823/…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/1823/…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/1823/…
Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/1823/…
Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/1822/…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/…
Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=c36fc50781995e6758ca…
Hi thanks for the report.
I think it has already been fixed upstream by https://github.com/llvm/llvm-project/pull/122550<https://github.com/llvm/llvm-project/pull/122550?notification_referrer_id=N…>. Please let me know if this was not the case.
Kind regards,
Tom
________________________________
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: Tuesday, January 14, 2025 10:57 PM
To: ohno.yasuyuki(a)fujitsu.com <ohno.yasuyuki(a)fujitsu.com>; itou.tetsuya(a)fujitsu.com <itou.tetsuya(a)fujitsu.com>; t-kawashima(a)fujitsu.com <t-kawashima(a)fujitsu.com>
Cc: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>; Tom Eccles <Tom.Eccles(a)arm.com>
Subject: [Linaro-TCWG-CI] llvmorg-20-init-17063-g303249c4490a: 9 regressions 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-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays, after:
| commit llvmorg-20-init-17063-g303249c4490a
| Author: Tom Eccles <tom.eccles(a)arm.com>
| Date: Wed Jan 8 10:05:21 2025 +0000
|
| [flang][StackArrays] track pointers through fir.convert (#121919)
|
| This does add a little computational complexity because now every
| freemem operation has to be tested for every allocation. This could be
| improved with some more memoisation but I think it is easier to read
| ... 6 lines of the commit log omitted.
Produces 9 regressions:
| Running test-suite:Fujitsu/Fortran/0073 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0073/Fujitsu-Fortran-0073_0018.test
| Running test-suite:Fujitsu/Fortran/0487 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0487/Fujitsu-Fortran-0487_0035.test
| NOEXE: test-suite :: Fujitsu/Fortran/0487/Fujitsu-Fortran-0487_0036.test
| ... and 7 more
| # "NOEXE" means : the test program cannot be compiled
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;openmp;clang-tools-extra" -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/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG -fstack-arrays" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-1515. 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
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…
Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…
Full commit : https://github.com/llvm/llvm-project/commit/303249c4490a7777a744d9afd449b64…
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,
Florian Hahn and I landed 2 patches for fixing FindLastIV reductions
idiom.
https://github.com/llvm/llvm-project/commit/0e528ac404e13ed2d952a2d83aaf838…https://github.com/llvm/llvm-project/commit/3397950f2d21426c7520d114a125881…
I think those can fix the issue you are facing. Please try them, and let me
know if you still have regression on it.
Mel
On Fri, Dec 13, 2024 at 7:11 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 tcwg_flang_test/main-aarch64-Ofast-sve_vla, after:
> | commit llvmorg-20-init-15150-gb3cba9be41bf
> | Author: Mel Chen <mel.chen(a)sifive.com>
> | Date: Thu Dec 12 16:48:31 2024 +0800
> |
> | [LoopVectorize] Vectorize select-cmp reduction pattern for
> increasing integer induction variable (#67812)
> |
> | Consider the following loop:
> | ```
> | int rdx = init;
> | ... 12 lines of the commit log omitted.
>
> Produces 2 regressions:
> | Running test-suite:Fujitsu/Fortran/0365 ...
> | FAIL: test-suite :: Fujitsu/Fortran/0365/Fujitsu-Fortran-0365_0185.test
> | FAIL: test-suite :: Fujitsu/Fortran/0365/Fujitsu-Fortran-0365_0186.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;openmp;clang-tools-extra"
> -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/bin/clang"
> -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++"
> -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/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=scalable -mllvm
> -scalable-vectorization=preferred -mllvm
> -treat-scalable-fixed-error-as-warning=false -DNDEBUG"
> -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve
> -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm
> -treat-scalable-fixed-error-as-warning=false -DNDEBUG"
> -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve
> -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm
> -treat-scalable-fixed-error-as-warning=false -DNDEBUG"
> -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu
> "$\WORKSPACE/test/test-suite"
>
> We track this bug report under
> https://linaro.atlassian.net/browse/LLVM-1482. 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
> *
> https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
> The full lists of regressions and improvements as well as configure and
> make commands are in
> *
> https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
> The list of [ignored] baseline and flaky failures are in
> *
> https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
>
> Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
>
> Current build :
> https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
> Reference build :
> https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
>
> Instruction to reproduce the build :
> https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…
>
> Full commit :
> https://github.com/llvm/llvm-project/commit/b3cba9be41bfa89bc0ec212706c6028…
On 2025-01-09 12:16, 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_build master-aarch64, after:
> | 8 patches in glibc
> | Patchwork URL: https://patchwork.sourceware.org/patch/104425
> | b2d4876946 [PATCH v16 8/8] Linux: Update internal copy of '<sys/rseq.h>'
> | cdd3e61830 [PATCH v16 7/8] nptl: Remove the rseq area from 'struct pthread'
> | a673377e3d [PATCH v16 6/8] nptl: Move the rseq area to the 'extra TLS' block
> | 86803776b0 [PATCH v16 5/8] nptl: Introduce <rseq-access.h> for RSEQ_* accessors
> | 928c07fc09 [PATCH v16 4/8] nptl: add rtld_hidden_proto to __rseq_size and __rseq_offset
> | ... and 3 more patches in glibc
> | ... applied on top of baseline commit:
> | e41aabcc93 tests: Verify inheritance of cpu affinity
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # init_abe_sysroot:
> | 0
> | # build_abe glibc -- --disable install:
> | # FAILED
> | # First few build errors in logs:
> | # 00:00:59 ../csu/libc-tls.c:221:64: error: ‘TLS_TP_OFFSET’ undeclared (first use in this function); did you mean ‘TLS_DTV_OFFSET’?
> | # 00:00:59 make[2]: *** [/home/tcwg-build/workspace/tcwg_gnu_5/abe/builds/aarch64-unknown-linux-gnu/aarch64-unknown-linux-gnu/glibc-glibc.git~master/sysd-rules:451: /home/tcwg-build/workspace/tcwg_gnu_5/abe/builds/aarch64-unknown-linux-gnu/aarch64-unknown-linux-gnu/glibc-glibc.git~master/csu/libc-tls.o] Error 1
> | # 00:00:59 make[1]: *** [Makefile:484: csu/subdir_lib] Error 2
> | # 00:00:59 make: *** [Makefile:20: all] Error 2
Is there a way to re-trigger this job on the current master branch without posting a new patchset?
I sent this by mistake before Florian's TLS_TP_OFFSET patch was pushed to master but it is now.
Thanks,
Michael