Hi there,
I can only locate the error message like "/tmp/cc4i9dn1.s:151930: Error: conditional branch out of range".
But failed to reproduce this when cross build, is there anywhere to get the build option for reproducing?
Thanks.
Pan
-----Original Message-----
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: Sunday, October 27, 2024 9:58 AM
To: Li, Pan2 <pan2.li(a)intel.com>
Cc: gcc-regression(a)gcc.gnu.org
Subject: [Linaro-TCWG-CI] gcc-15-4672-gdf4af89bc3e: Failure 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 understand 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-1389 , please let us know if you are looking at the problem and/or when you have a fix.
In bootstrap_build master-arm-bootstrap_profiled after:
| commit gcc-15-4672-gdf4af89bc3e
| Author: Pan Li <pan2.li(a)intel.com>
| Date: Thu Oct 24 21:57:04 2024 +0800
|
| Match: Simplify branch form 3 of unsigned SAT_ADD into branchless
|
| There are sorts of forms for the unsigned SAT_ADD. Some of them are
| complicated while others are cheap. This patch would like to simplify
| the complicated form into the cheap ones. For example as below:
| ... 65 lines of the commit log omitted.
Results changed to
# reset_artifacts:
-10
# true:
0
# build_abe bootstrap_profiled:
# FAILED
# First few build errors in logs:
# 01:33:58 make[3]: *** [Makefile:1195: gimple-match-1.o] Error 1
# 01:33:58 make[2]: *** [Makefile:5220: all-stageprofile-gcc] Error 2
# 01:33:58 make[1]: *** [Makefile:26089: stageprofile-bubble] Error 2
# 01:33:58 make: *** [Makefile:26343: profiledbootstrap] Error 2
From
# reset_artifacts:
-10
# true:
0
# build_abe bootstrap_profiled:
1
The configuration of this build is:
CI config tcwg_bootstrap_build master-arm-bootstrap_profiled
configure and test flags: --target arm-linux-gnueabihf
-----------------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…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
Full commit : https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=df4af89bc3eabbeaccb16539a…
On Wed, Oct 30, 2024 at 06:06:06AM +0000, ci_notify(a)linaro.org wrote:
> In CI config tcwg_kernel/llvm-master-aarch64-stable-allyesconfig after:
>
> | commit llvmorg-20-init-10266-g71315698c91d
> | Author: serge-sans-paille <sguelton(a)mozilla.com>
> | Date: Mon Oct 28 20:40:52 2024 +0000
> |
> | [clang] Warn about memset/memcpy to NonTriviallyCopyable types (#111434)
> |
> | This implements a warning that's similar to what GCC does in that
> | context: both memcpy and memset require their first and second operand
> | to be trivially copyable, let's warn if that's not the case.
Thanks for the report, this should be fixed in tip of tree now:
https://github.com/llvm/llvm-project/commit/dc56a86b96d77a93f761995d50f7b2f…
Cheers,
Nathan
ci_notify(a)linaro.org writes:
> 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 understand 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-1388 , please let us know if you are looking at the problem and/or when you have a fix.
Should be fixed with r15-4692-g40fedaf35fa99a9728d5b84d47035f4c92e1ba90.
thanks,
sam
Hi Linaro Toolchain Team,
I got this regression email for one of my patch but failure does not look like related to the change. Also this look like a false positive to me as test is failing in baseline also.
From the logs regression is shown in
| Running gdb:gdb.cp/nextoverthrow.exp ...
| FAIL: gdb.cp/nextoverthrow.exp: check for stap probe in unwinder (timeout)
You can find the failure logs in *.log.1.xz files in
* https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifac…
But the baseline file also has the same failure in sum file and somehow not shown in xfail file:
The list of [ignored] baseline and flaky failures are in
https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifac…
Thanks & Best Regards
Abdul Basit
-----Original Message-----
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: Saturday, October 26, 2024 4:29 AM
To: Ijaz, Abdul B <abdul.b.ijaz(a)intel.com>
Subject: [Linaro-TCWG-CI] gdb patch #99582: FAIL: 1 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 understand 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_check master-arm after:
| gdb patch https://patchwork.sourceware.org/patch/99582
| Author: Ijaz, Abdul B <abdul.b.ijaz(a)intel.com>
| Date: Fri Oct 25 16:37:46 2024 +0200
|
| [PATCH v8 1/1] fortran: Fix arrays of variable length strings for FORTRAN
|
| Before this change resolve_dynamic_array_or_string was called for
| all TYPE_CODE_ARRAY and TYPE_CODE_STRING types, but, in the end,
| this function always called create_array_type_with_stride, which
| ... 65 lines of the commit log omitted.
| ... applied on top of baseline commit:
| 3d17c881721 [gdb] Handle bad alloc in gdb_rl_callback_read_char_wrapper_noexcept
FAIL: 1 regressions
regressions.sum:
| === gdb tests ===
|
| Running gdb:gdb.cp/nextoverthrow.exp ...
| FAIL: gdb.cp/nextoverthrow.exp: check for stap probe in unwinder (timeout)
|
The configuration of this build is:
CI config tcwg_gdb_check master-arm
configure and test flags: --target arm-linux-gnueabihf
You can find the failure logs in *.log.1.xz files in
* https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifac…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifac…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifac…
The configuration of this build is:
CI config tcwg_gdb_check master-arm
configure and test flags: --target arm-linux-gnueabihf
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifac…
Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/1919/artifact/ar…
Warning: we do not enable maintainer-mode nor automatically update generated files, which may lead to failures if the patch modifies the master files.
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Sean Fennelly, Jeffrey Schneiderman, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
Fixed at r15-4720-ge320846fec00aa
On Mon, 28 Oct 2024 at 01:20, <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 understand 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-1390 , please let us know if you are looking at the problem and/or when you have a fix.
>
> In gcc_check master-arm after:
>
> | commit gcc-15-4709-gb281e13ecad1
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Tue Oct 8 21:15:18 2024 +0100
> |
> | libstdc++: Add P1206R7 from_range members to std::vector [PR111055]
> |
> | This is another piece of P1206R7, adding new members to std::vector and
> | std::vector<bool>.
> |
> | ... 40 lines of the commit log omitted.
>
> FAIL: 2 regressions
>
> regressions.sum:
> | === libstdc++ tests ===
> |
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL: 23_containers/vector/cons/from_range.cc -std=gnu++23 (test for excess errors)
> | FAIL: 23_containers/vector/cons/from_range.cc -std=gnu++26 (test for excess errors)
> |
> The configuration of this build is:
> CI config tcwg_gcc_check master-arm
> configure and test flags: --target arm-linux-gnueabihf
>
> You can find the failure logs in *.log.1.xz files in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2927/artifact/ar…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2927/artifact/ar…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2927/artifact/ar…
>
> The configuration of this build is:
> CI config tcwg_gcc_check master-arm
> configure and test flags: --target arm-linux-gnueabihf
>
> -----------------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-build/2927/artifact/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2926/artifact/ar…
>
> Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
>
> Full commit : https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=b281e13ecad12d07209924a72…
Hi there!
These are legitimate regressions: the code compiled to bogus BIND(C) ABI that only worked when using with Fortran to Fortran. A TODO is now correctly emitted until the proper ABI is implemented.
In Fujitsu-Fortran-0379_0074
```
function strfunc() bind(C)
type,bind(C) :: str
integer :: iii
end type
type(str) :: strfunc
end function
end interface
type,bind(C) :: str
integer :: iii
end type
````
Previously, the result was passed in as a hidden extra argument, like it is done in normal Fortran ABI. On ARM, the equivalent C code is returned in registered as far as I can see: https://godbolt.org/z/nec6jbhYM
0384_0028.f90 also has BIND(C) function returning such BIND(C) types.
So, both tests should not be run on ARM, or should expect a TODO error message until the feature is implemented on ARM.
Jean
-----Original Message-----
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: Monday, October 14, 2024 11:23 PM
To: ohno.yasuyuki(a)fujitsu.com; itou.tetsuya(a)fujitsu.com; t-kawashima(a)fujitsu.com
Cc: maxim.kuvyrkov(a)linaro.org; Jean Perier <jperier(a)nvidia.com>
Subject: [Linaro-TCWG-CI] llvmorg-20-init-8878-g367c3c968eb8: FAIL: 2 regressions on aarch64
External email: Use caution opening links or attachments
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 understand 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/LLVM-1398 , please let us know if you are looking at the problem and/or when you have a fix.
In CI config tcwg_flang_test/main-aarch64-Ofast-sve_vls-lto-lld after:
| commit llvmorg-20-init-8878-g367c3c968eb8
| Author: jeanPerier <jperier(a)nvidia.com>
| Date: Mon Oct 14 09:35:29 2024 +0200
|
| [flang] correctly deal with bind(c) derived type result ABI (#111969)
|
| Derived type results of BIND(C) function should be returned according
| the the C ABI for returning the related C struct type.
|
| ... 15 lines of the commit log omitted.
FAIL: 2 regressions
The configuration of this build is:
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;openmp;clang-tools-extra" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld
* Testsuite : cmake -GNinja -DCMAKE_C_COMPILER="$WORKSPACE/llvm-install/bin/clang" -DCMAKE_CXX_COMPILER="$WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$WORKSPACE/llvm-install/bin/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$WORKSPACE/test/test-suite"
regressions.sum:
| === test-suite tests ===
|
| Running test-suite:Fujitsu/Fortran/0379 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0379/Fujitsu-Fortran-0379_0074.test
|
| Running test-suite:Fujitsu/Fortran/0384 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0384/Fujitsu-Fortran-0384_0028.test
|
| # "NOEXE" means : the test program cannot be compiled
You can find the failure logs in *.log.1.xz files in
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…
Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…
Full commit : https://github.com/llvm/llvm-project/commit/367c3c968eb8f29b55fb8019b2464c7…
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 understand 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-1377 , please let us know if you are looking at the problem and/or when you have a fix.
In master-aarch64 after:
| commit v9.1.0-759-g07f0d32641e
| Author: Paolo Bonzini <pbonzini(a)redhat.com>
| Date: Thu Oct 3 16:28:43 2024 +0300
|
| Require meson version 1.5.0
|
| This is needed for Rust support.
|
| Signed-off-by: Paolo Bonzini <pbonzini(a)redhat.com>
| ... 3 lines of the commit log omitted.
The configuration of this build is:
CI config tcwg_gnu_cross_build master-aarch64
configure and test flags: --target aarch64-linux-gnu
Results changed to
# reset_artifacts:
-10
# true:
0
# build_abe binutils:
1
# build_abe stage1 --:
2
# build_abe linux:
3
# build_abe glibc:
4
# build_abe stage2 --:
5
# build_abe gdb:
6
# build_abe qemu:
# FAILED
From
# reset_artifacts:
-10
# true:
0
# build_abe binutils:
1
# build_abe stage1 --:
2
# build_abe linux:
3
# build_abe glibc:
4
# build_abe stage2 --:
5
# build_abe gdb:
6
# build_abe qemu:
7
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-build/854/ar…
Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-build/853/ar…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/qemu/s…
Full commit : https://gitlab.com/qemu-project/qemu/commit/07f0d32641e04703e6ed9626d061790…
Thanks for the report, I have opened
https://github.com/llvm/llvm-project/issues/111903 for this.
On Tue, Oct 08, 2024 at 07:40:22AM +0000, 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 understand 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/LLVM-1390 , please let us know if you are looking at the problem and/or when you have a fix.
>
> In CI config tcwg_kernel/llvm-master-aarch64-lts-allmodconfig after:
>
> | commit llvmorg-20-init-8119-gd2408c417cfa
> | Author: David Green <david.green(a)arm.com>
> | Date: Sun Oct 6 10:44:21 2024 +0100
> |
> | [InstCombine] Canonicalize more geps with constant gep bases and constant offsets. (#110033)
> |
> | This is another small but hopefully not performance negative step to
> | canonicalizing towards i8 geps. We looks for geps with a constant offset
> | base pointer of the form `gep (gep @glob, C1), x, C2` and expand the gep
> | ... 2 lines of the commit log omitted.
>
> The configuration of this build is:
> CI config tcwg_kernel/llvm-master-aarch64-lts-allmodconfig
> Results changed to
> # reset_artifacts:
> -10
> # build_abe binutils:
> -9
> # build_kernel_llvm:
> -5
> # build_abe qemu:
> -2
> # linux_n_obj:
> 24511
>
> From
> # reset_artifacts:
> -10
> # build_abe binutils:
> -9
> # build_kernel_llvm:
> -5
> # build_abe qemu:
> -2
> # linux_n_obj:
> 33835
> # linux build successful:
> all
>
> -----------------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-lts-allmodconfig…
> Reference build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-lts-allmodconfig…
>
> Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…
>
> Full commit : https://github.com/llvm/llvm-project/commit/d2408c417cfa71f1786c90978856037…
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 understand 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-1372 , please let us know if you are looking at the problem and/or when you have a fix.
In master-aarch64 after:
| commit glibc-2.40.9000-232-gd40ac01cbbc
| Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org>
| Date: Thu Oct 3 15:41:10 2024 -0300
|
| stdlib: Make abort/_Exit AS-safe (BZ 26275)
|
| The recursive lock used on abort does not synchronize with a new process
| creation (either by fork-like interfaces or posix_spawn ones), nor it
| is reinitialized after fork().
| ... 60 lines of the commit log omitted.
FAIL: 5 regressions
The configuration of this build is:
CI config tcwg_gnu_native_check_gdb master-aarch64
configure and test flags: --target aarch64-linux-gnu
regressions.sum:
| === gdb tests ===
|
| Running gdb:gdb.reverse/waitpid-reverse.exp ...
| ERROR: GDB process no longer exists
| UNRESOLVED: gdb.reverse/waitpid-reverse.exp: check waitpid record
| UNRESOLVED: gdb.reverse/waitpid-reverse.exp: continue to breakpoint: marker2
| UNRESOLVED: gdb.reverse/waitpid-reverse.exp: reverse to marker1
| UNRESOLVED: gdb.reverse/waitpid-reverse.exp: set breakpoint at marker1
|
You can find the failure logs in *.log.1.xz files in
* https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1…
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1…
Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/…
Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=d40ac01cbbc66e6d9dbd…