Thank you for your comment.
As you pointed out, it appears this commit is not related to the issue.
I apologize for the false detection.

As this issue appears to be identical to 
"https://github.com/llvm/llvm-project/issues/191844,"; which is currently being 
investigated by the community, we will close this issue.

Best regards,
Yasuyuki Ohno

Software Development Div.,
Advanced Technology Development Unit,
Fujitsu Research, Fujitsu Limited, JAPAN.

________________________________
差出人: Michael Kruse <[email protected]>
送信: 2026 年 6 月 20 日 (土曜日) 0:32
宛先: [email protected] <[email protected]>
Cc: [email protected] 
<[email protected]>; [email protected] 
<[email protected]>; [email protected] 
<[email protected]>
件名: Re: [Linaro-TCWG-CI] llvmorg-23-init-19659-g3fee6e5ab45d: 18533 regressions 
on aarch64

[Some people who received this message don't often get email from 
[email protected]. Learn why this is important at 
https://aka.ms/LearnAboutSenderIdentification ]

I think this is a misattribution of the failure. #203481 is a change
of the CMake build system, it does not change anything functional in
the flang compiler. #203481 had a build problem which was fixed in
#204438. But since Flang built successfully, it cannot be the problem
of that CI problem.

Michael

Am Fr., 19. Juni 2026 um 13:56 Uhr schrieb <[email protected]>:
>
> 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-23-init-19659-g3fee6e5ab45d
>   | Author: Michael Kruse <[email protected]>
>   | Date:   Wed Jun 17 16:13:40 2026 +0200
>   |
>   |     [Flang] Add mock flang driver (#203481)
>   |
>   |     Add a mock driver to pass CMake's compiler introspection for
>   |     CMake_Fortran_COMPILER. It's purpose is to not having to build the 
> full
>   |     flang compiler for the runtimes-configure phase in
>   | ... 59 lines of the commit log omitted.
>
> Produces 18533 regressions:
>   |
>   | regressions.sum:
>   | Running test-suite:Fujitsu/Fortran/0004 ...
>   | NOEXE: test-suite :: Fujitsu/Fortran/0004/Fujitsu-Fortran-0004_0001.test
>   | NOEXE: test-suite :: Fujitsu/Fortran/0004/Fujitsu-Fortran-0004_0002.test
>   | Running test-suite:Fujitsu/Fortran/0005 ...
>   | NOEXE: test-suite :: Fujitsu/Fortran/0005/Fujitsu-Fortran-0005_0001.test
>   | ... and 19173 more
>   | # "NOEXE" means : the test program cannot be compiled
>
> 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 -mcpu=neoverse-v1 
> -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -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 -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 -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-2235. 
> (Require Linaro login) Please let us know if you have a fix.
>
> If you have any questions regarding this report, please ask on 
> [email protected] 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-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays-build/builds/10332/archive/artifacts/00-sumfiles/
> 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-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays-build/builds/10332/archive/artifacts/notify/
> The list of [ignored] baseline and flaky failures are in
>  * 
> http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays-build/builds/10332/archive/artifacts/sumfiles/xfails.xfail
>
> Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
>
> Current build   : 
> http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays-build/builds/10332/archive/artifacts/
> Reference build : 
> http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays-build/builds/10331/archive/artifacts/
>
> Instruction to reproduce the build : 
> https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/sha1/3fee6e5ab45d1d352f995ae4eafa5106a0c5fc0d/tcwg_flang_test/main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays/reproduction_instructions.txt
>
> Full commit : 
> https://github.com/llvm/llvm-project/commit/3fee6e5ab45d1d352f995ae4eafa5106a0c5fc0d



--
Tardyzentrismus verboten!
_______________________________________________
linaro-toolchain mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to