Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-lts-allyesconfig updated (eacb7abc12 -> 4b0e747355)

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-lts-allyesconfig in repository toolchain/ci/base-artifacts. from eacb7abc12 22: onsuccess: #485: 19905: Success after binutils: 93 commits new 4b0e747355 23: onsuccess: #487: 19905: Success after qemu: 148 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 1644 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 30516 -> 30144 bytes 04-build_kernel_llvm/console.log.xz | Bin 63484 -> 62560 bytes 05-build_abe-qemu/console.log.xz | Bin 31964 -> 31884 bytes 06-build_linux/console.log.xz | Bin 4628 -> 5220 bytes 08-check_regression/console.log.xz | Bin 3124 -> 3016 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++++++---------- 14 files changed, 19 insertions(+), 19 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (9f65eecdbef -> f1adf45b17f)

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 9f65eecdbef c++: Add DECL_NTTP_OBJECT_P lang flag new f1adf45b17f Add instruction level discriminator support. 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: gcc/basic-block.h | 5 --- gcc/cfghooks.cc | 1 - gcc/cp/module.cc | 5 ++- gcc/final.cc | 26 ++++++++-------- gcc/gimple-pretty-print.cc | 2 -- gcc/gimple-streamer-in.cc | 1 - gcc/gimple-streamer-out.cc | 1 - gcc/input.cc | 36 ++++++++++++++++++++-- gcc/input.h | 4 +++ gcc/lto-streamer-in.cc | 19 ++++++++++-- gcc/lto-streamer-out.cc | 7 +++++ gcc/lto-streamer.h | 3 ++ gcc/print-rtl.cc | 4 +++ gcc/rtl.h | 1 + gcc/testsuite/c-c++-common/ubsan/pr85213.c | 7 ++++- gcc/tree-cfg.cc | 49 ++++++++++++++++++++++++------ gcc/tree-pretty-print.cc | 6 ++++ gcc/tree.cc | 10 ++++-- libcpp/include/line-map.h | 10 ++++-- libcpp/lex.cc | 7 +++-- libcpp/line-map.cc | 38 ++++++++++++++++++----- 21 files changed, 187 insertions(+), 55 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-arm updated (5e5e8845ad -> 8bc9f4b2a0)

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-arm in repository toolchain/ci/base-artifacts. discards 5e5e8845ad 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 95def9f5a4 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 4fae8108ff 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 20673712b5 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards fb152158e9 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards aefc6fba2b 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards b8284aa6ae 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 015c747747 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 7243e1d4b6 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards d22bfe8300 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 6cddd45359 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 6addbf367c 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 3c365629a6 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 23f13027a7 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 63a3637b17 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards adc35eeb4e 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards cd298989ad 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 2c1b4204dc 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards c5799dc35e 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 732e72b81c 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 1e33ea682e 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards d78e7790eb 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards ec1c17bf4e 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 62d0de1cab 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 4d9ae1e828 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards a96f220230 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards f5741aa80d 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards fcf6bca9b3 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards be089a9129 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards f4c4e9dd89 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards ab9ce46273 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 942d2db143 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 9b0feb33e2 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards a932fc982b 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 27ad7e64f8 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 6fe2337800 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 7c99022ea9 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 3950c1ff57 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 33089542a7 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 1cb7667aa1 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 21be0bc231 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 2ccd73db52 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 4157a52564 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards b30ce978d5 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 83af8f7516 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 771f9e1939 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards e6338fed4e 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 6a1a1fcd40 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards a75d12fe00 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 0a19108899 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards af01753e7a 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 5319de99f6 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 5c72ab6b7f 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 4698e64e49 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 5e7b070e41 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 2376a5ed34 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 23bb51504f 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards f4f249b027 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 3763b9cf72 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 086bc5cb8c 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards bf5cf211c0 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 17548048bb 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards c903c87c76 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 2c4130bb07 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards dcc466ee9b 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fee18781e7 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 90d92a77f7 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b9ef1a81ba 74: onsuccess: 1: Successful build after linux: 44 commits discards 8b98191e1f 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 9aeffbda60 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 359803b048 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards e26e9fc4b1 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards b989ab86cf 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards e8c85f7e1b 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 83029860bc 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0c16bff178 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c8b7e4811a 65: onsuccess: 1: Successful build after gcc: 4 commits discards 876bb81a01 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 91c4a82e02 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6d179e1a78 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 347dca9737 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards e5f719e7e4 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards b458c9a610 59: onsuccess: 1: Successful build after glibc: 2 commits discards fc4f003109 58: onsuccess: 1: Successful build after binutils: 2 commits discards 258e9c6fe9 57: onsuccess: 1: Successful build after gcc: 7 commits discards 239133e00f 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2984e5f192 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f0755c17e6 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards e1caef93e1 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 03cae93e16 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 70d9a5b1b3 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards cb9bb1b7d2 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f0e0dd5d2f 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0c541d59a9 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards f053ecfe21 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c8a788cf42 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards e4b3d6eb87 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5b8e0fd026 44: onsuccess: 1: Successful build after linux: 34 commits discards e090706c71 43: onsuccess: 1: Successful build after gcc: 2 commits discards 77629f3343 42: onsuccess: 1: Successful build after baseline build: no [...] discards da47c42ed0 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b27f1b336a 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fc50c36ae1 42: onsuccess: 1: Successful build after baseline build: no [...] new 567fb6ff7b 43: onsuccess: 1: Successful build after gcc: 2 commits new 663aef4434 44: onsuccess: 1: Successful build after linux: 34 commits new bbd198732e 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ab2d952eb4 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 6dde03fab9 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f9fff1e098 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 4e2b460e45 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b456ff6aa9 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b84b3f987d 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 64afe620f9 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 0f25c9255b 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 1604865fde 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new d68343c55a 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c74da04346 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2b0209b138 57: onsuccess: 1: Successful build after gcc: 7 commits new 5535a1356e 58: onsuccess: 1: Successful build after binutils: 2 commits new 953ca06727 59: onsuccess: 1: Successful build after glibc: 2 commits new b1ca9097af 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 8160f0fafe 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new cb61a597cc 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new a20d93404a 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f9e8508788 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e010542225 65: onsuccess: 1: Successful build after gcc: 4 commits new e4c6ccba72 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c46afbca4c 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1c3c77ec31 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new baea4d3d82 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 2b9ef3a981 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 9da6ac3a06 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 8714afe615 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a14c2ab260 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 2a5849fd9e 74: onsuccess: 1: Successful build after linux: 44 commits new a7122fb4f4 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 187336acd6 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 7d81171c45 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b3baf148d7 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 00aeef5344 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new b60159821a 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 04f35fba41 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 575e3f96f3 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new ebcefb5e88 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 6a5b8f9cfc 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 9d9451fed4 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new d03121965c 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 790e37c952 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 2e2a473757 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new d4259c7aec 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new fcb32117c2 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 00200af208 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 96240c3b6a 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 4ea5c0f1f0 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 1feb64d7c5 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new cdd5f384ed 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 7857103ee2 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new a45677a7c4 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 75aacdd156 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 5de9119f42 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new ca46fbd813 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 01f3f38dd8 101: onsuccess: #1693: 1: Success after glibc: 14 commits new af7cf1074a 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new e9560cf21c 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 5270923923 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 0d56c0762b 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 187a5753f0 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 7e6518c219 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new c08fdd475a 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 5e4ab5b436 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 810e77831f 110: onsuccess: #1703: 1: Success after gcc: 6 commits new d380307723 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 36130c6444 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new f0851fcc71 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 89113aec95 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new d56767c7ee 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 2e7d85f6c0 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 093869abaa 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 1e2992e38d 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 0872ae4fe5 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 49b212fa8a 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 43e56ed6f4 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 3ecd6a7d90 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 26509ee736 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 197cbb1036 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 3c2254bae8 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 4f70eba9e2 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new e748fdc42f 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 7230689084 128: onsuccess: #1723: 1: Success after linux: 12 commits new 3a4cb24a70 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new d67752466c 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 09beba1368 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 5a04795456 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 14824d42a9 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new c7a59c9144 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 71c6ed8f63 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 959755dc19 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 18448efd20 137: onsuccess: #1736: 1: Success after gcc: 5 commits new c3596228bc 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new b7367844d9 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 698d4c14c1 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 8d10f75a4b 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 8bc9f4b2a0 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] 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 (5e5e8845ad) \ 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 1744 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30624 -> 30144 bytes 04-build_abe-stage1/console.log.xz | Bin 91548 -> 91152 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 9304 -> 9256 bytes 07-build_abe-glibc/console.log.xz | Bin 234068 -> 234364 bytes 08-build_abe-stage2/console.log.xz | Bin 226196 -> 223344 bytes 09-build_abe-gdb/console.log.xz | Bin 37420 -> 37556 bytes 10-build_abe-qemu/console.log.xz | Bin 31784 -> 31096 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2800 -> 2744 bytes 13-check_regression/console.log.xz | Bin 6692 -> 6036 bytes 13-check_regression/mail-body.txt | 46 - 13-check_regression/results.compare | 70 +- 13-check_regression/results.compare2 | 129 +- 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 | 48 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- sumfiles/g++.log.xz | Bin 2687132 -> 2667716 bytes sumfiles/g++.sum | 108 +- sumfiles/gcc.log.xz | Bin 2205300 -> 2226364 bytes sumfiles/gcc.sum | 2883 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 884360 -> 881588 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201252 -> 201100 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2672 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 419324 -> 422680 bytes sumfiles/libstdc++.sum | 10 +- 40 files changed, 1619 insertions(+), 1865 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-arm-bootstrap updated (8d187495bf -> 1008ae9026)

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 in repository toolchain/ci/base-artifacts. discards 8d187495bf 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits discards d7a313edc8 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits discards 312372a958 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits discards 98bf246726 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits discards 8546209ca4 140: onsuccess: #1545: 1: Success after gcc: 7 commits discards 950967b874 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits discards 8482a70439 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits discards cc7afb4c5d 137: onsuccess: #1542: 1: Success after gcc: 4 commits discards 0c091f4ba2 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] discards cbc9be2f3c 135: force: #1540: 2: Success after gcc: 23 commits discards b7229567c6 134: onsuccess: #1538: 2: Success after binutils: 2 commits discards 897f13f915 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits discards 16d8494a91 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits discards 293568d333 131: onsuccess: #1534: 2: Success after gcc: 9 commits discards 04ee8b91ff 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] discards fa202d359c 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits discards 731627068e 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards c84f3b7e03 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits discards 63a1d5b845 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits discards 955702ea54 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits discards 6ea103485c 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits discards 33ffbef27f 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits discards f7bdda42b0 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits discards 2f1ebef138 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits discards 5181fedd0c 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits discards 29f7e7d16f 119: onsuccess: #1520: 2: Success after binutils: 8 commits discards d765674165 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards f5ca068cf5 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards 06cf83fa2f 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards fc57fa4b15 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards 46181d9550 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards 20e8a621bf 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards c9e06aaa03 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards bf08f277b3 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards 0fb69f76c7 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards 3e4ebe94e8 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] discards dfa936bf75 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards 5e7f994391 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] discards ba64d3b8fd 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards b602226c9d 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards 57a42dd1a0 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards 0d79b21f70 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards cbc1092044 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards 7578c08d4d 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards f474ea0b8d 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards 54e05e8186 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] discards 78e1927143 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] discards cb8bd1e7b8 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards 1cc548a918 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards 20c3bf8f87 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] discards da005b318a 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] discards d79e444d21 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards cc7bac15cf 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards f253a04f3a 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards 64eb35a1d6 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards 93c8934bae 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards df739ddbbb 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards 1c498a6786 87: onsuccess: 2: Success after gcc: 4 commits discards 3fddac4ac7 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards e8e51c2669 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards 51392dee26 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards 3f972c44aa 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards 825fc3d054 82: onsuccess: 1: Successful build after gcc: 3 commits discards a4cb5147cd 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 18d170433a 80: force: 2: Successful build after gcc: 14 commits discards 7d9474bed9 79: onsuccess: 2: Successful build after binutils: 5 commits discards c39a4141cf 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards e14c347240 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 194459e378 76: onsuccess: 2: Successful build after gcc: 12 commits discards 18cd480b70 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 4d4a05878c 74: onsuccess: 2: Successful build after baseline build: no [...] discards c902d6bda1 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards c17785ef2a 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 7e391ec4f7 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 7baa1320c6 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 072c6d9d80 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards d62d28c9d3 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 315a8aeebc 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards cd1fbeebfe 66: onsuccess: 2: Successful build after gcc: 9 commits discards 30bd9fc681 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards f33d56e8ef 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 5fc7b9b481 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 9f061bc262 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 79aa12a2c5 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards c5cde8a795 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards dffc1c72cb 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards be8cc9bbf3 58: force: 2: Successful build after gcc: 6 commits discards b7f276562d 57: onsuccess: 2: Successful build after binutils: gdb: new [...] discards 83f06259fb 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 9a254cc2fd 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards f719665a3b 54: onsuccess: 2: Successful build after gcc: 5 commits discards 2b96dfa5b0 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 381e505ef5 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards a21aa9635d 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards d41f5620d8 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 3f4b66066c 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 17d3d52795 48: onsuccess: 2: Successful build after gcc: 4 commits discards 0c6560e712 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 9263380980 46: onsuccess: 2: Successful build after baseline build: no [...] discards 4ce5b3da00 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards b6a438178a 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new c7debf78e8 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new d101dfc6d2 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 9f80016f1e 46: onsuccess: 2: Successful build after baseline build: no [...] new 0a8e4ad195 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits new b18875c449 48: onsuccess: 2: Successful build after gcc: 4 commits new 9149c4bd51 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits new cd4715d929 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits new db814157a9 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 8be81dddc4 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 257f8ba30b 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 9beff6f3e9 54: onsuccess: 2: Successful build after gcc: 5 commits new 060fbe79ce 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 01352dfdd0 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits new e14d5d94d0 57: onsuccess: 2: Successful build after binutils: gdb: new [...] new 60727f43ec 58: force: 2: Successful build after gcc: 6 commits new b23567c402 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 8a18d0ff57 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new 50a084f395 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new 6ebc0e678c 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new bf7792f53a 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 98512795d2 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 88e827ea8d 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 8c94a3bfdc 66: onsuccess: 2: Successful build after gcc: 9 commits new a9561b32fa 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 83fcd6595a 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 2cacaa3123 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 3af998297d 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 011aa66f8f 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 3688a2a0c0 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 338f47b194 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 980bd232cd 74: onsuccess: 2: Successful build after baseline build: no [...] new b119b8019e 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 3962942472 76: onsuccess: 2: Successful build after gcc: 12 commits new b3eb998a35 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 137c0618c0 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new d4d961c305 79: onsuccess: 2: Successful build after binutils: 5 commits new 31f2aa500c 80: force: 2: Successful build after gcc: 14 commits new 53b056092c 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 633cafa317 82: onsuccess: 1: Successful build after gcc: 3 commits new 7195d91775 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new 1a13cdd30c 84: onsuccess: 2: Success after binutils/gcc: 15 commits new d7a2858538 85: onsuccess: 2: Success after binutils/gcc: 25 commits new ba82fc5bfc 86: onsuccess: 2: Success after binutils/gcc: 10 commits new 7baa5547bf 87: onsuccess: 2: Success after gcc: 4 commits new e0406187df 88: onsuccess: 2: Success after binutils/gcc: 25 commits new a56e017864 89: onsuccess: 2: Success after binutils/gcc: 4 commits new ef3566c8f2 90: onsuccess: 2: Success after binutils/gcc: 16 commits new 606726f2f2 91: onsuccess: 2: Success after binutils/gcc: 7 commits new c215daa329 92: onsuccess: 2: Success after binutils/gcc: 9 commits new a74bdf2ee0 93: onsuccess: 2: Success after binutils/gcc: 3 commits new aa15ac5978 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] new 5346c23b6e 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] new 47e0ad8f1d 96: onsuccess: #1452: 2: Success after gcc: 2 commits new cac97a60a1 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new bdb82ccd81 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] new 67345f00f9 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] new 89858fb943 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new 929d1d07b7 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new 625a4d54c1 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new 0a483367d8 103: onsuccess: #1504: 2: Success after gcc: 2 commits new f82e0d5681 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new 5940289390 105: onsuccess: #1506: 2: Success after gcc: 2 commits new 63fb2994be 106: onsuccess: #1507: 2: Success after gcc: 2 commits new 7fe683f38c 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] new 53fe16f06d 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new 826e704351 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] new e591fe8a03 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new ee8b70dbb7 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new ba7bb7c121 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new 0b7e179396 113: onsuccess: #1514: 2: Success after gcc: 5 commits new 8c5acdb23f 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new 41165c04de 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new bbc6922d43 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new 51ca5f14f9 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new 42f474eb54 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new a6b217ad02 119: onsuccess: #1520: 2: Success after binutils: 8 commits new 4c638b221a 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits new 9f41f5c1b2 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits new 51b506434b 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits new d4446a9351 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits new 9869e93cc9 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits new 99198d6b09 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits new 9fafe3d275 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits new 9ae584c84c 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits new d17853eb7a 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new d50d69df6a 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits new 25a3eafc40 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] new 311dff2f9d 131: onsuccess: #1534: 2: Success after gcc: 9 commits new 3b21bbc36e 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits new 940b326fd2 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits new 7cf0632137 134: onsuccess: #1538: 2: Success after binutils: 2 commits new b0289eef0e 135: force: #1540: 2: Success after gcc: 23 commits new 4892af99a8 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] new b3bf804c10 137: onsuccess: #1542: 1: Success after gcc: 4 commits new 902a812ee0 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits new 6defc9fec6 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits new a51e61b7d6 140: onsuccess: #1545: 1: Success after gcc: 7 commits new b295598339 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits new 08118e22a5 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits new a432206a91 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits new b19b85984d 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits new 1008ae9026 145: onsuccess: #1550: 1: Success after binutils/gcc: 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 (8d187495bf) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] 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 1660 -> 1660 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 51380 -> 51624 bytes 05-build_abe-bootstrap/console.log.xz | Bin 111700 -> 112108 bytes 06-check_regression/console.log.xz | Bin 3032 -> 2948 bytes 07-update_baseline/console.log | 28 ++++++++++++++-------------- 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, 29 insertions(+), 29 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (db288230db5 -> 9f65eecdbef)

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 db288230db5 i386: Mark XMM4-XMM6 as clobbered by encodekey128/encodekey256 new 9f65eecdbef c++: Add DECL_NTTP_OBJECT_P lang flag 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: gcc/cp/cp-tree.h | 7 ++++++- gcc/cp/cxx-pretty-print.cc | 2 +- gcc/cp/error.cc | 2 +- gcc/cp/mangle.cc | 2 +- gcc/cp/pt.cc | 35 +++++++++++++++++------------------ 5 files changed, 26 insertions(+), 22 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[glibc] branch master updated (d7f32c9958 -> 3e5760fcb4)

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 d7f32c9958 hurd: Fix typo new 3e5760fcb4 Update _FloatN header support for C++ in GCC 13 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: bits/floatn-common.h | 40 +++++++++++++++++----------------- sysdeps/ia64/bits/floatn.h | 6 ++--- sysdeps/ieee754/ldbl-128/bits/floatn.h | 6 ++--- sysdeps/mips/ieee754/bits/floatn.h | 6 ++--- sysdeps/powerpc/bits/floatn.h | 6 ++--- sysdeps/x86/bits/floatn.h | 6 ++--- 6 files changed, 35 insertions(+), 35 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 updated (8d3ce50bb6 -> dffe7e64a4)

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 in repository toolchain/ci/base-artifacts. discards 8d3ce50bb6 139: onsuccess: #1566: 1: Success after gcc: 5 commits discards 2d7f49b62d 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] discards 97e24dd4bd 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] discards 85f9ef4d12 136: onsuccess: #1561: 2: Success after binutils: 3 commits discards e53ef5c895 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits discards 6fd16afad0 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits discards ade2f0c447 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits discards 5a81cdead8 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits discards 0611b2b6df 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits discards 2df96e5982 130: onsuccess: #1554: 2: Success after gcc: 9 commits discards 28657532c0 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] discards 4a60fef982 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards 55a005c03a 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] discards d488cadaff 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] discards ab3e7552c9 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards 099d426846 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards 8bf71148ba 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards 1aa09c9e24 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 4220f91247 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards 655630692b 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards 2c66720dc2 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards 6736bd40b0 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards 67c1011b89 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards 8c76e28b32 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards 6466e5b73b 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards d07fb31402 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards 520f617b8c 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards e006d20a7e 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards d0c4b4420b 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards 0fdf9314de 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards a36acc7e59 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards 31da94eca3 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards f4101169d3 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 585dca773b 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards ea35bbde20 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards a250a2c011 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards e21b53fd9a 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards 7de3c09bd6 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards e12789585e 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards 44b17f7e59 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards a3a92098d5 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards a529f2b8be 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 52ca284001 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards 16371344e0 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards 55c83b6936 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards 8500ee16fa 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards b11ee28046 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards 62dcb6be60 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 48712973d6 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards c9a019a51a 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards 3819152073 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards 283a417612 88: onsuccess: 1: Success after gcc: 20 commits discards 0771183c77 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards 2506632d75 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards bdce2ac01a 85: onsuccess: 2: Success after binutils: 4 commits discards 9ade228813 84: onsuccess: 2: Success after gcc: 9 commits discards 47c3a850bc 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards a557f4dbe0 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards 372b2ac658 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards 1e5110bf00 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 9809502afe 79: onsuccess: 1: Successful build after gcc: 3 commits discards 7c43b843ab 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 9c3ed7c27f 77: force: 2: Successful build after gcc: 32 commits discards c51b03f19d 76: onsuccess: 2: Successful build after binutils: 10 commits discards 6d20251af2 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 2ca9e6b3c1 74: onsuccess: 2: Successful build after gcc: 13 commits discards e9fdbbdbb2 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards e7af0b45f2 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 63524d1fa4 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 1e77c6bca6 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 3ab930845f 69: onsuccess: 2: Successful build after baseline build: no [...] discards 4777b33d30 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards d063059b07 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards bff996804f 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards c8f8552414 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 8649af42c6 64: onsuccess: 2: Successful build after gcc: 7 commits discards ea643cbd23 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 341a54ecc5 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 1f9eeee305 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards 07f02e7124 60: onsuccess: 1: Successful build after gcc: 15 commits discards 293b7ea278 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards c8636c2042 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards ee74832be8 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards 6453a596f2 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards dc7c0110ee 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 0b00dffb7e 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards eedd21a439 53: onsuccess: 2: Successful build after gcc: 5 commits discards 5428c6e577 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards f91be039ee 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 121679d000 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards c7bae43b54 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 41072eecf5 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards fe5695379d 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 6dced22d8c 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards ba5c9817de 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards 30cb9ce6b9 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 398b451d1c 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] discards c3ed263c57 42: onsuccess: 2: Successful build after gcc: 2 commits discards 64bb8724ae 41: onsuccess: 2: Successful build after baseline build: no [...] discards 0e1e68c1c7 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 457a838674 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 88ea6e373d 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 9a82deaf09 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 2645c6f7ec 41: onsuccess: 2: Successful build after baseline build: no [...] new 5a755ce570 42: onsuccess: 2: Successful build after gcc: 2 commits new 157c628e18 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new 7000d9480c 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 6d09b9354c 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 41dfc5430e 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 2d9e00ca61 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new cff74e1b22 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 9e8c011283 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 5d2d247355 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 435f42b3fa 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 59bcb84a77 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 1f34fdf8e6 53: onsuccess: 2: Successful build after gcc: 5 commits new 178a4865d0 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 7f09a53e5b 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 4c9bffe094 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 8d496666e4 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 385281cff7 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new af4c7cb2b4 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 6d4538fa99 60: onsuccess: 1: Successful build after gcc: 15 commits new 23b22cbecd 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new a79f286b64 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 8b385ff1b8 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new a24a10c930 64: onsuccess: 2: Successful build after gcc: 7 commits new 1f67d9b284 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 75981bf6d0 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 45e67ffbb0 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 7a9153f206 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 2ca5ee087d 69: onsuccess: 2: Successful build after baseline build: no [...] new 87c21bb655 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 7edfba27ce 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new e5aeb7928a 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 1a4f4f9229 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 74165f3c8f 74: onsuccess: 2: Successful build after gcc: 13 commits new 0b63f680d1 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 29f84e0a5c 76: onsuccess: 2: Successful build after binutils: 10 commits new 116adef768 77: force: 2: Successful build after gcc: 32 commits new b32084d20e 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 6b113239fb 79: onsuccess: 1: Successful build after gcc: 3 commits new 57277fbfde 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 0717c72393 81: onsuccess: 2: Success after binutils/gcc: 16 commits new e7ef387a6d 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 7e4cd4c665 83: onsuccess: 2: Success after binutils/gcc: 7 commits new 4f76d2c8d3 84: onsuccess: 2: Success after gcc: 9 commits new f49f3fbcc1 85: onsuccess: 2: Success after binutils: 4 commits new f6a6f6e8ae 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new 502efe2eb3 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new 0617c8302d 88: onsuccess: 1: Success after gcc: 20 commits new 8d0aa589b7 89: onsuccess: 2: Success after binutils/gcc: 39 commits new e5e4074570 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 237a8278cf 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 60d3432bf1 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 3b8bdbfc85 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new 3b53d22a56 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new e59cc35961 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new eb2d00236c 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new f1891e42a4 97: onsuccess: #1481: 2: Success after gcc: 8 commits new 904a1af05f 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new 6905a77008 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new c642153784 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new b2cf20ae98 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new 9ed795ab61 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new bf98fbea7a 103: onsuccess: #1524: 2: Success after gcc: 2 commits new 07db120b6c 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 90c42ee657 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 323a223e3e 106: onsuccess: #1527: 2: Success after gcc: 2 commits new a3c63e85b6 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new 0b795bebc9 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new 3bbb609891 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new 4c5664b55e 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 11b09fd6fd 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new fd45360139 112: onsuccess: #1533: 2: Success after gcc: 5 commits new d1e0a4d1f7 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new 8c8547ce9a 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new 8152a2fbe4 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new 66743fe5ce 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 8a89d87672 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new f6ea1fee85 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new 45422693ae 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new db73ab08db 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new 67c1dad625 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new af67af3263 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new 7e1a112706 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new fc169844ad 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new 3f7a3451aa 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new 3c9ff417e9 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] new 48b8570fa6 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] new d0643c32cb 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new f2102539cc 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] new 07a1e448ea 130: onsuccess: #1554: 2: Success after gcc: 9 commits new 1f86a7de80 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits new 0ad5d579f3 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits new b18efac88e 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits new 1f351730bb 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits new 758f6ac094 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits new 36033ee4e8 136: onsuccess: #1561: 2: Success after binutils: 3 commits new f8450a4e96 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] new 5bd3750114 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] new fc971084a2 139: onsuccess: #1566: 1: Success after gcc: 5 commits new dffe7e64a4 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 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 (8d3ce50bb6) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] 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 1728 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 39048 -> 38064 bytes 05-build_abe-bootstrap/console.log.xz | Bin 81024 -> 78636 bytes 06-check_regression/console.log.xz | Bin 2856 -> 3120 bytes 06-check_regression/mail-body.txt | 11 ------ 07-update_baseline/console.log | 64 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 13 +------ mail/mail-subject.txt | 2 +- manifest.sh | 19 +++++----- 14 files changed, 48 insertions(+), 69 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_build/master-arm updated (2081924bdb -> 30c3e235d1)

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_build/master-arm in repository toolchain/ci/base-artifacts. discards 2081924bdb 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] discards 3b8e886882 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits discards ee85a7930d 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] discards 4a8d88d9cb 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] discards 0076834b84 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards 2d5d0074c2 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] discards 1ca008c1bc 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards 63a7dac7d0 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards 306f92ea5d 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards c8e776dde4 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 51f5ecedd2 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards 5ce83f919a 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards 027a9d925f 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards 5d9387f432 132: onsuccess: #1645: 7: Success after linux: 23 commits discards 6883e9c98e 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards f7ef545319 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards 2fcd45725e 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 46d6552346 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards a48b9e06dc 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards 4455359299 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards c485971195 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards 7e8e997638 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards 7e1af11328 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards 13d5e7599a 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards 906bb93468 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards b1036306f0 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards 7b93718734 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards 4ebeb22665 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards 28a042b269 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards bfcd8607b8 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards a83f9b08bc 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards de482be433 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards b4935c21fd 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 076085c646 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards b58b7d7d7e 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 8b9f044884 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards d881658bcd 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards 4d83e52303 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards d45bbad653 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 37bb41723e 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 28f1cde17a 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards a2723a2053 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards b603ac9ef5 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards 6b60c34822 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 7fc830b55d 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards d9e76dc426 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 6636dbe7d8 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 366fc4183e 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards dc17f925b3 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards f735047dd9 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards 1a8da4b008 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards cfe524040b 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards ad840b8f1e 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards ddca8afe5b 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards cca83fc183 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 8710523c3f 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards a695f48d2d 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards e43454361e 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards b8d69312b0 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards ea590b7c8a 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 955518b538 85: onsuccess: 7: Success after gcc: 9 commits discards e395fd7b51 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards bf8201edff 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 47004cb4c4 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards d35fe66f93 81: onsuccess: 7: Successful build after gcc: 2 commits discards eb200688f0 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 0debaca0db 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 44e762cee3 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ff6231c735 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 3611dea089 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 60458f4008 75: onsuccess: 7: Successful build after linux: 44 commits discards ec1d311d29 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 3f7994e924 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards f7f06fa48f 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 4ed695688b 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 5b1fa5e4db 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards c4cfbc8c83 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 27a527d0a3 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards fc4335a04c 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 80eda4e0ed 66: onsuccess: 7: Successful build after gcc: 3 commits discards 23a8b4c7ed 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e1f8029427 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 36fd3df196 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards b5053a29d2 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 4fc0e79197 61: onsuccess: 4: Successful build after gcc: 15 commits discards cc77c92265 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards fe9e753768 59: force: 7: Successful build after gcc: 2 commits discards 0bee2123fd 58: onsuccess: 7: Successful build after glibc: 2 commits discards c96368cfdc 57: onsuccess: 7: Successful build after gcc: 7 commits discards b93e050af7 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards fe355ac936 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 1ecd8334dd 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards af87659204 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 94bdfe5ef4 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards f6e1ce9dc4 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 4c872c0490 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards c3fb27c5c7 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 8c27b60b1a 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards 19d1f5c442 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 780c924833 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 68d01079b4 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 59ca12bb20 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new c8f05a9492 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 3e5c33a278 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 4a06020c3a 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new 0af42f46f3 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 26b916726b 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 96ff5757ad 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 42c093b377 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new cebf8a350c 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 72442602f6 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new 6419aa4ec5 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 4760adea9a 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 1788c45115 57: onsuccess: 7: Successful build after gcc: 7 commits new 2b58508246 58: onsuccess: 7: Successful build after glibc: 2 commits new ae92effa19 59: force: 7: Successful build after gcc: 2 commits new 37b1c839ee 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 8f9e0f817e 61: onsuccess: 4: Successful build after gcc: 15 commits new cccecd93d0 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 9871cf19b5 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 65e3eeeceb 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new cb13df0148 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f0e1f1b0ea 66: onsuccess: 7: Successful build after gcc: 3 commits new 783604a055 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new cfab058404 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new a8bb77e5a1 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 903ff494a1 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new a65e0217b3 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 24f0908483 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new c4bcd32b61 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new c52bc08a6d 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new eb63abb001 75: onsuccess: 7: Successful build after linux: 44 commits new 2f3d7d2d7b 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new c58da9d1c3 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 8759bc274f 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ba1c8c8f78 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new a1e27a4e8c 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 6b8f5ab553 81: onsuccess: 7: Successful build after gcc: 2 commits new eb3766c2f7 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 6e5a3f752a 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 907b251ffa 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 20e3bdfbcb 85: onsuccess: 7: Success after gcc: 9 commits new 7b5e6a89c2 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 2ec1ca4b14 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new ded3cf4eb4 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 4b465f1fa1 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 1c0b1d4385 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 3483d5f6f1 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 1a8f686e58 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new f8191d79e9 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new ca6f898337 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 6d17af861a 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new c95b081cf2 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new b5f5998ef9 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new 6fe24b4b83 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 39d0947002 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new 07670cc210 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new 68ee53cc71 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 8946396fb6 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 9699667d49 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 0e4ef79fa4 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new f14c68e8f8 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new ae07a9199b 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 1f5d20ab63 107: onsuccess: #1618: 7: Success after gcc: 2 commits new ef5a513a6f 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new 145c5a5fb8 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new 50ea6c7aed 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new eed571ce73 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 4d1e6d1cdc 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 887bcb3e14 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 6cfad942bf 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new 8527ad15ac 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 4b97b7d7e1 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new 5c8142f579 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new 260094f831 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new 7a18dcadd7 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new eb74760a95 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 3057312286 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new 5efa611571 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new bdb55bd006 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new a778c51cdb 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new bd1a3ed940 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new e8881f11d5 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new 8f64c50419 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new fd65f9481f 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new 272792eac6 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new 866659b308 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new 1a7efd4e76 131: onsuccess: #1644: 7: Success after gcc: 10 commits new 1293cb4b2e 132: onsuccess: #1645: 7: Success after linux: 23 commits new 1939cda643 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new 059a5093de 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new b01ddcd352 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new 53b4505c7f 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 0779b1b394 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new 7178cac400 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new 862578ec82 139: onsuccess: #1654: 1: Success after gcc: 11 commits new f42e5525e9 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] new 68efea14ea 141: onsuccess: #1656: 7: Success after gcc: 7 commits new 8e34232ec4 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] new 4da951eddc 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] new d4d779c2bd 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits new 35c2b014a0 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] new 30c3e235d1 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] 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 (2081924bdb) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] 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 1732 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 30264 -> 30860 bytes 05-build_abe-stage1/console.log.xz | Bin 91436 -> 90900 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 9272 -> 8680 bytes 08-build_abe-glibc/console.log.xz | Bin 234396 -> 233216 bytes 09-build_abe-stage2/console.log.xz | Bin 224732 -> 224788 bytes 10-build_abe-gdb/console.log.xz | Bin 37424 -> 38124 bytes 11-build_abe-qemu/console.log.xz | Bin 31224 -> 30904 bytes 12-check_regression/console.log.xz | Bin 3788 -> 4504 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ 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 | 42 +++++++++++------------ 22 files changed, 62 insertions(+), 62 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/release-arm-bootstrap_debug updated (64b64828c4 -> ce8e42e1e6)

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_debug in repository toolchain/ci/base-artifacts. from 64b64828c4 15: onsuccess: #138: 2: Success after binutils/gcc: 8 commits new ce8e42e1e6 16: onsuccess: #139: 2: Success after binutils/gcc: 9 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 -> 1844 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 51528 -> 52564 bytes 05-build_abe-bootstrap_debug/console.log.xz | Bin 461272 -> 461600 bytes 06-check_regression/console.log.xz | Bin 2796 -> 2856 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_gcc_check/master-aarch64 updated (edef8893b5 -> 51b3175f11)

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-aarch64 in repository toolchain/ci/base-artifacts. discards edef8893b5 139: onsuccess: #2067: 1: Success after binutils: 2 commits discards bd77a6de86 138: onsuccess: #2064: 1: Success after binutils: 4 commits discards c7c8bb6888 137: onsuccess: #2061: 1: Success after binutils: 2 commits discards 7a17402ef7 136: onsuccess: #2056: 1: Success after binutils: 4 commits discards d4e4fae565 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits discards 396779ff35 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits discards 6612e2b663 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits discards 347411d5dd 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits discards 433531bee4 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] discards 14da87109d 130: onsuccess: #2049: 1: Success after gcc: 9 commits discards 797434e0e7 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] discards 028d8cabd2 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] discards a1121b037c 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] discards 9ebba4ffa0 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] discards c74811a98f 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits discards d8be50eb9c 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits discards a74ada23a9 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits discards dafb83e737 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits discards 0ab7fe98c0 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits discards 9e45f6a8bf 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits discards 7608fea1c0 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits discards b83fce8cc2 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits discards 35244ed7f1 117: onsuccess: #2034: 1: Success after binutils: 2 commits discards e4a0eb15e6 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits discards 72d4dade2c 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits discards e6c5232bfc 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits discards 0332750e00 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits discards da926eba68 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits discards 45b4d92b35 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits discards 592d80d4fd 110: onsuccess: #2027: 1: Success after gcc: 5 commits discards 9502e8c9b1 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits discards 75124fa70f 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits discards c0ce089162 107: onsuccess: #2024: 1: Success after gcc: 3 commits discards 38f1754625 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits discards f369df897f 105: onsuccess: #2022: 1: Success after gcc: 4 commits discards 0f8018d896 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits discards b15884e6e9 103: onsuccess: #2020: 1: Success after gcc: 2 commits discards 6e4f7b3d66 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] discards 594ee42e36 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits discards 9147b89643 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits discards a46bc2777f 99: onsuccess: #1974: 1: Success after gcc: 14 commits discards c740149d1f 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits discards 29123d8e36 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits discards fef8af2bb5 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] discards 9040f1c03f 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] discards 8023c951e6 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits discards f48e143242 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] discards 9ef2ee19c1 92: onsuccess: #1965: 1: Success after gcc: 2 commits discards 41b1167228 91: onsuccess: 1: Success after gcc: Daily bump. discards a39aab6383 90: onsuccess: 1: Success after binutils/gcc: 6 commits discards ae013eb0f7 89: onsuccess: 1: Success after binutils/gcc: 9 commits discards e9d0d88a0b 88: onsuccess: 1: Success after binutils/gcc: 16 commits discards c852081970 87: onsuccess: 1: Success after binutils/gcc: 4 commits discards 32baea0c2c 86: onsuccess: 1: Success after binutils/gcc: 13 commits discards 84eb92572f 85: onsuccess: 1: Success after binutils/gcc: 9 commits discards 972d4d434d 84: onsuccess: 1: Success after binutils/gcc: 9 commits discards c9b0684a99 83: onsuccess: 1: Success after gcc: 8 commits discards f4267a7ebd 82: onsuccess: 1: Success after binutils/gcc: 10 commits discards 1b4644016e 81: onsuccess: 1: Success after binutils/gcc: 27 commits discards 7368749753 80: onsuccess: 1: Success after binutils/gcc: 14 commits discards 29fced9152 79: onsuccess: 1: Successful build after gcc: Daily bump. discards 46e8bafda4 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 1bce15a14d 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards 254c774e42 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards c47c66c251 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 3193d01dca 74: onsuccess: 1: Successful build after binutils: Automatic [...] discards f2f427d942 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards 32823f85e3 72: onsuccess: 1: Successful build after gcc: 2 commits discards e84f354208 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 6691d1bbdd 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] discards 5f25ad8951 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards aa651467b2 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 504912d3d7 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 15e402d9a1 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards f41ca15abf 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 90078ccfd5 64: onsuccess: 1: Successful build after gcc: 5 commits discards a9bb7bae22 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards fef7b792f5 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards e4c81e5778 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits discards 391bac5f49 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 5e329cac1b 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits discards 490898dba4 58: onsuccess: 1: Successful build after binutils: 2 commits discards 2038bf9559 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits discards 125aaad0fb 56: onsuccess: 1: Successful build after gcc: Daily bump. discards cee5e2d60d 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards dff693ff58 54: onsuccess: 1: Successful build after gcc: 7 commits discards 68a07508e7 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards c5d360ece8 52: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 1682f8e43e 51: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 0ab9dc48bc 50: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 185f252436 49: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 5ff4af5292 48: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards e69b1dba59 47: onsuccess: 1: Successful build after binutils: 2 commits discards c4d4ae22c8 46: onsuccess: 1: Successful build after gcc: Daily bump. discards 7b4f4ac8f6 45: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 391b529ec8 44: onsuccess: 1: Successful build after gcc: 2 commits discards 8f476171c6 43: onsuccess: 1: Successful build after gcc: Daily bump. discards 7cb9498dfb 42: onsuccess: 1: Successful build after binutils: Automatic [...] discards 48646dd638 41: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards b55bb1c110 40: onsuccess: 1: Successful build after gcc: 2 commits discards fb3476a28a 39: onsuccess: 1: Successful build after binutils/gcc: 3 commits new f141228960 39: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 138f6a4927 40: onsuccess: 1: Successful build after gcc: 2 commits new 4a1e7e5f91 41: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 339e42a4fc 42: onsuccess: 1: Successful build after binutils: Automatic [...] new a07ebb8251 43: onsuccess: 1: Successful build after gcc: Daily bump. new ba40490a95 44: onsuccess: 1: Successful build after gcc: 2 commits new 28b328fb51 45: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 8e40210de2 46: onsuccess: 1: Successful build after gcc: Daily bump. new d074365810 47: onsuccess: 1: Successful build after binutils: 2 commits new a9146def7a 48: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 54502f68b2 49: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 870986b8cf 50: onsuccess: 1: Successful build after binutils/gcc: 6 commits new a3c81657f8 51: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 05365518e0 52: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 6c3d3e99c8 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits new c44e912020 54: onsuccess: 1: Successful build after gcc: 7 commits new 0253d94768 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 84c21554a4 56: onsuccess: 1: Successful build after gcc: Daily bump. new 6e42dfe560 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits new be1bbbc452 58: onsuccess: 1: Successful build after binutils: 2 commits new f84ebdcb64 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits new 2cbc968cb0 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 02098a12ad 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits new d3f490dccb 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 914abe791a 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits new c03affcbab 64: onsuccess: 1: Successful build after gcc: 5 commits new f9d7163fda 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 19e5edad26 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 940f1300ab 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new bf7bb447fc 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits new df46791e98 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 7a6305fb73 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] new 4d53a54cc8 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits new ae19f51dc2 72: onsuccess: 1: Successful build after gcc: 2 commits new 6482369947 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] new 277334a57e 74: onsuccess: 1: Successful build after binutils: Automatic [...] new 21101f856c 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits new e42c8d63c4 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 99f5c60a91 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits new b6610990b2 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 640a140abb 79: onsuccess: 1: Successful build after gcc: Daily bump. new c8d4aa3405 80: onsuccess: 1: Success after binutils/gcc: 14 commits new 7c90ae12c5 81: onsuccess: 1: Success after binutils/gcc: 27 commits new f0b7fa8a6b 82: onsuccess: 1: Success after binutils/gcc: 10 commits new 7e02de0e05 83: onsuccess: 1: Success after gcc: 8 commits new 0cd5458f07 84: onsuccess: 1: Success after binutils/gcc: 9 commits new 8bcadefec8 85: onsuccess: 1: Success after binutils/gcc: 9 commits new fea3771a7a 86: onsuccess: 1: Success after binutils/gcc: 13 commits new 97ca35feff 87: onsuccess: 1: Success after binutils/gcc: 4 commits new 9ef55f9aa6 88: onsuccess: 1: Success after binutils/gcc: 16 commits new 7151c7c78e 89: onsuccess: 1: Success after binutils/gcc: 9 commits new 0c5a6ccade 90: onsuccess: 1: Success after binutils/gcc: 6 commits new 2a345e23b7 91: onsuccess: 1: Success after gcc: Daily bump. new abf155637e 92: onsuccess: #1965: 1: Success after gcc: 2 commits new 6056267f6e 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] new ca2ed1da33 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits new 63cdacfe5a 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] new a2009dd381 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] new 22de06faff 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits new d35db73e30 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits new 4befb6b4f5 99: onsuccess: #1974: 1: Success after gcc: 14 commits new 89d7bc02f3 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits new 51bdeae6ac 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits new 39d076899b 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] new 96e6323696 103: onsuccess: #2020: 1: Success after gcc: 2 commits new c5e0106b13 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits new bc69b265af 105: onsuccess: #2022: 1: Success after gcc: 4 commits new 0f45b4a353 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits new 84550db676 107: onsuccess: #2024: 1: Success after gcc: 3 commits new c3d7a3c714 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits new 665fe12b1c 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits new 360918ce43 110: onsuccess: #2027: 1: Success after gcc: 5 commits new a8632c9ab7 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits new ef42da44ac 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits new 40f5e01df6 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits new e87f929b7e 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits new fa3c5da242 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits new 681921196a 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits new 7ea661d7ad 117: onsuccess: #2034: 1: Success after binutils: 2 commits new 29caa60f81 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits new 87c09d01b7 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits new 020530e355 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits new c55f2662e0 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits new 9d5c7a10cc 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits new 986c60a91b 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits new eec3299490 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits new c69063424a 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits new 60c7adf022 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] new cec3800041 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] new c75ba669fa 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] new 6ebf7792be 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] new 5a4c16678c 130: onsuccess: #2049: 1: Success after gcc: 9 commits new 7bc2c3af6f 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] new baacb519af 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits new 4072ed33c8 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits new 389ea81f50 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits new e6fd857d32 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits new 4bc0402d6d 136: onsuccess: #2056: 1: Success after binutils: 4 commits new b056ad53a0 137: onsuccess: #2061: 1: Success after binutils: 2 commits new 9a034fa335 138: onsuccess: #2064: 1: Success after binutils: 4 commits new a42b125eaf 139: onsuccess: #2067: 1: Success after binutils: 2 commits new 51b3175f11 140: onsuccess: #2070: 1: Success after binutils: 4 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 (edef8893b5) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-aarch64 [...] 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 1676 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 37516 -> 38944 bytes 04-build_abe-gcc/console.log.xz | Bin 211492 -> 214164 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3856 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2956 -> 2960 bytes 07-check_regression/console.log.xz | Bin 4272 -> 4400 bytes 07-check_regression/results.compare2 | 4 +- 08-update_baseline/console.log | 48 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 12 +- sumfiles/g++.log.xz | Bin 3555992 -> 3572384 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 3131056 -> 3134616 bytes sumfiles/gcc.sum | 4528 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1044004 -> 1043276 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2196 -> 2188 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 207136 -> 207140 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2544 -> 2548 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 443792 -> 440836 bytes sumfiles/libstdc++.sum | 2 +- 29 files changed, 2307 insertions(+), 2307 deletions(-) -- 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 September 2022