Hi!
On 2025-04-26T00:09:21+0000, ci_notify--- via Gcc-regression
<gcc-regress...@gcc.gnu.org> wrote:
> Our automatic CI has detected problems related to your patch(es). Please find
> some details below.
>
> In gcc_check master-arm, after:
> | commit gcc-16-130-gaafe942227b
> | Author: Thomas Schwinge <tschwi...@baylibre.com>
> | Date: Wed Apr 23 10:51:48 2025 +0200
> |
> | GCN, nvptx offloading: Host/device compatibility: Itanium C++ ABI,
> DSO Object Destruction API [PR119853, PR119854]
> |
> | '__dso_handle' for '__cxa_atexit', '__cxa_finalize'. See
> | <https://itanium-cxx-abi.github.io/cxx-abi/abi.html#dso-dtor>.
> |
> | ... 13 lines of the commit log omitted.
>
> Produces 10 regressions:
> |
> | regressions.sum:
> | Running libgomp:libgomp.c++/c++.exp ...
> | FAIL: libgomp.c++/target-cdtor-1.C scan-tree-dump-times optimized
> "gimple_call <__cxa_atexit, " 4
> | FAIL: libgomp.c++/target-cdtor-1.C scan-tree-dump-times optimized
> "gimple_call <__cxa_atexit, NULL, _ZN1SD1Ev, \\&sH1, \\&__dso_handle>" 1
> | FAIL: libgomp.c++/target-cdtor-1.C scan-tree-dump-times optimized
> "gimple_call <__cxa_atexit, NULL, _ZN1SD1Ev, \\&sH2, \\&__dso_handle>" 1
> | FAIL: libgomp.c++/target-cdtor-1.C scan-tree-dump-times optimized
> "gimple_call <__cxa_atexit, NULL, _ZN1SD1Ev, \\&sHD1, \\&__dso_handle>" 1
> | ... and 6 more
>
> Used configuration :
> *CI config* tcwg_gcc_check master-arm
> *configure and test flags:* none, autodetected on
> armv8l-unknown-linux-gnueabihf
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1568.
Is it expected that I'm not able to log into the Jira instance, and that
most of the links in there are either:
| Secure Connection Failed
|
| An error occurred during a connection to git-us.linaro.org. Cannot
communicate securely with peer: no common encryption algorithm(s).
..., or:
| Oops!
|
| Not Found
|
| This page may not exist, or you may not have permission to see it.
> Please let us know if you have a fix.
I should have a fix: the attached
"Adjust 'libgomp.c++/target-cdtor-{1,2}.C' for 'targetm.cxx.use_aeabi_atexit'
[PR119853, PR119854]"
ought to address this. I've "mock-tested" this locally; is there a way
for me to run this through the Linaro "pre-commit" CI?
Grüße
Thomas
> 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
> *
> https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3752/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-arm-build/3752/artifact/artifacts/notify/
> The list of [ignored] baseline and flaky failures are in
> *
> https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3752/artifact/artifacts/sumfiles/xfails.xfail
>
> Current build :
> https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3752/artifact/artifacts
> Reference build :
> https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3751/artifact/artifacts
>
> Instruction to reproduce the build :
> https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/aafe942227baf8c2bcd4cac2cb150e49a4b895a9/tcwg_gcc_check/master-arm/reproduction_instructions.txt
>
> Full commit :
> https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=aafe942227baf8c2bcd4cac2cb150e49a4b895a9
_______________________________________________
linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org
To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org
