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 8fbab79c59 427: onsuccess: #7: 1: Success after linux: 26 commits discards 50c00fc562 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards d74e1a92a1 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] discards 8f539e03a0 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards ec14b4cc11 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 39182bdd08 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 1e0cac5856 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] discards 68672a45df 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] discards f91345d849 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] discards 98d1cc4735 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] discards 97b57d3b88 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] discards 93f4a13793 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] discards fa3bf2b6fd 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] discards 46bf966b57 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] discards fe349d88d1 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] discards cb076ba73a 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] discards 2e63352234 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits discards 593b6d264d 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] discards 9cafb2ffb1 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] discards 6fffdd8236 408: onsuccess: #2662: 1: Success after linux: 11 commits discards e8141c6d36 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards 2625197b5e 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards 375a9fd1c9 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards e6d69968f3 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards baa29a1ec4 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards f0af7fcf15 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards 5a1c01b83f 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards e4be5f1012 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards 3e9a21391a 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards afcb56e975 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards babbe829ae 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards ab6c5dfe4f 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards f2e62de067 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards cdafed0564 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards aeb1e4ad9b 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards 16e8b1f69f 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards f0bcbb330d 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards b448ccd564 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 0f67e5ea2b 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards 8ac639adce 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards 48751ec652 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards 498bfed418 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 8919bd6130 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 7c68950ae2 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards f81015390e 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 952762bc79 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards a931437d4c 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 9853674b40 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards abd40e2e3b 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards b842101aa9 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 11b0022d43 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 523d9c04c2 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards b73ff3c62c 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 56466cbdc4 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards febaac9a40 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards f76de5582b 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards bce2c7e6e7 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 6d60ca3955 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 47b50d955b 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 2c89afd9f0 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 882078ab51 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 508ccd55d7 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards a029a991ee 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards dbae9682d2 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 0f79c549b7 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 1c4dd388ff 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 493dc6b3b0 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 49d226b1ae 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards ed827b6c5c 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 6f6220db77 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 515b047e99 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards a1d41b953e 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards a2da7c287e 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards e335ece267 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards cff19f203b 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 0f80fb5803 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 46ece2d4a5 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 608d01461a 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards f4a43c8969 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards d026d59d6d 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 8ef69bf8b0 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards d1088b7bd9 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 5a8f166d12 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 081805feb5 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards d219c37bf4 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards a7918e3c13 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards fdace854c8 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards ed8acd81da 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 24baf9d943 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 89e985266e 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 4341001a5f 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards ef5d47daca 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 0abf7051af 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 87265019a8 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 645d60d4bc 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards be1e12f606 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards c30bc36420 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards bc5df2bb41 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 2b039fb2a0 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards fdeab721af 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 77468b8649 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new ac8df6ad05 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 84aab24136 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 77624a449b 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 27e2fe4d8a 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 06028fd3ba 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 0deeb6989a 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new ddf85b0281 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new c253367054 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new e45ad04347 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new ef784ab5f6 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 90fea213ab 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 83aca06855 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 6a8fd3e7f3 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new c078ed343a 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 0e29d62d71 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 93484b7484 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 75aa5607b1 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 2830571484 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 0dfedd2d7b 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new c2563b3b80 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new eefc6045e7 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new d1cb4980be 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 573e5e472e 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new ceafa82ced 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 85cd281fb9 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 6698fbb3a9 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new bed22cbf52 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 0db89372c3 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new bad97df6ba 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new fdbcde75aa 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 012fa81ca0 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new d08f8980b4 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new a0f6b2010b 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new c22a914b8b 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 589355984f 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 9cef5d33f2 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 27da9082e8 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 46edc6238a 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 8a94166aba 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 51b2597f05 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new b9c9f832f2 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new ec01fc0f28 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new fd470cfc07 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new d275ef46b4 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 8bf351845c 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 894d3f518b 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 624f22ad77 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 4f86527aba 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 59c8fa9517 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new ea10d0ab0e 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 1468eae967 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new dfb4317ff2 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 652ff8bc29 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new fb3b98e2fd 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new e9ed60b27d 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 9fac46e6d7 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new fe2f6d96d0 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new 1663f03fd1 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new c3a8835e30 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new d4b3598876 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 1cc12b31ee 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 3dab4a6e8e 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new 6433ec03aa 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new 8b8c616cda 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new eefd09ed0f 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 28947389ef 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new d60bdb79b6 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new 247940020a 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new 6881b7bf92 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new 46b908c559 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new 262396b716 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new 888fae473e 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new 00d6a0f375 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new 8d69ed8a5a 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new c27f2f72cb 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new 2a6eb0d4dc 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new be0ec46098 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new 95e620493c 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new 177eeb92a8 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new 0688578b26 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new d456c9a9e8 407: onsuccess: #2661: 1: Success after gcc: 7 commits new 2a7ffb9f73 408: onsuccess: #2662: 1: Success after linux: 11 commits new 36aedc8fb6 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] new 13e17decba 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] new f0337ad6e1 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits new 7c4f88d19d 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] new ab9f3adc06 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] new 31c0e8987f 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] new ed41f9abd9 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] new 462c28189e 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] new 9cc63c540e 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] new 4971223e4f 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] new a70e4724ab 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] new 5a56874a44 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] new e4b1f35ddc 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] new 4055125e1f 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 7542529d61 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new dff75b2f42 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new b535239f22 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] new 7a4b8c3886 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 781102960f 427: onsuccess: #7: 1: Success after linux: 26 commits new 9a1248c2c0 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: [...]

This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:

* -- * -- B -- O -- O -- O (8fbab79c59) \ 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 1808 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30928 -> 30844 bytes 04-build_abe-stage1/console.log.xz | Bin 70960 -> 71832 bytes 06-build_abe-linux/console.log.xz | Bin 8496 -> 9612 bytes 07-build_abe-glibc/console.log.xz | Bin 243832 -> 243476 bytes 08-build_abe-stage2/console.log.xz | Bin 202648 -> 203240 bytes 09-build_abe-gdb/console.log.xz | Bin 38816 -> 38808 bytes 10-build_abe-qemu/console.log.xz | Bin 32152 -> 32012 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3816 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2596 -> 3240 bytes 13-check_regression/console.log.xz | Bin 6348 -> 50920 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 11 - 13-check_regression/mail-body.txt | 59 +- 13-check_regression/results.compare | 25 +- 13-check_regression/results.compare2 | 5827 ++++++++++++++++++++++++++++++- 13-check_regression/results.regressions | 31 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 61 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- results | 31 - sumfiles/g++.log.xz | Bin 3425708 -> 3396336 bytes sumfiles/g++.sum | 4282 +++++++++++------------ sumfiles/gcc.log.xz | Bin 3025780 -> 3021896 bytes sumfiles/gcc.sum | 1442 ++++---- sumfiles/gfortran.log.xz | Bin 1044104 -> 1041820 bytes sumfiles/gfortran.sum | 18 +- sumfiles/libatomic.log.xz | Bin 2312 -> 2316 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217204 -> 217432 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2688 -> 2680 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 437996 -> 436256 bytes sumfiles/libstdc++.sum | 62 +- 43 files changed, 8824 insertions(+), 3152 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