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 8a99856bf4 430: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] discards c5c76da56d 429: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] discards 735596ce2d 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: [...] discards c58fa854b1 427: onsuccess: #7: 1: Success after linux: 26 commits discards b630422ed5 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 7e6ee14153 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] discards 270c541b00 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards d98e7e8392 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 36850a6550 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 0df78818fe 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] discards 20461454c4 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] discards 00f2787e38 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] discards 4469bacc89 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] discards e9216b2334 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] discards 021d86b08c 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] discards ebc4ca0345 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] discards 03a610940e 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] discards 3df2783037 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] discards f9cc61f5dc 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] discards 4550d44351 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits discards 729d4b6d3a 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] discards afb4cf1a53 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] discards 755d0413e1 408: onsuccess: #2662: 1: Success after linux: 11 commits discards 3450e299e8 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards 18898d92b5 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards 36b782b125 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards f57a033a15 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards 4e15963ebc 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards 7cc5c932ce 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards ae56c71d4d 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards 79036d2f45 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards a30ba68940 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards 8a39a38bc7 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards 9ef6bd5d7a 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards 69be566db8 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards c4893e288c 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards fd81be5941 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards 2a8544cee3 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards 49dd2962dc 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards 7a69e46d1a 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards 9871143170 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 2ebe671bd2 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards b206c2403d 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards c21eed0aa6 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards 56d9121f4f 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards c31280cdeb 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 11d32268f5 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards acd5c07a69 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards baa448b0db 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 7437d93a5f 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 5d55d8cbad 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards f39bda015d 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards e231af0b80 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 34f60c2098 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards d2b8195dd1 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards b4f56bd04c 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 3dbfe51254 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards e28b4665a6 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 1bc38f3c72 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards a46b654c25 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 89a86abba0 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 560cf38aa3 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 6a7a2f9f58 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 194232c010 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards d62eff46d7 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards d8b94afe9c 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 5026ce83eb 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 37357bdfbe 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards ac4e984a82 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards ab67e4b433 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards a7556e3ebe 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 6f030debf8 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards bc227610d8 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards f1b6873711 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 6d3254720d 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 7cb12c3bc4 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 225fd9969c 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 2492557645 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards f9ad1c2fdb 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 7001a95247 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 84391743a9 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 91df815a1d 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 4c555df2fa 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 73c6d2066e 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards ae06723705 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 4deabebcfa 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 76419089b6 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 8f11b8a92b 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 137c648a44 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 3f51f782f7 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 5c244d9a71 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards ed7209dc2a 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards bb59094d05 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 4f4d292fe5 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 9b5c42ac6f 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 516691acb0 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards edc8524733 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards ba38a65ade 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards f70ad60d06 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 07ca2f7a9d 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards f748e189bd 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new be2ac9a8ad 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 692acf5b93 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new dffda96d73 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new f3a459e435 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 67dc2a6499 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new d62311db1e 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new d5de39cd96 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 32e4c94e53 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new b036c8d8d7 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new b3fb7d6a35 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 8812c4a049 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 03e8c0ccea 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 39dacda774 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new b35acb5225 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 0e228a41fd 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new c9fbb9b0ab 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 71dc120aea 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 9df0fac014 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new c0b94a32ba 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 45ee9cbbea 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 7fd2aab835 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new a3402af528 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 50169cf0ea 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 8c4ddef00f 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new d6407058b9 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new e93ad14687 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 96baa3f195 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new af46ff8885 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new fbe25f11fd 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new f4407db403 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new c3136846b4 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 7ea4f5eb76 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 8cc6cf28d2 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new d03452f5fb 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 843f6521aa 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 40e5dc7708 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new b7e06fd9f7 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new 535fbeae27 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 474d8dbfc1 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 0693a5900d 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new f9da731e4b 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new ae4b707dcd 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new c05e1f38ad 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 480d10c6ad 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new a73d228a10 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 058d49fd04 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 70b01fd6e5 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new a63d65e979 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 58bfea29df 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 8effcaa39e 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new ac54de5c83 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new dde46698a4 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new ba7b91c719 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new a0245e97b7 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new 920af4b12c 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 7e986ff7c9 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new 50d5e14208 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 7395fa9db8 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new e336ba73e2 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new 558289f5c5 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new e1839f14bc 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 45546bf672 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 441d74ea2b 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new 9fd0fb0cb3 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new 4770f4eed3 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new d08158d9dc 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new eaf62295fe 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new 02744efbca 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new ebbbd8ff1b 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new 1e880470d8 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new 865adde643 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new dc1dbf0927 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new 2f16278b9a 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new c83669f960 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new 602f32d817 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new c7d0e1f048 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new 8caf664486 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new d3c2ff55ce 407: onsuccess: #2661: 1: Success after gcc: 7 commits new 2c63e0176c 408: onsuccess: #2662: 1: Success after linux: 11 commits new 5798decb4f 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] new df7933fa38 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] new fcc2d76c54 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits new 5ec0140a37 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] new 7d1b613867 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] new 80786d71e1 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] new 2b78e1a308 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] new ae6b668688 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] new 77603725ea 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] new 61c714f0d2 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] new 1a1df12cbb 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] new 454678722b 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] new 0458cbb3c8 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] new c179473537 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 21b4fd0773 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 17acf94154 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new b58df5b878 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] new a5976466a0 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new ee8cadec87 427: onsuccess: #7: 1: Success after linux: 26 commits new 881bf13938 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: [...] new b3a7bf5867 429: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] new 90422b48dd 430: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] new 75f347497c 431: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...]

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 (8a99856bf4) \ 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 1792 -> 1824 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 31228 -> 31700 bytes 04-build_abe-stage1/console.log.xz | Bin 71640 -> 71716 bytes 06-build_abe-linux/console.log.xz | Bin 8804 -> 8864 bytes 07-build_abe-glibc/console.log.xz | Bin 244024 -> 243264 bytes 08-build_abe-stage2/console.log.xz | Bin 202924 -> 201792 bytes 09-build_abe-gdb/console.log.xz | Bin 38932 -> 39240 bytes 10-build_abe-qemu/console.log.xz | Bin 32100 -> 32816 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3852 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3004 -> 3136 bytes 13-check_regression/console.log.xz | Bin 7724 -> 30324 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 30 + 13-check_regression/mail-body.txt | 52 +- 13-check_regression/results.compare | 31 +- 13-check_regression/results.compare2 | 6070 +++++++++++++++++++- .../{mail-body.txt => results.regressions} | 53 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 54 +- mail/mail-subject.txt | 2 +- manifest.sh | 48 +- results | 50 + sumfiles/g++.log.xz | Bin 3396188 -> 3388172 bytes sumfiles/g++.sum | 4371 +++++++------- sumfiles/gcc.log.xz | Bin 3016460 -> 3026876 bytes sumfiles/gcc.sum | 1614 +++--- sumfiles/gfortran.log.xz | Bin 1036544 -> 1035916 bytes sumfiles/gfortran.sum | 22 +- sumfiles/libatomic.log.xz | Bin 2316 -> 2316 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217540 -> 217324 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2688 -> 2676 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434620 -> 423176 bytes sumfiles/libstdc++.sum | 21 +- 45 files changed, 9396 insertions(+), 3114 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum copy 13-check_regression/{mail-body.txt => results.regressions} (78%)