- linaro-toolchain - lists.linaro.org

by Thiago Jung Bauermann

Hello, # TCWG CI - Working on Abe change to always add detected flaky tests to the flaky.xfail file, even if they are already present in the baseline results. Sent a few versions of Gerrit review request already. # [GNU-981] FEAT_GCS (Guarded Control Stack) support in GDB - Prepared environment to develop and test GDB: built Linux kernel from Mark Brown's arm64-gcs branch and booted it in an Arm FVP supporting the feature. Successfully ran native GDB in it to debug a program (though I didn't use any GCS feature for this test). -- Thiago

2 years

1
0
0 0

[Linaro-TCWG-CI] v8.1.0-2321-gee95fae075: FAIL: 25 regressions on aarch64

by ci_notify＠linaro.org

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 master-aarch64 after: | commit v8.1.0-2321-gee95fae075 | Author: Richard Henderson <richard.henderson(a)linaro.org> | Date: Tue Jun 15 10:21:37 2021 -0700 | | linux-user/aarch64: Add vdso | | Reviewed-by: Philippe Mathieu-Daudé <philmd(a)linaro.org> | Signed-off-by: Richard Henderson <richard.henderson(a)linaro.org> FAIL: 25 regressions regressions.sum: === g++ tests === Running g++:g++.dg/dg.exp ... FAIL: g++.dg/ext/cleanup-10.C -std=gnu++14 execution test FAIL: g++.dg/ext/cleanup-10.C -std=gnu++17 execution test FAIL: g++.dg/ext/cleanup-10.C -std=gnu++20 execution test FAIL: g++.dg/ext/cleanup-10.C -std=gnu++98 execution test FAIL: g++.dg/ext/cleanup-11.C -std=gnu++14 execution test FAIL: g++.dg/ext/cleanup-11.C -std=gnu++17 execution test FAIL: g++.dg/ext/cleanup-11.C -std=gnu++20 execution test ... and 26 more entries You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/10… . The full lists of regressions and progressions are in - https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/10… . The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/10… . The configuration of this build is: CI config tcwg_gnu_cross_check_gcc/master-aarch64 -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/10… Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/10… Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/qemu/s… Full commit : https://gitlab.com/qemu-project/qemu/commit/ee95fae075c68cf1ae0fc1ffb00acca… Latest bug report status : https://linaro.atlassian.net/browse/GNU-991 List of configurations that regressed due to this commit : * tcwg_gnu_cross_check_gcc ** master-aarch64 *** FAIL: 25 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/qemu/s… *** https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/10…

2 years

1
0
0 0

[ACTIVITY] report week ending 3 Nov

by Peter Maydell

Progress: * UM-2 [QEMU upstream maintainership] - investigated and fixed a few bugs in FEAT_MOPS; patches sent - reviewed patch fixing bug in virt ACPI table for debug UART; added the necessary update-the-reference-files patches for 'make check'. Debugged why it broke console output on Linux -- turns out that Linux has a bug where acpi_parse_spcr() and pl011_console_match() disagree about how the former should tell the latter "use 16-bit MMIO"... We'll work around this by having the ACPI table report 32-bit MMIO; Raspberry Pi 4 firmware on real hardware already does that, so it should be a safe choice. - sent patch fixing failure to report BTI GP state correctly when doing a two-stage page table walk - code review and assembly of a pull request (softfreeze next week...) * QEMU-292 [ARMv8.3 FEAT_NV, Nested Virtualization] - got to a (hopefully) code-complete but untested state; will probably put this to one side for the moment leading up to softfreeze - tracked down the kernel and kvmtool patchsets that will be needed to test this (they are not upstream yet) thanks -- PMM

2 years

1
0
0 0

[Linaro-TCWG-CI] gcc-14-5059-gd880e093d92: Failure on aarch64

by ci_notify＠linaro.org

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 CI config tcwg_kernel/gnu-master-aarch64-mainline-allyesconfig after: | commit gcc-14-5059-gd880e093d92 | Author: Martin Uecker <uecker(a)tugraz.at> | Date: Thu Jul 27 13:36:05 2023 +0200 | | c: Add Walloc-size to warn about insufficient size in allocations [PR71219] | | Add option Walloc-size that warns about allocations that have | insufficient storage for the target type of the pointer the | storage is assigned to. Added to Wextra. | | PR c/71219 | ... 14 lines of the commit log omitted. Results changed to # reset_artifacts: -10 # build_abe binutils: -9 # build_abe stage1: -5 # build_abe qemu: -2 # linux_n_obj: 22669 # First few build errors in logs: # 00:33:49 drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v8.c:241:15: error: allocation of insufficient size ‘4’ for type ‘uint32_t[2]’ {aka ‘unsigned int[2]’} with size ‘8’ [-Werror=alloc-size] # 00:33:49 drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v8.c:327:15: error: allocation of insufficient size ‘4’ for type ‘uint32_t[2]’ {aka ‘unsigned int[2]’} with size ‘8’ [-Werror=alloc-size] # 00:33:49 drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v9.c:368:15: error: allocation of insufficient size ‘4’ for type ‘uint32_t[2]’ {aka ‘unsigned int[2]’} with size ‘8’ [-Werror=alloc-size] # 00:33:49 drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v9.c:465:15: error: allocation of insufficient size ‘4’ for type ‘uint32_t[2]’ {aka ‘unsigned int[2]’} with size ‘8’ [-Werror=alloc-size] # 00:33:50 make[6]: *** [scripts/Makefile.build:243: drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v8.o] Error 1 # 00:33:52 drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_arcturus.c:203:15: error: allocation of insufficient size ‘4’ for type ‘uint32_t[2]’ {aka ‘unsigned int[2]’} with size ‘8’ [-Werror=alloc-size] # 00:33:53 make[6]: *** [scripts/Makefile.build:243: drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_arcturus.o] Error 1 # 00:33:53 make[6]: *** [scripts/Makefile.build:243: drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v9.o] Error 1 # 00:33:56 drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gc_9_4_3.c:144:15: error: allocation of insufficient size ‘4’ for type ‘uint32_t[2]’ {aka ‘unsigned int[2]’} with size ‘8’ [-Werror=alloc-size] # 00:33:57 make[6]: *** [scripts/Makefile.build:243: drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gc_9_4_3.o] Error 1 From # reset_artifacts: -10 # build_abe binutils: -9 # build_abe stage1: -5 # build_abe qemu: -2 # linux_n_obj: 22751 # linux build successful: all The configuration of this build is: CI config tcwg_kernel/gnu-master-aarch64-mainline-allyesconfig -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-mainline-allyesco… Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-mainline-allyesco… 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/d880e093d92084f55b10626610ef059fd9… Latest bug report status : https://linaro.atlassian.net/browse/GNU-990 List of configurations that regressed due to this commit : * tcwg_kernel ** gnu-master-aarch64-mainline-allyesconfig *** Failure *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… *** https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-mainline-allyesco…

2 years

1
0
0 0

Re: [Linaro-TCWG-CI] v6.6-rc1-17-g1c6fdbd8f246: Failure on arm

by Nick Desaulniers

