On Sun, 2 Mar 2025 at 02:42, <ci_notify(a)linaro.org> wrote:
>
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In arm-eabi cortex-m7 hard, after:
> | commit gcc-15-7765-g3866ca796d5
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Thu Feb 27 13:27:17 2025 +0000
> |
> | libstdc++: Fix ranges::move and ranges::move_backward to use iter_move [PR105609]
> |
> | The ranges::move and ranges::move_backward algorithms are supposed to
> | use ranges::iter_move(iter) instead of std::move(*iter), which matters
> | for an iterator type with an iter_move overload findable by ADL.
> | ... 16 lines of the commit log omitted.
>
> Produces 8 regressions:
> |
> | regressions.sum:
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL: 25_algorithms/move/constrained.cc -std=gnu++20 (test for excess errors)
> | UNRESOLVED: 25_algorithms/move/constrained.cc -std=gnu++20 compilation failed to produce executable
> | FAIL: 25_algorithms/move/constrained.cc -std=gnu++26 (test for excess errors)
> | UNRESOLVED: 25_algorithms/move/constrained.cc -std=gnu++26 compilation failed to produce executable
> | ... and 4 more
It looks like thumb has some unusual linking requirements that I'm not
familiar with, so undefined functions (which are never actually called
in the test) cause linker errors:
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/arm-eabi/libstdc++-v3/include/bits/iterator_concepts.h:155:(.text._Z6test06N8pr1056091IE+0x6):
undefined reference to `pr105609::iter_move(pr105609::I const&)'
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld:
(_ZN8pr1056099iter_moveERKNS_1IE): Unknown destination type
(ARM/Thumb) in /tmp/ccqKQGzN.o
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/arm-eabi/libstdc++-v3/include/bits/iterator_concepts.h:155:(.text._Z6test06N8pr1056091IE+0x6):
dangerous relocation: unsupported relocation
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/arm-eabi/libstdc++-v3/include/bits/ranges_algobase.h:326:(.text._Z6test06N8pr1056091IE+0xc):
undefined reference to `pr105609::I::operator++()'
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld:
(_ZN8pr1056091IppEv): Unknown destination type (ARM/Thumb) in
/tmp/ccqKQGzN.o
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/arm-eabi/libstdc++-v3/include/bits/ranges_algobase.h:326:(.text._Z6test06N8pr1056091IE+0xc):
dangerous relocation: unsupported relocation
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld:
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/arm-eabi/libstdc++-v3/include/bits/ranges_algobase.h:323:(.text._Z6test06N8pr1056091IE+0x16):
undefined reference to `pr105609::I::operator==(pr105609::I) const'
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld:
(_ZNK8pr1056091IeqES0_): Unknown destination type (ARM/Thumb) in
/tmp/ccqKQGzN.o
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/arm-eabi/libstdc++-v3/include/bits/ranges_algobase.h:323:(.text._Z6test06N8pr1056091IE+0x16):
dangerous relocation: unsupported relocation
I think I should be able to workaround this.
On Thu, 6 Mar 2025 at 23:55, Giuseppe D'Angelo via Gcc-regression
<gcc-regression(a)gcc.gnu.org> wrote:
>
> On 06/03/2025 20:29, ci_notify(a)linaro.org wrote:
> > Dear contributor,
> >
> > Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> This has been fixed on trunk by r15-7863-gd2b022e38a778d.
>
Indeed I can see the test now passes.
Thanks,
Christophe
> Thank you,
> --
> Giuseppe D'Angelo
Hello,
I have recived the email quoted below. I wonder how my patch could have
caused an issue when the only file it touches is related to H8/300
target, not ARM. As far as I can see in the logs you are not building an
H8/300 toolchain.
Best regards,
/J.D.
PS. I am not subscribed so please CC me.
-------- Forwarded Message --------
Subject: [Linaro-TCWG-CI] gcc patch #107213: Failure on aarch64
Date: Fri, 28 Feb 2025 02:06:28 +0000 (UTC)
From: ci_notify(a)linaro.org
Reply-To: linaro-toolchain(a)lists.linaro.org
To: jdx(a)o2.pl
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please
find some details below.
In simplebootstrap_build master-aarch64-bootstrap, after:
| gcc patch https://patchwork.sourceware.org/patch/107213
| Author: Jan Dubiec <jdx(a)o2.pl>
| Date: Thu Feb 27 22:42:20 2025 +0100
| | [PATCH] H8/300: PR target/109189 Silence -Wformat warnings
on Windows
| | This patch fixes annoying -Wformat warnings when gcc is
built
| on Windows/MinGW64. Instead of %ld it uses HOST_WIDE_INT_PRINT_DEC
| macro, just like many other targets do.
| ... 12 lines of the commit log omitted.
| ... applied on top of baseline commit:
| 8371e7f240c gimple-fold: Fix a pasto in
fold_truth_andor_for_ifcombine [PR119030]
Produces Failure:
| Results changed to
| # reset_artifacts:
| -10
| # true:
| 0
| # build_abe bootstrap:
| # FAILED
| | From
| # reset_artifacts:
| -10
| # true:
| 0
| # build_abe bootstrap:
| 1
Used configuration :
*CI config* tcwg_simplebootstrap_build master-aarch64-bootstrap
*configure and test flags:* none, autodetected on
aarch64-unknown-linux-gnu
If you have any questions regarding this report, please ask on
linaro-toolchain(a)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
*
https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
The full lists of regressions and improvements as well as configure and
make commands are in
*
https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
Current build :
https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
Reference build :
https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
Warning: we do not enable maintainer-mode nor automatically update
generated files, which may lead to failures if the patch modifies the
master files.
Excerpts from ci_notify(a)linaro.org's message of Februar 27, 2025 7:38 pm:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In master-aarch64, after:
> | commit gcc-15-7709-gc2ece13931d
> | Author: Iain Buclaw <ibuclaw(a)gdcproject.org>
> | Date: Tue Feb 25 21:01:23 2025 +0100
> |
> | libphobos: Generate test files for phobos testsuite
> |
> | Extracts all public unittests from libphobos/src and emits them as
> | standalone tests in the testsuite using the tests_extractor script.
> |
> | ... 132 lines of the commit log omitted.
>
> Produces 1 regressions 10 improvements:
> |
> | regressions.sum:
> | Running libphobos:libphobos.phobos/phobos.exp ...
> | FAIL: libphobos.phobos/std_math_hardware.d execution test
> |
> | improvements.sum:
> | Running libphobos:libphobos.phobos/shared/phobos-shared.exp ...
> | FAIL: libphobos.phobos/shared/std/format/internal/floats.d execution test
> | ... and 10 more
>
This just a test that was already failing, it's been renamed from
std/math/hardware.d to std_math_hardware.d in the logs.
Iain.
Hi,
Sorry for this spurious notification, it seems we had a "disk full"
issue on the build machine.
You can ignore this error message.
Christophe
On Fri, 28 Feb 2025 at 03:12, <ci_notify(a)linaro.org> wrote:
>
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In simplebootstrap_build master-aarch64-bootstrap, after:
> | gcc patch https://patchwork.sourceware.org/patch/107194
> | Author: Vladimir Makarov <vmakarov(a)redhat.com>
> | Date: Thu Feb 27 13:43:37 2025 -0500
> |
> | [pushed][PR118940][LRA]: Add a test
> |
> | The following patch adds a test for
> |
> | https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118940
> | ... 17 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 8371e7f240c gimple-fold: Fix a pasto in fold_truth_andor_for_ifcombine [PR119030]
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | # FAILED
> |
> | From
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | 1
>
> Used configuration :
> *CI config* tcwg_simplebootstrap_build master-aarch64-bootstrap
> *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)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
> * https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
>
> Current build : https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
> Reference build : https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
Hi,
Sorry for this spurious notification, it seems we had a "disk full"
issue on the build machine.
You can ignore this error message.
Christophe
On Fri, 28 Feb 2025 at 03:06, <ci_notify(a)linaro.org> wrote:
>
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In simplebootstrap_build master-aarch64-bootstrap, after:
> | gcc patch https://patchwork.sourceware.org/patch/107213
> | Author: Jan Dubiec <jdx(a)o2.pl>
> | Date: Thu Feb 27 22:42:20 2025 +0100
> |
> | [PATCH] H8/300: PR target/109189 Silence -Wformat warnings on Windows
> |
> | This patch fixes annoying -Wformat warnings when gcc is built
> | on Windows/MinGW64. Instead of %ld it uses HOST_WIDE_INT_PRINT_DEC
> | macro, just like many other targets do.
> | ... 12 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 8371e7f240c gimple-fold: Fix a pasto in fold_truth_andor_for_ifcombine [PR119030]
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | # FAILED
> |
> | From
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | 1
>
> Used configuration :
> *CI config* tcwg_simplebootstrap_build master-aarch64-bootstrap
> *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)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
> * https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
>
> Current build : https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
> Reference build : https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
On Tue, Feb 25, 2025 at 03:13:10PM +0000, ci_notify(a)linaro.org wrote:
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In gcc_build master-arm, after:
> | gcc patch https://patchwork.sourceware.org/patch/107058
> | Author: Jakub Jelinek <jakub(a)redhat.com>
> | Date: Tue Feb 25 13:31:29 2025 +0100
> |
> | [PATCH] simplify-rtx: Fix up simplify_logical_relational_operation [PR119002]
> |
> | Hi!
> |
> | The following testcase is miscompiled on powerpc64le-linux starting with
> | ... 45 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | af73228fdb2 Fortran: Fix detection of descriptor arrays in coarray [PR107635]
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe gcc:
> | # FAILED
> | # First few build errors in logs:
> | # 00:07:45 /home/tcwg-build/workspace/tcwg_gnu_5/abe/snapshots/gcc.git~master/libstdc++-v3/src/c++17/floating_to_chars.cc:1306:3: internal compiler error: in reverse_condition, at jump.cc:536
> | # 00:07:46 make[5]: *** [Makefile:587: floating_to_chars.lo] Error 1
> | # 00:07:46 make[4]: *** [Makefile:797: all-recursive] Error 1
> | # 00:07:46 make[3]: *** [Makefile:577: all-recursive] Error 1
> | # 00:07:46 make[2]: *** [Makefile:502: all] Error 2
> | # 00:07:46 make[1]: *** [Makefile:12256: all-target-libstdc++-v3] Error 2
> | # 00:07:46 make: *** [Makefile:1062: all] Error 2
Wonder how is that possible, the patch uses REVERSE_CONDITION on GT and
that is handled by both reverse_condition and
reverse_condition_maybe_unordered.
Can I ask for preprocessed source + cc1plus command line + what -march=
etc. options one needs if it is just implied by configure, so that I can
have a look in a cross-compiler?
I really don't have access to 32-bit arm anymore.
Jakub
Hello,
I seem to have begun receiving CI/CD patch notifications from ci_notify(a)linaro.org. I don't understand them, and they might be premature. I don't want to ignore them, though, if they do matter.
I am supplying a 100,000 line patch, roughly, to add a COBOL front-end to gcc. As of now, there is no libgcobol or gcc/cobol directory in the master branch. The supplied patch came most recently in 14 "easy pieces". To be applied successfully, the patches to the Python scripts that create those directories must be applied first.
The URLs at the end of the mail come up 404. I suppose they are ephemeral. I haven't been able to look at a complete log to understand the basis of the report.
The mail says to ask here, so here I be. Please advise. I'm not subscribed to this list.
Thanks,
--jkl
Begin forwarded message:
Date: Wed, 19 Feb 2025 15:10:38 +0000 (UTC)
From: ci_notify(a)linaro.org
To: jklowden(a)schemamania.org
Subject: [Linaro-TCWG-CI] gcc patch #106762: Failure on aarch64
Dear contributor,
Our automatic CI has detected problems related to your patch(es).
Please find some details below.
In gcc_build master-aarch64, after:
| gcc patch https://patchwork.sourceware.org/patch/106762
| Author: James K. Lowden <jklowden(a)schemamania.org>
| Date: Tue Feb 18 18:37:13 2025 -0500
|
| [PATCH] COBOL v3: 3/14 80K bld: config and build machinery
|
| From f89a50238de62b73d9fc44ee7226461650ab119d Tue 18 Feb 2025
04:19:10 PM EST | From: "James K. Lowden" <jklowden(a)symas.com>
| Date: Tue 18 Feb 2025 04:19:10 PM EST
| ... 27 lines of the commit log omitted.
| ... applied on top of baseline commit:
| 427386042f0 LoongArch: Use normal RTL pattern instead of UNSPEC for
{x,}vsr{a,l}ri instructions
Produces Failure:
| Results changed to
| # reset_artifacts:
| -10
| # true:
| 0
| # build_abe gcc:
| # FAILED
| # First few build errors in logs:
| # 00:03:17 make[1]: *** [Makefile:4720: all-gcc] Error 2
| # 00:03:17 make: *** [Makefile:1063: all] Error 2
|
| From
| # reset_artifacts:
| -10
| # true:
| 0
| # build_abe gcc:
| 1
Used configuration :
*CI config* tcwg_gcc_build master-aarch64
*configure and test flags:*
If you have any questions regarding this report, please ask on
linaro-toolchain(a)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_build--master-aarch64-precommit/16368/ar…
The full lists of regressions and improvements as well as configure and
make commands are in
*
https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/16368/ar…
The list of [ignored] baseline and flaky failures are in
*
https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/16368/ar…
Current build :
https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/16368/ar…
Reference build :
https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/3164/artifac…
Warning: we do not enable maintainer-mode nor automatically update
generated files, which may lead to failures if the patch modifies the
master files.