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 30720ace6c 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards 589dc4e867 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards 991b37a294 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards f246fb6202 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards 507c776293 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards 6b3eee4581 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards 6ea459fd9c 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards a5a876fdad 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 8db7781d4c 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards 70d3d2a455 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards ad4ec7cacc 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards f2432365dd 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards f16ec07114 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards a41552b5de 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards c353d97ccc 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 1f995c9096 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 14260fb159 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards b85cc4d25a 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards 3c22b59917 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 8abdb27eb4 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 18830ce726 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 1f00ed0dff 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 89b9a74751 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 03606598c8 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 812faf6394 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 153e417c5c 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards dc62902c2b 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards cdec0198a4 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards d0efd66b27 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 85fcb2c899 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 84c5c2f6a0 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards a0d35f5da3 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 16cafad5dd 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards dd8fda801e 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards d8c8e0d8f4 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 9b934473d0 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 9f7d10018c 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 887968b25f 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards f1a3b2c14f 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards c002424db8 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 8dc1642027 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 718b537084 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards ffd349c942 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards ea89d76664 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards c0883c1644 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 5deb1c26dd 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards a445ae940e 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 1c4b50ad0e 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 0e2d56cd3d 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 5575dd85b0 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 09463f2312 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 19f574b2c6 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 1ad9fd514f 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 219c7ab076 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 4898188df4 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 422be20b4a 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards d9801d0c89 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards e1525f3f8b 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 47e79e230c 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards fa15838517 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards e99895eea1 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 4460bab87e 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 094b40e29e 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 01621fd62c 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 09988b3806 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 5f773b743d 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards bb8ccc6d71 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 7e53de1a1f 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 663dbe3573 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 23b4ec4070 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards eacd877852 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 6f842632c4 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 56143cd37b 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 62921269ac 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards f66bc439c9 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards be5b4ed5ed 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards e2cbd3dab7 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 35f8b62983 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 4685c0c14e 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards cae6a3cdea 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 997fdcd215 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards af87ff26bb 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards c9fd8e0431 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 4793b2524e 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 235de4503e 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 3afb7f3177 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 2ab0ce250c 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards ae933fe342 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 96bd706d33 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 2b90d89c2b 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 781a77fdfe 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 84f36d2e01 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 8227780773 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 1f5c2e76c0 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards c77d071521 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 83bd659018 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 6ca86c7cad 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards cae96cd355 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards dcd9e74281 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards ea986adf07 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 9c2d56a401 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 39e590c3ee 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new ed80f2da26 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 343f410755 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 86df2cdbd4 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 9f97fced27 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 6e3816aa80 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 5f162d9da1 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 3b785bf72f 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 1b6e09a849 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 2dbd24b544 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 3ccc8ecb1c 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new ad81acbff8 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new c6bf1fc892 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 9d6760e685 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 9b29824d3a 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new afb8df78c9 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new f109ae5f8b 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 8458b2b5b5 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 63d1540ecd 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new ef354794e1 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new d6d6215730 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new f009b1a03c 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 9f120101bb 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 7f724bcc91 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 8ec7e3a7a6 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new cd5a797730 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 973f1d2c18 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new d343a87080 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new cededd15ed 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 0778e0b960 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new ecdff99ea5 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 5e14a1e3c2 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 5ad48c6b4a 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new b9247cb1f7 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new fd6d6e17df 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new bce905dbd4 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new e0fff7ecac 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 6cc3f3f08f 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 197139be65 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new bf41bac989 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new ff4cdc8adc 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 5136f38b02 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 7218f7d066 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new a7374eb343 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 0a1f6d34bd 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new de9dbcdd80 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new dacb3e2fd8 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 8569fb8674 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 6e46276f8a 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 2908224b3d 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 63b6345e1c 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 96a7c6fca4 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 0c74a3b808 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 791321e677 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 59ff1bce31 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new a72bf661e1 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new d1b60ea802 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 04b5e9f879 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 7b16528ec3 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new a3ee5a1262 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 7658624c47 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new af2213e8d5 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new eaa184331c 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 3d9e50b8b2 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 074f8408e4 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new b447372adf 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 496787508d 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new de3fb99fc3 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 70e9f50a2c 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 9c0de97146 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new ff1500e365 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new c7df92a704 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 6f63b73c6f 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new c3f4df28fa 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 19af5e8cd9 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new dcecdb90e3 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 9edb9fa409 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new e6b0e09e61 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new d2a816805c 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 15ce8a8dfc 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 625a08099f 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new c25c21ee74 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 70084ab451 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 3e48be702c 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new eabdec1e0b 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 94f79e851c 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 72b55c3c2e 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new 51a9b6bf01 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 966826c4ad 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new 02375c3c33 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 19ee95155f 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 0ec323c38a 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new 89d3804a3c 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new f03f228327 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new cb473fe75f 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 708aa81606 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new a0957e831a 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new 010e0900d8 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new 619457f104 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new 5d41637037 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new da5dfe8d64 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new 24834b9129 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...]

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 (30720ace6c) \ 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 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31360 -> 31448 bytes 04-build_abe-stage1/console.log.xz | Bin 73316 -> 73240 bytes 06-build_abe-linux/console.log.xz | Bin 8608 -> 8596 bytes 07-build_abe-glibc/console.log.xz | Bin 245008 -> 244860 bytes 08-build_abe-stage2/console.log.xz | Bin 204972 -> 205016 bytes 09-build_abe-gdb/console.log.xz | Bin 38656 -> 38632 bytes 10-build_abe-qemu/console.log.xz | Bin 32608 -> 33072 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3936 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2640 -> 2764 bytes 13-check_regression/console.log.xz | Bin 6288 -> 6564 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 87 +- 13-check_regression/results.compare | 34 +- 13-check_regression/results.compare2 | 169 +- 13-check_regression/results.regressions | 51 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 89 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 51 - sumfiles/g++.log.xz | Bin 3382096 -> 3397040 bytes sumfiles/g++.sum | 64 +- sumfiles/gcc.log.xz | Bin 3023256 -> 3017960 bytes sumfiles/gcc.sum | 4737 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1038624 -> 1033856 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217592 -> 217580 bytes sumfiles/libgomp.sum | 6 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 436124 -> 431460 bytes sumfiles/libstdc++.sum | 42 +- 42 files changed, 2703 insertions(+), 2792 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