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 12b6fe4b07 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards 57aa2c022a 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards 0def9affea 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards d5f5d94183 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards 27030e8dc0 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards c16f7eb6fd 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards 723f389fb8 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards 959ec8d079 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards 6056ea2da8 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards 0f68e86818 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards 551b5e2caa 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 034bbee0d5 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards f41bf4f9e7 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards 4f0c281a3f 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards 4374de3f2f 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 600ffecd09 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards caf751f996 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 6162f7439e 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 906b75fe53 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 4dcc73ede5 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 003a46a308 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards 4a5f413f57 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 1f54a2a12f 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 8e153cbb34 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 143d7240ef 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 8dcdf4d605 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 0df0fb916d 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards e917404bff 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 1344e35b2f 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 362dd7062a 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 8936368e56 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 2a686722bb 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards e0a3f3ccd8 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards d8c7493374 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 6ae903aba2 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 0edb13cd84 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 98fbe6fc0b 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 8d63608c5c 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 32e898ce4c 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 0688d330a1 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 6041a5aef1 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 78d8e557eb 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 98da2862ab 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 70b7425068 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 50949b16eb 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards e3f8463003 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards c47f2508cd 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards c646ca9ec8 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards c2f88eedd5 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards ec1c07fda1 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 047ac1963e 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 2f82fadbdb 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 5d83e629d7 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards a34d12de3d 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards ed58bddbc2 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 1295660363 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 42e726516a 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards f83aadbf4c 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 5f28add259 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 61567924d3 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 2f1a1a6260 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 70ba68e55e 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 57bd68791f 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 4413a7aa51 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 20c80aac8c 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 327ab75d15 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 20f9c0d521 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 9b5657c042 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards bc21a310c3 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards afb23ab641 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards f958afbdf6 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 08ed1a2924 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 26a77d2666 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards bf83de0d40 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 9e0d939a83 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 374b1450fd 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 3aa9c88c45 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 12e1d18f3d 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards ee0804fda5 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards ff2db0c93b 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards a5a7fad9fe 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 30874ae96a 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 292e5d1f76 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 6e38069455 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards a079564b7e 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 2c7c443d8c 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards db0bf588e1 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards a3b213c5df 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 6025b53554 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 5cc620c9ec 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 5fdfb14b0e 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 6ead5b0b36 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 6e69c83fb4 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 41a514b4de 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 183fb2756b 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 410c5b0a79 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 82581a8ad9 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards b7426d8493 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards ba509a0aea 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards ec8db2ed33 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards b3af950b09 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 64dcaa8d06 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new ffbf6a7a5c 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 455824092c 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new ff89c0d65d 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new db72a1ce38 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 965ce4d8db 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new ebf258769b 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new c4f446a3fd 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 53dc1b6a65 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 825fbe1f88 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new bded1cc3cd 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new c5d7cbacf2 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new b3ecfd11d5 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 4510ed2b17 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 4f4c739d31 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new c44bc22c4a 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new fd817ac0a4 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new c7a332d4d7 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 8a5628bd67 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 9241eb40c7 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 4d0922b278 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 8580110c73 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 85f396128e 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 35ad261ff8 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 15cbc838fe 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 16d399b34e 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 241f07f738 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 7ae46d99a4 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 5a04cd962b 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new f5554220ff 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 5559157b01 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 1b811bad13 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 60d0060c67 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new d9457cc0d5 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 65681b1c93 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 4f26a152ce 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 11c1942ac6 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 41eb940de7 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new e35af88000 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new e79024f4b3 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 32a78e2f20 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new deb7f16cb3 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new b4cf8148e2 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 7703dd4068 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new d2f31d0e77 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new de584032d1 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 35a3a24bf3 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new a69f539da8 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new d9a2d0e284 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new dd62ead902 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new bd2ba6c7de 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 280e91f049 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 648706411c 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 91ebcfbe99 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new c9838dd55a 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 8514b417bc 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new b7430faf00 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 03fb06327a 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 442e5ea70a 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new b06fd9cd4a 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new f6a894f78e 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new d5f6080600 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new c50ad12b1c 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 28e8b90660 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 51921ceadb 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new ada0b739e2 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new e478e2a750 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new c1eedb6a83 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 4a59f0d0d1 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 29fdb7be10 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 39e5a05f4b 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 1f6aab38eb 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 640100d70b 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 218a50bfcf 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 124f1865b1 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 48d678ce52 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 092474abb5 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new d48bf81865 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 7b2b79321f 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new b30aeee192 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new fe6ae4122a 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new aae11a772d 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 39f07938f3 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 8796b61632 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new faa8304790 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 524dd00827 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new 91eedd8951 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 613a6462c2 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 4b4618df2c 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new ea82a7f149 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new 0e7b0b3861 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 7f3fa83432 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 66f6ed02e7 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new 5b1bc3e774 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new 5d744ae5ed 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new 361ad04b53 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new b48046151e 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new 6d767c5790 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new 077c3af836 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new 3742b194c0 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new b5a15b6583 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new df83701b0b 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...]

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 (12b6fe4b07) \ 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 1768 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31120 -> 31236 bytes 04-build_abe-stage1/console.log.xz | Bin 73488 -> 71264 bytes 06-build_abe-linux/console.log.xz | Bin 8516 -> 8452 bytes 07-build_abe-glibc/console.log.xz | Bin 244100 -> 243900 bytes 08-build_abe-stage2/console.log.xz | Bin 204988 -> 202488 bytes 09-build_abe-gdb/console.log.xz | Bin 38644 -> 39088 bytes 10-build_abe-qemu/console.log.xz | Bin 32488 -> 31740 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3956 -> 3832 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3576 -> 2852 bytes 13-check_regression/console.log.xz | Bin 6760 -> 8476 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 20 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 22 +- 13-check_regression/results.compare2 | 458 +- 13-check_regression/results.regressions | 40 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- results | 40 - sumfiles/g++.log.xz | Bin 3404084 -> 3412720 bytes sumfiles/g++.sum | 447114 ++++++++++++++--------------- sumfiles/gcc.log.xz | Bin 3021872 -> 3010904 bytes sumfiles/gcc.sum | 238629 +++++++-------- sumfiles/gfortran.log.xz | Bin 1036028 -> 1041412 bytes sumfiles/gfortran.sum | 19090 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217656 -> 217668 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2660 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 430088 -> 434228 bytes sumfiles/libstdc++.sum | 599 +- 43 files changed, 353285 insertions(+), 352940 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions