Hi H.J.,
We enabled guality tests in our CI setup yesterday, and this is part of the fallout. Please ignore this report.
Kind regards,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Feb 14, 2024, at 09:36, 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.
>
> In gcc_check master-arm after:
>
> | gcc patch https://patchwork.sourceware.org/patch/85681
> | Author: H.J. Lu <hjl.tools(a)gmail.com>
> | Date: Tue Feb 13 13:32:44 2024 -0800
> |
> | x86-64: Generate push2/pop2 only if the incoming stack is 16-byte aligned
> |
> | Since push2/pop2 requires 16-byte stack alignment, don't generate them
> | if the incoming stack isn't 16-byte aligned.
> |
> | gcc/
> |
> | ... 12 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 5f2cd521347 libstdc++: C++ item p2442 is version 1 only
>
> FAIL: 3 regressions
>
> regressions.sum:
> === g++ tests ===
>
> Running g++:g++.dg/guality/guality.exp ...
> FAIL: g++.dg/guality/pr55665.C -O2 -flto -fno-use-linker-plugin -flto-partition=none line 23 p == 40
>
> Running g++:g++.target/arm/arm.exp ...
> XPASS: g++.target/arm/bfloat_cpp_typecheck.C (test for bogus messages, line 10)
> XPASS: g++.target/arm/bfloat_cpp_typecheck.C (test for bogus messages, line 11)
>
>
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/6104/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-arm-precommit/6104/artifac…
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/6104/artifac…
>
> The configuration of this build is:
> CI config tcwg_gcc_check master-arm
>
> -----------------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-arm-precommit/6104/artifac…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1714/artifact/ar…
This does not make sense at all. The patch only touches aarch64 code and does NOT even touch arm code so there can't be any regressions with arm.
Thanks,
Andrew Pinski
> -----Original Message-----
> From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
> Sent: Tuesday, February 13, 2024 9:34 PM
> To: Andrew Pinski (QUIC) <quic_apinski(a)quicinc.com>
> Subject: [Linaro-TCWG-CI] gcc patch #85687: FAIL: 3 regressions on arm
>
> 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.
>
> In gcc_check master-arm after:
>
> | gcc patch https://patchwork.sourceware.org/patch/85687
> | Author: Andrew Pinski <quic_apinski(a)quicinc.com>
> | Date: Tue Feb 13 15:22:32 2024 -0800
> |
> | aarch64: Reword error message for mismatch guard size and probing
> interval [PR90155]
> |
> | The error message is not clear what options are being taked about when it
> says the values
> | need to match; plus there is a wrong quotation dealing with the
> diagnostic.
> | So this changes the error message to be exactly talking about the param
> options that
> | are being taked about and now with the options, it needs the quoting.
> |
> | ... 8 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 5f2cd521347 libstdc++: C++ item p2442 is version 1 only
>
> FAIL: 3 regressions
>
> regressions.sum:
> === g++ tests ===
>
> Running g++:g++.dg/guality/guality.exp ...
> FAIL: g++.dg/guality/pr55665.C -O2 -flto -fno-use-linker-plugin -flto-
> partition=none line 23 p == 40
>
> Running g++:g++.target/arm/arm.exp ...
> XPASS: g++.target/arm/bfloat_cpp_typecheck.C (test for bogus messages, line
> 10)
> XPASS: g++.target/arm/bfloat_cpp_typecheck.C (test for bogus messages, line
> 11)
>
>
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-
> precommit/6107/artifact/artifacts/artifacts.precommit/00-sumfiles/
> 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-arm-
> precommit/6107/artifact/artifacts/artifacts.precommit/notify/
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-
> precommit/6107/artifact/artifacts/artifacts.precommit/sumfiles/xfails.xfail
>
> The configuration of this build is:
> CI config tcwg_gcc_check master-arm
>
> -----------------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-arm-
> precommit/6107/artifact/artifacts
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-
> build/1714/artifact/artifacts
Hi Robin,
Please ignore this report. We had a bit of instability in CI testing yesterday.
--
Maxim Kuvyrkov
https://www.linaro.org
> On Feb 14, 2024, at 09:11, 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.
>
> In gcc_check master-arm after:
>
> | gcc patch https://patchwork.sourceware.org/patch/85664
> | Author: Robin Dapp <rdapp.gcc(a)gmail.com>
> | Date: Tue Feb 13 14:42:50 2024 +0100
> |
> | RISC-V: Adjust vec unit-stride load/store costs.
> |
> | Hi,
> |
> | scalar loads provide offset addressing while unit-stride vector
> | instructions cannot. The offset must be loaded into a general-purpose
> | register before it can be used. In order to account for this, this
> | ... 35 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 5f2cd521347 libstdc++: C++ item p2442 is version 1 only
>
> FAIL: 29 regressions
>
> regressions.sum:
> === g++ tests ===
>
> Running g++:g++.dg/dg.exp ...
> FAIL: g++.dg/ext/has_nothrow_copy-5.C -std=c++98 (test for excess errors)
> FAIL: g++.dg/ext/is_base_of_diagnostic.C -std=c++17 (test for errors, line 13)
> FAIL: g++.dg/ext/is_base_of_diagnostic.C -std=c++17 (test for warnings, line 4)
> FAIL: g++.dg/ext/is_base_of_diagnostic.C -std=c++17 (test for excess errors)
> FAIL: g++.dg/ext/packed4.C -std=gnu++17 execution test
> FAIL: g++.dg/ext/vector27.C -std=c++17 (test for excess errors)
> FAIL: g++.dg/ext/vector41.C -std=gnu++17 (test for errors, line 11)
> ... and 27 more entries
>
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/6102/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-arm-precommit/6102/artifac…
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/6102/artifac…
>
> The configuration of this build is:
> CI config tcwg_gcc_check master-arm
>
> -----------------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-arm-precommit/6102/artifac…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1714/artifact/ar…
Hi Jakub,
Please ignore this. I'm going to investigate, but most likely this is due to instability of guality tests.
--
Maxim Kuvyrkov
https://www.linaro.org
> On Feb 14, 2024, at 01:43, 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-1152 , 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-14-8948-g21de3391e4c
> | Author: Jakub Jelinek <jakub(a)redhat.com>
> | Date: Tue Feb 13 10:32:01 2024 +0100
> |
> | hwint: Fix up preprocessor conditions for GCC_PRISZ/fmt_size_t
> |
> | Using unsigned long long int for fmt_size_t and "ll" for GCC_PRISZ
> | as broke the gengtype on i686-linux before the libiberty fix is certainly
> | unexpected. size_t is there unsigned int, so expected fmt_size_t is
> | unsigned int (or some other 32-bit type).
> |
> | ... 8 lines of the commit log omitted.
>
> FAIL: 33 regressions
>
> regressions.sum:
> === gcc tests ===
>
> Running gcc:gcc.dg/guality/guality.exp ...
> FAIL: gcc.dg/guality/example.c -O1 -DPREVENT_OPTIMIZATION execution test
> FAIL: gcc.dg/guality/pr43051-1.c -O1 -DPREVENT_OPTIMIZATION line 34 c == &a[0]
> FAIL: gcc.dg/guality/pr43051-1.c -O1 -DPREVENT_OPTIMIZATION line 39 c == &a[0]
> FAIL: gcc.dg/guality/pr43051-1.c -O2 -DPREVENT_OPTIMIZATION line 34 c == &a[0]
> FAIL: gcc.dg/guality/pr43051-1.c -O2 -DPREVENT_OPTIMIZATION line 39 c == &a[0]
> FAIL: gcc.dg/guality/pr43051-1.c -O2 -flto -fno-use-linker-plugin -flto-partition=none -DPREVENT_OPTIMIZATION line 34 c == &a[0]
> FAIL: gcc.dg/guality/pr43051-1.c -O2 -flto -fno-use-linker-plugin -flto-partition=none -DPREVENT_OPTIMIZATION line 39 c == &a[0]
> ... and 27 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/1595/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/1595/artifac…
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1595/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/1595/artifac…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1592/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/21de3391e4cecfef6ad1b60772cb55616c…
>
> List of configurations that regressed due to this commit :
> * tcwg_gcc_check
> ** master-aarch64
> *** FAIL: 33 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/1595/artifac…
Hi Stephan,
Sorry this clearly looks like a false alarm.
We have enabled maintainer mode at configure time and it seems to have
unexpected consequences.
We've disabled it again, and will investigate what happened.
Sorry for the inconvenience.
Thanks,
Christophe
On Mon, 12 Feb 2024 at 14:31, <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.
>
> In gdb_build master-arm after:
>
> | gdb patch https://patchwork.sourceware.org/patch/85593
> | Author: Rohr, Stephan <stephan.rohr(a)intel.com>
> | Date: Mon Feb 12 04:47:40 2024 -0800
> |
> | gdb: Fix assertion in 'value_primitive_field'
> |
> | GDB asserts that the data location of a value's field with a dynamic
> | data location is resolved when fetching the field's value in
> | 'value_primitive_field'. This assertion was hit because of bogus DWARF
> | generated by the Intel Fortran compiler. While that compiler should fix
> | the DWARF, we prefer GDB to error out here instead, e.g. to allow the
> | ... 1 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | d4a45cd4d1c Automatic date update in version.in
>
> Results changed to
> # reset_artifacts:
> -10
> # true:
> 0
> # build_abe gdb:
> # FAILED
> # First few build errors in logs:
> # 00:02:38 make: *** [Makefile:3117: all-bfd] Error 2
> # 00:01:10 make[2]: *** [Makefile:668: BLD-POTFILES.in] Error 2
> # 00:01:10 make[2]: *** [Makefile:665: SRC-POTFILES.in] Error 2
> # 00:01:10 make[1]: *** [Makefile:1952: info-recursive] Error 1
> # 00:01:10 make: *** [Makefile:3117: all-bfd] Error 2
>
> From
> # reset_artifacts:
> -10
> # true:
> 0
> # build_abe gdb:
> 1
>
> The configuration of this build is:
> CI config tcwg_gdb_build master-arm
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_gdb_build--master-arm-precommit/2108/artifac…
> Reference build : https://ci.linaro.org/job/tcwg_gdb_build--master-arm-build/742/artifact/art…
Hello,
In our company we are using following version of Linaro compilers. I want to know if these versions are officially supported. If these versions are NOT supported, please let me know what is the version we may need to move to take advantage of support
* LINARO-GCC - AARCH64 4.9.4
* LINARO-GCC - AARCH64 6.3.1
* LINARO-GCC 4.9 2016.2
Thanks for your help
Regards/Anand
Series:
- Cleaned QEMU device model API abuses
- Suggest new "wiring" step in QEMU device model
- Add new qemu-system binary to experiment:
- single binary
- dynamic machine
- heterogeneous emulation
Started wiki document to share work:
https://wiki.qemu.org/Dynamic_machine_and_heterogeneous_emulation_roadmap
Progress:
- Refactor ICH9 device to fix another QDev IRQ abuse
Usual reviews
- Peter's MP3R new board