On Wed, Nov 1, 2023 at 7:42 AM <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 CI config tcwg_kernel/llvm-master-arm-mainline-allmodconfig after: ok, so ARCH=arm allmodconfig on mainline... > > | commit v6.6-rc1-17-g1c6fdbd8f246 > | Author: Kent Overstreet <kent.overstreet(a)gmail.com> > | Date: Thu Mar 16 22:18:50 2017 -0800 > | > | bcachefs: Initial commit > | > | Initially forked from drivers/md/bcache, bcachefs is a new copy-on-write > | filesystem with every feature you could possibly want. > | > | Website: https://bcachefs.org > | > | ... 1 lines of the commit log omitted. > > Results changed to > # reset_artifacts: > -10 > # build_abe binutils: > -9 > # build_kernel_llvm: > -5 > # build_abe qemu: > -2 > # linux_n_obj: > 23730 > # First few build errors in logs: > > # 00:23:16 fs/bcachefs/btree_cache.h:45:43: error: array index 0 is past the end of the array (that has type 'const __u64[0]' (aka 'const unsigned long long[0]')) [-Werror,-Warray-bounds] > # 00:23:17 fs/bcachefs/alloc.c:332:9: error: call to undeclared function 'COUNT_ARGS'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration] ^ $ file fs/bcachefs/alloc.c fs/bcachefs/alloc.c: cannot open `fs/bcachefs/alloc.c' (No such file or directory) > # 00:23:17 make[4]: *** [scripts/Makefile.build:243: fs/bcachefs/alloc.o] Error 1 > # 00:23:29 fs/bcachefs/btree_cache.h:45:43: error: array index 0 is past the end of the array (that has type 'const __u64[0]' (aka 'const unsigned long long[0]')) [-Werror,-Warray-bounds] > # 00:23:30 make[4]: *** [scripts/Makefile.build:243: fs/bcachefs/bset.o] Error 1 ^ $ make LLVM=1 ARCH=arm allmodconfig fs/bcachefs/bset.o CC [M] fs/bcachefs/bset.o $ > # 00:23:33 fs/bcachefs/btree_cache.h:45:43: error: array index 0 is past the end of the array (that has type 'const __u64[0]' (aka 'const unsigned long long[0]')) [-Werror,-Warray-bounds] > # 00:23:33 fs/bcachefs/btree_cache.h:45:43: error: array index 0 is past the end of the array (that has type 'const __u64[0]' (aka 'const unsigned long long[0]')) [-Werror,-Warray-bounds] > # 00:23:33 fs/bcachefs/btree_cache.c:67:9: error: array index 0 is past the end of the array (that has type 'const __u64[0]' (aka 'const unsigned long long[0]')) [-Werror,-Warray-bounds] > # 00:23:33 fs/bcachefs/btree_cache.c:120:2: error: array index 0 is past the end of the array (that has type '__u64[0]' (aka 'unsigned long long[0]')) [-Werror,-Warray-bounds] > # 00:23:33 fs/bcachefs/btree_cache.c:201:6: error: array index 0 is past the end of the array (that has type 'const __u64[0]' (aka 'const unsigned long long[0]')) [-Werror,-Warray-bounds] $ make LLVM=1 ARCH=arm allmodconfig fs/bcachefs/btree_cache.o CC [M] fs/bcachefs/btree_cache.o $ ... what's up with this report? > > From > # reset_artifacts: > -10 > # build_abe binutils: > -9 > # build_kernel_llvm: > -5 > # build_abe qemu: > -2 > # linux_n_obj: > 32815 > # linux build successful: > all > # linux boot successful: > boot > > The configuration of this build is: > CI config tcwg_kernel/llvm-master-arm-mainline-allmodconfig > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-arm-mainline-allmodconfi… > Reference build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-arm-mainline-allmodconfi… > > Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/linux/… > > Full commit : https://git.linaro.org/kernel-org/linux.git/commit/?id=1c6fdbd8f2465ddfb73a… > > Latest bug report status : https://linaro.atlassian.net/browse/LLVM-1015 > > List of configurations that regressed due to this commit : > * tcwg_kernel > ** llvm-master-arm-mainline-allmodconfig > *** Failure > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/linux/… > *** https://ci.linaro.org/job/tcwg_kernel--llvm-master-arm-mainline-allmodconfi… -- Thanks, ~Nick Desaulniers

2 years

3
4
0 0

Re: [Linaro-TCWG-CI] gcc-14-5032-ge3da1d7bb28: Failure on arm

by Maxim Kuvyrkov

Hi Richard, This patch also breaks profiled_bootstrap on aarch64-linux-gnu, which may be easier to reproduce, see [1]. [1] https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… Regards, -- Maxim Kuvyrkov https://www.linaro.org > On Nov 1, 2023, at 15:46, 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 bootstrap_build master-arm-bootstrap_profiled_lto_lean after: > > | commit gcc-14-5032-ge3da1d7bb28 > | Author: Richard Biener <rguenther(a)suse.de> > | Date: Tue Oct 31 10:13:13 2023 +0100 > | > | tree-optimization/112305 - SCEV cprop and conditional undefined overflow > | > | The following adjusts final value replacement to also rewrite the > | replacement to defined overflow behavior if there's conditionally > | evaluated stmts (with possibly undefined overflow), not only when > | we "folded casts". The patch hooks into expression_expensive for > | this. > | ... 10 lines of the commit log omitted. > > Results changed to > # reset_artifacts: > -10 > # true: > 0 > # build_abe bootstrap_profiled_lto_lean: > # FAILED > # First few build errors in logs: > # 01:55:54 /home/tcwg-buildslave/workspace/tcwg_gnu_4/abe/snapshots/gcc.git~master/libiberty/regex.c:5549: internal compiler error: Segmentation fault > # 01:55:54 make[4]: *** [/tmp/ccj2LJs3.mk:380: /tmp/ccIWXeRO.ltrans126.ltrans.o] Error 1 > # 01:57:45 lto-wrapper: fatal error: make returned 2 exit status > # 01:57:46 /usr/bin/ld: error: lto-wrapper failed > # 01:57:46 collect2: error: ld returned 1 exit status > # 01:57:46 make[3]: *** [/home/tcwg-buildslave/workspace/tcwg_gnu_4/abe/snapshots/gcc.git~master/gcc/cp/Make-lang.in:145: cc1plus] Error 1 > # 01:57:46 make[2]: *** [Makefile:5260: all-stagefeedback-gcc] Error 2 > # 01:57:46 make[1]: *** [Makefile:26669: stagefeedback-bubble] Error 2 > # 01:57:46 make: *** [Makefile:26689: profiledbootstrap] Error 2 > # 00:06:15 make[3]: [Makefile:1822: armv8l-unknown-linux-gnueabihf/bits/largefile-config.h] Error 1 (ignored) > # 00:47:56 make[3]: [Makefile:1822: armv8l-unknown-linux-gnueabihf/bits/largefile-config.h] Error 1 (ignored) > # 01:09:35 make[3]: [Makefile:1822: armv8l-unknown-linux-gnueabihf/bits/largefile-config.h] Error 1 (ignored) > # 01:14:05 /home/tcwg-buildslave/workspace/tcwg_gnu_4/abe/snapshots/gcc.git~master/libiberty/regex.c:5549:1: internal compiler error: Segmentation fault > # 01:14:05 /home/tcwg-buildslave/workspace/tcwg_gnu_4/abe/snapshots/gcc.git~master/libiberty/regex.c:5549:1: internal compiler error: Segmentation fault > # 01:14:05 /home/tcwg-buildslave/workspace/tcwg_gnu_4/abe/snapshots/gcc.git~master/libiberty/regex.c:5549:1: internal compiler error: Segmentation fault > # 01:14:05 make[4]: *** [/tmp/ccCI7mJj.mk:20: /tmp/ccH1y1BV.ltrans6.ltrans.o] Error 1 > # 01:14:05 make[4]: *** [/tmp/cciXJOsB.mk:20: /tmp/ccaXf4f5.ltrans6.ltrans.o] Error 1 > # 01:14:05 make[4]: *** [/tmp/cccYndDm.mk:20: /tmp/cc6tlPuq.ltrans6.ltrans.o] Error 1 > # 01:14:07 lto-wrapper: fatal error: make returned 2 exit status > > From > # reset_artifacts: > -10 > # true: > 0 > # build_abe bootstrap_profiled_lto_lean: > 1 > > The configuration of this build is: > CI config tcwg_bootstrap_build/master-arm-bootstrap_profiled_lto_lean > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_bootstrap_build--master-arm-bootstrap_profil… > Reference build : https://ci.linaro.org/job/tcwg_bootstrap_build--master-arm-bootstrap_profil… > > 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/e3da1d7bb288c8c864f0284bc4bc5877b4… > > Latest bug report status : https://linaro.atlassian.net/browse/GNU-989 > > List of configurations that regressed due to this commit : > * tcwg_bootstrap_build > ** master-arm-bootstrap_profiled_lto_lean > *** Failure > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_bootstrap_build--master-arm-bootstrap_profil…

