Tcwg-commits April 2023

tcwg-commits@lists.linaro.org

5 participants
5583 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-cpu2017rate/gnu-arm-master-O3 updated (39410cb7388e -> 085529365ac5)

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_bmk-code_size-cpu2017rate/gnu-arm-master-O3 in repository toolchain/ci/base-artifacts. from 39410cb7388e 0: init: #1: 1: [TCWG CI] No change after baseline build: [...] new 085529365ac5 1: onsuccess: #2: 1: [TCWG CI] Success after binutils/gcc/ [...] 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 2300 -> 2064 bytes 01-reset_artifacts/patch-env.sh | 2 - 02-prepare_abe/console.log.xz | Bin 2520 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 27288 -> 26760 bytes 04-build_abe-stage1/console.log.xz | Bin 89632 -> 89792 bytes 06-build_abe-linux/console.log.xz | Bin 8324 -> 8252 bytes 07-build_abe-glibc/console.log.xz | Bin 233076 -> 232980 bytes 08-build_abe-stage2/console.log.xz | Bin 210004 -> 210536 bytes 09-benchmark/benchmark-build.log | 109 +- 09-benchmark/benchmark.log | 107 +- 09-benchmark/console.log.xz | Bin 4160 -> 4060 bytes 10-check_regression/bmk-specific-variability.csv | 52 + .../compare-results-vs-first-internal.csv | 172 +- .../compare-results-vs-prev-internal.csv | 172 +- 10-check_regression/console.log.xz | Bin 11352 -> 15232 bytes .../csv-results-vs-first-1/md5sum.csv | 1545 +- .../csv-results-vs-first-1/perf.csv | 2001 +- .../csv-results-vs-first-1/results.csv | 28183 ++++++++++--------- .../csv-results-vs-first-1/size.csv | 26098 ++++++++--------- 10-check_regression/csv-results-vs-first-1/sve.csv | 4 +- .../csv-results-vs-prev-1/md5sum.csv | 1545 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 2001 +- .../csv-results-vs-prev-1/results.csv | 28183 ++++++++++--------- 10-check_regression/csv-results-vs-prev-1/size.csv | 26098 ++++++++--------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 4 +- 10-check_regression/exe.improvement | 1 + 10-check_regression/extra-bisect-params | 2 +- 10-check_regression/mail-body.txt | 3 + 10-check_regression/mail-subject.txt | 2 +- .../output-bmk-results/exe.improvement | 1 + .../output-bmk-results/exe.improvement.diff | 4 + .../output-bmk-results/symbol.regression | 2 + .../output-bmk-results/symbol.regression.diff | 1 + 10-check_regression/results-vs-first-brief.csv | 50 +- 10-check_regression/results-vs-first-full.csv | 2114 +- 10-check_regression/results-vs-first-internal.csv | 172 +- 10-check_regression/results-vs-first.csv | 172 +- 10-check_regression/results-vs-first.log | 1152 +- 10-check_regression/results-vs-prev-brief.csv | 50 +- 10-check_regression/results-vs-prev-compare.csv | 8 +- 10-check_regression/results-vs-prev-full.csv | 2114 +- 10-check_regression/results-vs-prev-internal.csv | 172 +- 10-check_regression/results-vs-prev.csv | 172 +- 10-check_regression/results-vs-prev.log | 906 +- 11-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- .../500.perlbench_r/results-metadata.json | 16 +- .../500.perlbench_r/results-metrics.json | 2 +- .../squad-vs-first/502.gcc_r/results-metadata.json | 16 +- .../503.bwaves_r/results-metadata.json | 16 +- .../squad-vs-first/505.mcf_r/results-metadata.json | 16 +- .../squad-vs-first/505.mcf_r/results-metrics.json | 2 +- .../507.cactuBSSN_r/results-metadata.json | 16 +- .../508.namd_r/results-metadata.json | 16 +- .../squad-vs-first/508.namd_r/results-metrics.json | 2 +- .../511.povray_r/results-metadata.json | 16 +- .../511.povray_r/results-metrics.json | 4 +- .../squad-vs-first/519.lbm_r/results-metadata.json | 16 +- .../520.omnetpp_r/results-metadata.json | 16 +- .../520.omnetpp_r/results-metrics.json | 2 +- .../squad-vs-first/521.wrf_r/results-metadata.json | 16 +- .../squad-vs-first/521.wrf_r/results-metrics.json | 2 +- .../525.x264_r/results-metadata.json | 16 +- .../527.cam4_r/results-metadata.json | 16 +- .../squad-vs-first/527.cam4_r/results-metrics.json | 2 +- .../531.deepsjeng_r/results-metadata.json | 16 +- .../531.deepsjeng_r/results-metrics.json | 2 +- .../538.imagick_r/results-metadata.json | 16 +- .../541.leela_r/results-metadata.json | 16 +- .../541.leela_r/results-metrics.json | 2 +- .../squad-vs-first/544.nab_r/results-metadata.json | 16 +- .../squad-vs-first/544.nab_r/results-metrics.json | 2 +- .../548.exchange2_r/results-metadata.json | 16 +- .../549.fotonik3d_r/results-metadata.json | 16 +- .../549.fotonik3d_r/results-metrics.json | 2 +- .../554.roms_r/results-metadata.json | 16 +- .../squad-vs-first/557.xz_r/results-metadata.json | 16 +- .../squad-vs-first/Mean/results-metadata.json | 16 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 86 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 26 + mail/changes-list-short.txt | 1 + manifest.sh => mail/last_good.sh | 0 mail/mail-body.txt | 13 - mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 36 +- results_id | 2 +- 91 files changed, 62526 insertions(+), 61386 deletions(-) delete mode 100644 01-reset_artifacts/patch-env.sh create mode 100644 10-check_regression/bmk-specific-variability.csv create mode 100644 10-check_regression/exe.improvement create mode 100644 10-check_regression/output-bmk-results/exe.improvement create mode 100644 10-check_regression/output-bmk-results/exe.improvement.diff create mode 100644 10-check_regression/output-bmk-results/symbol.regression create mode 100644 10-check_regression/output-bmk-results/symbol.regression.diff create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt copy manifest.sh => mail/last_good.sh (100%) delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (830bd4232ddc -> bdf9cf31f910)

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_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards 830bd4232ddc 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/ [...] discards dfa796455c7c 239: force: #106: 1: [TCWG CI] Success after baseline buil [...] discards bb41510f5793 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branch [...] discards ed40e0835daf 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits discards 12d21cab34e9 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: [...] discards 7ccf7bef045d 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/g [...] discards 4dd2dc54d919 234: force: #94: 1: [TCWG CI] Success after baseline build [...] discards cad3d51eed43 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards a5626c41d5d3 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards a211fb4469e4 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits discards 4c361e924857 230: onsuccess: #78: 1: Success after gdb: 2 commits discards 1df70db361d7 229: force: #77: 1: Failure after gdb-13-branchpoint-1594- [...] discards 94d6c3973ef5 228: force: #74: 1: Success after gdb: 53 commits discards 0e3370469341 227: onsuccess: #72: 1: Success after binutils/gcc/linux/g [...] discards 6fbfb3c18ce1 226: force: #70: 1: Success after baseline build: no new commits discards f69c7f068f59 225: force: #68: 1: Failure after gdb-13-branchpoint-1540- [...] discards b3c7fd7a24f7 224: force: #65: 1: Success after gdb: 50 commits discards a9701e3431d1 223: force: #63: 1: Failure after gdb-13-branchpoint-1489- [...] discards 90e5130d400d 222: force: #60: 1: Success after gdb: 16 commits discards 2410ff2bcf15 221: force: #53: 1: Success after gdb-13-branchpoint-1472- [...] discards f8d02b9a0bfb 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02d [...] discards 0f4d2e2d8b8f 219: force: #50: 1: Failure after linux: 2520 commits discards 2d25b307b7ad 218: force: #48: 1: Success after gdb-13-branchpoint-1471- [...] discards 539268ac3b2b 217: force: #45: 1: Success after linux: 1 commits discards a2f964d80722 216: force: #43: : Failure after baseline build: no new commits discards 801e6c698ae8 215: force: #41: 1: Failure after gdb-13-branchpoint-1470- [...] discards 29f59e394465 214: force: #39: 1: Failure after gdb-13-branchpoint-1470- [...] discards f52648ae012e 213: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards 08e6c299ad28 212: force: #27: : Failure after baseline build: no new commits discards f220f18cd0f7 211: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards d768711ed50f 210: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards 35581d745958 209: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 856be801a26f 208: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards 8ebd423fe30c 207: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 7bcd5c473a13 206: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 00c2064d38f7 205: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 3bfa4ee71ba7 204: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards fed0cdc9cbd6 203: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards 491f268bd92c 202: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 760ef24737c4 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards eaf31af96e6b 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 8e23140c6243 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards 62af980f6c36 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards c7b0a3c65f6a 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 7a4c1a730129 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards 89e43cafab85 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 4eb034886966 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] discards d1a1f5230851 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards ce809ed13256 192: onsuccess: #695: 1: Success after binutils/gcc/linux/ [...] discards aa2eed0f9234 191: onsuccess: #694: 1: Success after binutils/gcc/linux/ [...] discards 81db6cddfb53 190: onsuccess: #693: 1: Success after binutils/gcc/linux/ [...] discards c92d09fba0b7 189: onsuccess: #683: 1: Success after binutils/gcc/linux/ [...] discards 9919819c4bc4 188: onsuccess: #682: 1: Success after binutils/gcc/linux/ [...] discards 3e5990f61cc1 187: onsuccess: #681: 1: Success after binutils/gcc/linux/ [...] discards 94df4eac9c89 186: onsuccess: #680: 1: Success after binutils/gcc/linux/ [...] discards 60e962bbee17 185: onsuccess: #679: 1: Success after binutils/gcc/linux/ [...] discards 40935ecb117b 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/ [...] discards 9d720aba4b20 183: onsuccess: #677: 1: Success after binutils/gcc/linux/ [...] discards 8229140e012d 182: onsuccess: #676: 1: Success after binutils/gcc/linux/ [...] discards 7c48f05e4407 181: onsuccess: #675: 1: Success after binutils/gcc/linux/ [...] discards ba18729c6b2e 180: onsuccess: #674: 1: Success after binutils/gcc/linux/ [...] discards 712c3e2c0675 179: onsuccess: #673: 1: Success after binutils/gcc/linux/ [...] discards 684d6a68a041 178: onsuccess: #672: 1: Success after binutils/gcc/linux/ [...] discards f48eef2d52b8 177: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] discards faf34ee571a5 176: onsuccess: #670: 1: Success after binutils/gcc/linux/ [...] discards 40860c8b10e2 175: onsuccess: #669: 1: Success after binutils/gcc/linux/ [...] discards f89cd2cdced4 174: onsuccess: #668: 1: Success after binutils/gcc/linux/ [...] discards 66fb50090f4b 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 1 [...] discards e20a653aaaef 172: onsuccess: #666: 1: Success after binutils/gcc/linux/ [...] discards 0be9ce601a04 171: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] discards 9b05534e21f6 170: onsuccess: #664: 1: Success after binutils/gcc/linux/ [...] discards f66daa20d650 169: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] discards 2685648dab64 168: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] discards 6942cbeaf16b 167: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] discards 2aacd5b75f82 166: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] discards f623a1690deb 165: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] discards 3523b0f7923d 164: onsuccess: #658: 1: Success after binutils/gcc/linux/ [...] discards c77680da417d 163: onsuccess: #657: 1: Success after binutils/gcc/linux/ [...] discards ffad631c376c 162: onsuccess: #656: 1: Success after binutils/gcc/linux/ [...] discards 6b99432bee12 161: onsuccess: #655: 1: Success after binutils/gcc/linux/ [...] discards 85656c178cb3 160: onsuccess: #654: 1: Success after binutils/gcc/linux/ [...] discards d742f75b4db6 159: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] discards b434f6e76b58 158: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] discards a41033d8e413 157: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] discards 6a3e110e8269 156: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] discards 3c63b6cbf7e5 155: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] discards 1c0ab08f9b5d 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/ [...] discards 3e1f291fa7b0 153: onsuccess: #647: 1: Success after binutils/gcc/linux/ [...] discards 1ef9612ebaa9 152: onsuccess: #645: 1: Success after binutils/gcc/linux/ [...] discards 15a097580b2b 151: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] discards 10dd3067f3fd 150: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] discards 58be614ee2d0 149: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] discards 59994cc11108 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 [...] discards fbf30774a7a9 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 1 [...] discards 4544e3fed7f9 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 3 [...] discards 5ab84afe6479 145: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] discards ab6c80a0365e 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 4 [...] discards edad504ab634 143: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] discards 967f3d86f25b 142: onsuccess: #634: 1: Success after binutils/gcc/linux/ [...] discards 48b6c40be3e0 141: onsuccess: #633: 1: Success after binutils/gcc/linux/ [...] discards 4c55a30eb2a0 140: onsuccess: #631: 1: Success after binutils/gcc/linux/ [...] new ec349c66d7f8 140: onsuccess: #631: 1: Success after binutils/gcc/linux/ [...] new 67d72521a612 141: onsuccess: #633: 1: Success after binutils/gcc/linux/ [...] new 046393a65428 142: onsuccess: #634: 1: Success after binutils/gcc/linux/ [...] new de1d8afd1d4d 143: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] new f3d73c9c9c56 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 4 [...] new 62b306db9e8b 145: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] new f2790d4aa05c 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 3 [...] new 7b7dc7f76436 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 1 [...] new 81e6f50d2fcc 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 [...] new 248bc219924b 149: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] new f3b736cabe35 150: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] new 00916d8b1cc3 151: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] new 1368b242cd19 152: onsuccess: #645: 1: Success after binutils/gcc/linux/ [...] new fe210c1094d0 153: onsuccess: #647: 1: Success after binutils/gcc/linux/ [...] new 40ae465c8552 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/ [...] new ffc7535cfbcc 155: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] new 18544d518ded 156: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] new acc480b5ee45 157: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] new edb7f921e2bd 158: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] new 2151cf38768e 159: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] new b307c615ca3e 160: onsuccess: #654: 1: Success after binutils/gcc/linux/ [...] new c599f2983d26 161: onsuccess: #655: 1: Success after binutils/gcc/linux/ [...] new d825a4c1bd5e 162: onsuccess: #656: 1: Success after binutils/gcc/linux/ [...] new 9e72d8541235 163: onsuccess: #657: 1: Success after binutils/gcc/linux/ [...] new 9628006ff86c 164: onsuccess: #658: 1: Success after binutils/gcc/linux/ [...] new c545853161e0 165: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] new dc9d0545d9cc 166: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] new 03b98bd11e5f 167: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] new 2d493c752e7c 168: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] new 2be2ce0ff3cf 169: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] new 62d7008a0bbd 170: onsuccess: #664: 1: Success after binutils/gcc/linux/ [...] new 77d71fdea3ef 171: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] new c15166a51137 172: onsuccess: #666: 1: Success after binutils/gcc/linux/ [...] new f76eedc4294c 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 1 [...] new e750424ac7da 174: onsuccess: #668: 1: Success after binutils/gcc/linux/ [...] new d15e17ffecf3 175: onsuccess: #669: 1: Success after binutils/gcc/linux/ [...] new 2ffbff1ade03 176: onsuccess: #670: 1: Success after binutils/gcc/linux/ [...] new f9737da90410 177: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] new ef6a63a53276 178: onsuccess: #672: 1: Success after binutils/gcc/linux/ [...] new f2ef6cc0722d 179: onsuccess: #673: 1: Success after binutils/gcc/linux/ [...] new 6b67e7314026 180: onsuccess: #674: 1: Success after binutils/gcc/linux/ [...] new 462640e101c6 181: onsuccess: #675: 1: Success after binutils/gcc/linux/ [...] new 88d3dbd0b28f 182: onsuccess: #676: 1: Success after binutils/gcc/linux/ [...] new 535f559856c8 183: onsuccess: #677: 1: Success after binutils/gcc/linux/ [...] new 5f2c700ed6bf 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/ [...] new 01e65e6a6806 185: onsuccess: #679: 1: Success after binutils/gcc/linux/ [...] new 7f1fc2fb9242 186: onsuccess: #680: 1: Success after binutils/gcc/linux/ [...] new 5cb72c58086b 187: onsuccess: #681: 1: Success after binutils/gcc/linux/ [...] new 50a6843be550 188: onsuccess: #682: 1: Success after binutils/gcc/linux/ [...] new a91355b2ceae 189: onsuccess: #683: 1: Success after binutils/gcc/linux/ [...] new a89afad57c8f 190: onsuccess: #693: 1: Success after binutils/gcc/linux/ [...] new 5d2315640e1d 191: onsuccess: #694: 1: Success after binutils/gcc/linux/ [...] new 81b068fae0fe 192: onsuccess: #695: 1: Success after binutils/gcc/linux/ [...] new 53173a60baac 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new 92c753a3c909 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] new 3f07ec44fed3 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new 4ef1752bd6a1 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new 314db261da4f 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new 0d82f8738643 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new 909a4442cb03 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new 180f76fd45d3 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new 74961351e988 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new d3bd464d3d0e 202: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new 6a0d8184ba5f 203: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new a09155b3083f 204: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new 667212953d27 205: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new e8a00829e064 206: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new a4fb5e11e30c 207: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 7d39a40ccce6 208: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 3915c4b6d55b 209: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new a67ebd3836f6 210: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new b5849c4c0d6c 211: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new 15256a61845d 212: force: #27: : Failure after baseline build: no new commits new 1523fadece57 213: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new 2bb6702f62cf 214: force: #39: 1: Failure after gdb-13-branchpoint-1470- [...] new ae79e63d73df 215: force: #41: 1: Failure after gdb-13-branchpoint-1470- [...] new 0f339d7146d7 216: force: #43: : Failure after baseline build: no new commits new 463823d7aa26 217: force: #45: 1: Success after linux: 1 commits new d4a9f5f95a44 218: force: #48: 1: Success after gdb-13-branchpoint-1471- [...] new 2cda90ad379f 219: force: #50: 1: Failure after linux: 2520 commits new 705132cecf34 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02d [...] new b0ae2720e3c8 221: force: #53: 1: Success after gdb-13-branchpoint-1472- [...] new d16af11613c8 222: force: #60: 1: Success after gdb: 16 commits new e19051052964 223: force: #63: 1: Failure after gdb-13-branchpoint-1489- [...] new 28a16273918b 224: force: #65: 1: Success after gdb: 50 commits new 53e6be9eb2ca 225: force: #68: 1: Failure after gdb-13-branchpoint-1540- [...] new d46216979271 226: force: #70: 1: Success after baseline build: no new commits new fb9360f8a0cd 227: onsuccess: #72: 1: Success after binutils/gcc/linux/g [...] new 939122648653 228: force: #74: 1: Success after gdb: 53 commits new 0cd89aac18e0 229: force: #77: 1: Failure after gdb-13-branchpoint-1594- [...] new f71a5355d1ba 230: onsuccess: #78: 1: Success after gdb: 2 commits new ecdf624eca58 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits new 9386c8677ea5 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchp [...] new 409fb0d15a84 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchp [...] new 918126f9f196 234: force: #94: 1: [TCWG CI] Success after baseline build [...] new 6659626304ac 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/g [...] new 7379844547b0 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: [...] new 0eb1a6395302 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits new f47f46e59432 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branch [...] new 1120d8ddb457 239: force: #106: 1: [TCWG CI] Success after baseline buil [...] new 7e05b36246fc 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/ [...] new bdf9cf31f910 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/ [...] 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 (830bd4232ddc) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] 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 2096 -> 1976 bytes 02-prepare_abe/console.log.xz | Bin 2536 -> 2532 bytes 03-build_abe-binutils/console.log.xz | Bin 48924 -> 49024 bytes 04-build_abe-gcc/console.log.xz | Bin 235412 -> 235276 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8880 -> 8608 bytes 07-build_abe-glibc/console.log.xz | Bin 232296 -> 232232 bytes 08-build_abe-gdb/console.log.xz | Bin 47296 -> 46520 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3824 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4352 -> 4256 bytes 11-check_regression/console.log.xz | Bin 17500 -> 11496 bytes 11-check_regression/results.compare | 24 +- 11-check_regression/results.compare2 | 1133 +---- 12-update_baseline/console.log | 68 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 46 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 35 +- manifest.sh | 32 +- sumfiles/gdb.log.0.xz | Bin 2928340 -> 2933800 bytes sumfiles/gdb.log.1.xz | Bin 180604 -> 152260 bytes sumfiles/gdb.log.10.xz | Bin 10292 -> 0 bytes sumfiles/gdb.log.2.xz | Bin 11800 -> 16776 bytes sumfiles/gdb.log.3.xz | Bin 10184 -> 15276 bytes sumfiles/gdb.log.4.xz | Bin 10156 -> 14840 bytes sumfiles/gdb.log.5.xz | Bin 10252 -> 10032 bytes sumfiles/gdb.log.6.xz | Bin 10264 -> 0 bytes sumfiles/gdb.log.7.xz | Bin 10260 -> 0 bytes sumfiles/gdb.log.8.xz | Bin 10088 -> 0 bytes sumfiles/gdb.log.9.xz | Bin 9968 -> 0 bytes sumfiles/gdb.sum | 3721 +++++++++++++- sumfiles/gdb.sum.0 | 3741 +++++++++++++- sumfiles/gdb.sum.1 | 8986 ++------------------------------- sumfiles/gdb.sum.10 | 2163 -------- sumfiles/gdb.sum.2 | 212 +- sumfiles/gdb.sum.3 | 238 +- sumfiles/gdb.sum.4 | 235 +- sumfiles/gdb.sum.5 | 15 +- sumfiles/gdb.sum.6 | 2174 -------- sumfiles/gdb.sum.7 | 2163 -------- sumfiles/gdb.sum.8 | 2157 -------- sumfiles/gdb.sum.9 | 2155 -------- 45 files changed, 8517 insertions(+), 20791 deletions(-) delete mode 100644 sumfiles/gdb.log.10.xz delete mode 100644 sumfiles/gdb.log.6.xz delete mode 100644 sumfiles/gdb.log.7.xz delete mode 100644 sumfiles/gdb.log.8.xz delete mode 100644 sumfiles/gdb.log.9.xz delete mode 100644 sumfiles/gdb.sum.10 delete mode 100644 sumfiles/gdb.sum.6 delete mode 100644 sumfiles/gdb.sum.7 delete mode 100644 sumfiles/gdb.sum.8 delete mode 100644 sumfiles/gdb.sum.9 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[gcc] branch master updated (236cde7202a -> 802ab7d0db5)

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 236cde7202a Daily bump. new db4f7a9b47d RISC-V: Fix ICE and codegen error of scalar move in RV32 system. new 802ab7d0db5 RISC-V: Fix reload fail issue on vector mac instructions 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/riscv/riscv-protos.h | 1 + gcc/config/riscv/riscv-v.cc | 23 ++ gcc/config/riscv/vector.md | 398 +++++++++++---------- gcc/testsuite/g++.target/riscv/rvv/base/bug-19.C | 146 ++++++++ gcc/testsuite/g++.target/riscv/rvv/base/bug-20.C | 146 ++++++++ gcc/testsuite/g++.target/riscv/rvv/base/bug-21.C | 146 ++++++++ gcc/testsuite/g++.target/riscv/rvv/base/bug-22.C | 146 ++++++++ .../gcc.target/riscv/rvv/base/scalar_move-6.c | 8 - .../gcc.target/riscv/rvv/base/scalar_move-9.c | 26 ++ 9 files changed, 841 insertions(+), 199 deletions(-) create mode 100644 gcc/testsuite/g++.target/riscv/rvv/base/bug-19.C create mode 100644 gcc/testsuite/g++.target/riscv/rvv/base/bug-20.C create mode 100644 gcc/testsuite/g++.target/riscv/rvv/base/bug-21.C create mode 100644 gcc/testsuite/g++.target/riscv/rvv/base/bug-22.C create mode 100644 gcc/testsuite/gcc.target/riscv/rvv/base/scalar_move-9.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/gnu-aarch64-master-O2_LTO updated (1368532dff3d -> cc4c2ccfc6b9)

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_bmk-code_size-spec2k6/gnu-aarch64-master-O2_LTO in repository toolchain/ci/base-artifacts. from 1368532dff3d 4: force: #7: 1: [TCWG CI] Failure after basepoints/gcc-13 [...] new cc4c2ccfc6b9 5: onsuccess: #8: 1: [TCWG CI] Success after gcc: 3 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 1972 -> 2112 bytes 02-prepare_abe/console.log.xz | Bin 2488 -> 2564 bytes 03-build_abe-binutils/console.log.xz | Bin 27940 -> 28048 bytes 04-build_abe-stage1/console.log.xz | Bin 71220 -> 72016 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8352 -> 8332 bytes 07-build_abe-glibc/console.log.xz | Bin 241488 -> 241788 bytes 08-build_abe-stage2/console.log.xz | Bin 175928 -> 176748 bytes 09-benchmark/benchmark-build.log | 82 +- 09-benchmark/benchmark.log | 80 +- 09-benchmark/console.log.xz | Bin 3968 -> 4024 bytes .../454.calculix.symbols-regression | 1 - .../compare-results-vs-first-internal.csv | 77 +- .../compare-results-vs-prev-internal.csv | 79 +- 10-check_regression/console.log.xz | Bin 11204 -> 10624 bytes .../csv-results-vs-first-1/perf.csv | 137 +- .../csv-results-vs-first-1/results.csv | 22045 +++++------------- .../csv-results-vs-first-1/size.csv | 21896 +++++------------- 10-check_regression/csv-results-vs-prev-0/perf.csv | 141 +- .../csv-results-vs-prev-0/results.csv | 22745 ++++++++++++++----- 10-check_regression/csv-results-vs-prev-0/size.csv | 22624 +++++++++++++----- 10-check_regression/csv-results-vs-prev-1/perf.csv | 137 +- .../csv-results-vs-prev-1/results.csv | 22045 +++++------------- 10-check_regression/csv-results-vs-prev-1/size.csv | 21896 +++++------------- 10-check_regression/extra-bisect-params | 2 +- 10-check_regression/mail-body.txt | 3 - 10-check_regression/mail-subject.txt | 2 +- .../output-bmk-results/exe.improvement | 3 +- .../output-bmk-results/exe.improvement.diff | 2 +- .../output-bmk-results/exe.regression | 2 +- .../output-bmk-results/exe.regression.diff | 2 +- .../output-bmk-results/symbol.regression.diff | 1 - 10-check_regression/results-vs-first-brief.csv | 113 +- 10-check_regression/results-vs-first-full.csv | 147 +- 10-check_regression/results-vs-first-internal.csv | 106 +- 10-check_regression/results-vs-first.csv | 106 +- 10-check_regression/results-vs-first.log | 1396 +- 10-check_regression/results-vs-prev-brief.csv | 115 +- 10-check_regression/results-vs-prev-compare.csv | 26 +- 10-check_regression/results-vs-prev-full.csv | 163 +- 10-check_regression/results-vs-prev-internal.csv | 110 +- 10-check_regression/results-vs-prev.csv | 110 +- 10-check_regression/results-vs-prev.log | 1556 +- 10-check_regression/results.regressions | 17 - 10-check_regression/symbol.regression | 1 - 10-check_regression/trigger-bisect | 3 - 10-check_regression/trigger-notify | 0 11-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 8 +- .../400.perlbench/results-metrics.json | 2 +- .../squad-vs-first/401.bzip2/results-metadata.json | 8 +- .../squad-vs-first/401.bzip2/results-metrics.json | 2 +- .../squad-vs-first/403.gcc/results-metadata.json | 8 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../410.bwaves/results-metadata.json | 8 +- .../squad-vs-first/410.bwaves/results-metrics.json | 2 +- .../416.gamess/results-metadata.json | 8 +- .../squad-vs-first/429.mcf/results-metadata.json | 8 +- .../squad-vs-first/429.mcf/results-metrics.json | 2 +- .../squad-vs-first/433.milc/results-metadata.json | 8 +- .../434.zeusmp/results-metadata.json | 8 +- .../435.gromacs/results-metadata.json | 8 +- .../436.cactusADM/results-metadata.json | 8 +- .../436.cactusADM/results-metrics.json | 2 +- .../437.leslie3d/results-metadata.json | 8 +- .../437.leslie3d/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 8 +- .../squad-vs-first/444.namd/results-metrics.json | 2 +- .../squad-vs-first/445.gobmk/results-metadata.json | 8 +- .../447.dealII/results-metadata.json | 8 +- .../450.soplex/results-metadata.json | 8 +- .../453.povray/results-metadata.json | 8 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../454.calculix/results-metadata.json | 8 +- .../454.calculix/results-metrics.json | 2 +- .../squad-vs-first/456.hmmer/results-metadata.json | 8 +- .../squad-vs-first/458.sjeng/results-metadata.json | 8 +- .../squad-vs-first/458.sjeng/results-metrics.json | 2 +- .../459.GemsFDTD/results-metadata.json | 8 +- .../459.GemsFDTD/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 8 +- .../462.libquantum/results-metrics.json | 2 +- .../464.h264ref/results-metadata.json | 8 +- .../squad-vs-first/465.tonto/results-metadata.json | 8 +- .../squad-vs-first/465.tonto/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 8 +- .../squad-vs-first/470.lbm/results-metrics.json | 2 +- .../471.omnetpp/results-metadata.json | 8 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 8 +- .../squad-vs-first/473.astar/results-metrics.json | 2 +- .../squad-vs-first/481.wrf/results-metadata.json | 8 +- .../squad-vs-first/481.wrf/results-metrics.json | 2 +- .../482.sphinx3/results-metadata.json | 8 +- .../483.xalancbmk/results-metadata.json | 8 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 8 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 481 +- git/gcc_rev | 2 +- jenkins/notify.sh | 3 - mail/changes-list-long.txt | 8 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 18 +- mail/short-diag.txt | 2 +- manifest.sh | 20 +- results | 17 - results_id | 2 +- 108 files changed, 58434 insertions(+), 80374 deletions(-) delete mode 100644 10-check_regression/454.calculix.symbols-regression delete mode 100644 10-check_regression/output-bmk-results/symbol.regression.diff delete mode 100644 10-check_regression/results.regressions delete mode 100644 10-check_regression/symbol.regression delete mode 100644 10-check_regression/trigger-bisect delete mode 100644 10-check_regression/trigger-notify delete mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[gcc] branch releases/gcc-11 updated (37e4747f442 -> 35f7c0027f4)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-11 in repository gcc. from 37e4747f442 Daily bump. new 556f5a51b81 Fix fc-prototypes usage with C_INT64_T and non LP64 Targets. new 35f7c0027f4 Change "long_double" into "long double" for C prototypes fr [...] 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/fortran/dump-parse-tree.c | 5 +++++ 1 file changed, 5 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_binutils/master-aarch64 updated (39a81dbc7799 -> 2cfb4edf66fa)

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_binutils/master-aarch64 in repository toolchain/ci/base-artifacts. from 39a81dbc7799 4: onsuccess: #8: 1: [TCWG CI] Success after binutils/gcc/ [...] new 2cfb4edf66fa 5: onsuccess: #9: 1: [TCWG CI] Success after binutils/gcc/ [...] 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 2084 -> 2056 bytes 02-prepare_abe/console.log.xz | Bin 2548 -> 2544 bytes 03-build_abe-binutils/console.log.xz | Bin 27148 -> 27188 bytes 04-build_abe-stage1/console.log.xz | Bin 71112 -> 70792 bytes 06-build_abe-linux/console.log.xz | Bin 8920 -> 8664 bytes 07-build_abe-glibc/console.log.xz | Bin 241792 -> 241304 bytes 08-build_abe-stage2/console.log.xz | Bin 201804 -> 201680 bytes 09-build_abe-gdb/console.log.xz | Bin 34520 -> 34500 bytes 10-build_abe-qemu/console.log.xz | Bin 32452 -> 32460 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3904 bytes 12-build_abe-check_binutils/console.log.xz | Bin 2092 -> 2108 bytes 13-check_regression/console.log.xz | Bin 5632 -> 4716 bytes 13-check_regression/results.compare2 | 17 +++------- 14-update_baseline/console.log | 9 ++++++ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 49 ++++++++++------------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 46 +++++++++++++-------------- manifest.sh | 38 +++++++++++----------- sumfiles/binutils.log.xz | Bin 62308 -> 62192 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150640 -> 150608 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 107640 -> 107604 bytes sumfiles/ld.sum | 4 +-- 29 files changed, 84 insertions(+), 97 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-mainline-defconfig updated (24c36c6e8452 -> 76cbc019b5dc)

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-mainline-defconfig in repository toolchain/ci/base-artifacts. from 24c36c6e8452 58: onsuccess: #8: boot: Success after binutils/gcc/linux/ [...] new 76cbc019b5dc 59: onsuccess: #9: boot: [TCWG CI] Success after binutils/ [...] 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 1988 -> 2012 bytes 02-prepare_abe/console.log.xz | Bin 2592 -> 2524 bytes 03-build_abe-binutils/console.log.xz | Bin 26952 -> 26572 bytes 04-build_abe-stage1/console.log.xz | Bin 88596 -> 88868 bytes 05-build_abe-qemu/console.log.xz | Bin 31988 -> 31392 bytes 06-build_linux/console.log.xz | Bin 4600 -> 4580 bytes 07-boot_linux/console.log.xz | Bin 5680 -> 5652 bytes 08-check_regression/console.log.xz | Bin 4180 -> 4272 bytes 08-check_regression/mail-body.txt | 31 ------------------------------- 08-check_regression/mail-subject.txt | 1 - dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/changes-list-long.txt | 26 ++++++++++++++++++++++++++ mail/changes-list-short.txt | 1 + manifest.sh => mail/last_good.sh | 0 mail/mail-body.txt | 31 ------------------------------- mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 32 ++++++++++++++++---------------- 22 files changed, 49 insertions(+), 85 deletions(-) delete mode 100644 08-check_regression/mail-body.txt delete mode 100644 08-check_regression/mail-subject.txt create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt copy manifest.sh => mail/last_good.sh (100%) delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-mainline-allyesconfig updated (587b6a0ed447 -> 87fc9d3d4359)

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-aarch64-mainline-allyesconfig in repository toolchain/ci/base-artifacts. from 587b6a0ed447 56: onsuccess: #12: 21863: Success after binutils/gcc/linu [...] new 87fc9d3d4359 57: onsuccess: #13: 21863: [TCWG CI] Success after binutil [...] 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 2024 -> 2020 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 27168 -> 27104 bytes 04-build_abe-stage1/console.log.xz | Bin 70808 -> 71100 bytes 05-build_abe-qemu/console.log.xz | Bin 32380 -> 30880 bytes 06-build_linux/console.log.xz | Bin 8628 -> 8624 bytes 08-check_regression/console.log.xz | Bin 4216 -> 4304 bytes 08-check_regression/mail-body.txt | 23 ----------------------- 08-check_regression/mail-subject.txt | 1 - dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/changes-list-long.txt | 26 ++++++++++++++++++++++++++ mail/changes-list-short.txt | 1 + manifest.sh => mail/last_good.sh | 0 mail/mail-body.txt | 23 ----------------------- mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 32 ++++++++++++++++---------------- 21 files changed, 49 insertions(+), 69 deletions(-) delete mode 100644 08-check_regression/mail-body.txt delete mode 100644 08-check_regression/mail-subject.txt create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt copy manifest.sh => mail/last_good.sh (100%) delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[gcc] branch releases/gcc-12 updated (35bc637393c -> e287ed6fc09)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-12 in repository gcc. from 35bc637393c Daily bump. new e287ed6fc09 Change "long_double" into "long double" for C prototypes fr [...] 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/dump-parse-tree.cc | 2 ++ 1 file changed, 2 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 updated (22bcdca72944 -> 8416d5d20944)

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_check_binutils/master-aarch64 in repository toolchain/ci/base-artifacts. discards 22bcdca72944 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] discards e9c19f9bed03 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards 621be34b00d4 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards fc6e9018dfab 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] discards ba64dad01df2 222: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards 7c544160e5d4 221: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards ecb336fa466a 220: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards 13258bd572bb 219: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards 6f7186d2c1f7 218: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards 35a05c944f66 217: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards c137d2c24d20 216: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards b1cb544f7233 215: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards e5baa2a57808 214: onsuccess: #26: 1: Success after binutils: 12 commits discards 6c0a229e327c 213: force: #25: 1: Failure after gdb-13-branchpoint-1445- [...] discards 7471f8f927b5 212: force: #24: 1: Success after binutils: 2 commits discards a0a77261af6b 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards fb8f8764a940 210: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards 8439265ca1f9 209: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards 5d54f8dd85d3 208: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 9d53d513718d 207: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards 50665656aa0d 206: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards ff506c14123a 205: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 483b7c50ddcc 204: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 2c02ad76d6f8 203: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards a7a9a6dd7955 202: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards b78f49f50335 201: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards 9ae870628dd9 200: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 6d997d48b880 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 5a791f692b5e 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 25cee20e1b5f 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards b8c3c986b998 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards e6126fe9c1db 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 6a4952fd92c6 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards 91b373c9e832 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 44fa27ebe7dd 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] discards ad47e65835c3 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards f80e05a4ebc4 190: onsuccess: #726: 1: Success after binutils/gcc/linux/ [...] discards c822c09bdc88 189: onsuccess: #725: 1: Success after binutils/gcc/linux/ [...] discards 83cfcdf4aa10 188: onsuccess: #724: 1: Success after binutils/gcc/linux/ [...] discards a37254db7cb4 187: onsuccess: #723: 1: Success after binutils/gcc/linux/ [...] discards dd1f7e45a1ae 186: onsuccess: #722: 1: Success after binutils/gcc/linux/ [...] discards b929b31f0311 185: onsuccess: #721: 1: Success after binutils/gcc/linux/ [...] discards 8ae64a14686b 184: onsuccess: #720: 1: Success after binutils/gcc/linux/ [...] discards 40c88845b870 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 2 [...] discards 0bb84065bc73 182: onsuccess: #718: 1: Success after binutils/gcc/linux/ [...] discards 9733f67971d1 181: onsuccess: #717: 1: Success after binutils/gcc/linux/ [...] discards 2811bf9646e8 180: onsuccess: #716: 1: Success after binutils/gcc/linux/ [...] discards 9c6bf28e34e8 179: onsuccess: #715: 1: Success after binutils/gcc/linux/ [...] discards fda6363bc5ed 178: onsuccess: #714: 1: Success after binutils/gcc/linux/ [...] discards dfd0595177b7 177: onsuccess: #712: 1: Success after binutils/gcc/linux/ [...] discards ba51cfb1aa63 176: onsuccess: #711: 1: Success after binutils/gcc/linux/ [...] discards 8b8ebd9159c7 175: onsuccess: #710: 1: Success after binutils/gcc/linux/ [...] discards c205ae92fa33 174: onsuccess: #709: 1: Success after binutils/gcc/linux/ [...] discards fc873720eccf 173: onsuccess: #708: 1: Success after binutils/gcc/linux/ [...] discards d2231b39c57f 172: onsuccess: #707: 1: Success after binutils/gcc/linux/ [...] discards c0b396734e19 171: onsuccess: #706: 1: Success after binutils/gcc/linux/ [...] discards 65bd90d78e96 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/ [...] discards 390195895b20 169: onsuccess: #704: 1: Success after binutils/gcc/linux/ [...] discards 8b85cbdbf70b 168: onsuccess: #703: 1: Success after binutils/gcc/linux/ [...] discards b9e94adf4459 167: onsuccess: #702: 1: Success after binutils/gcc/linux/ [...] discards e94c85e7f409 166: onsuccess: #701: 1: Success after binutils/gcc/linux/ [...] discards d3f47cf1fb5f 165: onsuccess: #700: 1: Success after binutils/gcc/linux/ [...] discards 27074672d9ff 164: onsuccess: #699: 1: Success after binutils/gcc/linux/ [...] discards 2805740df6b3 163: onsuccess: #698: 1: Success after binutils/gcc/linux/ [...] discards 78322ff1899d 162: onsuccess: #697: 1: Success after binutils/gcc/linux/ [...] discards cc6bed519f28 161: onsuccess: #696: 1: Success after binutils/gcc/linux/ [...] discards 9407f7531019 160: onsuccess: #695: 1: Success after binutils/gcc/linux/ [...] discards afc525c5bea4 159: onsuccess: #694: 1: Success after binutils/gcc/linux/ [...] discards ccbca671e21d 158: onsuccess: #693: 1: Success after binutils/gcc/linux/ [...] discards 8da4558a1add 157: onsuccess: #692: 1: Success after binutils/gcc/linux/ [...] discards 9d0314fc3ff3 156: onsuccess: #691: 1: Success after binutils/gcc/linux/ [...] discards 7d6dd4f0ae40 155: onsuccess: #690: 1: Success after binutils/gcc/linux/ [...] discards 729979446472 154: onsuccess: #689: 1: Success after binutils/gcc/linux/ [...] discards 96c18b97387b 153: onsuccess: #688: 1: Success after binutils/gcc/linux/ [...] discards 4f5d4315d8a1 152: onsuccess: #687: 1: Success after binutils/gcc/linux/ [...] discards 470d7d1e2563 151: onsuccess: #686: 1: Success after binutils/gcc/linux/ [...] discards 1ae13cb11aa6 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/ [...] discards 3d7aa492fcce 149: onsuccess: #684: 1: Success after linux: 10 commits discards 60b32882f4b5 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 9ca22acdfcd4 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 79dbbc438675 146: onsuccess: #680: 1: Success after binutils: 20 commits discards d6b65f039f71 145: onsuccess: #678: 1: Success after binutils/gcc/linux/ [...] discards 7eed9855e447 144: onsuccess: #677: 1: Success after binutils/gcc/linux/ [...] discards 05911190ffa1 143: onsuccess: #676: 1: Success after binutils/gcc/linux/ [...] discards 183e0bbed0be 142: onsuccess: #675: 1: Success after binutils/gcc/linux/ [...] discards 8cb515d70d0a 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 1 [...] discards f8122c5f9d54 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 2 [...] discards 20d6a67792ec 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 2 [...] discards 8b3aa950eb42 138: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] discards 8dccce2fe855 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 4 [...] discards 8992ec749a04 136: onsuccess: #669: 1: Success after binutils/gcc/linux/ [...] discards 61ee2c65128b 135: onsuccess: #668: 1: Success after binutils/gcc/linux/ [...] discards c060e720cc1e 134: onsuccess: #667: 1: Success after binutils/gcc/linux/ [...] discards f22532fbc70d 133: onsuccess: #666: 1: Success after binutils/gcc/linux/ [...] discards 4c67973cd002 132: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] discards 82db390c850b 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...] discards 371c14ef2009 130: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] discards cae20cf216b7 129: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] discards 8abacdcdbfa7 128: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] discards 13959ba9d0d5 127: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] discards 6286f409f9ec 126: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] new 03708cff0b88 126: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] new b2551d0e29ca 127: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] new 9298017b822b 128: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] new 1706cdd3ee2f 129: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] new 2f5d75b7f330 130: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] new c97f30624f2e 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...] new 5b568092ff27 132: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] new fe765c7ef6cb 133: onsuccess: #666: 1: Success after binutils/gcc/linux/ [...] new 348e9ae3dd65 134: onsuccess: #667: 1: Success after binutils/gcc/linux/ [...] new 74921897bd04 135: onsuccess: #668: 1: Success after binutils/gcc/linux/ [...] new b2ae219c6b53 136: onsuccess: #669: 1: Success after binutils/gcc/linux/ [...] new 325e82948eea 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 4 [...] new d0bfce806364 138: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] new 013f308b01a4 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 2 [...] new af3bec595c7f 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 2 [...] new 6be71bef8335 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 1 [...] new abbb5b2aa1f9 142: onsuccess: #675: 1: Success after binutils/gcc/linux/ [...] new 03bd401b5c57 143: onsuccess: #676: 1: Success after binutils/gcc/linux/ [...] new aaa47151e280 144: onsuccess: #677: 1: Success after binutils/gcc/linux/ [...] new 57bdcf06e9b5 145: onsuccess: #678: 1: Success after binutils/gcc/linux/ [...] new c1a684330d71 146: onsuccess: #680: 1: Success after binutils: 20 commits new 0114b8f100a6 147: onsuccess: #681: 1: Success after gcc: 6 commits new 9bc85fe0ad79 148: onsuccess: #683: 1: Success after glibc: 9 commits new e54d705f3bd5 149: onsuccess: #684: 1: Success after linux: 10 commits new a741d418782e 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/ [...] new b84a0a39979b 151: onsuccess: #686: 1: Success after binutils/gcc/linux/ [...] new 702b929a8e54 152: onsuccess: #687: 1: Success after binutils/gcc/linux/ [...] new ed42158ab63c 153: onsuccess: #688: 1: Success after binutils/gcc/linux/ [...] new 144404859f25 154: onsuccess: #689: 1: Success after binutils/gcc/linux/ [...] new ddc3c25c05a3 155: onsuccess: #690: 1: Success after binutils/gcc/linux/ [...] new 4ef3024f809b 156: onsuccess: #691: 1: Success after binutils/gcc/linux/ [...] new 9c7c0356826b 157: onsuccess: #692: 1: Success after binutils/gcc/linux/ [...] new c0d694bee4c7 158: onsuccess: #693: 1: Success after binutils/gcc/linux/ [...] new 521c2f4a4008 159: onsuccess: #694: 1: Success after binutils/gcc/linux/ [...] new 9cb90b441863 160: onsuccess: #695: 1: Success after binutils/gcc/linux/ [...] new 0828ddf68fd4 161: onsuccess: #696: 1: Success after binutils/gcc/linux/ [...] new 8165b4e5aa62 162: onsuccess: #697: 1: Success after binutils/gcc/linux/ [...] new b974d32a0046 163: onsuccess: #698: 1: Success after binutils/gcc/linux/ [...] new f7d329932637 164: onsuccess: #699: 1: Success after binutils/gcc/linux/ [...] new 66de428ae787 165: onsuccess: #700: 1: Success after binutils/gcc/linux/ [...] new d517d077f098 166: onsuccess: #701: 1: Success after binutils/gcc/linux/ [...] new 455b4e21b46b 167: onsuccess: #702: 1: Success after binutils/gcc/linux/ [...] new 7fca25c814ae 168: onsuccess: #703: 1: Success after binutils/gcc/linux/ [...] new 24d10553aeec 169: onsuccess: #704: 1: Success after binutils/gcc/linux/ [...] new b36ea5c59894 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/ [...] new 469804a47934 171: onsuccess: #706: 1: Success after binutils/gcc/linux/ [...] new 8e1016efe922 172: onsuccess: #707: 1: Success after binutils/gcc/linux/ [...] new 91fd820044a4 173: onsuccess: #708: 1: Success after binutils/gcc/linux/ [...] new 006e8117eab3 174: onsuccess: #709: 1: Success after binutils/gcc/linux/ [...] new e813917963d6 175: onsuccess: #710: 1: Success after binutils/gcc/linux/ [...] new 21dc3d3c224f 176: onsuccess: #711: 1: Success after binutils/gcc/linux/ [...] new 9bc8e7a3a92b 177: onsuccess: #712: 1: Success after binutils/gcc/linux/ [...] new 54d3c1556597 178: onsuccess: #714: 1: Success after binutils/gcc/linux/ [...] new 8495442fab08 179: onsuccess: #715: 1: Success after binutils/gcc/linux/ [...] new 67456e628b1d 180: onsuccess: #716: 1: Success after binutils/gcc/linux/ [...] new 169c9319b025 181: onsuccess: #717: 1: Success after binutils/gcc/linux/ [...] new 458bcb8aa9a9 182: onsuccess: #718: 1: Success after binutils/gcc/linux/ [...] new 75a9a31212a9 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 2 [...] new ad3a8589244e 184: onsuccess: #720: 1: Success after binutils/gcc/linux/ [...] new 824b9089dd3b 185: onsuccess: #721: 1: Success after binutils/gcc/linux/ [...] new 51da5668163e 186: onsuccess: #722: 1: Success after binutils/gcc/linux/ [...] new 81284f7aad5f 187: onsuccess: #723: 1: Success after binutils/gcc/linux/ [...] new 92f145eb4c17 188: onsuccess: #724: 1: Success after binutils/gcc/linux/ [...] new 6f7fc63779b0 189: onsuccess: #725: 1: Success after binutils/gcc/linux/ [...] new 50ff725c65a9 190: onsuccess: #726: 1: Success after binutils/gcc/linux/ [...] new 4bdfd55a1645 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new 63c07f9b792d 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] new 0066b0346d75 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new cea0a89f143a 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new 005855cb0e56 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new 2068f026c1a4 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new 773c25dfced8 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new c1f08ccfbb0a 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new 30df575b0daf 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new ed87a3a8cbd8 200: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new ba80398f78db 201: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new 70793a296438 202: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new 63bc921d172e 203: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new 381caee3170d 204: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 6dc3edfdf5e6 205: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new cf73b15bd8f2 206: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 49632b6374c9 207: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new febc028b2acb 208: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 787f76bc7624 209: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 7b7683ad2215 210: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new d1fac31991fa 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new b7a79a4d098f 212: force: #24: 1: Success after binutils: 2 commits new c5f62bcb69a2 213: force: #25: 1: Failure after gdb-13-branchpoint-1445- [...] new 52464fe91346 214: onsuccess: #26: 1: Success after binutils: 12 commits new fce842d7c0ca 215: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new 9decb6219dc2 216: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new 7788c7ba84c3 217: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new 5e782e88e8e1 218: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new 39bcf1c93733 219: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new 3e14b2949432 220: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new 13e8f4135a06 221: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new 3ffb057434d9 222: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new c54267efea9e 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] new 5339edd78e2a 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new a2ef64840363 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new 9e213107e120 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] new 8416d5d20944 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/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 (22bcdca72944) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...] 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 2092 -> 2060 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2520 bytes 03-build_abe-binutils/console.log.xz | Bin 35004 -> 35072 bytes 04-build_abe-gcc/console.log.xz | Bin 204000 -> 203704 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8880 -> 8644 bytes 07-build_abe-glibc/console.log.xz | Bin 240516 -> 240648 bytes 08-build_abe-gdb/console.log.xz | Bin 34692 -> 34784 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3788 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2100 -> 2104 bytes 11-check_regression/console.log.xz | Bin 4984 -> 4512 bytes 11-check_regression/results.compare | 8 +++--- 11-check_regression/results.compare2 | 20 ++++---------- 12-update_baseline/console.log | 42 ++++++++++++++-------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 43 ++++++++++++----------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 36 ++++++++++++------------ manifest.sh | 32 ++++++++++----------- sumfiles/binutils.log.xz | Bin 63000 -> 62816 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150812 -> 150656 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122632 -> 122644 bytes sumfiles/ld.sum | 4 +-- 29 files changed, 93 insertions(+), 110 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits April 2023