> -----Original Message-----
> From: ci_not...@linaro.org <ci_not...@linaro.org>
> Sent: Thursday, August 22, 2024 10:30 AM
> To: rgue...@gcc.gnu.org
> Cc: gcc-regression@gcc.gnu.org; Andrew Pinski (QUIC)
> <quic_apin...@quicinc.com>
> Subject: [Linaro-TCWG-CI] gcc-15-3087-gb07f8a30115: FAIL: 2
> regressions on aarch64
> 
> 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-
> toolch...@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-1317 , please let us
> know if you are looking at the problem and/or when you have
> a fix.

I have filed https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116463 for the 
failure (which was a missed optimization even before the patch; the detection 
of vector complex multiply is very sensitive in changes to the IR differences).


Thanks,
Andrew Pinski


> 
> In gcc_check master-aarch64 after:
> 
>   | commit gcc-15-3087-gb07f8a30115
>   | Author: Andrew Pinski <quic_apin...@quicinc.com>
>   | Date:   Wed Aug 21 17:41:38 2024 -0700
>   |
>   |     fold: Fix `a * 1j` if a has side effects [PR116454]
>   |
>   |     The problem here was a missing save_expr around arg0
> since
>   |     it is used twice, once in REALPART_EXPR and once in
> IMAGPART_EXPR.
>   |     Thia adds the save_expr and reformats the code slightly
> so it is a
>   |     little easier to understand.  It excludes the case when arg0
> is
>   |     a COMPLEX_EXPR since in that case we'll end up with the
> distinct
>   | ... 19 lines of the commit log omitted.
> 
> FAIL: 2 regressions
> 
> regressions.sum:
>               === gcc tests ===
> 
> Running gcc:gcc.dg/vect/complex/complex.exp ...
> FAIL: gcc.dg/vect/complex/fast-math-complex-mls-double.c
> scan-tree-dump vect "Found COMPLEX_FMA"
> FAIL: gcc.dg/vect/complex/fast-math-complex-mls-float.c
> scan-tree-dump vect "Found COMPLEX_FMA"
> 
> 
> You can find the failure logs in *.log.1.xz files in
>  - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-
> build/2486/artifact/artifacts/00-sumfiles/
> 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-aarch64-
> build/2486/artifact/artifacts/notify/
> The list of [ignored] baseline and flaky failures are in
>  - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-
> build/2486/artifact/artifacts/sumfiles/xfails.xfail
> 
> 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/2486/artifact/artifacts
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--
> master-aarch64-build/2485/artifact/artifacts
> 
> Reproduce last good and first bad builds: https://git-
> us.linaro.org/toolchain/ci/interesting-
> commits.git/plain/gcc/sha1/b07f8a301158e53717b8688cc8ea
> 430b6f02574c/tcwg_gcc_check/master-
> aarch64/reproduction_instructions.txt
> 
> Full commit : https://github.com/gcc-
> mirror/gcc/commit/b07f8a301158e53717b8688cc8ea430b6f0
> 2574c
> 
> List of configurations that regressed due to this commit :
> * tcwg_gcc_check
> ** master-aarch64
> *** FAIL: 2 regressions
> *** https://git-us.linaro.org/toolchain/ci/interesting-
> commits.git/plain/gcc/sha1/b07f8a301158e53717b8688cc8ea
> 430b6f02574c/tcwg_gcc_check/master-aarch64/details.txt
> *** https://ci.linaro.org/job/tcwg_gcc_check--master-
> aarch64-build/2486/artifact/artifacts

Reply via email to