2 years

1
0
0 0

[ACTIVITY] Report for week #43

by Philippe Mathieu-Daudé

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].

2 years

1
0
0 0

[ACTIVITY] Report for week #43

by Thiago Jung Bauermann

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

2 years

1
0
0 0

[weekly][linaro] report week ending 27 Oct

by Peter Maydell

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

2 years

1
0
0 0

Re: [Linaro-TCWG-CI] 31 patches in gcc: Failure on aarch64

by Christophe Lyon

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…

2 years

2
1
0 0

[Linaro-TCWG-CI] glibc-2.38.9000-193-gb121fdc552: FAIL: 2 regressions on arm

by ci_notify＠linaro.org

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 glibc_check master-arm after: | commit glibc-2.38.9000-193-gb121fdc552 | Author: Arjun Shankar <arjun(a)redhat.com> | Date: Mon Oct 2 14:55:15 2023 +0200 | | Remove 'grp' and merge into 'nss' and 'posix' | | The majority of grp routines are entry points for nss functionality. | This commit removes the 'grp' subdirectory and moves all nss-relevant | functionality and all tests to 'nss', and the 'setgroups' stub into | 'posix' (alongside the 'getgroups' stub). References to grp/ are | accordingly changed. In addition, compat-initgroups.c, a fallback | ... 6 lines of the commit log omitted. FAIL: 2 regressions regressions.sum: === glibc tests === Running glibc:nss ... FAIL: nss/tst-initgroups1 FAIL: nss/tst-initgroups2 === Results Summary === You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/678/artifact/a… . The full lists of regressions and progressions are in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/678/artifact/a… . The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/678/artifact/a… . The configuration of this build is: CI config tcwg_glibc_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_glibc_check--master-arm-build/678/artifact/a… Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/676/artifact/a… Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=b121fdc552f392cd86b2… Latest bug report status : https://linaro.atlassian.net/browse/GNU-979 List of configurations that regressed due to this commit : * tcwg_glibc_check ** master-arm *** FAIL: 2 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… *** https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/678/

2 years

1
0
0 0

Re: [Linaro-TCWG-CI] gcc patch #78468: Failure on aarch64

by Christophe Lyon

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…

2 years

1
0
0 0

Re: [Linaro-TCWG-CI] gcc patch #78433: FAIL: 1162 regressions on aarch64

by Christophe Lyon

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…

2 years

1
0
0 0

Re: [Linaro-TCWG-CI] gcc patch #78469: Failure on aarch64

by Christophe Lyon

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…

2 years

1
0
0 0

Re: [Linaro-TCWG-CI] gcc patch #78466: Failure on aarch64

by Christophe Lyon

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…

2 years

1
0
0 0

[Linaro-TCWG-CI] v8.1.0-1799-g38ee0a7dfb: FAIL: 2 regressions on aarch64

by ci_notify＠linaro.org

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 master-aarch64 after: | commit v8.1.0-1799-g38ee0a7dfb | Author: Richard Henderson <richard.henderson(a)linaro.org> | Date: Sat Sep 30 12:05:11 2023 -0700 | | linux-user: Remap guest SIGABRT | | Distinguish host SIGABRT from guest SIGABRT by mapping | the guest signal onto one of the host RT signals. | | This prevents a cycle by which a host assertion failure | is caught and handled by host_signal_handler, queued for | ... 6 lines of the commit log omitted. FAIL: 2 regressions regressions.sum: === libstdc++ tests === Running libstdc++:libstdc++-dg/conformance.exp ... FAIL: 30_threads/condition_variable/members/103382.cc -std=gnu++17 execution test FAIL: 30_threads/thread/native_handle/cancel.cc -std=gnu++17 execution test === Results Summary === You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/10… . The full lists of regressions and progressions are in - https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/10… . The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/10… . The configuration of this build is: CI config tcwg_gnu_cross_check_gcc/master-aarch64 -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/10… Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/10… Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/qemu/s… Full commit : https://gitlab.com/qemu-project/qemu/commit/38ee0a7dfb4b15407678df26448e4a1… Latest bug report status : https://linaro.atlassian.net/browse/GNU-974 List of configurations that regressed due to this commit : * tcwg_gnu_cross_check_gcc ** master-aarch64 *** FAIL: 2 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/qemu/s… *** https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/10…

2 years

1
0
0 0

[ACTIVITY] Report for week #42

by Thiago Jung Bauermann

Hello, # [GNU-767] Support changing SVE vector length in remote debugging - Implemented support for expressing variable-sized vector registers in the XML target description. Now making some changes in GDB's handling of the expedited registers in the remote protocol and adjusting of the g/G packet size. # TCWG CI - Analysed and closed LLVM code size regression GNU-963. -- Thiago

2 years

1
0
0 0

Re: [PATCH v2] ARM: Block predication on atomics [PR111235]

by Ramana Radhakrishnan

