Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[glibc] branch master updated (385f2ecda9 -> 2e81493fa6)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository glibc. from 385f2ecda9 hurd: Fix SIOCADD/DELRT ioctls new 73e9fe43ac riscv: Consolidate the libm-test-ulps new 2e81493fa6 riscv: Remove RV32 floating point functions The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: sysdeps/riscv/rv32/rvd/libm-test-ulps | 1405 ---------------------- sysdeps/riscv/rv32/rvd/libm-test-ulps-name | 1 - sysdeps/riscv/rv32/rvd/s_lrint.c | 31 - sysdeps/riscv/rv32/rvd/s_lround.c | 31 - sysdeps/riscv/rv32/rvf/s_lrintf.c | 31 - sysdeps/riscv/rv32/rvf/s_lroundf.c | 31 - sysdeps/riscv/{rv64 => }/rvd/libm-test-ulps | 0 sysdeps/riscv/{rv64 => }/rvd/libm-test-ulps-name | 0 sysdeps/riscv/{rv64 => }/rvd/s_lrint.c | 12 +- sysdeps/riscv/{rv64 => }/rvd/s_lround.c | 12 +- sysdeps/riscv/{rv64 => }/rvf/s_lrintf.c | 12 +- sysdeps/riscv/{rv64 => }/rvf/s_lroundf.c | 12 +- 12 files changed, 40 insertions(+), 1538 deletions(-) delete mode 100644 sysdeps/riscv/rv32/rvd/libm-test-ulps delete mode 100644 sysdeps/riscv/rv32/rvd/libm-test-ulps-name delete mode 100644 sysdeps/riscv/rv32/rvd/s_lrint.c delete mode 100644 sysdeps/riscv/rv32/rvd/s_lround.c delete mode 100644 sysdeps/riscv/rv32/rvf/s_lrintf.c delete mode 100644 sysdeps/riscv/rv32/rvf/s_lroundf.c rename sysdeps/riscv/{rv64 => }/rvd/libm-test-ulps (100%) rename sysdeps/riscv/{rv64 => }/rvd/libm-test-ulps-name (100%) rename sysdeps/riscv/{rv64 => }/rvd/s_lrint.c (83%) rename sysdeps/riscv/{rv64 => }/rvd/s_lround.c (83%) rename sysdeps/riscv/{rv64 => }/rvf/s_lrintf.c (83%) rename sysdeps/riscv/{rv64 => }/rvf/s_lroundf.c (83%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-mainline-allmodconfig updated (f084d0ebf -> 99ee0a475)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-arm-mainline-allmodconfig in repository toolchain/ci/base-artifacts. from f084d0ebf 10: onsuccess: #416: all: Success after binutils/gcc/linux: 9 [...] new 99ee0a475 11: onsuccess: #417: all: Success after binutils/gcc/linux/qe [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1876 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 29952 -> 29876 bytes 04-build_abe-stage1/console.log.xz | Bin 86780 -> 87044 bytes 05-build_abe-qemu/console.log.xz | Bin 31796 -> 31508 bytes 06-build_linux/console.log.xz | Bin 3032 -> 3024 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 2860 -> 3240 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- 17 files changed, 23 insertions(+), 23 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[binutils-gdb] branch master updated (6f1d2f789bf -> 517a63c2c48)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from 6f1d2f789bf gdbsupport: change path_join parameter to array_view<const char *> new 198f946ffe9 gdbsupport: move include/gdb/fileio.h contents to fileio.h new b872057a63c gdbsupport: convert FILEIO_* macros to an enum new 517a63c2c48 gdbsupport: move fileio_errno_to_host to fileio.{h,cc} and rename The 3 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gdb/gdb_bfd.c | 70 ++++-------------------- gdb/inf-child.c | 14 ++--- gdb/inf-child.h | 14 ++--- gdb/linux-nat.c | 6 +-- gdb/linux-nat.h | 6 +-- gdb/linux-tdep.c | 2 +- gdb/remote.c | 139 ++++++++++++++++------------------------------- gdb/sparc64-tdep.c | 8 +-- gdb/target.c | 48 ++++++++--------- gdb/target.h | 29 +++++----- gdbserver/hostio.cc | 2 +- gdbserver/win32-low.cc | 2 +- gdbsupport/fileio.cc | 55 ++++++++++++++++++- gdbsupport/fileio.h | 120 ++++++++++++++++++++++++++++++++++++++++- include/gdb/fileio.h | 144 ------------------------------------------------- 15 files changed, 293 insertions(+), 366 deletions(-) delete mode 100644 include/gdb/fileio.h -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[glibc] branch release/2.34/master updated (f50a6c843a -> 044755e2fa)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch release/2.34/master in repository glibc. from f50a6c843a gconv: Use 64-bit interfaces in gconv_parseconfdir (bug 29583) new 1a3afdfe31 resolv: Add tst-resolv-byaddr for testing reverse lookup new 6a833d798e resolv: Add tst-resolv-aliases new 4d2e67d6e5 resolv: Add internal __res_binary_hnok function new bb8adbba4f resolv: Add the __ns_samebinaryname function new c288e032ae resolv: Add internal __ns_name_length_uncompressed function new e7c03f4765 resolv: Add DNS packet parsing helpers geared towards wire format new d9c979abf9 nss_dns: Split getanswer_ptr from getanswer_r new 32e5db3768 nss_dns: Rewrite _nss_dns_gethostbyaddr2_r and getanswer_ptr new 7267341ec1 nss_dns: Remove remnants of IPv6 address mapping new 9abc40d9b5 nss_dns: Rewrite getanswer_r to match getanswer_ptr (bug 121 [...] new c36e7cca35 nss_dns: In gaih_getanswer_slice, skip strange aliases (bug 12154) new 480c820493 resolv: Add new tst-resolv-invalid-cname new 2def56a349 nss_dns: Rewrite _nss_dns_gethostbyname4_r using current interfaces new 044755e2fa resolv: Fix building tst-resolv-invalid-cname for earlier C [...] The 14 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: NEWS | 2 + include/arpa/nameser.h | 106 +++ include/resolv.h | 3 + resolv/Makefile | 23 + resolv/README | 3 - resolv/mapv4v6addr.h | 69 -- resolv/mapv4v6hostent.h | 84 --- resolv/ns_name_length_uncompressed.c | 72 ++ resolv/ns_rr_cursor_init.c | 62 ++ resolv/ns_rr_cursor_next.c | 74 ++ resolv/ns_samebinaryname.c | 55 ++ resolv/nss_dns/dns-host.c | 1155 ++++++++++++------------------ resolv/res-name-checking.c | 14 +- resolv/tst-ns_name_length_uncompressed.c | 135 ++++ resolv/tst-ns_rr_cursor.c | 227 ++++++ resolv/tst-ns_samebinaryname.c | 62 ++ resolv/tst-resolv-aliases.c | 254 +++++++ resolv/tst-resolv-byaddr.c | 326 +++++++++ resolv/tst-resolv-invalid-cname.c | 406 +++++++++++ resolv/tst-resolv-maybe_insert_sig.h | 32 + 20 files changed, 2300 insertions(+), 864 deletions(-) delete mode 100644 resolv/mapv4v6addr.h delete mode 100644 resolv/mapv4v6hostent.h create mode 100644 resolv/ns_name_length_uncompressed.c create mode 100644 resolv/ns_rr_cursor_init.c create mode 100644 resolv/ns_rr_cursor_next.c create mode 100644 resolv/ns_samebinaryname.c create mode 100644 resolv/tst-ns_name_length_uncompressed.c create mode 100644 resolv/tst-ns_rr_cursor.c create mode 100644 resolv/tst-ns_samebinaryname.c create mode 100644 resolv/tst-resolv-aliases.c create mode 100644 resolv/tst-resolv-byaddr.c create mode 100644 resolv/tst-resolv-invalid-cname.c create mode 100644 resolv/tst-resolv-maybe_insert_sig.h -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/master-arm updated (71d64753a -> bb8a20f4f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_build/master-arm in repository toolchain/ci/base-artifacts. from 71d64753a 51: onsuccess: #452: 6: Success after binutils/gcc/glibc/gdb: [...] new bb8a20f4f 52: onsuccess: #453: 6: Success after binutils/gcc/linux/glib [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1632 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 51292 -> 52512 bytes 05-build_abe-gcc/console.log.xz | Bin 232740 -> 235032 bytes 06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 07-build_abe-linux/console.log.xz | Bin 8260 -> 8644 bytes 08-build_abe-glibc/console.log.xz | Bin 231984 -> 234328 bytes 09-build_abe-gdb/console.log.xz | Bin 49136 -> 51352 bytes 10-check_regression/console.log.xz | Bin 3232 -> 3484 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +++++++++++++++++------------------ 19 files changed, 27 insertions(+), 27 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-arm updated (3f5577eb2 -> 126fa668f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/master-arm in repository toolchain/ci/base-artifacts. discards 3f5577eb2 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits discards 71bdda861 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits discards 39f5c91f3 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits discards fe1893dcd 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits discards 6ee564e81 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits discards 5f76c691a 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits discards 0a3f78ba9 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits discards fc015fae1 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits discards 74afaadbf 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-271 [...] discards e012d595b 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits discards 9f7cf04b9 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-271 [...] discards f37a90ff2 106: onsuccess: #1702: 1: Success after gcc: 4 commits discards 0bdb0cb03 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits discards 8cd5dc741 104: onsuccess: #1700: 1: Success after gcc: 2 commits discards e548de509 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits discards d0175efa8 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits discards 2c97f0c3a 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits discards 7678ebe0b 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-250 [...] discards f2892847c 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits discards 364efedbd 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits discards 09b0e66d0 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits discards b18008d7c 96: onsuccess: #1654: 1: Success after gcc: 5 commits discards faf4c0fec 95: onsuccess: #1653: 1: Success after gcc: 13 commits discards 858d2cd2a 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits discards 748a46759 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-2393 [...] discards f749e2f8c 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits discards 2a36c9239 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-2391 [...] discards 49a97014c 90: onsuccess: #1645: 1: Success after gcc: 2 commits discards e7cd003ab 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-2388 [...] discards 37413c92e 88: onsuccess: 1: Success after binutils/gcc: 2 commits discards dd875e578 87: onsuccess: 1: Success after gcc: 6 commits discards 1ac1cefca 86: onsuccess: 1: Success after binutils/gcc: 8 commits discards bd5267eca 85: onsuccess: 1: Success after binutils/gcc: 19 commits discards 5a108ecf7 84: onsuccess: 1: Success after binutils/gcc: 2 commits discards 4e35c1b44 83: onsuccess: 1: Success after gcc: 14 commits discards 53be32f73 82: onsuccess: 1: Success after binutils/gcc: 9 commits discards bb408da13 81: onsuccess: 1: Success after binutils/gcc: 8 commits discards b98ac7096 80: onsuccess: 1: Success after binutils/gcc: 8 commits discards 825a113cc 79: onsuccess: 1: Success after binutils/gcc: 23 commits discards b350ffc8e 78: onsuccess: 1: Success after binutils/gcc: 17 commits discards 96e6d2b1a 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 73cbc71b4 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 05ce4bb01 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 62f1d5821 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits discards 65ed0a297 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 3edb206ef 72: onsuccess: 1: Successful build after baseline build: no n [...] discards d0b3681e2 71: onsuccess: 1: Successful build after binutils: PR29494 Tr [...] discards 760d3f47d 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 491a161f0 69: onsuccess: 1: Successful build after gcc: d: Merge upstre [...] discards 0f953dc26 68: onsuccess: 1: Successful build after gcc: 2 commits discards d2645e16d 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards c5f124f1e 66: onsuccess: 1: Successful build after gcc: 4 commits discards 887b9e045 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards c9f29c6bd 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards 0bcf192a7 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards e72e812a7 62: onsuccess: 1: Successful build after gcc: 4 commits discards 38c272da8 61: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 4d155e2ea 60: onsuccess: 1: Successful build after binutils/gcc: 12 commits discards 56a3be594 59: onsuccess: 1: Successful build after binutils/gcc: 29 commits discards 178f80065 58: onsuccess: 1: Successful build after binutils: ld: pe: Ma [...] discards 5b8eded48 57: onsuccess: 1: Successful build after binutils: 2 commits discards 777d235dc 56: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards 6b8c04dfa 55: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 51e7c8a29 54: onsuccess: 1: Successful build after gcc: 5 commits discards e6fe8f442 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards dd4907f64 52: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards f89d4d3ac 51: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 781f46592 50: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 8074a1f1f 49: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 6a1b53099 48: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 0cb882e19 47: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 48b95d772 46: onsuccess: 1: Successful build after baseline build: no n [...] discards 1a28e423b 45: onsuccess: 1: Successful build after binutils: Fix crash [...] discards b4fe74fd4 44: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 2c3d32fec 43: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 92b93b3ff 42: onsuccess: 1: Successful build after baseline build: no n [...] discards ac6e76b8d 41: onsuccess: 1: Successful build after gcc: 2 commits discards 08c6bf0ee 40: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 898360144 39: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 63fd035b9 38: onsuccess: 1: Successful build after gcc: 2 commits discards 26d9ae0e3 37: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 26de8ceea 36: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 2e7cbc4f4 35: onsuccess: 1: Successful build after binutils/gcc: 12 commits discards 885a899ff 34: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 8250eb19a 33: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards f7eff3c71 32: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 2713c8be6 31: onsuccess: 1: Successful build after gcc: 9 commits discards 0ada528ef 30: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards ec3cb725d 29: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 05fea15ac 28: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 07a3fe0b0 27: onsuccess: 1: Successful build after binutils/gcc: 12 commits discards 1f17234fe 26: onsuccess: 1: Successful build after binutils/gcc: 22 commits discards aa557bfd3 25: onsuccess: binutils-gcc: 1 discards 3f1946a4a 24: onsuccess: binutils-gcc: 1 discards b839c3526 23: onsuccess: binutils-gcc: 1 discards e2fdfacda 22: onsuccess: binutils-gcc: 1 discards a7a329082 21: onsuccess: binutils-gcc: 1 discards 466339328 20: onsuccess: binutils-gcc: 1 discards 54dbcf9b7 19: onsuccess: binutils-gcc: 1 discards 3b28fe419 18: onsuccess: binutils-gcc: 1 discards b5e85e29c 17: onsuccess: binutils-gcc: 1 new 8de60efb3 17: onsuccess: binutils-gcc: 1 new fe212cf8e 18: onsuccess: binutils-gcc: 1 new c8c984b3e 19: onsuccess: binutils-gcc: 1 new 709c5ffc1 20: onsuccess: binutils-gcc: 1 new 7959ba166 21: onsuccess: binutils-gcc: 1 new 2c5bbb570 22: onsuccess: binutils-gcc: 1 new ad927eff8 23: onsuccess: binutils-gcc: 1 new d9c1aafeb 24: onsuccess: binutils-gcc: 1 new a084c6473 25: onsuccess: binutils-gcc: 1 new d90eabc1a 26: onsuccess: 1: Successful build after binutils/gcc: 22 commits new bfa705c5a 27: onsuccess: 1: Successful build after binutils/gcc: 12 commits new 749b3b29b 28: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 9ebfd31a4 29: onsuccess: 1: Successful build after binutils/gcc: 3 commits new a6c871a4f 30: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 44c51514d 31: onsuccess: 1: Successful build after gcc: 9 commits new 81ac7662e 32: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 8275acb4f 33: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 1648f0eea 34: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 8f988e77e 35: onsuccess: 1: Successful build after binutils/gcc: 12 commits new 3d7490a69 36: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 2cc596976 37: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 69871d2ae 38: onsuccess: 1: Successful build after gcc: 2 commits new 72ae7779e 39: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 2b01a65ee 40: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 7f7ea8715 41: onsuccess: 1: Successful build after gcc: 2 commits new d16fd66f2 42: onsuccess: 1: Successful build after baseline build: no n [...] new ddf4824da 43: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 984e6f355 44: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 34ddaed50 45: onsuccess: 1: Successful build after binutils: Fix crash [...] new f70126a5c 46: onsuccess: 1: Successful build after baseline build: no n [...] new f78e78464 47: onsuccess: 1: Successful build after binutils/gcc: 4 commits new f4915c58f 48: onsuccess: 1: Successful build after binutils/gcc: 6 commits new b19c7c176 49: onsuccess: 1: Successful build after binutils/gcc: 3 commits new e828a53cf 50: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 79dc9e4d0 51: onsuccess: 1: Successful build after binutils/gcc: 4 commits new df46605c5 52: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 09ce8f2fa 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 7410243e4 54: onsuccess: 1: Successful build after gcc: 5 commits new f2f937670 55: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 1e779f50f 56: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 9cf872c29 57: onsuccess: 1: Successful build after binutils: 2 commits new 77ae52384 58: onsuccess: 1: Successful build after binutils: ld: pe: Ma [...] new 8a79bd9c8 59: onsuccess: 1: Successful build after binutils/gcc: 29 commits new bfa958cd2 60: onsuccess: 1: Successful build after binutils/gcc: 12 commits new 8b03fb03d 61: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 43f3ba6a2 62: onsuccess: 1: Successful build after gcc: 4 commits new ef538f616 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 32a4d5991 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits new 519585d0d 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits new 741d5a9a5 66: onsuccess: 1: Successful build after gcc: 4 commits new e1b72f892 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 775852209 68: onsuccess: 1: Successful build after gcc: 2 commits new 2fa7eefae 69: onsuccess: 1: Successful build after gcc: d: Merge upstre [...] new c174b618c 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 4d790b8cb 71: onsuccess: 1: Successful build after binutils: PR29494 Tr [...] new 277212f54 72: onsuccess: 1: Successful build after baseline build: no n [...] new 654264678 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits new e7adb1c5f 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits new ae25f0adf 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits new b45ffce80 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits new f4f0a6555 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 040aeea07 78: onsuccess: 1: Success after binutils/gcc: 17 commits new d832b58e8 79: onsuccess: 1: Success after binutils/gcc: 23 commits new 63d772edd 80: onsuccess: 1: Success after binutils/gcc: 8 commits new 80b7d11aa 81: onsuccess: 1: Success after binutils/gcc: 8 commits new 65af56097 82: onsuccess: 1: Success after binutils/gcc: 9 commits new 6d748d3d8 83: onsuccess: 1: Success after gcc: 14 commits new 9fde268bc 84: onsuccess: 1: Success after binutils/gcc: 2 commits new 20975c13a 85: onsuccess: 1: Success after binutils/gcc: 19 commits new c340b63c7 86: onsuccess: 1: Success after binutils/gcc: 8 commits new 4fbe4a74c 87: onsuccess: 1: Success after gcc: 6 commits new e21223a8a 88: onsuccess: 1: Success after binutils/gcc: 2 commits new 7c452adc3 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-2388 [...] new eb70d7725 90: onsuccess: #1645: 1: Success after gcc: 2 commits new fd1c96ace 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-2391 [...] new 13b18f3e5 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits new 9b3c1f74c 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-2393 [...] new f5ec77255 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits new 8995205b8 95: onsuccess: #1653: 1: Success after gcc: 13 commits new c7b1cd00e 96: onsuccess: #1654: 1: Success after gcc: 5 commits new b3d363e16 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits new 17710ae9a 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits new edd89aa5a 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits new f831383cf 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-250 [...] new 4f65d8141 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits new 6601f5955 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits new 3add4e91f 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits new beb524240 104: onsuccess: #1700: 1: Success after gcc: 2 commits new f8e51873d 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits new 7a9034b36 106: onsuccess: #1702: 1: Success after gcc: 4 commits new 75d1ecc18 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-271 [...] new f0e73648b 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits new 6ebecf36c 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-271 [...] new 18060dad3 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits new 6033e983b 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits new e3d326645 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits new 787c891d4 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits new 5450073e0 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits new a6505bd97 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits new 400d4f11c 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits new 13ebd7332 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits new 126fa668f 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (3f5577eb2) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (12 [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1664 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2704 bytes 03-build_abe-binutils/console.log.xz | Bin 50616 -> 51804 bytes 04-build_abe-gcc/console.log.xz | Bin 232532 -> 232648 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3804 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2568 -> 2512 bytes 07-check_regression/console.log.xz | Bin 5108 -> 4132 bytes 07-check_regression/extra-bisect-params | 1 - 07-check_regression/fails.sum | 11 - 07-check_regression/mail-body.txt | 22 +- 07-check_regression/results.compare | 55 +- 07-check_regression/results.compare2 | 75 +- 07-check_regression/results.regressions | 56 - 08-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 24 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 56 - sumfiles/g++.log.xz | Bin 2764948 -> 2767308 bytes sumfiles/g++.sum | 118 +- sumfiles/gcc.log.xz | Bin 2383248 -> 2385692 bytes sumfiles/gcc.sum | 4634 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 903920 -> 908756 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2172 -> 2180 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 204284 -> 204152 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2532 -> 2544 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 465604 -> 466492 bytes sumfiles/libstdc++.sum | 10 +- 36 files changed, 2488 insertions(+), 2706 deletions(-) delete mode 100644 07-check_regression/extra-bisect-params delete mode 100644 07-check_regression/fails.sum delete mode 100644 07-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[glibc] branch master updated (fd36873ff9 -> 385f2ecda9)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository glibc. from fd36873ff9 elf: Use C11 atomics on _dl_mcount new 9ba0f010a6 hurd: Add _IOT_ifrtreq to <net/route.h> new b84199eb18 hurd: Drop struct rtentry and in6_rtmsg new 385f2ecda9 hurd: Fix SIOCADD/DELRT ioctls The 3 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: sysdeps/mach/hurd/bits/ioctls.h | 4 ++-- sysdeps/mach/hurd/net/route.h | 39 +-------------------------------------- 2 files changed, 3 insertions(+), 40 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_O3 updated (ee6992bfc -> 92392a29d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_O3 in repository toolchain/ci/base-artifacts. from ee6992bfc 13: onsuccess: #122: 2: Success after binutils/gcc: 10 commits new 92392a29d 14: onsuccess: #123: 2: Success after binutils/gcc: 12 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1672 -> 1648 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 51788 -> 52144 bytes 05-build_abe-bootstrap_O3/console.log.xz | Bin 461500 -> 464300 bytes 06-check_regression/console.log.xz | Bin 2148 -> 2152 bytes 07-update_baseline/console.log | 9 --------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++++--------- 13 files changed, 15 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (81db82c2e -> 4e4736de9)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards 81db82c2e 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/gd [...] discards 1c1f3ce9b 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/gd [...] discards 7287bcccc 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/gl [...] discards f869f3a11 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/gd [...] discards cbfc38059 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards c5536f87d 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards b035ffc0a 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 74ef9a315 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/gd [...] discards a95793fd5 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-271 [...] discards 65a4e010d 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards c93b2d532 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...] discards d42c8054b 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] discards fd1fc7253 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 2adf37029 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] discards 0900136c9 99: onsuccess: #2074: 1: Success after baseline build: no new [...] discards b70cd855a 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards b51813179 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards ea4cd3eee 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 763e37f57 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] discards 09934e304 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] discards 30324ebc2 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 397281c37 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 6435cb139 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards e25005cfa 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards f24f5ad2b 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 9249afd90 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 3102e45da 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 063280d48 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 4ec0985ec 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards ed624ff44 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 2ac2557d9 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards da132e6d8 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards cc65f2447 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits discards dea5c1796 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards a13af89e7 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 8635343de 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 3db47de37 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits discards 05c47cce5 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 417f657ad 75: onsuccess: 1: Successful build after linux: 44 commits discards 0ed1bb346 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards f97371327 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b4518438c 72: onsuccess: 1: Successful build after linux: 12 commits discards 86a6277c3 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards fc83feac1 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 7f064315c 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards cdc8d24a5 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 73430a4c2 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] discards 72054d279 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards fc6e9eabb 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 66137bf6d 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 5120d3224 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards a8a8119a2 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] discards 2b2207674 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards d89dca92d 60: onsuccess: 1: Successful build after glibc: 2 commits discards 46c5f3876 59: onsuccess: 1: Successful build after binutils: 2 commits discards 6418f9f57 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] discards 4bdf577aa 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards e62ea6332 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e03f7152d 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] discards cf680d33f 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 6abe05f2e 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 272c25136 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits discards 6ebc58887 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards d774ddfee 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 0bafd6548 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 6b75dcc36 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards dd5ca3872 47: onsuccess: 1: Successful build after linux: 10 commits discards 75857f86b 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 9ed71a364 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 02ab4bb45 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards bb75eb203 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards b9af34dc5 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] discards ae3caa0a6 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 675e14c74 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards 59fb7dd0c 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 8296b92c5 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards 784be32c5 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards b2c1b11f7 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards d97205c39 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards b99b2bfb7 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 0baeeb62f 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 40187dbc5 32: onsuccess: 1: Successful build after gcc: 7 commits discards c0f379888 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 825d75ea4 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards b0173c74c 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 1b4e92fb8 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards ca132b284 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 25 [...] discards 12e9db773 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 535a464b6 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 4c088258f 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 7f7a2676a 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a846b62d8 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f55ed9ebc 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 2da53b316 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b8ea61b87 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c01d98bd5 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 01c5e05da 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f5e4f495a 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a2ed40cc4 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e2a21b8ee 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 834f4cb5d 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 75b0046d9 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 76b5496b8 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b59cb0c86 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 1944bc2fa 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 12c3ec638 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 05276b493 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 7d828e8be 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b208c0870 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8950f7ca6 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 453727fec 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 963cf5d27 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 256b8b227 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ea00214c9 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 7575bb1f2 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d23e8d055 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 25 [...] new 4d6bfcc24 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 9e9dc21db 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 8df63be7b 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 5c2d084a0 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 5bd2597b1 32: onsuccess: 1: Successful build after gcc: 7 commits new 47a0402bd 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 9ee0ae88f 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 14e41293c 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new b8fa65dce 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 0670d0b3b 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 98b15bd02 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new d96e5c31f 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new a25826e14 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new a9c114966 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c104b2f8e 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] new 73954d358 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 6cf0c6973 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 1805d01c0 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 6e223668a 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 6169b4923 47: onsuccess: 1: Successful build after linux: 10 commits new 0ec3af9db 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new cf8f7ef94 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 3624c02a2 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 6fb0b9658 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 7afe02efc 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits new 4ee829b01 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new ae09e4918 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 29bd93db2 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] new a549c20c4 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new dd7e913bc 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 0f2943e83 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] new f298d4009 59: onsuccess: 1: Successful build after binutils: 2 commits new 8ffb9f39a 60: onsuccess: 1: Successful build after glibc: 2 commits new 9ef32dec9 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 2b34d64a3 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] new 2a22bded3 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 8a2de5467 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c3309a7a0 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a5f25cbf6 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new fb5c09dea 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] new d624e16bb 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 1f14a1da6 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new dd04dc007 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 904d479d0 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 7e4442642 72: onsuccess: 1: Successful build after linux: 12 commits new e87f54e29 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 7b858ed67 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 5c0840568 75: onsuccess: 1: Successful build after linux: 44 commits new c7f26f047 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 70612a5f9 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits new 11cfbf7be 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 7782212ab 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 6ab0c4981 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 0cc9250e9 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits new 912a86ed7 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new 54f29b0f3 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new dac818a27 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 1c3bc8e30 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 4a5b2a881 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new dcbb68c6f 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new ef4aa1140 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 7a3578446 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 1bbfc8f34 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 292c4b743 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new d04d8646d 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new b4d3337f5 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new eae0feadf 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] new e3c76b7a8 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] new 5107263cd 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 22902e540 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new df9e3b356 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new a2cf0dad0 99: onsuccess: #2074: 1: Success after baseline build: no new [...] new 4455e2ebf 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] new 65a4f24fe 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 47e57e340 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] new 5be214ca2 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...] new 36b70af86 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 8086e4fd8 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-271 [...] new d4f4eb28f 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/gd [...] new 626f345c3 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 7fd70efc1 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 397b5a02e 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new adbc862ff 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/gd [...] new 59faa85ad 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/gl [...] new 4cbde58eb 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/gd [...] new 0ded324dd 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/gd [...] new 4e4736de9 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/gd [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (81db82c2e) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1716 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 30988 -> 30268 bytes 04-build_abe-stage1/console.log.xz | Bin 73504 -> 72492 bytes 06-build_abe-linux/console.log.xz | Bin 8600 -> 8584 bytes 07-build_abe-glibc/console.log.xz | Bin 240152 -> 239288 bytes 08-build_abe-stage2/console.log.xz | Bin 206912 -> 203488 bytes 09-build_abe-gdb/console.log.xz | Bin 38468 -> 37464 bytes 10-build_abe-qemu/console.log.xz | Bin 31544 -> 31264 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3928 -> 3892 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3452 -> 2672 bytes 13-check_regression/console.log.xz | Bin 21468 -> 32812 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 572 +-- 13-check_regression/mail-body.txt | 170 +- 13-check_regression/results.compare | 117 +- 13-check_regression/results.compare2 | 5877 ++++++++++++++++++----- 13-check_regression/results.regressions | 136 +- 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 172 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 136 +- sumfiles/g++.log.xz | Bin 3421100 -> 3396252 bytes sumfiles/g++.sum | 3432 ++++++-------- sumfiles/gcc.log.xz | Bin 2986720 -> 3022208 bytes sumfiles/gcc.sum | 7885 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1024924 -> 1027216 bytes sumfiles/gfortran.sum | 16 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201916 -> 202104 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2660 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 426136 -> 426948 bytes sumfiles/libstdc++.sum | 84 +- 43 files changed, 10514 insertions(+), 8218 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_ubsan updated (9133c747e2 -> a23ac71e08)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_ubsan in repository toolchain/ci/base-artifacts. from 9133c747e2 46: onsuccess: #454: 2: Success after binutils/gcc: 27 commits new a23ac71e08 47: onsuccess: #455: 2: Success after binutils/gcc: 47 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1628 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 50904 -> 51796 bytes 05-build_abe-bootstrap_ubsan/console.log.xz | Bin 529512 -> 529888 bytes 06-check_regression/console.log.xz | Bin 2496 -> 2368 bytes 07-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++++--------- 13 files changed, 16 insertions(+), 16 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits September 2022