Hi,
I am looking into these regressions.
Regards,
Surya
On 26/06/24 7:51 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. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> We track this report status in https://linaro.atlassian.net/browse/GNU-1270 , please let us know if you are looking at the problem and/or when you have a fix.
>
> In gcc_check master-aarch64 after:
>
> | commit gcc-15-1619-g3b9b8d6cfdf5
> | Author: Surya Kumari Jangala <jskumari(a)linux.ibm.com>
> | Date: Tue Jun 25 08:37:49 2024 -0500
> |
> | ira: Scale save/restore costs of callee save registers with block frequency
> |
> | In assign_hard_reg(), when computing the costs of the hard registers, the
> | cost of saving/restoring a callee-save hard register in prolog/epilog is
> | taken into consideration. However, this cost is not scaled with the entry
> | block frequency. Without scaling, the cost of saving/restoring is quite
> | small and this can result in a callee-save register being chosen by
> | ... 14 lines of the commit log omitted.
>
> FAIL: 4 regressions
>
> regressions.sum:
> === g++ tests ===
>
> Running g++:g++.target/aarch64/sve/acle/aarch64-sve-acle.exp ...
> FAIL: gcc.target/aarch64/sve/acle/general/cpy_1.c -march=armv8.2-a+sve -moverride=tune=none check-function-bodies dup_x0_m
> === gcc tests ===
>
> Running gcc:gcc.dg/dg.exp ...
> FAIL: gcc.dg/pr10474.c scan-rtl-dump pro_and_epilogue "Performing shrink-wrapping"
>
> Running gcc:gcc.target/aarch64/sve/acle/aarch64-sve-acle.exp ...
> ... and 5 more entries
>
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2235/artifac…
> The full lists of regressions and progressions as well as configure and make commands are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2235/artifac…
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2235/artifac…
>
> The configuration of this build is:
> CI config tcwg_gcc_check master-aarch64
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2235/artifac…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2234/artifac…
>
> Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
>
> Full commit : https://github.com/gcc-mirror/gcc/commit/3b9b8d6cfdf59337f4b7ce10ce92a98044…
>
> List of configurations that regressed due to this commit :
> * tcwg_gcc_check
> ** master-aarch64
> *** FAIL: 4 regressions
> *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
> *** https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2235/artifac…
Hi Matthias,
Looking at [1], we are seeing this error only for bare-metal 32-bit ARM target, which, I believe, is not a configuration that compiler explorer supports. The specific configurations are either soft-float, or target ARM cores without NEON (aka no SIMD FPU).
Maybe the test should be guarded on the target supporting vectorization? I.e., maybe add
// { dg-require-effective-target vect_int }
?
[1] https://linaro.atlassian.net/browse/GNU-1265
--
Maxim Kuvyrkov
https://www.linaro.org
> On Jun 21, 2024, at 19:03, Matthias Kretz via Gcc-regression <gcc-regression(a)gcc.gnu.org> wrote:
>
> Hi,
>
> I looked into this and still don't understand how to reproduce it.
>
> The issue as logged in libstdc++.log is a call from
> find_last_set(simd_mask<int, _VecBuiltin<16>>) to
> _MaskImplNeonMixin::_S_to_bits, which calls vpadd_s32 with two
> [[gnu::vector_size(8)]] int arguments. The CI compiler complains "error:
> cannot convert '__vector(2) int' to 'int32x2_t'".
>
> Why is that an error on your side and not on any compiler I have at hand?
>
> https://compiler-explorer.com/z/88WhcM7Kb not an error here.
>
> In any case, the new test only exposes an existing issue in the <experimental/
> simd> implementation (or its interaction with some variants of GCC?). The
> change did not introduce a new bug to libstdc++.
>
> Best,
> Matthias
>
>
> On Friday, 21 June 2024 17:00:23 GMT+2 ci_notify(a)linaro.org wrote:
>> Dear contributor, our automatic CI has detected problems related to your
>> patch(es). Please find some details below. If you have any questions,
>> please follow up on linaro-toolchain(a)lists.linaro.org mailing list,
>> Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain
>> developer on the usual project channel.
>>
>> We appreciate that it might be difficult to find the necessary logs or
>> reproduce the issue locally. If you can't get what you need from our CI
>> within minutes, let us know and we will be happy to help.
>>
>> We track this report status in https://linaro.atlassian.net/browse/GNU-1265
>> , please let us know if you are looking at the problem and/or when you have
>> a fix.
>> In arm-eabi v7-a softfp after:
>> | commit gcc-15-1500-g1340ddea015
>> | Author: Matthias Kretz <m.kretz(a)gsi.de>
>> | Date: Fri Jun 14 15:11:25 2024 +0200
>> |
>> | libstdc++: Fix find_last_set(simd_mask) to ignore padding bits
>> |
>> | With the change to the AVX512 find_last_set implementation, the
>> | change
>> | to AVX512 operator!= is unnecessary. However, the latter was not
>> | producing optimal code and unnecessarily set the padding bits. In
>> | theory, the compiler could determine that with the new !=
>> | implementation, the bit operation for clearing the padding bits is a
>> |
>> | ... 13 lines of the commit log omitted.
>>
>> FAIL: 2 regressions
>>
>> regressions.sum:
>> === libstdc++ tests ===
>>
>> Running libstdc++:libstdc++-dg/conformance.exp ...
>> FAIL: experimental/simd/pr115454_find_last_set.cc -mfpu=neon -ffast-math -O2
>> -Wno-psabi (test for excess errors) UNRESOLVED:
>> experimental/simd/pr115454_find_last_set.cc -mfpu=neon -ffast-math -O2
>> -Wno-psabi compilation failed to produce executable
>>
>>
>> You can find the failure logs in *.log.1.xz files in
>> -
>> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e
>> abi-build/512/artifact/artifacts/00-sumfiles/ The full lists of regressions
>> and progressions as well as configure and make commands are in -
>> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e
>> abi-build/512/artifact/artifacts/notify/ The list of [ignored] baseline and
>> flaky failures are in
>> -
>> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e
>> abi-build/512/artifact/artifacts/sumfiles/xfails.xfail
>>
>> The configuration of this build is:
>> CI config tcwg_gnu_embed_check_gcc arm-eabi -marm -march=armv7-a
>> -mfpu=vfpv3-d16 -mfloat-abi=softfp
>>
>> -----------------8<--------------------------8<--------------------------8<-
>> ------------------------- The information below can be used to reproduce a
>> debug environment:
>>
>> Current build :
>> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e
>> abi-build/512/artifact/artifacts Reference build :
>> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e
>> abi-build/511/artifact/artifacts
>>
>> Reproduce last good and first bad builds:
>> https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh
>> a1/1340ddea0158de3f49aeb75b4013e5fc313ff6f4/tcwg_gnu_embed_check_gcc/master-
>> arm_v7a_softfp_eabi/reproduction_instructions.txt
>>
>> Full commit :
>> https://github.com/gcc-mirror/gcc/commit/1340ddea0158de3f49aeb75b4013e5fc31
>> 3ff6f4
>>
>> List of configurations that regressed due to this commit :
>> * tcwg_gnu_embed_check_gcc
>> ** master-arm_v7a_softfp_eabi
>> *** FAIL: 2 regressions
>> ***
>> https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh
>> a1/1340ddea0158de3f49aeb75b4013e5fc313ff6f4/tcwg_gnu_embed_check_gcc/master-
>> arm_v7a_softfp_eabi/details.txt ***
>> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e
>> abi-build/512/artifact/artifacts
>
>
> --
> ──────────────────────────────────────────────────────────────────────────
> Dr. Matthias Kretz https://mattkretz.github.io
> GSI Helmholtz Center for Heavy Ion Research https://gsi.de
> std::simd
> ──────────────────────────────────────────────────────────────────────────
Progress:
* UM-2 [QEMU upstream maintainership]
+ code review and target-arm pullreq
+ Coverity gardening: triage of new issues; update of component definitions
+ respin of "allow a second UART in virt machine" patchset from last year
+ KVM Forum programme committee work
-- PMM
Hello Linaro Toolchain Working Group,
clang-arm64-windows-msvc cannot checkout LLVM because of this error:
fatal: Unable to create
'C:/Users/tcwg/llvm-worker/clang-arm64-windows-msvc/llvm/.git/index.lock':
File exists.
Looks like it needs some love and care. Could you look at this, please?
Thanks
Galina
On Wed, 2024-06-12 at 20:25 +0000, ci_notify(a)linaro.org wrote:
> Dear contributor, our automatic CI has detected problems related to
> your patch(es). Please find some details below. If you have any
> questions, please follow up on
> linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg
> channel, or ping your favourite Linaro toolchain developer on the
> usual project channel.
>
> We appreciate that it might be difficult to find the necessary logs
> or reproduce the issue locally. If you can't get what you need from
> our CI within minutes, let us know and we will be happy to help.
>
> We track this report status in
> https://linaro.atlassian.net/browse/GNU-1254 , please let us know if
> you are looking at the problem and/or when you have a fix.
Sorry about the breakage.
I had filed this as https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115465
and I believe I've fixed it with r15-1220-
ge35f4eab68773b08324f9784ca69f8ace3c657cc.
Dave
>
> In gcc_build master-aarch64 after:
>
> | commit gcc-15-1209-gc5e3be45688
> | Author: David Malcolm <dmalcolm(a)redhat.com>
> | Date: Wed Jun 12 09:15:09 2024 -0400
> |
> | pretty_printer: make all fields private
> |
> | No functional change intended.
> |
> | gcc/analyzer/ChangeLog:
> | * access-diagram.cc (access_range::dump): Update for
> fields of
> | pretty_printer becoming private.
> | ... 227 lines of the commit log omitted.
>
> Results changed to
> # reset_artifacts:
> -10
> # true:
> 0
> # build_abe gcc:
> # FAILED
> # First few build errors in logs:
> # 00:03:27 ../../../../../../gcc/gcc/config/aarch64/aarch64-early-
> ra.cc:3449:23: error: ‘class pretty_printer’ has no member named
> ‘buffer’; did you mean ‘output_buffer* pretty_printer::m_buffer’?
> (not accessible from this context)
> # 00:03:27 make[2]: *** [/home/tcwg-
> buildslave/workspace/tcwg_gnu_3/abe/snapshots/gcc.git~master/gcc/conf
> ig/aarch64/t-aarch64:200: aarch64-early-ra.o] Error 1
> # 00:03:27 make[1]: *** [Makefile:4704: all-gcc] Error 2
> # 00:03:27 make: *** [Makefile:1065: all] Error 2
>
> From
> # reset_artifacts:
> -10
> # true:
> 0
> # build_abe gcc:
> 1
>
> The configuration of this build is:
> CI config tcwg_gcc_build master-aarch64
>
> -----------------8<--------------------------8<----------------------
> ----8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build :
> https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/2157/artifac…
> Reference build :
> https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/2156/artifac…
>
> Reproduce last good and first bad builds:
> https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
>
> Full commit :
> https://github.com/gcc-mirror/gcc/commit/c5e3be456888aa48f591512ec28183703e…
>
> List of configurations that regressed due to this commit :
> * tcwg_gcc_build
> ** master-aarch64
> *** Failure
> ***
> https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
> ***
> https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/2157/artifac…