Hi, This test is incorrect. Therefore, we will correct the test.
The issue became visible after LLVM commit(70d088d) changed symbol resolution behavior to prefer a specific procedure defined in a generic interface over an explicitly declared intrinsic procedure. As a result, int(1,1), which had previously been resolved as the intrinsic function INT(A,KIND), is now resolved as ifunc01(1,1). Consequently, its result changes from 1 to 2. Because the test still assumes the previous behavior and retains the corresponding expected output, the failure is exposed.
To address this issue, the test should be updated to verify the results of the intrinsic function INT and the specific procedure ifunc01 independently. Before: if (int(1).ne.int(1,1)) print *,'error' After: if (int(1).ne.1) print *,'erro*' if (*nt(1,1).ne.2) print *,'error'
This change explicitly verifies that the intrinsic function INT returns 1 and that the specific procedure ifunc01 associated with the generic interface returns 2, eliminating the dependency on the previous symbol resolution behavior.
Please ignore the mail. We'll update the test. We apologize for the false detection.
Best regards, Yasuyuki Ohno
Software Development Div., Advanced Technology Development Unit, Fujitsu Research, Fujitsu Limited, JAPAN.
________________________________ 差出人: ci_notify@linaro.org ci_notify@linaro.org 送信: 2026 年 9 月 4 日 (金曜日) 21:34 宛先: contact-ci-compiler-test-suite@cs.jp.fujitsu.com contact-ci-compiler-test-suite@cs.jp.fujitsu.com Cc: maxim.kuvyrkov@linaro.org maxim.kuvyrkov@linaro.org; ali.bahrani94521036@gmail.com ali.bahrani94521036@gmail.com 件名: [Linaro-TCWG-CI] llvmorg-24-init-7065-g70d088d10d20: 1 regression 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-24-init-7065-g70d088d10d20 | Author: Ali Bahrani ali.bahrani94521036@gmail.com | Date: Wed Sep 2 13:40:28 2026 -0400 | | [Flang] Interface vs explicit intrinsics priority (#215355) | | Updated `ExpressionAnalyzer::ResolveGeneric` method to prioritize | internal interface definition over explicit intrinsic in symbol resolution. | | ... 4 lines of the commit log omitted.
Produces 1 regression: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/0625 ... | FAIL: test-suite :: Fujitsu/Fortran/0625/Fujitsu-Fortran-0625_0035.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 -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-2273. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain@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-O3-neoverse_v1-... 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-... 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-...
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-... Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1-...
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/s...
Full commit : https://github.com/llvm/llvm-project/commit/70d088d10d207483dca826b5f51ee9d6...