+ linaro-toolchain as I don't understand the CI issues on patchwork. On Wed, Sep 27, 2023 at 8:40 PM Wilco Dijkstra <Wilco.Dijkstra(a)arm.com> wrote: > > Hi Ramana, > > > Hope this helps. > > Yes definitely! > > >> Passes regress/bootstrap, OK for commit? > > > > Target ? armhf ? --with-arch , -with-fpu , -with-float parameters ? > > Please be specific. > > I used --target=arm-none-linux-gnueabihf --host=arm-none-linux-gnueabihf > --build=arm-none-linux-gnueabihf --with-float=hard. However it seems that the > default armhf settings are incorrect. I shouldn't need the --with-float=hard since > that is obviously implied by armhf, and they should also imply armv7-a with vfpv3 > according to documentation. It seems to get confused and skip some tests. I tried > using --with-fpu=auto, but that doesn't work at all, so in the end I forced it like: > --with-arch=armv8-a --with-fpu=neon-fp-armv8. With this it runs a few more tests. Yeah that's a wart that I don't like. armhf just implies the hard float ABI and came into being to help distinguish from the Base PCS for some of the distros at the time (2010s). However we didn't want to set a baseline arch at that time given the imminent arrival of v8-a and thus the specification of --with-arch , --with-fpu and --with-float became second nature to many of us working on it at that time. I can see how it can be confusing. With the advent of fpu=auto , I thought this could be made better but that is a matter for another patch and another discussion. However until then do remember to baseline to --with-arch , --with-fpu and --with-float . Unfortunate but needed. If there is a bug with --with-fpu=auto , good to articulate it as I understand that to be the state of the art. Thank you for working through it. > > > Since these patterns touch armv8m.baseline can you find all the > > testcases in the testsuite and ensure no change in code for > > armv8m.baseline as that's unpredicated already and this patch brings > > this in line with the same ? Does the testsuite already cover these > > arch variants and are you satisfied that the tests in the testsuite > > can catch / don't make any additional code changes to the other > > architectures affected by this ? > > There are various v8-m(.base/.main) tests and they all pass. The generated > code is generally unchanged if there was no conditional execution. I made > the new UNSPEC_LDR/STR patterns support offsets so there is no difference > in generated code for relaxed loads/stores (since they used to use a plain > load/store which has an immediate offset). > > >> * onfig/arm/sync.md (arm_atomic_load<mode>): Add new pattern. > > > > Nit: s/onfig/config > > Fixed. Thanks > > >> (atomic_load<mode>): Always expand atomic loads explicitly. > >> (atomic_store<mode>): Always expand atomic stores explicitly. > > > > Nit: Change message to : > > Switch patterns to define_expand. > > Fixed. Thanks. > > > Largely looks ok though I cannot work out tonight if we need more v8-a > > or v8m-baseline specific tests for scan-assembler patterns. > > > > Clearly our testsuite doesn't catch it , so perhaps the OP could help > > validate this patch with their formal models to see if this fixes > > these set of issues and creates no new regressions ? Is that feasible > > to do ? > > Disabling conditional execution avoids the issue. It's trivial to verify that > atomics can no longer be conditionally executed (no "%?"). When this is > committed, we can run the random testing again to confirm the issue > is no longer present. Ok, thanks for promising to do so - I trust you to get it done. Please try out various combinations of -march v7ve, v7-a , v8-a with the tool as each of them have slightly different rules. For instance v7ve allows LDREXD and STREXD to be single copy atomic for 64 bit loads whereas v7-a did not . > > > -(define_insn "atomic_load<mode>" > > - [(set (match_operand:QHSI 0 "register_operand" "=r,r,l") > > +(define_insn "arm_atomic_load<mode>" > > + [(set (match_operand:QHSI 0 "register_operand" "=r,l") > > (unspec_volatile:QHSI > > - [(match_operand:QHSI 1 "arm_sync_memory_operand" "Q,Q,Q") > > - (match_operand:SI 2 "const_int_operand" "n,Pf,n")] ;; model > > + [(match_operand:QHSI 1 "memory_operand" "m,m")] > > > > Remind me again why is it safe to go from the Q constraint to the m > > constraint here and everywhere else you've done this ? > > That's because the relaxed loads/stores use LDR/STR wrapped in an > UNSPEC. To avoid regressions we have to use 'm' so that an immediate > offset can be merged into the memory access. This is because the instructions used here are ldr and str and the use of the 'm' constraint is considered safe. > > >> - VUNSPEC_LDA ; Represent a store-register-acquire. > >> + VUNSPEC_LDR ; Represent a load-register-relaxed. > >> + VUNSPEC_LDA ; Represent a load-register-acquire. > > > > Nit: LDA before LDR ? Though I suspect this list can be alphabetically > > ordered at another point of time. > > Swapped. Thanks > > > There are new tests added for v7-a , what happens with the output for > > v8-a and the changes for ldacq and other such instructions ? > > v7-a and v8-a generate the same instructions for relaxed load/store. > The acquire/release versions are identical except they are no longer > predicated. Basically the new patterns are not only significantly simpler, > they are now the same between the many ARM/Thumb-2/v7-a/v8-m/v8-a > combinations, so test coverage is much higher now. This is how these > patterns should have been designed all along. > > v2 follows below. > > Cheers, > Wilco > > > [PATCH v2] ARM: Block predication on atomics [PR111235] > > The v7 memory ordering model allows reordering of conditional atomic > instructions. To avoid this, make all atomic patterns unconditional. > Expand atomic loads and stores for all architectures so the memory access > can be wrapped into an UNSPEC. > > gcc/ChangeLog/ > PR target/111235 > * config/arm/constraints.md: Remove Pf constraint. > * config/arm/sync.md (arm_atomic_load<mode>): Add new pattern. > (arm_atomic_load_acquire<mode>): Likewise. > (arm_atomic_store<mode>): Likewise. > (arm_atomic_store_release<mode>): Likewise. > (atomic_load<mode>): Switch patterns to define_expand. > (atomic_store<mode>): Likewise. > (arm_atomic_loaddi2_ldrd): Remove predication. > (arm_load_exclusive<mode>): Likewise. > (arm_load_acquire_exclusive<mode>): Likewise. > (arm_load_exclusivesi): Likewise. > (arm_load_acquire_exclusivesi: Likewise. > (arm_load_exclusivedi): Likewise. > (arm_load_acquire_exclusivedi): Likewise. > (arm_store_exclusive<mode>): Likewise. > (arm_store_release_exclusivedi): Likewise. > (arm_store_release_exclusive<mode>): Likewise. > * gcc/config/arm/unspecs.md: Add VUNSPEC_LDR and VUNSPEC_STR. > > gcc/testsuite/ChangeLog/ > PR target/111235 > * gcc.dg/rtl/arm/stl-cond.c: Remove test. > * gcc.target/arm/atomic_loaddi_7.c: Fix dmb count. > * gcc.target/arm/atomic_loaddi_8.c: Likewise. > * gcc.target/arm/pr111235.c: Add new test. > > --- > > diff --git a/gcc/config/arm/constraints.md b/gcc/config/arm/constraints.md > index 05a4ebbdd67601d7b92aa44a619d17634cc69f17..d7c4a1b0cd785f276862048005e6cfa57cdcb20d 100644 > --- a/gcc/config/arm/constraints.md > +++ b/gcc/config/arm/constraints.md > @@ -36,7 +36,7 @@ > ;; in Thumb-1 state: Pa, Pb, Pc, Pd, Pe > ;; in Thumb-2 state: Ha, Pj, PJ, Ps, Pt, Pu, Pv, Pw, Px, Py, Pz, Rd, Rf, Rb, Ra, > ;; Rg, Ri > -;; in all states: Pf, Pg > +;; in all states: Pg > > ;; The following memory constraints have been used: > ;; in ARM/Thumb-2 state: Uh, Ut, Uv, Uy, Un, Um, Us, Up, Uf, Ux, Ul > @@ -239,13 +239,6 @@ (define_constraint "Pe" > (and (match_code "const_int") > (match_test "TARGET_THUMB1 && ival >= 256 && ival <= 510"))) > > -(define_constraint "Pf" > - "Memory models except relaxed, consume or release ones." > - (and (match_code "const_int") > - (match_test "!is_mm_relaxed (memmodel_from_int (ival)) > - && !is_mm_consume (memmodel_from_int (ival)) > - && !is_mm_release (memmodel_from_int (ival))"))) > - > (define_constraint "Pg" > "@internal In Thumb-2 state a constant in range 1 to 32" > (and (match_code "const_int") > diff --git a/gcc/config/arm/sync.md b/gcc/config/arm/sync.md > index 7626bf3c443285dc63b4c4367b11a879a99c93c6..2210810f67f37ce043b8fdc73b4f21b54c5b1912 100644 > --- a/gcc/config/arm/sync.md > +++ b/gcc/config/arm/sync.md > @@ -62,68 +62,110 @@ (define_insn "*memory_barrier" > (set_attr "conds" "unconditional") > (set_attr "predicable" "no")]) > > -(define_insn "atomic_load<mode>" > - [(set (match_operand:QHSI 0 "register_operand" "=r,r,l") > +(define_insn "arm_atomic_load<mode>" > + [(set (match_operand:QHSI 0 "register_operand" "=r,l") > (unspec_volatile:QHSI > - [(match_operand:QHSI 1 "arm_sync_memory_operand" "Q,Q,Q") > - (match_operand:SI 2 "const_int_operand" "n,Pf,n")] ;; model > + [(match_operand:QHSI 1 "memory_operand" "m,m")] > + VUNSPEC_LDR))] > + "" > + "ldr<sync_sfx>\t%0, %1" > + [(set_attr "arch" "32,any")]) > + > +(define_insn "arm_atomic_load_acquire<mode>" > + [(set (match_operand:QHSI 0 "register_operand" "=r") > + (unspec_volatile:QHSI > + [(match_operand:QHSI 1 "arm_sync_memory_operand" "Q")] > VUNSPEC_LDA))] > "TARGET_HAVE_LDACQ" > - { > - if (aarch_mm_needs_acquire (operands[2])) > - { > - if (TARGET_THUMB1) > - return "lda<sync_sfx>\t%0, %1"; > - else > - return "lda<sync_sfx>%?\t%0, %1"; > - } > - else > - { > - if (TARGET_THUMB1) > - return "ldr<sync_sfx>\t%0, %1"; > - else > - return "ldr<sync_sfx>%?\t%0, %1"; > - } > - } > - [(set_attr "arch" "32,v8mb,any") > - (set_attr "predicable" "yes")]) > + "lda<sync_sfx>\t%0, %C1" > +) > > -(define_insn "atomic_store<mode>" > - [(set (match_operand:QHSI 0 "memory_operand" "=Q,Q,Q") > +(define_insn "arm_atomic_store<mode>" > + [(set (match_operand:QHSI 0 "memory_operand" "=m,m") > + (unspec_volatile:QHSI > + [(match_operand:QHSI 1 "register_operand" "r,l")] > + VUNSPEC_STR))] > + "" > + "str<sync_sfx>\t%1, %0"; > + [(set_attr "arch" "32,any")]) > + > +(define_insn "arm_atomic_store_release<mode>" > + [(set (match_operand:QHSI 0 "arm_sync_memory_operand" "=Q") > (unspec_volatile:QHSI > - [(match_operand:QHSI 1 "general_operand" "r,r,l") > - (match_operand:SI 2 "const_int_operand" "n,Pf,n")] ;; model > + [(match_operand:QHSI 1 "register_operand" "r")] > VUNSPEC_STL))] > "TARGET_HAVE_LDACQ" > - { > - if (aarch_mm_needs_release (operands[2])) > - { > - if (TARGET_THUMB1) > - return "stl<sync_sfx>\t%1, %0"; > - else > - return "stl<sync_sfx>%?\t%1, %0"; > - } > - else > - { > - if (TARGET_THUMB1) > - return "str<sync_sfx>\t%1, %0"; > - else > - return "str<sync_sfx>%?\t%1, %0"; > - } > - } > - [(set_attr "arch" "32,v8mb,any") > - (set_attr "predicable" "yes")]) > + "stl<sync_sfx>\t%1, %C0") > + > + > +(define_expand "atomic_load<mode>" > + [(match_operand:QHSI 0 "register_operand") ;; val out > + (match_operand:QHSI 1 "arm_sync_memory_operand") ;; memory > + (match_operand:SI 2 "const_int_operand")] ;; model > + "" > +{ > + memmodel model = memmodel_from_int (INTVAL (operands[2])); > + > + if (TARGET_HAVE_LDACQ && !is_mm_relaxed (model)) > + { > + emit_insn (gen_arm_atomic_load_acquire<mode> (operands[0], operands[1])); > + DONE; > + } > + > + /* The seq_cst model needs a barrier before the load to block reordering with > + earlier accesses. */ > + if (is_mm_seq_cst (model)) > + expand_mem_thread_fence (model); > + > + emit_insn (gen_arm_atomic_load<mode> (operands[0], operands[1])); > + > + /* All non-relaxed models need a barrier after the load when load-acquire > + instructions are not available. */ > + if (!is_mm_relaxed (model)) > + expand_mem_thread_fence (model); > + > + DONE; > +}) > + > +(define_expand "atomic_store<mode>" > + [(match_operand:QHSI 0 "arm_sync_memory_operand") ;; memory > + (match_operand:QHSI 1 "register_operand") ;; store value > + (match_operand:SI 2 "const_int_operand")] ;; model > + "" > +{ > + memmodel model = memmodel_from_int (INTVAL (operands[2])); > + > + if (TARGET_HAVE_LDACQ && !is_mm_relaxed (model)) > + { > + emit_insn (gen_arm_atomic_store_release<mode> (operands[0], operands[1])); > + DONE; > + } > + > + /* All non-relaxed models need a barrier after the load when load-acquire > + instructions are not available. */ > + if (!is_mm_relaxed (model)) > + expand_mem_thread_fence (model); > + > + emit_insn (gen_arm_atomic_store<mode> (operands[0], operands[1])); > + > + /* The seq_cst model needs a barrier after the store to block reordering with > + later accesses. */ > + if (is_mm_seq_cst (model)) > + expand_mem_thread_fence (model); > + > + DONE; > +}) > > ;; An LDRD instruction usable by the atomic_loaddi expander on LPAE targets > > (define_insn "arm_atomic_loaddi2_ldrd" > [(set (match_operand:DI 0 "register_operand" "=r") > (unspec_volatile:DI > - [(match_operand:DI 1 "arm_sync_memory_operand" "Q")] > + [(match_operand:DI 1 "memory_operand" "m")] > VUNSPEC_LDRD_ATOMIC))] > "ARM_DOUBLEWORD_ALIGN && TARGET_HAVE_LPAE" > - "ldrd%?\t%0, %H0, %C1" > - [(set_attr "predicable" "yes")]) > + "ldrd\t%0, %H0, %1" > +) > > ;; There are three ways to expand this depending on the architecture > ;; features available. As for the barriers, a load needs a barrier > @@ -152,6 +194,11 @@ (define_expand "atomic_loaddi" > DONE; > } > > + /* The seq_cst model needs a barrier before the load to block reordering with > + earlier accesses. */ > + if (is_mm_seq_cst (model)) > + expand_mem_thread_fence (model); > + > /* On LPAE targets LDRD and STRD accesses to 64-bit aligned > locations are 64-bit single-copy atomic. We still need barriers in the > appropriate places to implement the ordering constraints. */ > @@ -160,7 +207,6 @@ (define_expand "atomic_loaddi" > else > emit_insn (gen_arm_load_exclusivedi (operands[0], operands[1])); > > - > /* All non-relaxed models need a barrier after the load when load-acquire > instructions are not available. */ > if (!is_mm_relaxed (model)) > @@ -446,54 +492,42 @@ (define_insn_and_split "atomic_nand_fetch<mode>" > [(set_attr "arch" "32,v8mb")]) > > (define_insn "arm_load_exclusive<mode>" > - [(set (match_operand:SI 0 "s_register_operand" "=r,r") > + [(set (match_operand:SI 0 "s_register_operand" "=r") > (zero_extend:SI > (unspec_volatile:NARROW > - [(match_operand:NARROW 1 "mem_noofs_operand" "Ua,Ua")] > + [(match_operand:NARROW 1 "mem_noofs_operand" "Ua")] > VUNSPEC_LL)))] > "TARGET_HAVE_LDREXBH" > - "@ > - ldrex<sync_sfx>%?\t%0, %C1 > - ldrex<sync_sfx>\t%0, %C1" > - [(set_attr "arch" "32,v8mb") > - (set_attr "predicable" "yes")]) > + "ldrex<sync_sfx>\t%0, %C1" > +) > > (define_insn "arm_load_acquire_exclusive<mode>" > - [(set (match_operand:SI 0 "s_register_operand" "=r,r") > + [(set (match_operand:SI 0 "s_register_operand" "=r") > (zero_extend:SI > (unspec_volatile:NARROW > - [(match_operand:NARROW 1 "mem_noofs_operand" "Ua,Ua")] > + [(match_operand:NARROW 1 "mem_noofs_operand" "Ua")] > VUNSPEC_LAX)))] > "TARGET_HAVE_LDACQ" > - "@ > - ldaex<sync_sfx>%?\\t%0, %C1 > - ldaex<sync_sfx>\\t%0, %C1" > - [(set_attr "arch" "32,v8mb") > - (set_attr "predicable" "yes")]) > + "ldaex<sync_sfx>\\t%0, %C1" > +) > > (define_insn "arm_load_exclusivesi" > - [(set (match_operand:SI 0 "s_register_operand" "=r,r") > + [(set (match_operand:SI 0 "s_register_operand" "=r") > (unspec_volatile:SI > - [(match_operand:SI 1 "mem_noofs_operand" "Ua,Ua")] > + [(match_operand:SI 1 "mem_noofs_operand" "Ua")] > VUNSPEC_LL))] > "TARGET_HAVE_LDREX" > - "@ > - ldrex%?\t%0, %C1 > - ldrex\t%0, %C1" > - [(set_attr "arch" "32,v8mb") > - (set_attr "predicable" "yes")]) > + "ldrex\t%0, %C1" > +) > > (define_insn "arm_load_acquire_exclusivesi" > - [(set (match_operand:SI 0 "s_register_operand" "=r,r") > + [(set (match_operand:SI 0 "s_register_operand" "=r") > (unspec_volatile:SI > - [(match_operand:SI 1 "mem_noofs_operand" "Ua,Ua")] > + [(match_operand:SI 1 "mem_noofs_operand" "Ua")] > VUNSPEC_LAX))] > "TARGET_HAVE_LDACQ" > - "@ > - ldaex%?\t%0, %C1 > - ldaex\t%0, %C1" > - [(set_attr "arch" "32,v8mb") > - (set_attr "predicable" "yes")]) > + "ldaex\t%0, %C1" > +) > > (define_insn "arm_load_exclusivedi" > [(set (match_operand:DI 0 "s_register_operand" "=r") > @@ -501,8 +535,8 @@ (define_insn "arm_load_exclusivedi" > [(match_operand:DI 1 "mem_noofs_operand" "Ua")] > VUNSPEC_LL))] > "TARGET_HAVE_LDREXD" > - "ldrexd%?\t%0, %H0, %C1" > - [(set_attr "predicable" "yes")]) > + "ldrexd\t%0, %H0, %C1" > +) > > (define_insn "arm_load_acquire_exclusivedi" > [(set (match_operand:DI 0 "s_register_operand" "=r") > @@ -510,8 +544,8 @@ (define_insn "arm_load_acquire_exclusivedi" > [(match_operand:DI 1 "mem_noofs_operand" "Ua")] > VUNSPEC_LAX))] > "TARGET_HAVE_LDACQEXD && ARM_DOUBLEWORD_ALIGN" > - "ldaexd%?\t%0, %H0, %C1" > - [(set_attr "predicable" "yes")]) > + "ldaexd\t%0, %H0, %C1" > +) > > (define_insn "arm_store_exclusive<mode>" > [(set (match_operand:SI 0 "s_register_operand" "=&r") > @@ -530,14 +564,11 @@ (define_insn "arm_store_exclusive<mode>" > Note that the 1st register always gets the > lowest word in memory. */ > gcc_assert ((REGNO (operands[2]) & 1) == 0 || TARGET_THUMB2); > - return "strexd%?\t%0, %2, %H2, %C1"; > + return "strexd\t%0, %2, %H2, %C1"; > } > - if (TARGET_THUMB1) > - return "strex<sync_sfx>\t%0, %2, %C1"; > - else > - return "strex<sync_sfx>%?\t%0, %2, %C1"; > + return "strex<sync_sfx>\t%0, %2, %C1"; > } > - [(set_attr "predicable" "yes")]) > +) > > (define_insn "arm_store_release_exclusivedi" > [(set (match_operand:SI 0 "s_register_operand" "=&r") > @@ -550,20 +581,16 @@ (define_insn "arm_store_release_exclusivedi" > { > /* See comment in arm_store_exclusive<mode> above. */ > gcc_assert ((REGNO (operands[2]) & 1) == 0 || TARGET_THUMB2); > - return "stlexd%?\t%0, %2, %H2, %C1"; > + return "stlexd\t%0, %2, %H2, %C1"; > } > - [(set_attr "predicable" "yes")]) > +) > > (define_insn "arm_store_release_exclusive<mode>" > - [(set (match_operand:SI 0 "s_register_operand" "=&r,&r") > + [(set (match_operand:SI 0 "s_register_operand" "=&r") > (unspec_volatile:SI [(const_int 0)] VUNSPEC_SLX)) > - (set (match_operand:QHSI 1 "mem_noofs_operand" "=Ua,Ua") > + (set (match_operand:QHSI 1 "mem_noofs_operand" "=Ua") > (unspec_volatile:QHSI > - [(match_operand:QHSI 2 "s_register_operand" "r,r")] > + [(match_operand:QHSI 2 "s_register_operand" "r")] > VUNSPEC_SLX))] > "TARGET_HAVE_LDACQ" > - "@ > - stlex<sync_sfx>%?\t%0, %2, %C1 > - stlex<sync_sfx>\t%0, %2, %C1" > - [(set_attr "arch" "32,v8mb") > - (set_attr "predicable" "yes")]) > + "stlex<sync_sfx>\t%0, %2, %C1") > diff --git a/gcc/config/arm/unspecs.md b/gcc/config/arm/unspecs.md > index 6a5b1f8f623b00dc014c9f829c591477f8faa9a1..4713ec840abae48ca70f418dbc0d4028ad4ad527 100644 > --- a/gcc/config/arm/unspecs.md > +++ b/gcc/config/arm/unspecs.md > @@ -221,8 +221,10 @@ (define_c_enum "unspecv" [ > VUNSPEC_SC ; Represent a store-register-exclusive. > VUNSPEC_LAX ; Represent a load-register-acquire-exclusive. > VUNSPEC_SLX ; Represent a store-register-release-exclusive. > - VUNSPEC_LDA ; Represent a store-register-acquire. > + VUNSPEC_LDA ; Represent a load-register-acquire. > + VUNSPEC_LDR ; Represent a load-register-relaxed. > VUNSPEC_STL ; Represent a store-register-release. > + VUNSPEC_STR ; Represent a store-register-relaxed. > VUNSPEC_GET_FPSCR ; Represent fetch of FPSCR content. > VUNSPEC_SET_FPSCR ; Represent assign of FPSCR content. > VUNSPEC_SET_FPSCR_NZCVQC ; Represent assign of FPSCR_nzcvqc content. > diff --git a/gcc/testsuite/gcc.dg/rtl/arm/stl-cond.c b/gcc/testsuite/gcc.dg/rtl/arm/stl-cond.c > deleted file mode 100644 > index e47ca6bf36dac500b90d80e52e150a19c95c7219..0000000000000000000000000000000000000000 > --- a/gcc/testsuite/gcc.dg/rtl/arm/stl-cond.c > +++ /dev/null > @@ -1,61 +0,0 @@ > -/* { dg-do compile { target arm*-*-* } } */ > -/* { dg-require-effective-target arm_arm_ok } */ > -/* { dg-require-effective-target arm_arch_v8a_ok } */ > -/* { dg-options "-O2 -marm" } */ > -/* { dg-add-options arm_arch_v8a } */ > - > -/* We want to test that the STL instruction gets the conditional > - suffix when under a COND_EXEC. However, COND_EXEC is very hard to > - generate from C code because the atomic_store expansion adds a compiler > - barrier before the insn, preventing if-conversion. So test the output > - here with a hand-crafted COND_EXEC wrapped around an STL. */ > - > -void __RTL (startwith ("final")) foo (int *a, int b) > -{ > -(function "foo" > - (param "a" > - (DECL_RTL (reg/v:SI r0)) > - (DECL_RTL_INCOMING (reg:SI r0)) > - ) > - (param "b" > - (DECL_RTL (reg/v:SI r1)) > - (DECL_RTL_INCOMING (reg:SI r1)) > - ) > - (insn-chain > - (block 2 > - (edge-from entry (flags "FALLTHRU")) > - (cnote 5 [bb 2] NOTE_INSN_BASIC_BLOCK) > - > - (insn:TI 7 (parallel [ > - (set (reg:CC cc) > - (compare:CC (reg:SI r1) > - (const_int 0))) > - (set (reg/v:SI r1) > - (reg:SI r1 )) > - ]) ;; {*movsi_compare0} > - (nil)) > - > - ;; A conditional atomic store-release: STLNE for Armv8-A. > - (insn 10 (cond_exec (ne (reg:CC cc) > - (const_int 0)) > - (set (mem/v:SI (reg/v/f:SI r0) [-1 S4 A32]) > - (unspec_volatile:SI [ > - (reg/v:SI r1) > - (const_int 3) > - ] VUNSPEC_STL))) ;; {*p atomic_storesi} > - (expr_list:REG_DEAD (reg:CC cc) > - (expr_list:REG_DEAD (reg/v:SI r1) > - (expr_list:REG_DEAD (reg/v/f:SI r0) > - (nil))))) > - (edge-to exit (flags "FALLTHRU")) > - ) ;; block 2 > - ) ;; insn-chain > - (crtl > - (return_rtx > - (reg/i:SI r0) > - ) ;; return_rtx > - ) ;; crtl > -) ;; function > -} > - > -/* { dg-final { scan-assembler "stlne" } } */ > diff --git a/gcc/testsuite/gcc.target/arm/atomic_loaddi_7.c b/gcc/testsuite/gcc.target/arm/atomic_loaddi_7.c > index 6743663f1e6831d3fc441e80fcfe3d761987970b..79e36edbb8fa86712b8d283b9a81b794610f4813 100644 > --- a/gcc/testsuite/gcc.target/arm/atomic_loaddi_7.c > +++ b/gcc/testsuite/gcc.target/arm/atomic_loaddi_7.c > @@ -6,4 +6,4 @@ > #include "atomic_loaddi_seq_cst.x" > > /* { dg-final { scan-assembler-times "ldrexd\tr\[0-9\]+, r\[0-9\]+, \\\[r\[0-9\]+\\\]" 1 } } */ > -/* { dg-final { scan-assembler-times "dmb\tish" 1 } } */ > +/* { dg-final { scan-assembler-times "dmb\tish" 2 } } */ > diff --git a/gcc/testsuite/gcc.target/arm/atomic_loaddi_8.c b/gcc/testsuite/gcc.target/arm/atomic_loaddi_8.c > index f7bd3e5a2b515d91418f5f4a7a8db00336a8b594..7241d361313997b0133056c1a3a7c1b546708e43 100644 > --- a/gcc/testsuite/gcc.target/arm/atomic_loaddi_8.c > +++ b/gcc/testsuite/gcc.target/arm/atomic_loaddi_8.c > @@ -6,4 +6,4 @@ > #include "atomic_loaddi_seq_cst.x" > > /* { dg-final { scan-assembler-times "ldrd\tr\[0-9\]+, r\[0-9\]+, \\\[r\[0-9\]+\\\]" 1 } } */ > -/* { dg-final { scan-assembler-times "dmb\tish" 1 } } */ > +/* { dg-final { scan-assembler-times "dmb\tish" 2 } } */ > diff --git a/gcc/testsuite/gcc.target/arm/pr111235.c b/gcc/testsuite/gcc.target/arm/pr111235.c > new file mode 100644 > index 0000000000000000000000000000000000000000..b06a5bfb8e294edf04ec9b7b6d8fe5d1ac73b1e7 > --- /dev/null > +++ b/gcc/testsuite/gcc.target/arm/pr111235.c > @@ -0,0 +1,39 @@ > +/* { dg-do compile } */ > +/* { dg-options "-O2" } */ > +/* { dg-require-effective-target arm_arch_v7a_ok } */ > +/* { dg-add-options arm_arch_v7a } */ > + > +#include <stdatomic.h> > + > +int t0 (int *p, int x) > +{ > + if (x > 100) > + x = atomic_load_explicit (p, memory_order_relaxed); > + return x + 1; > +} > + > +long long t1 (long long *p, int x) > +{ > + if (x > 100) > + x = atomic_load_explicit (p, memory_order_relaxed); > + return x + 1; > +} > + > +void t2 (int *p, int x) > +{ > + if (x > 100) > + atomic_store_explicit (p, x, memory_order_relaxed); > +} > + > +void t3 (long long *p, int x) > +{ > + if (x > 100) > + atomic_store_explicit (p, x, memory_order_relaxed); > +} > + > +/* { dg-final { scan-assembler-times "ldrexd\tr\[0-9\]+, r\[0-9\]+, \\\[r\[0-9\]+\\\]" 2 } } */ > +/* { dg-final { scan-assembler-not "ldrgt" } } */ > +/* { dg-final { scan-assembler-not "ldrdgt" } } */ > +/* { dg-final { scan-assembler-not "ldrexdgt" } } */ > +/* { dg-final { scan-assembler-not "strgt" } } */ > +/* { dg-final { scan-assembler-not "strdgt" } } */ Ok if no regressions but as you might get nagged by the post commit CI ... While it is not policy yet to look at these bots but given the enthusiasm at Cauldron for patchwork and pre-commit CI and because all my armhf boxes are boxed up, I decided to do something a bit novel ! I tried reviewing this via patchwork https://patchwork.sourceware.org/project/gcc/patch/PAWPR08MB8982A6AA40749B7… and notice that https://ci.linaro.org/job/tcwg_gcc_build--master-arm-precommit/2393/artifac… says nothing could be built. Possibly worth double checking the status for it being a false negative as to why the build failed. It was green on patchwork but remembering that Green is not Green for CI in patchwork I clicked on the afore mentioned ci.linaro.org link and see that it's actually broken. regards Ramana

2 years

4
3
0 0

[ACTIVITY] report week ending 20 Oct

by Peter Maydell

Progress: * UM-2 [QEMU upstream maintainership] - post-holiday catchup on email and code review - respin and resend of a patch fixing a bug in rdma code - sent a target-arm pull request * QEMU-292 [ARMv8.3 FEAT_NV, Nested Virtualization] - did an initial read-through of the relevant portions of the Arm ARM to identify the work required here thanks -- PMM

2 years

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-18-init-8757-gfd311126349b: Failure on aarch64

by Nick Desaulniers

Thanks for the report. Looks like Nathan has reported this, too (as have Google3 folks): https://github.com/llvm/llvm-project/commit/fd311126349b8fe1684d62154a9fa5a… On Wed, Oct 18, 2023 at 7:31 PM <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 CI config tcwg_kernel/llvm-master-aarch64-stable-defconfig after: > > | commit llvmorg-18-init-8757-gfd311126349b > | Author: Florian Hahn <flo(a)fhahn.com> > | Date: Tue Oct 17 19:17:40 2023 +0100 > | > | [VPlan] Insert Trunc/Exts for reductions directly in VPlan. > | > | Update the code to create Trunc/Ext recipes directly in > | adjustRecipesForReductions instead of fixing it up later in > | fixReductions. > | > | This explicitly models the required conversions and also makes sure they > | ... 2 lines of the commit log omitted. > > Results changed to > # reset_artifacts: > -10 > # build_abe binutils: > -9 > # build_kernel_llvm: > -5 > # build_abe qemu: > -2 > # linux_n_obj: > 8020 > # First few build errors in logs: > > # 00:12:40 clang: error: clang frontend command failed with exit code 134 (use -v to see invocation) > # 00:12:40 make[5]: *** [scripts/Makefile.build:243: drivers/platform/chrome/cros_ec_i2c.o] Error 1 > # 00:13:18 make[4]: *** [scripts/Makefile.build:480: drivers/platform/chrome] Error 2 > # 00:13:18 make[3]: *** [scripts/Makefile.build:480: drivers/platform] Error 2 > # 00:13:37 clang: error: clang frontend command failed with exit code 134 (use -v to see invocation) > # 00:13:37 make[7]: *** [scripts/Makefile.build:243: drivers/net/ethernet/intel/igb/igb_main.o] Error 1 > # 00:13:46 make[6]: *** [scripts/Makefile.build:480: drivers/net/ethernet/intel/igb] Error 2 > # 00:13:53 make[5]: *** [scripts/Makefile.build:480: drivers/net/ethernet/intel] Error 2 > # 00:16:54 make[4]: *** [scripts/Makefile.build:480: drivers/net/ethernet] Error 2 > # 00:16:54 make[3]: *** [scripts/Makefile.build:480: drivers/net] Error 2 > > From > # reset_artifacts: > -10 > # build_abe binutils: > -9 > # build_kernel_llvm: > -5 > # build_abe qemu: > -2 > # linux_n_obj: > 9166 > # linux build successful: > all > # linux boot successful: > boot > > The configuration of this build is: > CI config tcwg_kernel/llvm-master-aarch64-stable-defconfig > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-stable-defconfig… > Reference build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-stable-defconfig… > > Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > > Full commit : https://github.com/llvm/llvm-project/commit/fd311126349b8fe1684d62154a9fa5a… > > Latest bug report status : https://linaro.atlassian.net/browse/LLVM-1007 > > List of configurations that regressed due to this commit : > * tcwg_kernel > ** llvm-master-aarch64-stable-defconfig > *** Failure > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > *** https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-stable-defconfig… -- Thanks, ~Nick Desaulniers

2 years

2
1
0 0

[ACTIVITY] Report for week #41

by Thiago Jung Bauermann

Hello, # TCWG CI - Flakiness in gdb.base/gdb-sigterm.exp causes false positives on tcwg_check_gdb--master-arm-precommit, so started investigating its failures. - Investigated regressions reported by the CI: - GCC regression GNU-935: Not a real regression, just already existing failures being reported for a new version of the C++ standard. - linux-next regression GNU-936: Fixed in the newest linux-next tree. - GCC regression GNU-962: Opened GCC bug 111802 ("New analyser diagram failures since commit b365e9d57ad4"). - GCC regression GNU-965: Arm already opened GCC bug 111784 ("[14 Regression] aarch64: ldp_stp_{15,16,17,18}.c test failures since r14-4579.") about this issue. - GCC regression GNU-966: This problem has been fixed in trunk. - linux-next regression GNU-967: A patch was sent to fix the error. # [GNU-767] Support changing SVE vector length in remote debugging - Working on adapting gdbserver's regcache to support registers with a variable size. - Also enabling the target description XML to express vector register sizes in terms of another register. -- Thiago

2 years

1
0
0 0

Re: WoA machines in the lab

by Lina Iyer

+ linaro-toolchain(a)lists.linaro.org Could someone help with this information in Maxim's absence ? Thanks, Lina On Tue, Oct 10 2023 at 10:07 -0600, Lina Iyer wrote: >Hi Maxim, > >Do you have a list of machines and who provided us with those machines >that we use for WoA projects? I see the list in [1] but not where we got >them from. Marcus from MS was asking for a list of MS provided machines >that we have in use. > >Thanks, >Lina > >[1]. >https://linaro.atlassian.net/wiki/spaces/TCWG/pages/22395192116/Accessing+W…

2 years

1
0
0 0

Fwd: [Linaro-TCWG-CI] llvmorg-18-init-7933-ge13bed4c5f35: slowed down by 6% - 464.h264ref on aarch64 O2

by Maxim Kuvyrkov

Hi Dmitriy, Linaro Benchmarking CI has flagged several interesting code-speed and code-size regressions for your patch -- see [1]. In particular, could you check if below regressions can be avoided: - grew in size by 21% - 473.astar:[.] _ZN7way2obj12releasepointEii - slowed down by 61% - 505.mcf_r:[.] price_out_impl Both of these are for 32-bit ARM, but AArch64 also has code-speed and code-size regressions. Let me know if you need any assistance in reproducing these problems. [1] https://linaro.atlassian.net/browse/LLVM-1001 Kind regards, -- Maxim Kuvyrkov https://www.linaro.org > Begin forwarded message: > > From: ci_notify(a)linaro.org > Subject: [Linaro-TCWG-CI] llvmorg-18-init-7933-ge13bed4c5f35: slowed down by 6% - 464.h264ref on aarch64 O2 > Date: October 8, 2023 at 04:26:39 GMT+4 > To: maxim.kuvyrkov(a)linaro.org > Reply-To: linaro-toolchain(a)lists.linaro.org > > 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 CI config tcwg_bmk-code_speed-spec2k6/llvm-aarch64-master-O2 after: > > | commit llvmorg-18-init-7933-ge13bed4c5f35 > | Author: Dmitriy Smirnov <dmitriy.smirnov(a)arm.com> > | Date: Fri Oct 6 11:15:00 2023 +0100 > | > | [PATCH] [llvm] [InstCombine] Canonicalise ADD+GEP > | > | This patch tries to canonicalise add + gep to gep + gep. > | > | Co-authored-by: Paul Walker <paul.walker(a)arm.com> > | > | Reviewed By: nikic > | ... 2 lines of the commit log omitted. > > the following benchmarks slowed down by more than 3%: > - slowed down by 6% - 464.h264ref - from 11126 to 11766 perf samples > the following hot functions slowed down by more than 15% (but their benchmarks slowed down by less than 3%): > - slowed down by 44% - 464.h264ref:[.] FastFullPelBlockMotionSearch - from 1531 to 2206 perf samples > > The configuration of this build is: > Below reproducer instructions can be used to re-build both "first_bad" and "last_good" cross-toolchains used in this bisection. Naturally, the scripts will fail when triggerring benchmarking jobs if you don\'t have access to Linaro TCWG CI. > > Configuration: > - Benchmark: > - Toolchain: Clang + Glibc + LLVM Linker > - Version: all components were built from their tip of trunk > - Target: aarch64-linux-gnu > - Compiler flags: O2 > - Hardware: NVidia TX1 4x Cortex-A57 > > This benchmarking CI is work-in-progress, and we welcome feedback and suggestions at linaro-toolchain(a)lists.linaro.org . In our improvement plans is to add support for SPEC CPU2017 benchmarks and provide "perf report/annotate" data behind these reports. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_bmk-code_speed-spec2k6--llvm-aarch64-master-… > Reference build : https://ci.linaro.org/job/tcwg_bmk-code_speed-spec2k6--llvm-aarch64-master-… > > Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > > Full commit : https://github.com/llvm/llvm-project/commit/e13bed4c5f3544c076ce57e36d9a11e… > > Latest bug report status : https://linaro.atlassian.net/browse/LLVM-1001 > > List of configurations that regressed due to this commit : > * tcwg_bmk-code_speed-spec2k6 > ** llvm-aarch64-master-O2 > *** slowed down by 6% - 464.h264ref > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > *** https://ci.linaro.org/job/tcwg_bmk-code_speed-spec2k6--llvm-aarch64-master-…

2 years, 1 month

2
1
0 0

[ACTIVITY] Report for weeks #37 to #40

by Thiago Jung Bauermann

Hello, Attended two events in a row in September, so had a bit of a time crunch and the weekly report fell through the cracks... # TCWG CI - Investigated and fixed a few false positives in the GDB precommit CI which were caused by random failures in gdb.threads/process-dies-while-detaching.exp. Posted upstream and later committed patch fixing the testcase to be more stable. - After conversations during GNU Tools Cauldron and following Maxim's suggestion, changed Linaro's CI to use the read1 library while running the GDB testsuite to improve the stability of its results. - After review from Tom Tromey, posted v2 and later committed a patch which adds '--with-additional-debug-dirs' configure option. - Committed a couple of changes to our CI scripts which make sure that the kernel.yama.ptrace_scope and kernel.core_pattern sysctls have correct values for running the GDB testsuite. # [GNU-767] Support changing SVE vector length in remote debugging - Now that Luis pushed his SME and SME2 patches, merged current GDB main branch into my local branch. It builds but doesn't work yet. # GDB Upstream - Reviewed patch series "[PATCH v3 0/4] Dynamic properties of pointers". - Investigated upstream bugzilla "18898 - Cannot specify non-default list of directories as argument of --with-auto-load-dir on Windows", but concluded it's an autoconf limitation that isn't easy to fix. # Misc - Prepared for Linaro's Employees Meeting. - Attended GNU Tools Cauldron. - Took a few days of vacation. -- Thiago

2 years, 1 month

1
0
0 0

Re: [Linaro-TCWG-CI] 13 patches in glibc: FAIL: 7 regressions

by Maxim Kuvyrkov

Hi Arjun, Please ignore this report. We had a new machine added to the testing pool, and it behaved differently than the others. -- Maxim Kuvyrkov https://www.linaro.org > On Oct 4, 2023, at 22:30, 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 CI config tcwg_glibc_check/master-arm after: > > | 13 patches in glibc > | Patchwork URL: https://patchwork.sourceware.org/patch/76970 > | 72a0ec189c Move 'rpc' routines from 'inet' into 'nss' > | e9e10ad39b Move 'protocols' routines from 'inet' into 'nss' > | e0694af485 Move 'networks' routines from 'inet' into 'nss' > | 547bcf6d44 Move 'netgroup' routines from 'inet' into 'nss' > | 6c43eb641a Move 'hosts' routines from 'inet' into 'nss' > | ... and 8 more patches in glibc > | ... applied on top of baseline commit: > | 1056e5b4c3 tunables: Terminate if end of input is reached (CVE-2023-4911) > > FAIL: 7 regressions > > regressions.sum: > === glibc tests === > > Running glibc:io ... > FAIL: io/tst-close_range > > Running glibc:misc ... > FAIL: misc/tst-epoll > FAIL: misc/tst-epoll-time64 > FAIL: misc/tst-mount > FAIL: misc/tst-process_mrelease > ... and 6 more entries > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/802/artifa… . > The full lists of regressions and progressions are in > - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/802/artifa… . > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/802/artifa… . > > > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/802/artifa… > Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/650/artifact/a…

2 years, 1 month

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain