Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[gcc] branch master updated (866263a5fe0 -> 06aa66af7d0)

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 gcc. from 866263a5fe0 libstdc++: Fix tests broken by C++23 P2266R3 "Simpler impli [...] new 53acc10ee81 c: Adjust LDBL_EPSILON for C2x for IBM long double new 06aa66af7d0 arm: Add missing early clobber to MVE vrev64q_m patterns 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: gcc/c-family/c-cppbuiltin.cc | 2 +- gcc/config/arm/mve.md | 4 ++-- gcc/testsuite/gcc.dg/c11-float-7.c | 24 ++++++++++++++++++++++ gcc/testsuite/gcc.dg/c2x-float-12.c | 19 +++++++++++++++++ .../{vcreateq_f16.c => vrev64q_m_s16-clobber.c} | 12 +++++++---- 5 files changed, 54 insertions(+), 7 deletions(-) create mode 100644 gcc/testsuite/gcc.dg/c11-float-7.c create mode 100644 gcc/testsuite/gcc.dg/c2x-float-12.c copy gcc/testsuite/gcc.target/arm/mve/intrinsics/{vcreateq_f16.c => vrev64q_m_s16- [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/master-aarch64 updated (a1b127937e -> 0e5297e3c0)

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-aarch64 in repository toolchain/ci/base-artifacts. from a1b127937e 56: onsuccess: #470: 6: Success after binutils/gcc/linux/gli [...] new 0e5297e3c0 57: onsuccess: #471: 6: Success after binutils/gcc/linux/gdb [...] 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 1708 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2712 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 37928 -> 37620 bytes 05-build_abe-gcc/console.log.xz | Bin 213900 -> 212868 bytes 07-build_abe-linux/console.log.xz | Bin 9076 -> 8388 bytes 08-build_abe-glibc/console.log.xz | Bin 241736 -> 241320 bytes 09-build_abe-gdb/console.log.xz | Bin 38244 -> 38212 bytes 10-check_regression/console.log.xz | Bin 4312 -> 4332 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++++++++++----------------- 17 files changed, 25 insertions(+), 25 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-norov-allnoconfig updated (73b23fb30d -> 19f0c52f98)

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-master-arm-norov-allnoconfig in repository toolchain/ci/base-artifacts. from 73b23fb30d 10: onsuccess: #39: all: Success after binutils/gcc/linux/qe [...] new 19f0c52f98 11: onsuccess: #40: 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 1704 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30132 -> 29908 bytes 04-build_abe-stage1/console.log.xz | Bin 90756 -> 90664 bytes 05-build_abe-qemu/console.log.xz | Bin 31076 -> 31568 bytes 06-build_linux/console.log.xz | Bin 4008 -> 4004 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4284 -> 4364 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 | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[binutils-gdb] branch master updated (01292987969 -> 907b52f4ceb)

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 01292987969 RISC-V: Move supervisor instructions after all unprivileged ones new 907b52f4ceb readelf: DO not load section headers from file offset zero 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: binutils/ChangeLog | 6 ++++++ binutils/readelf.c | 13 +++++++++++++ 2 files changed, 19 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_O3 updated (35da6c049c -> b5c68f708d)

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_O3 in repository toolchain/ci/base-artifacts. from 35da6c049c 53: onsuccess: #471: 2: Success after binutils/gcc: 8 commits new b5c68f708d 54: onsuccess: #472: 2: Success after binutils/gcc: 33 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 1704 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2716 bytes 04-build_abe-binutils/console.log.xz | Bin 52260 -> 51168 bytes 05-build_abe-bootstrap_O3/console.log.xz | Bin 464336 -> 462788 bytes 06-check_regression/console.log.xz | Bin 2856 -> 3084 bytes 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 | 20 ++++++++++---------- 12 files changed, 16 insertions(+), 16 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-norov-allyesconfig updated (04f07cf748 -> acc9c2ab8f)

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/llvm-master-arm-norov-allyesconfig in repository toolchain/ci/base-artifacts. from 04f07cf748 19: onsuccess: #71: 36: Success after llvm: 172 commits new acc9c2ab8f 20: onsuccess: #72: 20867: Success after binutils/llvm/linux [...] 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 1688 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 30272 -> 30316 bytes 04-build_kernel_llvm/console.log.xz | Bin 62988 -> 64524 bytes 05-build_abe-qemu/console.log.xz | Bin 32364 -> 31880 bytes 06-build_linux/console.log.xz | Bin 3936 -> 5140 bytes 08-check_regression/console.log.xz | Bin 3024 -> 4548 bytes 08-check_regression/mail-body.txt | 9 +-------- 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 11 ++--------- mail/mail-subject.txt | 2 +- manifest.sh | 31 +++++++++++++++++-------------- results | 2 +- 19 files changed, 32 insertions(+), 43 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled updated (936596c154 -> c34c500ab8)

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-aarch64-bootstrap_profiled in repository toolchain/ci/base-artifacts. from 936596c154 50: onsuccess: #446: 1: Success after gcc: 16 commits new c34c500ab8 51: onsuccess: #447: 2: Success after binutils/gcc: 182 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 1724 -> 1628 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 37732 -> 38336 bytes 05-build_abe-bootstrap_profiled/console.log.xz | Bin 79832 -> 514804 bytes 06-check_regression/console.log.xz | Bin 2660 -> 3172 bytes 06-check_regression/mail-body.txt | 13 +------------ 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 | 15 ++------------- mail/mail-subject.txt | 2 +- manifest.sh | 19 ++++++++++--------- results | 2 +- 15 files changed, 28 insertions(+), 40 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-norov-defconfig updated (4ab739735c -> 033d944c3a)

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-norov-defconfig in repository toolchain/ci/base-artifacts. from 4ab739735c 10: onsuccess: #38: boot: Success after binutils/gcc/linux/q [...] new 033d944c3a 11: onsuccess: #39: boot: Success after binutils/gcc/linux/q [...] 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 1696 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30028 -> 29708 bytes 04-build_abe-stage1/console.log.xz | Bin 87224 -> 86692 bytes 05-build_abe-qemu/console.log.xz | Bin 31956 -> 30728 bytes 06-build_linux/console.log.xz | Bin 3424 -> 3428 bytes 07-boot_linux/console.log.xz | Bin 5824 -> 5844 bytes 08-check_regression/console.log.xz | Bin 3956 -> 4240 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 | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-arm updated (d5ad2f906f -> cbf65dff56)

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 d5ad2f906f 156: onsuccess: #1776: 1: Success after binutils/gcc: 4 commits discards 4ee7f86097 155: onsuccess: #1775: 1: Success after binutils: 2 commits discards f7192e2727 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 commits discards 953dea0485 153: onsuccess: #1773: 1: Success after gcc: 4 commits discards ac1377b41f 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits discards 314556c05b 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] discards fb6b7fc8f2 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] discards 6f19307b6f 149: onsuccess: #1769: 1: Success after gcc: 3 commits discards fce1c993cb 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits discards 8fb7a5c6e4 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits discards ce5f8fb3b3 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits discards 442a5c6c01 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits discards 2fc2dfd0f6 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits discards 467524e75d 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits discards c5f4c2f5c4 142: onsuccess: #1761: 1: Success after gcc: 83 commits discards 474bed3325 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] discards eae50328cc 140: onsuccess: #1756: 1: Success after binutils: 3 commits discards a20a0ef94c 139: onsuccess: #1753: 1: Success after binutils: 5 commits discards da71314b51 138: onsuccess: #1749: 1: Success after binutils: 5 commits discards c477bf0e83 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] discards b9f6a54251 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] discards cddb7cbb4a 135: onsuccess: #1739: 1: Success after binutils: 4 commits discards 5448d508e5 134: onsuccess: #1736: 1: Success after binutils: 3 commits discards 34c1cee3e8 133: onsuccess: #1733: 1: Success after binutils: 3 commits discards 7663d16749 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits discards ddd5049e2e 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits discards 79ff462ac2 130: onsuccess: #1729: 1: Success after gcc: 9 commits discards 93dd29dacb 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] discards 862913b7a6 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits discards d90a7b8374 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] discards cd9c34fb84 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits discards 88c2dde081 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits discards f4ac77841c 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits discards 19ba7cf16e 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits discards 5fe2b8f63e 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits discards 717602683f 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits discards e277a5ed68 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits discards c15aec552c 119: onsuccess: #1715: 1: Success after binutils: 4 commits discards c6f51c00e7 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits discards 11c610e9b4 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits discards 7e6f81e755 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits discards 9556446c1c 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits discards 2355a29f43 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits discards 798db5d99f 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits discards 49c15a8028 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits discards 2580e2d998 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits discards db8ff18837 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits discards 3702522239 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] discards 6e5c79a2f8 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits discards 7231233cd0 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] discards 08fa285679 106: onsuccess: #1702: 1: Success after gcc: 4 commits discards b2b23c6940 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits discards fd8b9cbbde 104: onsuccess: #1700: 1: Success after gcc: 2 commits discards d116ea3ba5 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits discards e2bc26d662 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits discards 013af144db 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits discards 4c83116b68 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] discards 8b72cb2ede 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits discards a8012f1bcf 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits discards c8a53e05b3 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits discards 2ea4cdb2f0 96: onsuccess: #1654: 1: Success after gcc: 5 commits discards 812edb513a 95: onsuccess: #1653: 1: Success after gcc: 13 commits discards 09e463ccab 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits discards a4db3aaae7 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] discards 4dad260312 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits discards ff3a46bd1f 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] discards b02007acd7 90: onsuccess: #1645: 1: Success after gcc: 2 commits discards 24d0685342 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] discards 110e9e6942 88: onsuccess: 1: Success after binutils/gcc: 2 commits discards 1b1e62e456 87: onsuccess: 1: Success after gcc: 6 commits discards acef546356 86: onsuccess: 1: Success after binutils/gcc: 8 commits discards 918ead87e1 85: onsuccess: 1: Success after binutils/gcc: 19 commits discards bf454bc9cd 84: onsuccess: 1: Success after binutils/gcc: 2 commits discards 8ff42c0fa7 83: onsuccess: 1: Success after gcc: 14 commits discards 67e7a9b3c1 82: onsuccess: 1: Success after binutils/gcc: 9 commits discards 52ae058f77 81: onsuccess: 1: Success after binutils/gcc: 8 commits discards 4e759d7a82 80: onsuccess: 1: Success after binutils/gcc: 8 commits discards 6a8a25d2c2 79: onsuccess: 1: Success after binutils/gcc: 23 commits discards a44e62cdb3 78: onsuccess: 1: Success after binutils/gcc: 17 commits discards 3925512906 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 2b4f423ce3 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 2f911cd62f 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 3d9193a8d9 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits discards 07a3f1df82 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 2f5eff3b5d 72: onsuccess: 1: Successful build after baseline build: no [...] discards 90a2e06f0a 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards a3a3008b1d 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards cdc3cf4e29 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] discards 580b932a50 68: onsuccess: 1: Successful build after gcc: 2 commits discards 43aee283f0 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards c6e165ad2d 66: onsuccess: 1: Successful build after gcc: 4 commits discards 8280af0921 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards 98d77928d3 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards bc3ed34d8c 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards fdcce19f14 62: onsuccess: 1: Successful build after gcc: 4 commits discards 3c86daa0b9 61: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards e14280600c 60: onsuccess: 1: Successful build after binutils/gcc: 12 commits discards b309b2ac20 59: onsuccess: 1: Successful build after binutils/gcc: 29 commits discards 47723a78d3 58: onsuccess: 1: Successful build after binutils: ld: pe: M [...] discards 361b293cc1 57: onsuccess: 1: Successful build after binutils: 2 commits discards deb1f7741f 56: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 7d65723ea7 56: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 17d222699f 57: onsuccess: 1: Successful build after binutils: 2 commits new f1c1a9c6b8 58: onsuccess: 1: Successful build after binutils: ld: pe: M [...] new 6179cb15e0 59: onsuccess: 1: Successful build after binutils/gcc: 29 commits new 1f2c11007c 60: onsuccess: 1: Successful build after binutils/gcc: 12 commits new eb3b8a4006 61: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 4591edb6a1 62: onsuccess: 1: Successful build after gcc: 4 commits new 2d377def71 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits new c9f84edf5e 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits new c562f82b3c 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits new 9da9abc495 66: onsuccess: 1: Successful build after gcc: 4 commits new 2d4daa5fef 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 960cf10bbb 68: onsuccess: 1: Successful build after gcc: 2 commits new 0051b20df0 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] new 8a13f56d1a 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits new d762822ba5 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] new 306e38d5f5 72: onsuccess: 1: Successful build after baseline build: no [...] new 739622183a 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits new 282ccf8acf 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits new 0561c35f37 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 09630815a7 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 482cfbba2b 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 44e2d9f137 78: onsuccess: 1: Success after binutils/gcc: 17 commits new 1d0d15e94d 79: onsuccess: 1: Success after binutils/gcc: 23 commits new 7c5d568cd9 80: onsuccess: 1: Success after binutils/gcc: 8 commits new 3368040dee 81: onsuccess: 1: Success after binutils/gcc: 8 commits new 49a1f2a06c 82: onsuccess: 1: Success after binutils/gcc: 9 commits new 0b0d1ef87d 83: onsuccess: 1: Success after gcc: 14 commits new 12782ee156 84: onsuccess: 1: Success after binutils/gcc: 2 commits new 312e55123b 85: onsuccess: 1: Success after binutils/gcc: 19 commits new 50bda34cc1 86: onsuccess: 1: Success after binutils/gcc: 8 commits new d0208a3367 87: onsuccess: 1: Success after gcc: 6 commits new c1d43adee4 88: onsuccess: 1: Success after binutils/gcc: 2 commits new 6ba25f4614 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] new 6c8c01a8fc 90: onsuccess: #1645: 1: Success after gcc: 2 commits new 5af8182fbf 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] new c97517fa2c 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits new 1d1b92d38a 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] new fcb8f9bc0e 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits new 39e916dee5 95: onsuccess: #1653: 1: Success after gcc: 13 commits new fbc0c67e0d 96: onsuccess: #1654: 1: Success after gcc: 5 commits new 675a4702de 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits new b8cd0ec5cf 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits new ca93f20f33 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits new 51049d20b2 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] new e690c1514e 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits new 1a9585115d 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits new f5cf9a3eeb 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits new 310665f35e 104: onsuccess: #1700: 1: Success after gcc: 2 commits new 3aafb6bade 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits new c09d5bf1ac 106: onsuccess: #1702: 1: Success after gcc: 4 commits new 4a192b18ed 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] new 8c3e0369b8 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits new e15aec31cf 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] new f53097ea5e 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits new 3d1ab90256 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits new e998909587 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits new 5b3ec4b8e1 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits new 5285c6d65d 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits new b38eb3218d 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits new 7ab8839e79 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits new 7b6ac8846a 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits new a9f896b98d 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits new e454f52414 119: onsuccess: #1715: 1: Success after binutils: 4 commits new e1f9ad85d1 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits new 861085d662 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits new 4ce21a23de 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits new 80a7fc0cb6 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits new ce69fb0f90 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits new 98acf71a57 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits new 80230ab1ca 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits new 477830da1a 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] new 9d6f5db5f3 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits new be65363a6f 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] new f386b0f8d8 130: onsuccess: #1729: 1: Success after gcc: 9 commits new 47cd3ac957 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits new 5adc6198ad 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits new b82db5a742 133: onsuccess: #1733: 1: Success after binutils: 3 commits new 1a67de6406 134: onsuccess: #1736: 1: Success after binutils: 3 commits new d8ee7b3458 135: onsuccess: #1739: 1: Success after binutils: 4 commits new 3a74efdab3 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] new 3e4bbba939 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] new 00f7406c29 138: onsuccess: #1749: 1: Success after binutils: 5 commits new 6cce9d5a67 139: onsuccess: #1753: 1: Success after binutils: 5 commits new 963596e230 140: onsuccess: #1756: 1: Success after binutils: 3 commits new 75901cb09f 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] new 0159366fdc 142: onsuccess: #1761: 1: Success after gcc: 83 commits new 626ecbddab 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits new 1ebb8421e7 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits new 59065d8c52 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits new b1abfee52d 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits new e1c96978ba 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits new 8c3fe43511 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits new 36e23123fa 149: onsuccess: #1769: 1: Success after gcc: 3 commits new 9a07dfa8df 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] new d3aa85ed56 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] new 939e978497 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits new dc2228876d 153: onsuccess: #1773: 1: Success after gcc: 4 commits new 7f94fe9d36 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 commits new 719448f2e9 155: onsuccess: #1775: 1: Success after binutils: 2 commits new d29caa3467 156: onsuccess: #1776: 1: Success after binutils/gcc: 4 commits new cbf65dff56 157: onsuccess: #1777: 1: Success after binutils/gcc: 3 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 (d5ad2f906f) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (cb [...] 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 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2712 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 50648 -> 50744 bytes 04-build_abe-gcc/console.log.xz | Bin 234492 -> 231760 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3808 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2396 -> 2532 bytes 07-check_regression/console.log.xz | Bin 4468 -> 4784 bytes 07-check_regression/results.compare | 17 + 07-check_regression/results.compare2 | 23 +- 08-update_baseline/console.log | 58 +- 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 | 20 +- sumfiles/g++.log.xz | Bin 2782780 -> 2774124 bytes sumfiles/g++.sum | 6 +- sumfiles/gcc.log.xz | Bin 2380156 -> 2360900 bytes sumfiles/gcc.sum | 4306 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 912348 -> 912528 bytes sumfiles/gfortran.sum | 16 +- sumfiles/libatomic.log.xz | Bin 2160 -> 2164 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 204428 -> 204668 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2548 -> 2544 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 464160 -> 460852 bytes sumfiles/libstdc++.sum | 2 +- 31 files changed, 2247 insertions(+), 2219 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (068e421f86 -> 25eb8ef8dc)

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 068e421f86 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 01fc05a6e0 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards a82a0c79f4 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 160de55447 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards cd65df7f83 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 26b5195b47 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 848f26f1ca 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards b583b3e130 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 49de3f8e9c 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 8eb6bc0599 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 9e4f4174f3 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 563cb87b5a 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards b084eed31a 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 4b6a42f6ea 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards bc70d1cf0c 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 28d10fffde 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 274ea7ab1a 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards e83b49d640 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 419600e248 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards c4a6b1ec5e 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards e183ab7241 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 0f44721c69 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 0f0d5e2c54 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards ba42e673a9 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 0b9b399ff9 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards da022fa3ec 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 87824472f2 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards f9d96f8030 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards c9fa4b4feb 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 4021a0cc2e 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 83e91162bf 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 2a4f7d9d66 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards cdfd41346c 124: onsuccess: #2159: 1: Success after linux: 23 commits discards a1383f684c 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards e55547bd7f 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 4fd81086d0 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards b86257f97a 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 4429de90df 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards d5b194c71e 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards f53de9ff16 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards aa5de271bd 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 05e681558d 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards ca424385e8 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards de5f591f6b 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 11c3043304 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards dd3f88e809 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards e39c873921 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 36233c6494 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards bddd2aa1cb 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 1390536b91 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 7487b7463a 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 091a9c0570 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 14b1242b04 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards eec9ff7b4a 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 51124edaa5 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards de1e25c2a8 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards ff4d305d35 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 936a8d905f 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 1ff02ff4ae 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 4eb248c844 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards fda124138b 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 37ea60cce9 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 90e3674ae5 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 0821d1e404 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 3f8fe43fea 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 1909a930af 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 893172ad2d 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 16e3725d79 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 3b75bb8b83 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 4109ce9398 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards a21ab63670 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 4703574521 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards d3962ad708 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards fe62cb5d21 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 74365579cf 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards a6a9e5534e 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 531759ca59 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards e784f0173d 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards e87545e12a 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards e35b3786f3 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 3687b0307a 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 91ebf9353d 75: onsuccess: 1: Successful build after linux: 44 commits discards d7eca240ef 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards a70a667c2c 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2cd28e09ff 72: onsuccess: 1: Successful build after linux: 12 commits discards d467ec9847 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards eec562af1d 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 6fc9b72e77 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 84fa7d72aa 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 63cd8bc3a6 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 247b31a4d6 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 0790c6b1bb 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0dac5fc1ac 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6867a62829 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 28a6af862b 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards a3bd176a1e 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 1daffc42f1 60: onsuccess: 1: Successful build after glibc: 2 commits discards 0616675025 59: onsuccess: 1: Successful build after binutils: 2 commits discards 0f13b1f63a 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 826db87721 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 1758f18e34 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e3a5dee840 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b215787d77 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new e22e3b06ac 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 38afd41ce6 59: onsuccess: 1: Successful build after binutils: 2 commits new 67aed3f8e6 60: onsuccess: 1: Successful build after glibc: 2 commits new cfac6c4c4b 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 6896343c4b 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new af936b6a30 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new daa0a9ea72 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c99eef1102 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d217d796bb 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new f6ec6051bb 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 4353660b0c 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3b90ec1437 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 69a9e95dcb 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new db94db49e4 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new a73ce032b2 72: onsuccess: 1: Successful build after linux: 12 commits new 035cc42d97 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9b9a2188b5 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 19e855aa20 75: onsuccess: 1: Successful build after linux: 44 commits new ab54080669 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0a9e06a5ec 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new d28b8248fb 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 6baaa2c2bb 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new fd1e3f2303 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 1985fee0de 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new ec2a676b9c 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 4a63e188c2 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 91eee9321c 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new afbcdc1e47 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 6fde556902 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 07e1e4b8a3 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 20a97b86f8 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new b23883226d 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 78d03360df 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 96d062a69c 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 046ddbd95d 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new d45a595d05 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new cf1133abdd 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 4404f4de81 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 15eefe67df 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 5261cd439b 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new e527246415 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 61f546aeec 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new ae6b79e362 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new a9cd644924 101: onsuccess: #2130: 1: Success after binutils: 81 commits new e18983a345 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 8602eb7df0 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new ef7784f6a5 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new baed0756b9 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 96fd1ae7ee 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 363ba30318 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 7a75d8fc1c 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 38dead2eb8 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 983ee7e6c8 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 36faf4da03 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 0f57d3a769 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 7423c7f638 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 1f76398cab 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 602c538d60 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new aa01867ca9 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new e1e996992f 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 42664ac6a2 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 625546d305 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new f2171341b9 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 6bbc636a40 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 713d0a78d8 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 0859b95d96 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new a0126ed71f 124: onsuccess: #2159: 1: Success after linux: 23 commits new 873cd7937f 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 5968918e1b 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 704ec862f4 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 2e31b3a5de 128: onsuccess: #2163: 1: Success after linux: 23 commits new 334927ee5e 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 656e61d493 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 1755ab453b 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 6b005e6f90 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new a1b5b6970f 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new f204d97362 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 784d2196a4 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 164a593580 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new f669c09e2f 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 72b724315c 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new b6bf550c15 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 59d966fef5 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 1a382759a7 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 5c437441eb 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 1ea3dcfb33 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new c37396202d 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 37b8037a7a 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new e3a2c90c9c 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new eea98d80a6 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 76a6be61d0 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new f88483dd79 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new c0eb4d2512 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 4c5d0c6d1e 151: onsuccess: #2186: 1: Success after gcc: 2 commits new a84bd4fd9a 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 1aca0ae517 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new be6c3e297e 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new efb9c5d4e3 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 46805b8f4b 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 25eb8ef8dc 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 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 (068e421f86) \ 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 1748 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30136 -> 30720 bytes 04-build_abe-stage1/console.log.xz | Bin 72460 -> 72340 bytes 06-build_abe-linux/console.log.xz | Bin 8320 -> 8328 bytes 07-build_abe-glibc/console.log.xz | Bin 239796 -> 240108 bytes 08-build_abe-stage2/console.log.xz | Bin 203216 -> 203088 bytes 09-build_abe-gdb/console.log.xz | Bin 37548 -> 37928 bytes 10-build_abe-qemu/console.log.xz | Bin 31928 -> 31776 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3896 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2440 -> 2600 bytes 13-check_regression/console.log.xz | Bin 6008 -> 5856 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 8 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 32 +- 13-check_regression/results.compare2 | 38 +- 13-check_regression/results.regressions | 28 - 14-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 28 - sumfiles/g++.log.xz | Bin 3408516 -> 3437232 bytes sumfiles/g++.sum | 56 +- sumfiles/gcc.log.xz | Bin 3023416 -> 3008240 bytes sumfiles/gcc.sum | 4356 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1033820 -> 1034132 bytes sumfiles/gfortran.sum | 18 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202416 -> 202196 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2652 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 423608 -> 423804 bytes sumfiles/libstdc++.sum | 8 +- 42 files changed, 2356 insertions(+), 2417 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits October 2022