Hi
So, I have a ci fail email, and it seems likely to be a valid complaint -
but the reproduce instructions do not work on my platform (bash is not new enough)
and also do not work on cfarm186 (../jenkins-scripts/jenkins-helpers.sh: line 1762: ts: command not found)
For the record, the patch that is flagged as failing *was* tested on aarch64-linux-gnu (cfarm185)
So, I am trying to figure out if the target is different, or some other configure argument.
.. but I cannot work out the failing configure line at present - nor can I see a place to download the console log from the actual failing GCC build (which would presumably have that configure line).
any help much appreciated.
Iain
Progress:
* QEMU-610 [Remove qemu_get_cpu() from hardware models]
- Big rework of Cortex-A MPCore models. A common class is now used
and various duplicated code from ARM boards got removed.
Possible follow-up with QEMU-601 [Implement TYPE_CORTEXR52_PRIV].
Hello,
# [GNU-981] FEAT_GCS (Guarded Control Stack) support in GDB
- Started working on this feature. Currently adding ptrace and core file
support for the NT_ARM_GCS regset.
# Upstream community
- Implemented fix for ‘--with-auto-load-dir’ and
‘--with-auto-load-safe-path’ configure options on Windows (since Eli
mentioned it earlier this month) and posted “[PATCH] gdb/configure.ac:
Fix auto-load options to work with Windows path separator”.
--
Thiago
Progress:
* UM-2 [QEMU upstream maintainership]
- Took a prototype set of patches to add a second UART to the
virt board which I'd written before going off on holiday; cleaned
them up and got them into shape to send out for review. This is
likely to be QEMU 9.0 material because we want to wait for the
fix to EDK2 to make it handle the second uart more sensibly to
get into an upstream EDK2 before landing the QEMU patches.
- More code review work; sent this week's target-arm pull request
* QEMU-292 [ARMv8.3 FEAT_NV, Nested Virtualization]
- Started on implementation. This seems to be shaping up to be a less
difficult task than our initial estimate suggested; I have
code-complete patches for most of the necessary behaviour
changes already. (Testing may be a more drawn-out effort :-))
-- PMM
Sorry, there was a temporary breakage in our CI scripts, you can
ignore this bogus report.
On Tue, 24 Oct 2023 at 18:25, <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.
>
> In gcc_build master-aarch64 after:
>
> | 31 patches in gcc
> | Patchwork URL: https://patchwork.sourceware.org/patch/78409
> | ecdd9931b4f libstdc++: Optimize std::is_pointer compilation performance
> | 2d53274d549 c++: Implement __is_pointer built-in trait
> | 9414aba0b5b libstdc++: Optimize std::remove_pointer compilation performance
> | b0f04909269 c++: Implement __remove_pointer built-in trait
> | f5ae5fbcc28 libstdc++: Optimize std::is_object compilation performance
> | ... and 26 more patches in gcc
> | ... applied on top of baseline commit:
> | 326a8c047ec testsuite: Fix gcc.target/arm/mve/mve_vadcq_vsbcq_fpscr_overwrite.c
>
> Results changed to
> # reset_artifacts:
> -10
> # true:
> 0
> # build_abe gcc:
> # FAILED
> # First few build errors in logs:
>
> 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-precommit/3362/art…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/1263/artifac…
Sorry, there was a temporary breakage in our CI scripts, you can
ignore this bogus report.
On Tue, 24 Oct 2023 at 18:41, <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.
>
> In gcc_build master-aarch64 after:
>
> | gcc patch https://patchwork.sourceware.org/patch/78468
> | Author: Daniil Frolov <exactlywb(a)ispras.ru>
> | Date: Tue Oct 24 17:11:24 2023 +0300
> |
> | Detecting lifetime-dse issues via Valgrind
> |
> | PR 66487 is asking to provide sanitizer-like detection for C++ object lifetime
> | violations that are worked around with -fno-lifetime-dse in Firefox, LLVM,
> | OpenJade.
> |
> | The discussion in the PR was centered around extending MSan, but MSan was not
> | ... 33 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 326a8c047ec testsuite: Fix gcc.target/arm/mve/mve_vadcq_vsbcq_fpscr_overwrite.c
>
> Results changed to
> # reset_artifacts:
> -10
> # true:
> 0
> # build_abe gcc:
> # FAILED
> # First few build errors in logs:
>
> 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-precommit/3368/art…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/1263/artifac…
Sorry, there was a temporary breakage in our CI scripts, you can
ignore this bogus report.
On Tue, 24 Oct 2023 at 18:40, <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.
>
> In gcc_check master-aarch64 after:
>
> | gcc patch https://patchwork.sourceware.org/patch/78433
> | Author: Ajit Agarwal <aagarwa1(a)linux.ibm.com>
> | Date: Tue Oct 24 15:01:11 2023 +0530
> |
> | ree: Improve ree pass using defined abi interfaces
> |
> | Hello Vineet, Jeff and Bernhard:
> |
> | This version 13 of the patch uses abi interfaces to remove zero and sign extension elimination.
> | Bootstrapped and regtested on powerpc-linux-gnu.
> |
> | ... 40 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 0fc13e8c0e3 Improve factor_out_conditional_operation for conversions and constants
>
> FAIL: 1162 regressions
>
> regressions.sum:
> === g++ tests ===
>
> Running g++:g++.dg/asan/asan.exp ...
> FAIL: c-c++-common/asan/alloca_big_alignment.c -O2 output pattern test
> FAIL: c-c++-common/asan/alloca_big_alignment.c -O2 -flto -fno-use-linker-plugin -flto-partition=none output pattern test
> FAIL: c-c++-common/asan/alloca_detect_custom_size.c -O2 output pattern test
> FAIL: c-c++-common/asan/alloca_detect_custom_size.c -O2 -flto -fno-use-linker-plugin -flto-partition=none output pattern test
> FAIL: c-c++-common/asan/alloca_detect_custom_size.c -O3 -g output pattern test
> FAIL: c-c++-common/asan/alloca_detect_custom_size.c -Os output pattern test
> FAIL: c-c++-common/asan/alloca_overflow_partial.c -O2 output pattern test
> ... and 1191 more entries
>
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/3409/art… .
> The full lists of regressions and progressions are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/3409/art… .
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/3409/art… .
>
> 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-precommit/3409/art…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1093/artifac…
Sorry, there was a temporary breakage in our CI scripts, you can
ignore this bogus report.
On Tue, 24 Oct 2023 at 18:38, <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.
>
> In gcc_build master-aarch64 after:
>
> | gcc patch https://patchwork.sourceware.org/patch/78469
> | Author: Stefan Schulze Frielinghaus <stefansf(a)linux.ibm.com>
> | Date: Tue Oct 24 17:26:55 2023 +0200
> |
> | testsuite: Fix _BitInt in gcc.misc-tests/godump-1.c
> |
> | Currently _BitInt is only supported on x86_64 which means that for other
> | targets all tests fail with e.g.
> |
> | gcc.misc-tests/godump-1.c:237:1: sorry, unimplemented: '_BitInt(32)' is not supported on this target
> | 237 | _BitInt(32) b32_v;
> | ... 12 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 326a8c047ec testsuite: Fix gcc.target/arm/mve/mve_vadcq_vsbcq_fpscr_overwrite.c
>
> Results changed to
> # reset_artifacts:
> -10
> # true:
> 0
> # build_abe gcc:
> # FAILED
> # First few build errors in logs:
>
> 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-precommit/3369/art…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/1263/artifac…
Sorry, there was a temporary breakage in our CI scripts, you can
ignore this bogus report.
On Tue, 24 Oct 2023 at 18:35, <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.
>
> In gcc_build master-aarch64 after:
>
> | gcc patch https://patchwork.sourceware.org/patch/78466
> | Author: Jose E. Marchesi <jose.marchesi(a)oracle.com>
> | Date: Tue Oct 24 14:41:13 2023 +0200
> |
> | gcov-io.h: fix comment regarding length of records
> |
> | The length of gcov records is stored as a signed 32-bit number of bytes.
> | Ok?
> | ... applied on top of baseline commit:
> | 326a8c047ec testsuite: Fix gcc.target/arm/mve/mve_vadcq_vsbcq_fpscr_overwrite.c
>
> Results changed to
> # reset_artifacts:
> -10
> # true:
> 0
> # build_abe gcc:
> # FAILED
> # First few build errors in logs:
>
> 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-precommit/3366/art…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/1263/artifac…