Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (4127416d5c -> edb036b732)

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 4127416d5c 145: onsuccess: #2078: 1: Success after binutils/gcc: 10 commits discards 19b5c8f698 144: onsuccess: #2077: 1: Success after binutils/gcc: 15 commits discards 571e9d07f9 143: onsuccess: #2076: 1: Success after binutils/gcc: 14 commits discards ac1ec96b1a 142: onsuccess: #2075: 1: Success after binutils/gcc: 71 commits discards 94784fa72b 141: onsuccess: #2073: 1: Success after binutils: 3 commits discards 40b56abf08 140: onsuccess: #2070: 1: Success after binutils: 4 commits discards 33beca1845 139: onsuccess: #2067: 1: Success after binutils: 2 commits discards 53ed044e52 138: onsuccess: #2064: 1: Success after binutils: 4 commits discards 35bfb7787f 137: onsuccess: #2061: 1: Success after binutils: 2 commits discards 475fe7649f 136: onsuccess: #2056: 1: Success after binutils: 4 commits discards d087c3eb14 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits discards d4ee24fef7 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits discards a483136803 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits discards 860955f10c 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits discards db04826ce1 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] discards 7092228590 130: onsuccess: #2049: 1: Success after gcc: 9 commits discards 1c6c9833cb 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] discards a49dd43ca8 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] discards 9e9bce8f0f 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] discards 6c8f82b104 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] discards 313bb468db 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits discards 4243caaf26 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits discards 6b33a48f8f 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits discards 59c7c6144a 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits discards 551c1701a2 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits discards 74f07f3398 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits discards 4224235c17 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits discards 05a7a6abb3 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits discards 1202439a60 117: onsuccess: #2034: 1: Success after binutils: 2 commits discards 0f6b582251 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits discards bd9be62898 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits discards bf6dd0634c 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits discards cf21d4388a 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits discards 331417ccb3 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits discards 0f48e51cbe 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits discards 3bfc488332 110: onsuccess: #2027: 1: Success after gcc: 5 commits discards 09fe868a3a 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits discards b00ae5c6df 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits discards a47182266c 107: onsuccess: #2024: 1: Success after gcc: 3 commits discards 0587cf8aaf 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits discards 57674dcffe 105: onsuccess: #2022: 1: Success after gcc: 4 commits discards aca929f226 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits discards 0c6d2108ac 103: onsuccess: #2020: 1: Success after gcc: 2 commits discards 62f10e26ce 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] discards 269fbb5cbb 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits discards 15fed3be18 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits discards 2a91523d72 99: onsuccess: #1974: 1: Success after gcc: 14 commits discards e5306b3c97 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits discards 0bd6ddb9c1 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits discards b7d7ebbe50 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] discards 1a0613095b 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] discards f63a90abf8 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits discards 3e6572c7b5 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] discards d0599f2a71 92: onsuccess: #1965: 1: Success after gcc: 2 commits discards 8b4d2e7dbc 91: onsuccess: 1: Success after gcc: Daily bump. discards e9bfb63dd0 90: onsuccess: 1: Success after binutils/gcc: 6 commits discards 7fed26eebf 89: onsuccess: 1: Success after binutils/gcc: 9 commits discards 612dcda40c 88: onsuccess: 1: Success after binutils/gcc: 16 commits discards 1677ae3e81 87: onsuccess: 1: Success after binutils/gcc: 4 commits discards a8bb61531a 86: onsuccess: 1: Success after binutils/gcc: 13 commits discards 53da167529 85: onsuccess: 1: Success after binutils/gcc: 9 commits discards 393722885b 84: onsuccess: 1: Success after binutils/gcc: 9 commits discards 1b39c517b6 83: onsuccess: 1: Success after gcc: 8 commits discards 39c18759b2 82: onsuccess: 1: Success after binutils/gcc: 10 commits discards efe52fecf2 81: onsuccess: 1: Success after binutils/gcc: 27 commits discards 3e772308e9 80: onsuccess: 1: Success after binutils/gcc: 14 commits discards 212f412b04 79: onsuccess: 1: Successful build after gcc: Daily bump. discards b3c0ba150a 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards a756c86a80 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards ac93780669 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards cd24c90347 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 81edbf08a6 74: onsuccess: 1: Successful build after binutils: Automatic [...] discards c5c5ae3fc7 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards 3f87a42514 72: onsuccess: 1: Successful build after gcc: 2 commits discards 3ccbb0d45c 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 991f937dfc 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] discards c1c1298611 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards f14591e784 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 6ff45aedac 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 86cb74d1b8 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards b31396958d 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 75f062127f 64: onsuccess: 1: Successful build after gcc: 5 commits discards 6deb6d201d 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 7a9a3d2d8b 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 7baa6eb208 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits discards 980703e043 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 580b55c61a 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits discards 4885e12fcd 58: onsuccess: 1: Successful build after binutils: 2 commits discards 1b84370f9c 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits discards 0054781c66 56: onsuccess: 1: Successful build after gcc: Daily bump. discards 5d132af293 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 4d78034f47 54: onsuccess: 1: Successful build after gcc: 7 commits discards 30de8bb389 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards 9e8fb5de43 52: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 871c0de9eb 51: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 21871bc1d5 50: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 693046cfba 49: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 78a1ac45b2 48: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 2432936b27 47: onsuccess: 1: Successful build after binutils: 2 commits discards 6494cf8e1f 46: onsuccess: 1: Successful build after gcc: Daily bump. discards 8574e28ac1 45: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 6d7f2f6f99 45: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 826c970905 46: onsuccess: 1: Successful build after gcc: Daily bump. new 13e52f35e5 47: onsuccess: 1: Successful build after binutils: 2 commits new 26b2ef2dd0 48: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 22ce3184ac 49: onsuccess: 1: Successful build after binutils/gcc: 6 commits new ceec6ecd60 50: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 42b016004e 51: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 06c2be07c7 52: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 932060cc36 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 8dca8d6d62 54: onsuccess: 1: Successful build after gcc: 7 commits new 60870ba6dc 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 28e4610633 56: onsuccess: 1: Successful build after gcc: Daily bump. new da6c97f25d 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits new 980c51e7d8 58: onsuccess: 1: Successful build after binutils: 2 commits new 8fc060b0a8 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits new d2c94821be 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 8a6d025b25 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits new 0d36e47bd0 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits new b5c1c3b5c6 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 354c1cef8e 64: onsuccess: 1: Successful build after gcc: 5 commits new e3fd9f9108 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 7ecf22ed6b 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits new cff7df920d 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 53890f84d1 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits new a443bb1682 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 00bd929440 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] new 92e4c6c6c1 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits new be7c231a29 72: onsuccess: 1: Successful build after gcc: 2 commits new 94bdf565cf 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] new 65e896aba0 74: onsuccess: 1: Successful build after binutils: Automatic [...] new 4cab0d7cd2 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits new 1af3450a20 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits new bb80db79bb 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 2fc18aa27a 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 4e63952e8f 79: onsuccess: 1: Successful build after gcc: Daily bump. new c356081e10 80: onsuccess: 1: Success after binutils/gcc: 14 commits new b6b49743a3 81: onsuccess: 1: Success after binutils/gcc: 27 commits new d1d9e9f63e 82: onsuccess: 1: Success after binutils/gcc: 10 commits new fac1b158df 83: onsuccess: 1: Success after gcc: 8 commits new 2240282645 84: onsuccess: 1: Success after binutils/gcc: 9 commits new 3b34171edc 85: onsuccess: 1: Success after binutils/gcc: 9 commits new 0db189c584 86: onsuccess: 1: Success after binutils/gcc: 13 commits new a26bbaf752 87: onsuccess: 1: Success after binutils/gcc: 4 commits new b50801f729 88: onsuccess: 1: Success after binutils/gcc: 16 commits new 3ade1f7626 89: onsuccess: 1: Success after binutils/gcc: 9 commits new 7ec65e0892 90: onsuccess: 1: Success after binutils/gcc: 6 commits new f6b3c4be14 91: onsuccess: 1: Success after gcc: Daily bump. new 2f760d4dac 92: onsuccess: #1965: 1: Success after gcc: 2 commits new 5d3ebe9568 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] new 067f92fe58 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits new 0e36f29960 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] new a7ea01c9f9 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] new 23d1073513 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits new 9fd396cd04 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits new 0af656e91e 99: onsuccess: #1974: 1: Success after gcc: 14 commits new ab1e1e3d0a 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits new 40739cd869 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits new 32cfd23041 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] new 5fb03d0245 103: onsuccess: #2020: 1: Success after gcc: 2 commits new faa9e4c6a1 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits new d221a6b270 105: onsuccess: #2022: 1: Success after gcc: 4 commits new 40c841e2a9 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits new 021cde3f21 107: onsuccess: #2024: 1: Success after gcc: 3 commits new 25ae94ef27 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits new 54ad8735b6 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits new 8337a879ca 110: onsuccess: #2027: 1: Success after gcc: 5 commits new 7083a2bd4d 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits new 253040233d 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits new df9f4b04f3 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits new 205aec77fa 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits new 4e7bf1d8d8 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits new 8b9fa3310b 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits new 0e7fcb4b6e 117: onsuccess: #2034: 1: Success after binutils: 2 commits new c35abc8261 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits new 2e1173858b 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits new 91f25648e5 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits new 856cf016dc 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits new 47aad657e1 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits new f826e9136b 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits new d56844b3c4 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits new a17084416f 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits new d2aa8002fb 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] new 3c6efd77c0 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] new a951db640d 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] new 8dacca487e 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] new 8d68633a97 130: onsuccess: #2049: 1: Success after gcc: 9 commits new 624b2b4b08 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] new 6bcf18cd14 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits new 03e40c2f92 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits new 84f2708c0c 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits new 6df4a07a2f 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits new cf575d24c8 136: onsuccess: #2056: 1: Success after binutils: 4 commits new 092b2000b5 137: onsuccess: #2061: 1: Success after binutils: 2 commits new 671a79a015 138: onsuccess: #2064: 1: Success after binutils: 4 commits new 25c426b662 139: onsuccess: #2067: 1: Success after binutils: 2 commits new 7e09783be8 140: onsuccess: #2070: 1: Success after binutils: 4 commits new 844ef94d65 141: onsuccess: #2073: 1: Success after binutils: 3 commits new 57c1f85115 142: onsuccess: #2075: 1: Success after binutils/gcc: 71 commits new f2454e15e1 143: onsuccess: #2076: 1: Success after binutils/gcc: 14 commits new 9ca808ea80 144: onsuccess: #2077: 1: Success after binutils/gcc: 15 commits new 2976d453e0 145: onsuccess: #2078: 1: Success after binutils/gcc: 10 commits new edb036b732 146: onsuccess: #2079: 1: Success after binutils/gcc: 14 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 (4127416d5c) \ 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 1712 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 38460 -> 37572 bytes 04-build_abe-gcc/console.log.xz | Bin 213908 -> 211604 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3848 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2724 -> 3124 bytes 07-check_regression/console.log.xz | Bin 4712 -> 5388 bytes 07-check_regression/results.compare2 | 67 +- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- sumfiles/g++.log.xz | Bin 3569964 -> 3575892 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 3100244 -> 3095800 bytes sumfiles/gcc.sum | 4484 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1041792 -> 1043508 bytes sumfiles/gfortran.sum | 12 +- sumfiles/libatomic.log.xz | Bin 2184 -> 2188 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 207396 -> 207568 bytes sumfiles/libgomp.sum | 45 +- sumfiles/libitm.log.xz | Bin 2544 -> 2544 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 443520 -> 448256 bytes sumfiles/libstdc++.sum | 2 +- 30 files changed, 2399 insertions(+), 2305 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_ubsan updated (9b5d662a6b -> 10b86458e4)

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 9b5d662a6b 48: onsuccess: #474: 1: Success after gcc: 10 commits new 10b86458e4 49: onsuccess: #475: 2: Success after binutils/gcc: 121 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 1720 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 38004 -> 37652 bytes 05-build_abe-bootstrap_ubsan/console.log.xz | Bin 80016 -> 325504 bytes 06-check_regression/console.log.xz | Bin 2668 -> 3164 bytes 06-check_regression/mail-body.txt | 13 +------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 15 ++------------- mail/mail-subject.txt | 2 +- manifest.sh | 21 +++++++++++---------- results | 2 +- 14 files changed, 20 insertions(+), 41 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_native_build/master-aarch64 updated (826d1bda50 -> 64bd0df6de)

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 826d1bda50 53: onsuccess: #467: 6: Success after binutils/gcc/linux/gli [...] new 64bd0df6de 54: onsuccess: #468: 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 1652 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2716 bytes 04-build_abe-binutils/console.log.xz | Bin 37532 -> 37584 bytes 05-build_abe-gcc/console.log.xz | Bin 211624 -> 213212 bytes 06-clean_sysroot/console.log.xz | Bin 312 -> 316 bytes 07-build_abe-linux/console.log.xz | Bin 8624 -> 8548 bytes 08-build_abe-glibc/console.log.xz | Bin 241704 -> 241800 bytes 09-build_abe-gdb/console.log.xz | Bin 38408 -> 38232 bytes 10-check_regression/console.log.xz | Bin 4808 -> 4460 bytes 10-check_regression/mail-body.txt | 8 +++++++- 11-update_baseline/console.log | 9 +++++++++ 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 | 10 +++++++-- mail/mail-subject.txt | 2 +- manifest.sh | 38 +++++++++++++++++------------------ 21 files changed, 51 insertions(+), 30 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_O3 updated (c7c77f9c12 -> 860202c228)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_O3 in repository toolchain/ci/base-artifacts. from c7c77f9c12 50: onsuccess: #468: 1: Success after gcc: 26 commits new 860202c228 51: onsuccess: #469: 2: Success after binutils/gcc: 121 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 1688 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2716 bytes 04-build_abe-binutils/console.log.xz | Bin 51052 -> 50316 bytes 05-build_abe-bootstrap_O3/console.log.xz | Bin 110844 -> 461740 bytes 06-check_regression/console.log.xz | Bin 2676 -> 3116 bytes 06-check_regression/mail-body.txt | 11 +---------- 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 | 21 +++++++++++---------- results | 2 +- 14 files changed, 20 insertions(+), 37 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (c09663eabfb -> c23b5006d3f)

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 c09663eabfb testsuite: [arm] Relax expected register names in MVE tests new c28957176dc rs6000/test: Adjust pr104992.c with vect_int_mod [PR106516] new c23b5006d3f rs6000: Rework ELFv2 support for -fpatchable-function-entry [...] The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/config/rs6000/rs6000-internal.h | 4 ++ gcc/config/rs6000/rs6000-logue.cc | 32 ++++++++++++++++ gcc/config/rs6000/rs6000.cc | 10 ++++- gcc/config/rs6000/rs6000.h | 4 ++ gcc/doc/invoke.texi | 8 +++- .../patchable_function_entry-default.c | 3 ++ gcc/testsuite/gcc.dg/pr104992.c | 3 +- gcc/testsuite/gcc.target/powerpc/pr99888-1.c | 43 ++++++++++++++++++++++ gcc/testsuite/gcc.target/powerpc/pr99888-2.c | 43 ++++++++++++++++++++++ gcc/testsuite/gcc.target/powerpc/pr99888-3.c | 11 ++++++ gcc/testsuite/gcc.target/powerpc/pr99888-4.c | 13 +++++++ gcc/testsuite/gcc.target/powerpc/pr99888-5.c | 13 +++++++ gcc/testsuite/gcc.target/powerpc/pr99888-6.c | 14 +++++++ gcc/testsuite/lib/target-supports.exp | 8 ++++ 14 files changed, 204 insertions(+), 5 deletions(-) create mode 100644 gcc/testsuite/gcc.target/powerpc/pr99888-1.c create mode 100644 gcc/testsuite/gcc.target/powerpc/pr99888-2.c create mode 100644 gcc/testsuite/gcc.target/powerpc/pr99888-3.c create mode 100644 gcc/testsuite/gcc.target/powerpc/pr99888-4.c create mode 100644 gcc/testsuite/gcc.target/powerpc/pr99888-5.c create mode 100644 gcc/testsuite/gcc.target/powerpc/pr99888-6.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-mainline-allyesconfig updated (ee9b8d41a4 -> cf0064eeb9)

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-aarch64-mainline-allyesconfig in repository toolchain/ci/base-artifacts. from ee9b8d41a4 16: onsuccess: #503: all: Success after binutils: 24 commits new cf0064eeb9 17: onsuccess: #505: all: Success after qemu: 118 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 1720 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30388 -> 30352 bytes 04-build_kernel_llvm/console.log.xz | Bin 65408 -> 63736 bytes 05-build_abe-qemu/console.log.xz | Bin 31972 -> 31616 bytes 06-build_linux/console.log.xz | Bin 3216 -> 3108 bytes 07-boot_linux/console.log.xz | Bin 576 -> 576 bytes 08-check_regression/console.log.xz | Bin 3012 -> 2956 bytes 08-check_regression/mail-body.txt | 2 +- 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++++++---------- results | 2 +- 17 files changed, 22 insertions(+), 22 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (44510e44e71 -> c09663eabfb)

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 44510e44e71 tree-optimization/107095 - fix typo in .MASK_STORE DSE handling new c09663eabfb testsuite: [arm] Relax expected register names in MVE tests 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.target/arm/mve/mve_load_memory_modes.c | 58 +++++++++++----------- .../gcc.target/arm/mve/mve_store_memory_modes.c | 58 +++++++++++----------- 2 files changed, 58 insertions(+), 58 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch devel/omp/gcc-12 updated (c455181c13a -> 5ee8de3513b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch devel/omp/gcc-12 in repository gcc. from c455181c13a Merge branch 'releases/gcc-12' into devel/omp/gcc-12 new 5ee8de3513b Fortran: Update use_device_ptr for OpenMP 5.1 [PR105318] 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/fortran/ChangeLog.omp | 10 ++ gcc/fortran/openmp.cc | 70 ++++++--- gcc/testsuite/ChangeLog.omp | 11 ++ gcc/testsuite/gfortran.dg/gomp/is_device_ptr-1.f90 | 8 +- gcc/testsuite/gfortran.dg/gomp/is_device_ptr-2.f90 | 2 +- gcc/testsuite/gfortran.dg/gomp/is_device_ptr-3.f90 | 3 +- libgomp/ChangeLog.omp | 8 ++ .../testsuite/libgomp.fortran/is_device_ptr-2.f90 | 159 +++++++++++++++++++++ 8 files changed, 244 insertions(+), 27 deletions(-) create mode 100644 libgomp/testsuite/libgomp.fortran/is_device_ptr-2.f90 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (3943ef17c3 -> 2215e7f30b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards 3943ef17c3 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 787481397c 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 5dfe1e8c9d 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards dc2283d773 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards e7d681620f 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 5431a7d60f 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 99f1bb7fec 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 16b9b0c344 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 505b00255f 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 3d99b06d8a 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 8beaa9ac8c 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 64a71d5d96 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 8fbb5b9f96 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards c60979b242 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 1f106314c6 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards dc2d559315 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 3cc39e45d8 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 1cedef2da6 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 5f9a3b9946 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards b36a3219e6 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 9059c2b63b 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 7484b3c9c7 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 901d3006af 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 4348a3c025 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 0e44afa5ae 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 69935ab006 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 0f9cbcfe65 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards a905f9eb34 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 986702590c 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards f9dbedf1c8 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 0156404bc9 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 53f41d8e41 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 5181a21259 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 4a2e9decc2 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards e3e912cf3f 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards b05dfc05d3 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards e595e5ffd4 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards cd45df225a 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 0d19cdf1f2 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 39acccc973 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards c4d2350b3c 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards ba073081f2 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards ddd8788c48 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 878127e2d0 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards cf6413bf20 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards dc320e504a 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 51e592e2f1 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 1654b1d68b 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards f9a032c510 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards e6c47c7bf6 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 89d38dcad3 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 43bfd02c40 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 6e41d0dbc8 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 04cb8b2b6a 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards cba44c13f4 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards da3f10b913 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 8665cdc360 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 5d39123d1d 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 89cea660f7 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 593d153e9b 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 1f5ee70afe 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 785deca647 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 2077b478bd 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 2e19f43b5e 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 137da7954d 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards d1cc036524 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 70e87cb461 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 3f5ea8ccf3 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 0e87defb6d 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 0c08bef861 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7dc0771d39 75: onsuccess: 1: Successful build after linux: 44 commits discards 8ed00318f2 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 5148cc9cfc 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bb29e2732e 72: onsuccess: 1: Successful build after linux: 12 commits discards 84494f2f72 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards a2de583ccf 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 75d33ee957 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards cfa25305ab 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1b68c19ffa 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards d439142b2e 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 08155e106c 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d62e56a854 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b9def31c05 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 88bc304076 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 17775cfbad 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards ee141547be 60: onsuccess: 1: Successful build after glibc: 2 commits discards e08e809406 59: onsuccess: 1: Successful build after binutils: 2 commits discards 408a03c40b 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 750b7d20db 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 9e629da782 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a02e4b37cc 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 3b72d5e8f2 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards c1c2961d04 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 74d6dfc93b 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 540dd0d969 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a96bbf4538 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 866a8a9e4b 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards a7954c698e 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9a46de5cb9 47: onsuccess: 1: Successful build after linux: 10 commits discards 8cd2a5c101 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards b3b34b6601 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2ef72516c7 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a695757ec4 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 5960da2622 47: onsuccess: 1: Successful build after linux: 10 commits new cb99b1e51b 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e14194f051 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 83c3e83347 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b6edb5a4c3 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c477254496 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 038acc2abe 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 2624f828fa 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new ca110a7e51 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 2bb14a88c9 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 85ecac66dd 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 465b185a13 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new a4bb5182b1 59: onsuccess: 1: Successful build after binutils: 2 commits new a7f482a89a 60: onsuccess: 1: Successful build after glibc: 2 commits new 856e9bd614 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 3adcfae811 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 0481103e1f 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 4e30d63fcc 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 65f4bb13b3 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 65b9da04d6 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 6b8d5f5fcb 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new aa8b0bcf5c 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ae485b8a65 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new a6ce167a72 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 26559f8df7 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 195c2dc6bf 72: onsuccess: 1: Successful build after linux: 12 commits new b070241808 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f6031352a9 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 088c8d79eb 75: onsuccess: 1: Successful build after linux: 44 commits new 0f218c61ae 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1091bd92c2 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new a325b28438 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new b8548e5629 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new bbb617d110 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 393f1385a3 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 735409b1c0 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 499e525f55 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 6505f81338 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new f9deeebfde 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new e4d501029d 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 44cbb6f96a 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 05c29611ad 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 0ab04b094f 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 5e023ffd5f 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 787fa0bb2f 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 3cb40ffd40 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new eb10c166e8 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 670abe78f7 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 2aab5aa631 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 07b72a3121 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new bd672fd8eb 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new b4dec405d7 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 193b53cea9 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new a0933cf32e 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new bad8bc65ca 101: onsuccess: #2130: 1: Success after binutils: 81 commits new cd91565b42 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new ba3540a46f 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 1f8a394fcd 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 021b28098f 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new e28b50f915 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 76a9633b1c 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 4a2a8017aa 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new f6c395c20c 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 19aa25fadb 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 8b7a16c9f8 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 7dff448db6 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new dc7a58411c 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new cf969cf480 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 9734bad17a 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new ae140e38bd 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 5e5edfa25d 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 76f7a2420a 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 695f1e5ca3 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 804460c7a7 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new e49f69bd77 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new e0211ec63b 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 0fb72c13f7 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new c7a803fbde 124: onsuccess: #2159: 1: Success after linux: 23 commits new 989a64da38 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new afd72f6849 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 92beeec99c 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 41db5ca3ba 128: onsuccess: #2163: 1: Success after linux: 23 commits new dfa85ca827 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new cb5b05b93b 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 057b30ba76 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 56da5b2424 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 0318f655ee 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new c9566ff76e 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 28f296f525 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new f53f625404 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 34f6d3ceed 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 488c7164e9 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new a1873116c7 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 4640c42d5b 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 0fd7c8e4cd 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new d0f0ea2279 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 83b8444a9b 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 00b5a297ae 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 2d06ee2311 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 2215e7f30b 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] 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 (3943ef17c3) \ 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 1696 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30300 -> 30304 bytes 04-build_abe-stage1/console.log.xz | Bin 72300 -> 72600 bytes 06-build_abe-linux/console.log.xz | Bin 8472 -> 8484 bytes 07-build_abe-glibc/console.log.xz | Bin 239608 -> 239776 bytes 08-build_abe-stage2/console.log.xz | Bin 202884 -> 203040 bytes 09-build_abe-gdb/console.log.xz | Bin 37496 -> 37412 bytes 10-build_abe-qemu/console.log.xz | Bin 31904 -> 31900 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2784 -> 2808 bytes 13-check_regression/console.log.xz | Bin 8936 -> 8132 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 49 +- 13-check_regression/mail-body.txt | 126 +- 13-check_regression/results.compare | 49 +- 13-check_regression/results.compare2 | 314 +-- 13-check_regression/results.regressions | 49 +- 14-update_baseline/console.log | 58 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 128 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 49 +- sumfiles/g++.log.xz | Bin 3439504 -> 3408532 bytes sumfiles/g++.sum | 63 +- sumfiles/gcc.log.xz | Bin 3011328 -> 3029088 bytes sumfiles/gcc.sum | 4603 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1035292 -> 1028292 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2300 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202308 -> 202120 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2660 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 425728 -> 428316 bytes sumfiles/libstdc++.sum | 8 +- 42 files changed, 2734 insertions(+), 2818 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

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

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/master-arm in repository toolchain/ci/base-artifacts. discards b0ce12373f 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits discards 3ec250ddd7 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits discards 0a97b8e985 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits discards e098e01a69 142: onsuccess: #1761: 1: Success after gcc: 83 commits discards da59ac4dae 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] discards 3b2705d0c4 140: onsuccess: #1756: 1: Success after binutils: 3 commits discards 534fade5df 139: onsuccess: #1753: 1: Success after binutils: 5 commits discards dd8641446d 138: onsuccess: #1749: 1: Success after binutils: 5 commits discards fecf7863bb 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] discards e4a10d2e40 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] discards db9683ea21 135: onsuccess: #1739: 1: Success after binutils: 4 commits discards db6b084216 134: onsuccess: #1736: 1: Success after binutils: 3 commits discards 9f4afd1a7b 133: onsuccess: #1733: 1: Success after binutils: 3 commits discards 200116e8ae 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits discards 986c3d79eb 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits discards 290ef386c2 130: onsuccess: #1729: 1: Success after gcc: 9 commits discards b7c322eef4 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] discards 2f3aa5d482 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits discards f7deea452d 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] discards 298029fc1b 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits discards de6d72c77d 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits discards be7fe19d99 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits discards 0875c37659 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits discards 12a6735e4b 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits discards 9b91520200 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits discards bd5966f9e9 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits discards f5c80f6c91 119: onsuccess: #1715: 1: Success after binutils: 4 commits discards 25cc6d4f76 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits discards 2e83c534c6 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits discards 862393c7f5 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits discards 4664e28d3e 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits discards c61b385d23 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits discards 798f31fc1e 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits discards 63da8d64cd 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits discards 78ae0a54c3 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits discards 04ae5e422b 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits discards 4555a05922 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] discards a567105609 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits discards a34a5edc14 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] discards d4f6eccde9 106: onsuccess: #1702: 1: Success after gcc: 4 commits discards 2f233868bf 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits discards d41392fdf0 104: onsuccess: #1700: 1: Success after gcc: 2 commits discards b3075a9002 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits discards 3ea3a70883 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits discards 7f99161db0 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits discards 998133b968 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] discards f77b877771 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits discards a1def53bb8 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits discards 340b4255e7 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits discards 7edd815d5e 96: onsuccess: #1654: 1: Success after gcc: 5 commits discards 69e091c72d 95: onsuccess: #1653: 1: Success after gcc: 13 commits discards c44dcf0d32 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits discards ccff2b47b5 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] discards 93f5729f9d 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits discards a4b0dcb448 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] discards c8bf6b90fb 90: onsuccess: #1645: 1: Success after gcc: 2 commits discards caaede8d6b 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] discards 983a19c80b 88: onsuccess: 1: Success after binutils/gcc: 2 commits discards c1b3647211 87: onsuccess: 1: Success after gcc: 6 commits discards f7f0459774 86: onsuccess: 1: Success after binutils/gcc: 8 commits discards c173bcf7b2 85: onsuccess: 1: Success after binutils/gcc: 19 commits discards c522446002 84: onsuccess: 1: Success after binutils/gcc: 2 commits discards ae90d0cc4d 83: onsuccess: 1: Success after gcc: 14 commits discards cbe5e176f3 82: onsuccess: 1: Success after binutils/gcc: 9 commits discards 1cd1a1f3b1 81: onsuccess: 1: Success after binutils/gcc: 8 commits discards 0b6ebc3156 80: onsuccess: 1: Success after binutils/gcc: 8 commits discards 85eeee9dba 79: onsuccess: 1: Success after binutils/gcc: 23 commits discards b5e7890a22 78: onsuccess: 1: Success after binutils/gcc: 17 commits discards 24cf76e20b 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 7787194811 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards a66b804122 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards de987583eb 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits discards 6a35a727bc 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 835fd0a88b 72: onsuccess: 1: Successful build after baseline build: no [...] discards 584644dbc3 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards 3f62356a49 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 209608a0fa 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] discards aa9839de24 68: onsuccess: 1: Successful build after gcc: 2 commits discards 4bd8e6c18f 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 1cf382205a 66: onsuccess: 1: Successful build after gcc: 4 commits discards 85f3cf3a20 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards 2ef3954181 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards 0d0b4f3f78 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 59da154016 62: onsuccess: 1: Successful build after gcc: 4 commits discards 788eeca06d 61: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards c8039bbdba 60: onsuccess: 1: Successful build after binutils/gcc: 12 commits discards 03c30e7652 59: onsuccess: 1: Successful build after binutils/gcc: 29 commits discards 6b447cb7dd 58: onsuccess: 1: Successful build after binutils: ld: pe: M [...] discards 32ad536c78 57: onsuccess: 1: Successful build after binutils: 2 commits discards 3990fa13e9 56: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards 23d728e938 55: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 254e69fe6b 54: onsuccess: 1: Successful build after gcc: 5 commits discards 6363339345 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards 28deece49d 52: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 9e60824f5c 51: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 861517e70e 50: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 7f79597baf 49: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards c91f103400 48: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 9d02d5440e 47: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 6445f8f0e9 46: onsuccess: 1: Successful build after baseline build: no [...] discards 9c6b43a87c 45: onsuccess: 1: Successful build after binutils: Fix crash [...] new 06b4e15a43 45: onsuccess: 1: Successful build after binutils: Fix crash [...] new ce3c92fbb3 46: onsuccess: 1: Successful build after baseline build: no [...] new b69eb77768 47: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 0f946c08c8 48: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 70be0ab538 49: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 20f9471456 50: onsuccess: 1: Successful build after binutils/gcc: 10 commits new fb1f0df9b2 51: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 785ce21280 52: onsuccess: 1: Successful build after binutils/gcc: 6 commits new a2f6ccd054 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 378530b53d 54: onsuccess: 1: Successful build after gcc: 5 commits new d1503a25c1 55: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 2a8c4a3f87 56: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 5f1664bafe 57: onsuccess: 1: Successful build after binutils: 2 commits new 21ef42147a 58: onsuccess: 1: Successful build after binutils: ld: pe: M [...] new fdaf01ed03 59: onsuccess: 1: Successful build after binutils/gcc: 29 commits new 85c10f5277 60: onsuccess: 1: Successful build after binutils/gcc: 12 commits new b8ce706861 61: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 76fa60d9c5 62: onsuccess: 1: Successful build after gcc: 4 commits new 4df002e232 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits new a971b99a49 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits new 44159412c2 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits new 82f4797d7d 66: onsuccess: 1: Successful build after gcc: 4 commits new 26b31d9217 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new e53e27dafc 68: onsuccess: 1: Successful build after gcc: 2 commits new 7dc82b3ddd 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] new 572c928421 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 7556c0c8b7 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] new 851fb31c3b 72: onsuccess: 1: Successful build after baseline build: no [...] new e37c5656a9 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits new 6955e1937c 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits new 260fb975a3 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits new bd4bce9bc4 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits new dbca056fe8 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 8456d99d4f 78: onsuccess: 1: Success after binutils/gcc: 17 commits new 9f2f4ab0c8 79: onsuccess: 1: Success after binutils/gcc: 23 commits new 3fb5348a3e 80: onsuccess: 1: Success after binutils/gcc: 8 commits new 2c9f50d9ce 81: onsuccess: 1: Success after binutils/gcc: 8 commits new 007ca31868 82: onsuccess: 1: Success after binutils/gcc: 9 commits new cbf2c47578 83: onsuccess: 1: Success after gcc: 14 commits new cda3a94518 84: onsuccess: 1: Success after binutils/gcc: 2 commits new d9aaffe09e 85: onsuccess: 1: Success after binutils/gcc: 19 commits new 897ecabeed 86: onsuccess: 1: Success after binutils/gcc: 8 commits new b41cca659b 87: onsuccess: 1: Success after gcc: 6 commits new 9799c5038c 88: onsuccess: 1: Success after binutils/gcc: 2 commits new fbd9882085 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] new 8158da6d85 90: onsuccess: #1645: 1: Success after gcc: 2 commits new f7c0c64a42 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] new db84153942 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits new 46b006aefc 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] new c7b3cc8cd6 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits new 1b4987e48a 95: onsuccess: #1653: 1: Success after gcc: 13 commits new 3190fbde35 96: onsuccess: #1654: 1: Success after gcc: 5 commits new fba4ad302d 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits new 1b3d0b7eca 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits new 69f23cc4e9 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits new 979d38a7f1 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] new 198bef2a77 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits new df2cd86eb4 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits new a6deea21c6 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits new d0ae46c28e 104: onsuccess: #1700: 1: Success after gcc: 2 commits new e6d9584d9b 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits new 47e4d53db3 106: onsuccess: #1702: 1: Success after gcc: 4 commits new bb3a7e8ff4 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] new ff2a843c95 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits new f8dbbeea07 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] new 67d8752f83 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits new 8e37e79bfa 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits new 8922b3cfc1 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits new 918e9c86c7 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits new 5cf3c5a150 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits new 6237782926 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits new 578a28fa2f 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits new 78b844c000 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits new 649955cbce 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits new 61e1a89b4c 119: onsuccess: #1715: 1: Success after binutils: 4 commits new eb662591fa 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits new 19f53bd443 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits new 6425ce8024 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits new 4bf504b7f0 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits new 0544bcea56 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits new 6f59f86c82 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits new 682f8b1964 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits new 01b011ff5a 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] new 662819ff64 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits new a2dad4b9a1 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] new fc4aabe19a 130: onsuccess: #1729: 1: Success after gcc: 9 commits new eb5691296f 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits new d3941928c7 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits new b659beed1d 133: onsuccess: #1733: 1: Success after binutils: 3 commits new 4f5dca0fc4 134: onsuccess: #1736: 1: Success after binutils: 3 commits new 052b1f33e7 135: onsuccess: #1739: 1: Success after binutils: 4 commits new 86d655fa2d 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] new 72224ed8e9 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] new ff62208735 138: onsuccess: #1749: 1: Success after binutils: 5 commits new ad129bc60d 139: onsuccess: #1753: 1: Success after binutils: 5 commits new fd2a0f2a9c 140: onsuccess: #1756: 1: Success after binutils: 3 commits new 06bbeb4a30 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] new 238c920509 142: onsuccess: #1761: 1: Success after gcc: 83 commits new b385c0e6e5 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits new c231fff5db 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits new 23615e49e0 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits new f575f2f612 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 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 (b0ce12373f) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (f5 [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1664 -> 1660 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2716 bytes 03-build_abe-binutils/console.log.xz | Bin 50672 -> 50340 bytes 04-build_abe-gcc/console.log.xz | Bin 232240 -> 232720 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3800 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2736 -> 2684 bytes 07-check_regression/console.log.xz | Bin 5464 -> 5124 bytes 07-check_regression/extra-bisect-params | 1 - 07-check_regression/fails.sum | 7 - 07-check_regression/mail-body.txt | 22 +- 07-check_regression/results.compare | 9 +- 07-check_regression/results.compare2 | 98 +- 07-check_regression/results.regressions | 27 - 08-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 24 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 27 - sumfiles/g++.log.xz | Bin 2778720 -> 2782984 bytes sumfiles/g++.sum | 24 +- sumfiles/gcc.log.xz | Bin 2381068 -> 2357976 bytes sumfiles/gcc.sum | 3654 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 914984 -> 911680 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2172 -> 2172 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 204524 -> 204520 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2532 -> 2532 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 464936 -> 463804 bytes sumfiles/libstdc++.sum | 2 +- 36 files changed, 1935 insertions(+), 2038 deletions(-) delete mode 100644 07-check_regression/extra-bisect-params delete mode 100644 07-check_regression/fails.sum delete mode 100644 07-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

← Newer
1
...
4
5
6
7
8
9
10
...
469
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits September 2022