Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (734bb58c4a -> c31b8d9e73)

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 734bb58c4a 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards 2f392ac2db 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards ab971f5397 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards 8d30402f9c 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards 64f7c232bd 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 3eee6b44b8 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards d87f8755b6 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards e43927c898 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards 6525d136aa 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 6b184e0b86 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards 72a7457c45 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 32df7ebdec 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards 8bccbb56e4 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards 97aaf3b6dc 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 72c6121728 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards c9b42546e2 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards b7ff5a621e 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 132b0d364a 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 87c9e85ca8 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards b5aecb8d5d 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 1c9af6f108 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 45cda857e8 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards ed11d94037 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 728957d5a9 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards d8212ba4c5 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards b519a18d46 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards 4b83f798e4 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards 5a0a00a038 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 7fd4c4e811 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards 5f27850c53 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 306941b4cf 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 31c2ed5751 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 039d9cb7ce 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards f791445664 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 0fd135313e 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 93bc9e249d 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards a1238fc27a 85: onsuccess: 7: Success after gcc: 9 commits discards ae170da085 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 7ba63f4b91 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards d57c49e69c 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 1056eab7b0 81: onsuccess: 7: Successful build after gcc: 2 commits discards 0ddc1fb232 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 80a041ac38 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards b37fd0061b 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 9edfd8d07a 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 9cc5b0d6b7 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 0fd5b63e1d 75: onsuccess: 7: Successful build after linux: 44 commits discards 0556c594de 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 7173135c95 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ac3d3d38a8 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 8ab1a59e41 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards ed6911f529 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 1e9357964e 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 861f69b029 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards da739e6669 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 28b7717955 66: onsuccess: 7: Successful build after gcc: 3 commits discards 0d83af1f38 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards cf5ce5704f 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards bb00a23bb4 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards eb05037762 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards dcec1f2225 61: onsuccess: 4: Successful build after gcc: 15 commits discards 96e14eba98 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards c3ba9878b9 59: force: 7: Successful build after gcc: 2 commits discards 0701310e04 58: onsuccess: 7: Successful build after glibc: 2 commits discards 36438e05dc 57: onsuccess: 7: Successful build after gcc: 7 commits discards 45625fd092 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 691aee899f 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 8fbb2a113c 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards 41696f3050 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards ad9f1fb214 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards a7d0c5228f 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 33eebdcbfb 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards fbf61cd749 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 677a53ea41 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards c0130dd5e3 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 9064efb1f8 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards b4020342b1 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 12c870026e 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards f5bad464c8 43: onsuccess: 7: Successful build after gcc: 2 commits discards 3a652baa1c 42: onsuccess: 7: Successful build after baseline build: no [...] discards a47e266248 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 719bc73a03 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 08562f405a 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 [...] discards c90b37c237 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards 675908b75a 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards cb03c1a7a2 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 8ac99d2bd9 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 18f7510789 34: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 3e371eee3d 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 854fadbaa2 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 7789c00b53 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 62e7704001 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 3e1d14a9f6 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards 3076798d0e 28: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 72b2869e19 27: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards d7b415ff12 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards a6db88d34f 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 3ee9b35dec 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 04abfff558 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards ec94ee135d 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 008104fb19 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 0d286f129c 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 39eb154507 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 314f1097e8 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 5f271bfb75 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 9db8c80e21 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 5ffbc9db0c 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new db22471fd3 27: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new c30f37b30a 28: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7f34a4e93a 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new db22db8f22 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 5507c41a18 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 3361656c59 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new 325af6fe9c 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 911f775199 34: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new d68bbc4dae 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 447ed930a2 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 475a719a8e 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 76e8203fd4 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new cbd6dbb154 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 [...] new 389c189750 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 39da3bfb4a 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new a767e326cb 42: onsuccess: 7: Successful build after baseline build: no [...] new 7d41dc0890 43: onsuccess: 7: Successful build after gcc: 2 commits new 799f1a80f0 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new 2427951ff9 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 3f78b184d4 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new aae9cea298 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7e701591a3 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new 3baa528b99 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 68e53cc0d5 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b4628c209a 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new f80683e9e4 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 6621ce56da 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 796756069a 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new fb6bab1e22 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 4a4d1fd5cd 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5b6b121668 57: onsuccess: 7: Successful build after gcc: 7 commits new 12d3d27a78 58: onsuccess: 7: Successful build after glibc: 2 commits new c0ad6e0204 59: force: 7: Successful build after gcc: 2 commits new f18c3fa678 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 5cbc3da9fc 61: onsuccess: 4: Successful build after gcc: 15 commits new aa1bb901e3 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new da3a1d4235 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 6aadb39258 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 3e33994df1 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 9ad670432e 66: onsuccess: 7: Successful build after gcc: 3 commits new a8c6892095 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new ee01a30a09 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 69d6aa930d 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 2e4381b8ee 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 0f02668d2a 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 37320d3cbf 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 92df71b511 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new db28b82484 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new d46176055f 75: onsuccess: 7: Successful build after linux: 44 commits new c373bdc3b9 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 49fc63c779 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new a87aaa5ff8 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new d1fbef3983 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 2f4d936c3c 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 629786bcb8 81: onsuccess: 7: Successful build after gcc: 2 commits new 8f72e71766 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 2e58bd434a 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 14d00af283 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 5f4abfecd6 85: onsuccess: 7: Success after gcc: 9 commits new 7e325e73d3 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new b5f46a8e95 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 74ff286349 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new a8e6e1f8a8 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 6fa1f50600 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 0fc6e4c447 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new bed3d15e23 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 5217168bfe 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new 67bd8fce1a 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new b6b166c957 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new 431dc89b48 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new 151d5b8b2f 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new d9cd804a72 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 34876508fe 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new 3eb985a027 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new 16b3d9b6a5 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 68b6e1b8fc 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new b3565d640b 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new d0d64d8fe1 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 774816839a 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new 40aa13e157 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 8d87f960c7 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 447a1a85b2 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new d8e67dbe6a 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new b24badc8e6 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new e917104276 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 061c940021 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 4481469d8d 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 97ef2d6e0f 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new 599d799515 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 99a39ccfcc 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new f69070503b 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new 93270e9ade 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new 594804c974 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 4ba699fbdf 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 4cd7bf5caa 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new c31b8d9e73 122: onsuccess: #1633: 7: 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 (734bb58c4a) \ 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 1636 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 30224 -> 29944 bytes 05-build_abe-stage1/console.log.xz | Bin 90408 -> 90896 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 8572 -> 8528 bytes 08-build_abe-glibc/console.log.xz | Bin 233636 -> 233268 bytes 09-build_abe-stage2/console.log.xz | Bin 222768 -> 225024 bytes 10-build_abe-gdb/console.log.xz | Bin 37276 -> 37164 bytes 11-build_abe-qemu/console.log.xz | Bin 31860 -> 31392 bytes 12-check_regression/console.log.xz | Bin 2716 -> 3088 bytes 13-update_baseline/console.log | 62 +++++++++++++++++------------------ 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++++++++++----------- 21 files changed, 58 insertions(+), 58 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[gcc] branch master updated (f35be1268c9 -> 4b4b51445f7)

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 f35be1268c9 cmd/cgo: add and use runtime/cgo.Incomplete instead of //go [...] new 4b4b51445f7 libstdc++: Rearrange tests for <bitset> 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: libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/18604.cc | 0 libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/45713.cc | 0 .../{23_containers/bitset/to_string => 20_util/bitset/access}/dr396.cc | 0 .../bitset/to_string/1.cc => 20_util/bitset/access/to_string.cc} | 0 .../bitset/to_ullong/1.cc => 20_util/bitset/access/to_ullong.cc} | 0 .../bitset/to_ulong/1.cc => 20_util/bitset/access/to_ulong.cc} | 0 libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/cons/1.cc | 0 libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/cons/16020.cc | 0 libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/cons/2.cc | 0 libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/cons/3.cc | 0 libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/cons/38244.cc | 0 libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/cons/50268.cc | 0 libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/cons/6282.cc | 0 .../testsuite/{23_containers => 20_util}/bitset/cons/constexpr.cc | 0 libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/cons/dr1325-1.cc | 0 libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/cons/dr1325-2.cc | 0 libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/cons/dr396.cc | 0 .../testsuite/{23_containers => 20_util}/bitset/debug/invalidation/1.cc | 0 libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/ext/15361.cc | 0 libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/hash/1.cc | 0 .../{23_containers/bitset/input/1.cc => 20_util/bitset/io/input.cc} | 0 .../{23_containers/bitset/count => 20_util/bitset/observers}/6124.cc | 0 .../{23_containers/bitset/all/1.cc => 20_util/bitset/observers/all.cc} | 0 .../{23_containers/bitset/test/1.cc => 20_util/bitset/observers/test.cc} | 0 libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/operations/1.cc | 0 .../testsuite/{23_containers => 20_util}/bitset/operations/13838.cc | 0 libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/operations/2.cc | 0 .../testsuite/{23_containers => 20_util}/bitset/operations/96303.cc | 0 .../testsuite/{23_containers => 20_util}/bitset/operations/constexpr-2.cc | 0 .../testsuite/{23_containers => 20_util}/bitset/operations/constexpr.cc | 0 .../{23_containers => 20_util}/bitset/requirements/constexpr_functions.cc | 0 .../bitset/requirements/explicit_instantiation/1.cc | 0 .../bitset/requirements/explicit_instantiation/1_c++0x.cc | 0 .../testsuite/{23_containers => 20_util}/headers/bitset/synopsis.cc | 0 34 files changed, 0 insertions(+), 0 deletions(-) rename libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/18604.cc (100%) rename libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/45713.cc (100%) rename libstdc++-v3/testsuite/{23_containers/bitset/to_string => 20_util/bitset/ac [...] rename libstdc++-v3/testsuite/{23_containers/bitset/to_string/1.cc => 20_util/bits [...] rename libstdc++-v3/testsuite/{23_containers/bitset/to_ullong/1.cc => 20_util/bits [...] rename libstdc++-v3/testsuite/{23_containers/bitset/to_ulong/1.cc => 20_util/bitse [...] rename libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/cons/1.cc (100%) rename libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/cons/16020.cc (100%) rename libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/cons/2.cc (100%) rename libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/cons/3.cc (100%) rename libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/cons/38244.cc (100%) rename libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/cons/50268.cc (100%) rename libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/cons/6282.cc (100%) rename libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/cons/constexpr.cc (100%) rename libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/cons/dr1325-1.cc (100%) rename libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/cons/dr1325-2.cc (100%) rename libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/cons/dr396.cc (100%) rename libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/debug/invalidation [...] rename libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/ext/15361.cc (100%) rename libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/hash/1.cc (100%) rename libstdc++-v3/testsuite/{23_containers/bitset/input/1.cc => 20_util/bitset/i [...] rename libstdc++-v3/testsuite/{23_containers/bitset/count => 20_util/bitset/observ [...] rename libstdc++-v3/testsuite/{23_containers/bitset/all/1.cc => 20_util/bitset/obs [...] rename libstdc++-v3/testsuite/{23_containers/bitset/test/1.cc => 20_util/bitset/ob [...] rename libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/operations/1.cc (100%) rename libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/operations/13838.c [...] rename libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/operations/2.cc (100%) rename libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/operations/96303.c [...] rename libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/operations/constex [...] rename libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/operations/constex [...] rename libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/requirements/const [...] rename libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/requirements/expli [...] rename libstdc++-v3/testsuite/{23_containers => 20_util}/bitset/requirements/expli [...] rename libstdc++-v3/testsuite/{23_containers => 20_util}/headers/bitset/synopsis.c [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_ubsan updated (7615380cb6 -> 57a244aeb9)

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_ubsan in repository toolchain/ci/base-artifacts. from 7615380cb6 40: onsuccess: #462: 2: Success after binutils/gcc: 47 commits new 57a244aeb9 41: onsuccess: #463: 2: Success after binutils/gcc: 39 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 1692 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2760 bytes 04-build_abe-binutils/console.log.xz | Bin 38964 -> 39080 bytes 05-build_abe-bootstrap_ubsan/console.log.xz | Bin 323468 -> 325992 bytes 06-check_regression/console.log.xz | Bin 2356 -> 2392 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 | 18 +++++++++--------- 12 files changed, 15 insertions(+), 15 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (34a9ac52a9 -> 0c8ff94330)

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-aarch64 in repository toolchain/ci/base-artifacts. discards 34a9ac52a9 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards e613b0ad7a 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards 8eb1db95c8 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards 8f168d5d36 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards bfbb737261 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards 21f71d8a95 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards ece3d03298 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards 85260cf1ce 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards 7873453f67 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 5cd117a3c4 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 0e4a5df213 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards 9e9ae91686 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards f772556761 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards 80833d9156 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards b9ecd08f0b 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards d1b7c7ea98 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards f38e0fc97e 102: force: #1551: 1: Failure after gcc: 306 commits discards 5752610c4f 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 95a16d393a 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards e473cd11a7 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 092d8d2c64 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards bdefce9e38 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 9d769bc029 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 63ae949707 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards aeac0c9d6f 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 1ddd0509db 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 4da1ca855c 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 1ae4a222ba 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards f3c5e28334 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards a6747c1105 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 4a98719481 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 3465daab96 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards e8b9c5fa5b 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 055bc4c8fb 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards e413c3a9a7 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards c1f14ac86c 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 5af27d5380 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards b542829a6c 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 26a085c8b9 80: onsuccess: 7: Successful build after linux: 44 commits discards a9dd388d6c 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 5099dd2fcb 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards 420a1a6c6c 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 249d5a81dd 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 6f13c714f3 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards f7be7dae44 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards d18135e44d 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards f34fc156c0 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 3c67f17821 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards b806b9979d 70: onsuccess: 7: Successful build after gcc: 4 commits discards d9cdc4712f 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 0d2f8bc549 68: onsuccess: 7: Successful build after linux: 6 commits discards fdffe2f7e8 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards a13065f90e 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards 211976a815 65: onsuccess: 7: Successful build after binutils: 3 commits discards 1f466cafc5 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards c54398e19b 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 18d317b1ed 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 564626d875 61: onsuccess: 4: Successful build after gcc: 5 commits discards 2bd06cd1a5 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 826a21f3c6 59: force: 7: Successful build after gcc: 3 commits discards 2249e17cf5 58: onsuccess: 7: Successful build after glibc: 2 commits discards f2212678e3 57: onsuccess: 7: Successful build after gcc: 7 commits discards 3a2f3b8f98 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ecf7aaf67f 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards d8faf3fb87 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards 8b6c224732 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards f5ededea60 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] discards adba085481 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 7bdf5c113d 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards da169d55d7 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 64c4496418 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards 76e2c91727 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards c0a72d5130 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 742bcd1610 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards a367785286 44: onsuccess: 7: Successful build after linux: 34 commits discards c520aa34b1 43: onsuccess: 7: Successful build after gcc: 2 commits discards 84be169108 42: onsuccess: 7: Successful build after baseline build: no [...] discards c658927e71 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards f5634245a8 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards b88bd28951 39: onsuccess: 7: Successful build after gcc: 2 commits discards a7ea6c4890 38: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 47192a8d13 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards d6614fc366 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards d62742bb3c 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 9a001b301f 34: onsuccess: 7: Successful build after gcc: 3 commits discards a9c0b5ef64 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards de914325c7 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 97ffcd91af 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 713dc76f81 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits discards e0bda9e091 29: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 860f31e607 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards b1e344accf 27: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 2d3685a759 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 28585d6603 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards b36004d1e1 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards c538210530 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e54c622aa1 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 252dd340c3 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d2aa7264f0 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d7c61b79b0 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 7887ae5e08 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a957d95042 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 671375cac0 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 82cd1ae7ad 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new aa721f77af 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 623a780720 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new c8bc7e05c5 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 0f274017d1 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new bab6b1b4fe 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d24a83c27b 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new b171952a5a 27: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new eae73dc4cc 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new e15a43d147 29: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ac5c50a5bb 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits new 21df245bf6 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new d1122a7099 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new 2d25cdb71a 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 3e62d67248 34: onsuccess: 7: Successful build after gcc: 3 commits new 53f9dfc455 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 119236eeac 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 6757041bbf 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new c690dd90de 38: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 1a1e69e8e2 39: onsuccess: 7: Successful build after gcc: 2 commits new ecc83e2ce3 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 3ece676ccc 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new d60cec7942 42: onsuccess: 7: Successful build after baseline build: no [...] new 8c2d26d159 43: onsuccess: 7: Successful build after gcc: 2 commits new 72207dc358 44: onsuccess: 7: Successful build after linux: 34 commits new 198080d4b0 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b7c65955e6 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new fc263510ef 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5fef2d1cf4 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new 65be65201a 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 827b611f93 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 369e7f140c 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new b8fd04fe2a 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] new 34e6caef04 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 867781f1b3 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new 63128457d2 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 8cc540f437 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ace0af7401 57: onsuccess: 7: Successful build after gcc: 7 commits new 89f64dd91f 58: onsuccess: 7: Successful build after glibc: 2 commits new d2399b4fba 59: force: 7: Successful build after gcc: 3 commits new 807207ef49 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new b84295e3ce 61: onsuccess: 4: Successful build after gcc: 5 commits new 02c4fb0fb5 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new d27fa33125 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new bca8a06d80 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 3d4fda9f5f 65: onsuccess: 7: Successful build after binutils: 3 commits new a7d912e94f 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new 6c58ce60b5 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new a9d56bc189 68: onsuccess: 7: Successful build after linux: 6 commits new 289c1578de 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 451bd78ea6 70: onsuccess: 7: Successful build after gcc: 4 commits new 161ef296eb 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new f472143703 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new aee240c061 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 521e9c8c09 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 751c6df587 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 6345d26d26 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new e91c045987 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new c3ad61b7d6 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new 09ffc46c39 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new ae05a472ba 80: onsuccess: 7: Successful build after linux: 44 commits new db6b487ec0 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7b29686cfd 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 66b57f84e8 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5b01ecad90 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 786f55fead 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 0d259971ca 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 25f11e261d 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 611147f0ff 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 00451f2c14 89: onsuccess: 7: Success after gcc/glibc: 8 commits new f06b0e7c7d 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 4a6e7cb2eb 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 9bf24115b1 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 2bb2effce8 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 59712771b0 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 6039af19ab 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new c52ace98ce 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new aca272998f 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 0ebd430006 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 7257d50689 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 8f4a811420 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new 2dac63145c 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 71641ef7d1 102: force: #1551: 1: Failure after gcc: 306 commits new 86049ec851 103: onsuccess: #1552: 1: Success after gcc: 5 commits new e6bf5613ff 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new 0e9df82e15 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new d40009d0f9 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 271eb8635d 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new 5c7cf1eda2 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new 382863c99d 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new ff2247bce5 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 3be84fdc71 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new ff75280c9c 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new 7bf7405c95 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new 7eb5765440 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new ada348abf6 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new 85704310ad 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new 518b91be5b 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new 997125d019 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new 0c8ff94330 119: onsuccess: #1568: 7: 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 (34a9ac52a9) \ 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 1724 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 30240 -> 30292 bytes 05-build_abe-stage1/console.log.xz | Bin 72456 -> 72700 bytes 06-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 07-build_abe-linux/console.log.xz | Bin 8612 -> 8584 bytes 08-build_abe-glibc/console.log.xz | Bin 240100 -> 239640 bytes 09-build_abe-stage2/console.log.xz | Bin 202820 -> 203276 bytes 10-build_abe-gdb/console.log.xz | Bin 37448 -> 37476 bytes 11-build_abe-qemu/console.log.xz | Bin 31788 -> 31764 bytes 12-check_regression/console.log.xz | Bin 2400 -> 3140 bytes 13-update_baseline/console.log | 38 +++++++++++++++++------------------ 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +++++++++++++++++------------------ 21 files changed, 46 insertions(+), 46 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[gcc] branch master updated (44dba051d72 -> f35be1268c9)

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 44dba051d72 tree-optimization/102801 - testcase for uninit diagnostic new f35be1268c9 cmd/cgo: add and use runtime/cgo.Incomplete instead of //go [...] 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/go/gofrontend/MERGE | 2 +- libgo/go/cmd/cgo/gcc.go | 77 ++++++++++++++++++------------------ libgo/go/cmd/cgo/main.go | 1 - libgo/go/cmd/cgo/out.go | 13 +++--- libgo/go/cmd/go/internal/load/pkg.go | 8 ++-- libgo/go/runtime/cgo/cgo.go | 18 +++++++++ 6 files changed, 67 insertions(+), 52 deletions(-) create mode 100644 libgo/go/runtime/cgo/cgo.go -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (a0e26ef777 -> 79afd0fe70)

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 a0e26ef777 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits discards 6520b8edeb 117: onsuccess: #2034: 1: Success after binutils: 2 commits discards f10e61c704 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits discards b2893c46d2 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits discards 9d5a1b3100 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits discards fcc2f51cdb 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits discards 6073f5495c 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits discards d4482404e6 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits discards aeb18d586f 110: onsuccess: #2027: 1: Success after gcc: 5 commits discards 3c4ab1638f 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits discards d3680f7630 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits discards f38b8f60b6 107: onsuccess: #2024: 1: Success after gcc: 3 commits discards b0ee82a785 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits discards dce6b68d2d 105: onsuccess: #2022: 1: Success after gcc: 4 commits discards 2808f35d20 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits discards a2c96a1783 103: onsuccess: #2020: 1: Success after gcc: 2 commits discards 892d3265ee 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] discards a5d2d35aa8 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits discards c0ab9016c6 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits discards 4eaaae85bc 99: onsuccess: #1974: 1: Success after gcc: 14 commits discards 5495325532 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits discards 20295f1290 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits discards 3c8e409fb3 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] discards 9f8365506d 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] discards 5202285b5b 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits discards be3d0b3b7a 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] discards d66702b84a 92: onsuccess: #1965: 1: Success after gcc: 2 commits discards eb9e9a9777 91: onsuccess: 1: Success after gcc: Daily bump. discards 073edd4540 90: onsuccess: 1: Success after binutils/gcc: 6 commits discards 2fa0f88434 89: onsuccess: 1: Success after binutils/gcc: 9 commits discards 35d3e5707d 88: onsuccess: 1: Success after binutils/gcc: 16 commits discards 9e336cdfe1 87: onsuccess: 1: Success after binutils/gcc: 4 commits discards 8c8bfa7fd2 86: onsuccess: 1: Success after binutils/gcc: 13 commits discards dd883ca1e8 85: onsuccess: 1: Success after binutils/gcc: 9 commits discards 1d3d44c774 84: onsuccess: 1: Success after binutils/gcc: 9 commits discards 58aa9965e8 83: onsuccess: 1: Success after gcc: 8 commits discards 4b79d7b6be 82: onsuccess: 1: Success after binutils/gcc: 10 commits discards 8d3b400788 81: onsuccess: 1: Success after binutils/gcc: 27 commits discards 11e4e32642 80: onsuccess: 1: Success after binutils/gcc: 14 commits discards 09b36e6ec0 79: onsuccess: 1: Successful build after gcc: Daily bump. discards 0bfa48a4c5 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards b7e1600de0 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards 8fc4221aff 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards 59bf60658f 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 62cba021bb 74: onsuccess: 1: Successful build after binutils: Automatic [...] discards 638c842a12 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards f14ca83138 72: onsuccess: 1: Successful build after gcc: 2 commits discards c848900d51 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards dfdeec7777 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] discards dd9a3fddda 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 19ae3a6133 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 342da42f4c 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards c077869a03 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards fde8fbe766 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards f6916f62fb 64: onsuccess: 1: Successful build after gcc: 5 commits discards dff13303a1 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 2a52e65813 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 6f10e9afff 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits discards 433db072f5 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 695b3ed9b7 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits discards 689abc1842 58: onsuccess: 1: Successful build after binutils: 2 commits discards 235bb9c742 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits discards 86f7bed7b3 56: onsuccess: 1: Successful build after gcc: Daily bump. discards e6ef7e6764 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 99fd009b3c 54: onsuccess: 1: Successful build after gcc: 7 commits discards 102ef0f15d 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards 7220e31a02 52: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 733c4c613b 51: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 798bd57aa6 50: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 8a32a12e63 49: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 0a6cff1df2 48: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards e84cfbd03c 47: onsuccess: 1: Successful build after binutils: 2 commits discards 923d632216 46: onsuccess: 1: Successful build after gcc: Daily bump. discards 221b3ce644 45: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 4e09e0336e 44: onsuccess: 1: Successful build after gcc: 2 commits discards 01589e90ad 43: onsuccess: 1: Successful build after gcc: Daily bump. discards d7f55226be 42: onsuccess: 1: Successful build after binutils: Automatic [...] discards 19bae75c3b 41: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 38821d45c0 40: onsuccess: 1: Successful build after gcc: 2 commits discards 4f4ac82a94 39: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 96c29ea109 38: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 17296c899b 37: onsuccess: 1: Successful build after binutils/gcc: 12 commits discards d3ec359aee 36: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards 33cfbcda33 35: onsuccess: 1: Successful build after gcc: 4 commits discards 09fd8e5e5b 34: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 1b417b1b89 33: onsuccess: 1: Successful build after gcc: 10 commits discards a411c398a5 32: onsuccess: 1: Successful build after binutils/gcc: 9 commits discards 9d9e334c48 31: onsuccess: 1: Successful build after gcc: 2 commits discards afbc15ffe2 30: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards f536c89209 29: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 7e07135e23 28: onsuccess: 1: Successful build after binutils/gcc: 22 commits discards 175abff7b4 27: onsuccess: binutils-gcc: 1 discards 3e2906f8fc 26: onsuccess: binutils-gcc: 1 discards f5ff167fff 25: onsuccess: binutils-gcc: 1 discards 13ce9b1572 24: onsuccess: binutils-gcc: 1 discards fd6a098de5 23: onsuccess: binutils-gcc: 1 discards c43628bac8 22: onsuccess: binutils-gcc: 1 discards f23501d15a 21: onsuccess: binutils-gcc: 1 discards 154b0d760a 20: onsuccess: binutils-gcc: 1 discards 04782bc62d 19: onsuccess: binutils-gcc: 1 discards 7e4e898694 18: onsuccess: binutils-gcc: 1 new d1d38599e1 18: onsuccess: binutils-gcc: 1 new 600d3d6fc9 19: onsuccess: binutils-gcc: 1 new 68a15e53d9 20: onsuccess: binutils-gcc: 1 new 12ff86e981 21: onsuccess: binutils-gcc: 1 new b629982aef 22: onsuccess: binutils-gcc: 1 new e09b4105d7 23: onsuccess: binutils-gcc: 1 new e83a1f296b 24: onsuccess: binutils-gcc: 1 new fa82f350b8 25: onsuccess: binutils-gcc: 1 new 37edd37cad 26: onsuccess: binutils-gcc: 1 new 484d9c4790 27: onsuccess: binutils-gcc: 1 new 4a788cb8e7 28: onsuccess: 1: Successful build after binutils/gcc: 22 commits new f1676a988b 29: onsuccess: 1: Successful build after binutils/gcc: 10 commits new e06712dad8 30: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 782cf5efd3 31: onsuccess: 1: Successful build after gcc: 2 commits new e4a15f14f4 32: onsuccess: 1: Successful build after binutils/gcc: 9 commits new 4cf0739b6c 33: onsuccess: 1: Successful build after gcc: 10 commits new 22449e5cbc 34: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 1e638031af 35: onsuccess: 1: Successful build after gcc: 4 commits new 97e1f68c5a 36: onsuccess: 1: Successful build after binutils/gcc: 11 commits new 9f1fa94ac3 37: onsuccess: 1: Successful build after binutils/gcc: 12 commits new b4c5188dea 38: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 87bde09d7b 39: onsuccess: 1: Successful build after binutils/gcc: 3 commits new dfcc7cf3cd 40: onsuccess: 1: Successful build after gcc: 2 commits new e39a66b1b6 41: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 16eb2981da 42: onsuccess: 1: Successful build after binutils: Automatic [...] new b05ef794d4 43: onsuccess: 1: Successful build after gcc: Daily bump. new cc2ec5c0eb 44: onsuccess: 1: Successful build after gcc: 2 commits new 55fa9c8a1b 45: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 8895bd002c 46: onsuccess: 1: Successful build after gcc: Daily bump. new 6a50b77f36 47: onsuccess: 1: Successful build after binutils: 2 commits new 01ad61dc5f 48: onsuccess: 1: Successful build after binutils/gcc: 3 commits new bd51acdf89 49: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 94c759b79a 50: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 5abd39f544 51: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 72f880563f 52: onsuccess: 1: Successful build after binutils/gcc: 4 commits new d363c6e998 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits new dbba2a792c 54: onsuccess: 1: Successful build after gcc: 7 commits new c7573ee7d5 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits new d258444971 56: onsuccess: 1: Successful build after gcc: Daily bump. new 04ccbb3196 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits new 3a670668c6 58: onsuccess: 1: Successful build after binutils: 2 commits new 03c1d52a4d 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits new 1cf35f9669 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits new a3f5a1b25d 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits new f4f55e3e42 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits new fedbb7a00e 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 9d4b32b869 64: onsuccess: 1: Successful build after gcc: 5 commits new 44bd299cd9 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 46225d723d 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 7eaaf3d9b7 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new f1b749fad7 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 5993107ad7 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] new ce1f20e7aa 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] new b500957dc0 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 851b6263c3 72: onsuccess: 1: Successful build after gcc: 2 commits new 5c396938e6 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] new 01ac67b1b1 74: onsuccess: 1: Successful build after binutils: Automatic [...] new 3ca90139f9 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits new f4b93e149c 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 428bb7c8d2 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 3be1857c7a 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 08c603da5c 79: onsuccess: 1: Successful build after gcc: Daily bump. new 18f9434c8c 80: onsuccess: 1: Success after binutils/gcc: 14 commits new 62aad58c78 81: onsuccess: 1: Success after binutils/gcc: 27 commits new 0e55f94aca 82: onsuccess: 1: Success after binutils/gcc: 10 commits new 871a64a7ee 83: onsuccess: 1: Success after gcc: 8 commits new a941933d1d 84: onsuccess: 1: Success after binutils/gcc: 9 commits new e6490f4c7b 85: onsuccess: 1: Success after binutils/gcc: 9 commits new a4f9ea7149 86: onsuccess: 1: Success after binutils/gcc: 13 commits new c054b2544f 87: onsuccess: 1: Success after binutils/gcc: 4 commits new 3fa5053dab 88: onsuccess: 1: Success after binutils/gcc: 16 commits new cdb93250d6 89: onsuccess: 1: Success after binutils/gcc: 9 commits new f708d436f8 90: onsuccess: 1: Success after binutils/gcc: 6 commits new 9ea4e13ce5 91: onsuccess: 1: Success after gcc: Daily bump. new 5e388544ba 92: onsuccess: #1965: 1: Success after gcc: 2 commits new 1823605886 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] new b592a5e826 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits new eb85007fa5 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] new 16b54b21d5 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] new 02905bfa49 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits new 79734a08c9 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits new 60993d6a0b 99: onsuccess: #1974: 1: Success after gcc: 14 commits new 171ff5bec3 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits new 1f2cbff806 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits new 7456868a46 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] new ae9376c8ce 103: onsuccess: #2020: 1: Success after gcc: 2 commits new a7587180e9 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits new 32b1bf1fb2 105: onsuccess: #2022: 1: Success after gcc: 4 commits new 2b4c898963 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits new a0927ac8de 107: onsuccess: #2024: 1: Success after gcc: 3 commits new 7f9c557bc9 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits new 8f8b54fcf2 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits new f534762c6d 110: onsuccess: #2027: 1: Success after gcc: 5 commits new 5175e9bd0c 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits new 54929780b7 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits new a6a7f597d1 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits new 986b712943 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits new 77a0e90e46 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits new 28c83116be 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits new 70013ad0a9 117: onsuccess: #2034: 1: Success after binutils: 2 commits new 9dd1506fd4 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits new 79afd0fe70 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 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 (a0e26ef777) \ 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 1684 -> 1852 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 38188 -> 37952 bytes 04-build_abe-gcc/console.log.xz | Bin 213812 -> 211716 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3824 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2508 -> 3060 bytes 07-check_regression/console.log.xz | Bin 3704 -> 9156 bytes 07-check_regression/extra-bisect-params | 1 + 07-check_regression/fails.sum | 579 ++++ 07-check_regression/mail-body.txt | 101 + 07-check_regression/results.compare | 598 +++- 07-check_regression/results.compare2 | 636 +++- 07-check_regression/results.regressions | 101 + 08-update_baseline/console.log | 36 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 103 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 101 + sumfiles/g++.log.xz | Bin 3573976 -> 3589148 bytes sumfiles/g++.sum | 644 ++-- sumfiles/gcc.log.xz | Bin 3082004 -> 3128596 bytes sumfiles/gcc.sum | 4881 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1042052 -> 1040436 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2184 -> 2188 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 207328 -> 207180 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2548 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 444776 -> 448372 bytes sumfiles/libstdc++.sum | 12 +- 36 files changed, 5101 insertions(+), 2786 deletions(-) create mode 100644 07-check_regression/extra-bisect-params create mode 100644 07-check_regression/fails.sum create mode 100644 07-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_lto updated (dae2b1ba45 -> be0cf828f5)

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_lto in repository toolchain/ci/base-artifacts. from dae2b1ba45 41: onsuccess: #447: 2: Success after binutils/gcc: 45 commits new be0cf828f5 42: onsuccess: #448: 2: Success after binutils/gcc: 39 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 1680 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2704 bytes 04-build_abe-binutils/console.log.xz | Bin 50772 -> 50964 bytes 05-build_abe-bootstrap_lto/console.log.xz | Bin 472628 -> 472996 bytes 06-check_regression/console.log.xz | Bin 2360 -> 2312 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 | 18 +++++++++--------- 12 files changed, 15 insertions(+), 15 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[gcc] branch master updated (32d8123cd6c -> 44dba051d72)

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 32d8123cd6c c++ modules: partial variable template specializations [PR106826] new 44dba051d72 tree-optimization/102801 - testcase for uninit diagnostic 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/testsuite/g++.dg/warn/Wuninitialized-33.C | 55 +++++++++++++++++++++++++++ 1 file changed, 55 insertions(+) create mode 100644 gcc/testsuite/g++.dg/warn/Wuninitialized-33.C -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-stable-allyesconfig updated (30c4960bba -> db96d678f4)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-stable-allyesconfig in repository toolchain/ci/base-artifacts. from 30c4960bba 14: onsuccess: #473: 33: Success after binutils/gcc/linux/qe [...] new db96d678f4 15: onsuccess: #474: 33: Success after binutils/gcc/linux/qe [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1708 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30016 -> 30060 bytes 04-build_abe-stage1/console.log.xz | Bin 91264 -> 90648 bytes 05-build_abe-qemu/console.log.xz | Bin 31288 -> 31444 bytes 06-build_linux/console.log.xz | Bin 5328 -> 4900 bytes 08-check_regression/console.log.xz | Bin 3256 -> 3408 bytes 09-update_baseline/console.log | 9 +++++++++ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- 17 files changed, 32 insertions(+), 23 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/master-aarch64 updated (ade0e645c2 -> 95408ddf2b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_build/master-aarch64 in repository toolchain/ci/base-artifacts. from ade0e645c2 42: onsuccess: #454: 6: Success after binutils/gcc/linux/gli [...] new 95408ddf2b 43: onsuccess: #455: 6: Success after binutils/gcc/linux/gli [...] 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 1668 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 37768 -> 37680 bytes 05-build_abe-gcc/console.log.xz | Bin 212996 -> 212568 bytes 06-clean_sysroot/console.log.xz | Bin 312 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 8704 -> 8716 bytes 08-build_abe-glibc/console.log.xz | Bin 241724 -> 241964 bytes 09-build_abe-gdb/console.log.xz | Bin 38632 -> 38452 bytes 10-check_regression/console.log.xz | Bin 3568 -> 3560 bytes 11-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +++++++++++++++++------------------ 20 files changed, 28 insertions(+), 28 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits September 2022