gfortran.dg/pr112877-1.f90 is
-----------
! { dg-do compile }
! { dg-options "-Os" }
program test
use iso_c_binding, only: c_short
interface
subroutine foo(a) bind(c)
import c_short
integer(kind=c_short), intent(in), value :: a
end subroutine foo
end interface
integer(kind=c_short) a(5);
call foo (a(3))
end
! { dg-final { scan-assembler "movswl\t10\\(%rsp\\), %edi" { target { { *-*-linu
x* *-*-gnu* } && { ! ia32 } } } } }
! { dg-final { scan-assembler "movswl\t-14\\(%ebp\\), %eax" { target { { *-*-lin
ux* *-*-gnu* } && { ia32 } } } } }
----------
Why does it fail
FAIL: gfortran.dg/pr112877-1.f90 -O scan-assembler movswl\t10\\(%rsp\\), %edi
on arm-linux-gnueabihf?
H.J.
---------- Forwarded message ---------
From: <ci_notify(a)linaro.org>
Date: Wed, Dec 4, 2024 at 7:26 PM
Subject: [Linaro-TCWG-CI] 7 patches in gcc: 1 regressions on arm
To: <hjl.tools(a)gmail.com>
Dear contributor,
Our automatic CI has detected problems related to your patch(es).
Please find some details below.
In gcc_check master-arm, after:
| 7 patches in gcc
| Patchwork URL: https://patchwork.sourceware.org/patch/102351
| 97708c5e402 [PATCH v5 7/7] ssa-fre-4.c: Enable for all targets and
adjust scan match
| 9c6ba8e5347 [PATCH v5 6/7] scev-cast.c: Enable for all targets and
adjust scan matches
| d78236fd00e [PATCH v5 5/7] vect-simd-clone-1[6-8][cd].c: Expect
in-branch clones for x86
| a9ef03a445d [PATCH v5 4/7] i386: Adjust apx-ndd.c for frontend
promotion removal
| 14ece135ff9 [PATCH v5 3/7] Use incoming small integer argument
type if possible
| ... and 2 more patches in gcc
| ... applied on top of baseline commit:
| fb64a7b0e1d RISC-V: Add assert for insn operand out of range
access [PR117878][NFC]
Produces 1 regressions:
| Running gfortran:gfortran.dg/dg.exp ...
| FAIL: gfortran.dg/pr112877-1.f90 -O scan-assembler
movswl\t10\\(%rsp\\), %edi
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/10456/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/10456/artifa…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/10456/artifa…
Current build :
https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/10456/artifa…
Reference build :
https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3116/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.
--
H.J.
Should have been reported as follows.
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 fujitsu_testsuite#a0e269d5d
| Author: KAWASHIMA Takahiro <t-kawashima(a)fujitsu.com>
| Date: Tue Nov 19 17:58:42 2024 +0900
|
| Update RUN.md
|
| - Change the Flang command name
| - Add a notice about `LD_LIBRARY_PATH`
| - Explain about `NOEXE`
Produces 2 regressions:
| Running test-suite:Fujitsu/Fortran/0106 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0106/Fujitsu-Fortran-0106_0033.test
| NOEXE: test-suite :: Fujitsu/Fortran/0106/Fujitsu-Fortran-0106_0034.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-1451. 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/95/a…
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/95/a…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/95/a…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build :
https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/95/a…
Reference build :
https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/90/a…
Instruction to reproduce the build :
https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/fujits…
Full commit : https://github.com/fujitsu/compiler-test-suite/commit/a0e269d5d279c3a0781bb…
On Fri, 29 Nov 2024 at 04:54, <ci_notify(a)linaro.org> wrote:
> [Error replacing 'FILE' - Error processing tokens]
Should have been reported as follows.
Some regressions and some improvements after this commit in fujitsu
testsuite.
Regards,
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 fujitsu_testsuite#471c71be0
| Author: Ichinose, Katsumi <1nose(a)jp.fujitsu.com>
| Date: Wed Nov 27 18:43:38 2024 +0900
|
| Add test programs for the 2024-11 release
Produces 19 regressions:
| Running test-suite:Fujitsu/C/0068 ...
| NOEXE: test-suite :: Fujitsu/C/0068/Fujitsu-C-0068_0113.test
| NOEXE: test-suite :: Fujitsu/C/0068/Fujitsu-C-0068_0115.test
| Running test-suite:Fujitsu/C/0072 ...
| NOEXE: test-suite :: Fujitsu/C/0072/Fujitsu-C-0072_0006.test
| ... and 22 more
141 improvements : | # "NOEXE" means : the test program cannot be compiled
| # "FAIL" means : the execution of the compiled binary failed /
output of the binary differs from the expected one
| Running test-suite:Fujitsu/Fortran/0070 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0070/Fujitsu-Fortran-0070_0185.test
| FAIL: test-suite :: Fujitsu/Fortran/0070/Fujitsu-Fortran-0070_0184.test
| Running test-suite:Fujitsu/Fortran/0080 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0080/Fujitsu-Fortran-0080_0008.test
| ... and 179 more
| # "NOEXE" means : the test program cannot be compiled
| # "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 -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-1449. 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/fujits…
Full commit : https://github.com/fujitsu/compiler-test-suite/commit/471c71be0fe507ecb02b5…
On Thu, 28 Nov 2024 at 17:08, <ci_notify(a)linaro.org> wrote:
> [Error replacing 'FILE' - Error processing tokens]
Hi Alexey,
It seems your patch below causes build failure of 654.roms_s for "-O3 -flto" on aarch64-linux-gnu. Has this been reported already?
Let me know if not, and I'll help with the reporting and reproduction.
Thanks!
--
Maxim Kuvyrkov
https://www.linaro.org
> On Nov 26, 2024, at 12:32, 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_bmk-code_vect-cpu2017fast/llvm-aarch64-master-O3_LTO, after:
> | commit llvmorg-20-init-13176-gb8703369daf7
> | Author: Alexey Bataev <a.bataev(a)outlook.com>
> | Date: Fri Nov 22 16:10:17 2024 -0500
> |
> | [SLP] Match poison as instruction with the same opcode
> |
> | Patch allows to vector scalar instruction + poison values as if poisons
> | are instructions with the same opcode. It allows better vectorization of
> | the repeated values, reduces number of insertelement instructions and
> | ... 54 lines of the commit log omitted.
>
> Produces 654.roms_s failed to build:
> | the following benchmarks now fails :
> | - 654.roms_s failed to build
>
> Used configuration :
> Below reproducer instructions can be used to re-build both "first_bad" and "last_good" cross-toolchains used in this bisection. Naturally, the scripts will fail when triggerring benchmarking jobs if you don\'t have access to Linaro TCWG CI.
>
> Configuration:
> - Benchmark: SPEC CPU2017
> - Toolchain: Clang + Glibc + LLVM Linker
> - Version: all components were built from their tip of trunk
> - Target: aarch64-linux-gnu
> - Compiler flags: O3 -LTO
> - Hardware: <unknown>
>
> This benchmarking CI is work-in-progress, and we welcome feedback and suggestions at linaro-toolchain(a)lists.linaro.org . In our improvement plans is to add support for SPEC CPU2017 benchmarks and provide "perf report/annotate" data behind these reports.
>
> We track this bug report under https://linaro.atlassian.net/browse/LLVM-1448. 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:
>
>
>
> Current build : https://ci.linaro.org/job/tcwg_bmk-code_vect-cpu2017fast--llvm-aarch64-mast…
> Reference build : https://ci.linaro.org/job/tcwg_bmk-code_vect-cpu2017fast--llvm-aarch64-mast…
>
> 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/b8703369daf777706196ff914c0376c…
The results now produced by flang(-new) for Fujitsu Fortran test 0676_0160 are better than the desired results of the test.
The test uses the SUM intrinsic function to compute the sum of 100 complex numbers. These values are all identical. The new results from the SUM intrinsic function match the value of 100 times this value exactly. The expected value used by the test does not, and perhaps it reflects the result of a compiler using a less accurate summation method than flang is now using.
Should have been reported as below.
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-13009-g3f594741cf8e
| Author: Peter Klausler <pklausler(a)nvidia.com>
| Date: Thu Nov 21 10:47:21 2024 -0800
|
| [flang] Fix implementation of Kahan summation (#116897)
|
| In the runtime's implementation of floating-point SUM, the
| implementation of Kahan's algorithm for increased precision is
| incorrect. The running correction factor should be subtracted from
each
| ... 4 lines of the commit log omitted.
Produces 1 regressions1 improvements:
| Running test-suite:Fujitsu/Fortran/0676 ...
| FAIL: test-suite :: Fujitsu/Fortran/0676/Fujitsu-Fortran-0676_0160.test
| # "FAIL" means : the execution of the compiled binary failed / output
of the binary differs from the expected one
| Running test-suite:Fujitsu/Fortran/0366 ...
| FAIL: test-suite :: Fujitsu/Fortran/0366/Fujitsu-Fortran-0366_0097.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-1446.
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/3f594741cf8e1537fb25f84ef3cf224…
It should have been reported as below. This is after this commit in
llvm-test-suite.
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-19.1.1-16-g9f743a87e
| Author: KAWASHIMA Takahiro <t-kawashima(a)fujitsu.com>
| Date: Fri Nov 22 10:41:14 2024 +0900
|
| [cmake] Support more Fortran filename suffixes (#180)
|
| These Fortran suffixes are aligned with the `lookupTypeForExtension`
| function in `clang/lib/Driver/Types.cpp`.
Produces 30 regressions:
| Running test-suite:Fujitsu/Fortran/0647 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0647/Fujitsu-Fortran-0647_0001.test
| NOEXE: test-suite :: Fujitsu/Fortran/0647/Fujitsu-Fortran-0647_0002.test
| NOEXE: test-suite :: Fujitsu/Fortran/0647/Fujitsu-Fortran-0647_0004.test
| NOEXE: test-suite :: Fujitsu/Fortran/0647/Fujitsu-Fortran-0647_0006.test
| ... and 27 more
| # "NOEXE" means : the test program cannot be compiled
| # "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-1447. 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_t…
Full commit : https://github.com/llvm/llvm-test-suite/commit/9f743a87e20346070725bd1f06cc…
On Sat, 23 Nov 2024 at 11:20, <ci_notify(a)linaro.org> wrote:
> [Error replacing 'FILE' - Error processing tokens]