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 a7af40e369 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards 0e3c83bcc4 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards 3abbbccf0a 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards 0760f2ac6e 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 8e62f715fd 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards 253ae2c402 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards fa8678f78a 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards 62a33d46e0 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards e53449b702 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 7057df565d 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 0a2690d432 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards a55f2aca0f 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 8bac394bd9 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 676746667d 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards a16caa9cf3 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 9c51358a54 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 1483a0962b 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards f0c8a5aedb 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards ec72f2d75f 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 1bc37e3eb8 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 1487ddcfe7 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 029c2d8d42 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards b9885757a5 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards b2236a28d0 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards d3fc3f5bc7 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 8f54fa26c5 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 88117ed59c 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 77ead7ba3b 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 5da64fe4e5 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 9fcfb4b057 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards f683f39b67 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 532e828c52 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards faa7bdf216 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 5e76a9ae54 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards c220405985 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 9dc6bc3d85 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards b8058faa75 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards c1838be17b 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards c3304d95e7 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 5ae4151e68 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 9687fd383a 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 90570d089b 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 6e26fb2734 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 456decf138 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 272f2c97ee 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards d2ceed6f7e 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 0113361e0c 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards ca719476f5 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards f75dd51349 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards f2cfb1ea0d 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 73a9676a28 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards ecbdfee09a 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 41d838e3f0 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards a4e0432ec0 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 811d8ec6ce 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards e77b076844 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards d7e1525f32 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards afbd64d2f1 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 9444f6a5a4 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 5d023de303 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards eaea5621f8 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 80aa266ce8 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards ae53e22c94 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards e01b8b7506 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards bd94a609ee 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards b62db5e393 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 2d980cdbed 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 93be0a932b 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards e5e5f00d5a 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 6b670ce323 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards cfdb4a4656 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 06224eca96 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 5faf509383 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 42bc6f1eda 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 355392176d 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards fef0a9d3a2 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards ff8a8aacaa 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 98914b35a1 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 2d25c47f8d 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 93a044241c 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 902b557df8 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 9d0dfec783 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 7277881781 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 989b4fef40 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 23dd61e9bf 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards f17b28de14 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 633975c44d 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 8d06762f88 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 1e28e5d69f 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 19bb7f830f 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards c8183f9521 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 0c135a4280 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards df4189a200 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards d554a70724 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards feb9b4247a 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 6cea333c45 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards a5a765a8bb 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 084b565790 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 60cb6e7003 295: onsuccess: #2545: 1: Success after linux: 10 commits discards b7d480283e 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 68edefb239 293: onsuccess: #2542: 1: Success after gcc: 5 commits new f70f0b0947 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 39bb2f7374 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 9c92074e87 295: onsuccess: #2545: 1: Success after linux: 10 commits new 9d136a9030 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 3d36b0a815 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 4f1d0901e6 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 0473f1b041 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new a630849dfd 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new c5db1ac50e 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new e5358d45ab 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 3ae7f8791f 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new bc0ebe6102 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 5a6a7ca8d4 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new a84688d9f9 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 0f30c89602 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 49d2ac0282 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new b0909dec16 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new ee864d6d27 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new fde83f40fa 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 0cf2e7d66a 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new d3db9d8bb0 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 7859f06220 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new f94318a154 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 42dbd7ce5f 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new ecffcceaff 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new edefa32d9d 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new e4c5c15353 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 5e00069cfd 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 2d8df25eea 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 5bca365da2 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 0b7e79d3a5 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 18fed1e934 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new b91acde4cf 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 7461601ec3 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new a76c7fa646 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new d676d07a60 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 690714c500 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new fad5fe811d 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new a4969f1a73 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 50e3c683a6 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new a666661cdf 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 40b8448afd 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 02970ac3f4 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 716ffc723c 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new e4178ca5e6 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new e36bc7a6a5 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 19f862fb23 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 0342ec2005 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 7bf117de7b 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new a4efee4adb 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new e9ce30a4e8 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 2fb9ae7550 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 6d51486b96 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 38f1dd9768 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new abfffb4c23 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 509c6d17e2 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 583e43836b 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new ef39328c3f 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new e453601ecb 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new ff3ee161ce 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 3bbaa9ee6f 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new b8d124feda 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 26acccc0d8 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 92c3183abd 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 99b942306b 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 890d033d0f 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 45cec3fcfc 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 42047a6e6b 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 1f8767812f 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 3b1b622cc7 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 3bbb4e5344 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 5b1317cf0d 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 99a450d1c2 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 6e21e586a4 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new 5b694487a6 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 7f96ce326f 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 1bb08f0b99 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new f86e0f5e72 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new ee6350e71f 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 46f2612c70 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new adf5abdfbf 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new d25f1dc4b8 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new a82ba39e56 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 345d97f17e 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 9ab9bf4aaa 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new befd500734 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 7f525037e7 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 8d22af4f29 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 756c8ff14d 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 08ad079d39 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new e8f1e50a19 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new deb066d9f2 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 2a48751f85 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new c018ba8d61 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 63c02d3e99 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 655cb77f65 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new fbea9f62c5 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new c55c25b5ea 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 822ff6e63b 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 79a10e2911 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new c6159504f3 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new 7b7bb9f3d5 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/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 (a7af40e369) \ 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 1776 -> 1812 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31284 -> 31120 bytes 04-build_abe-stage1/console.log.xz | Bin 73516 -> 72968 bytes 06-build_abe-linux/console.log.xz | Bin 8932 -> 8896 bytes 07-build_abe-glibc/console.log.xz | Bin 245100 -> 244620 bytes 08-build_abe-stage2/console.log.xz | Bin 205364 -> 204124 bytes 09-build_abe-gdb/console.log.xz | Bin 38676 -> 38484 bytes 10-build_abe-qemu/console.log.xz | Bin 32572 -> 32512 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3944 -> 3932 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3072 -> 2800 bytes 13-check_regression/console.log.xz | Bin 6400 -> 6580 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 23 + 13-check_regression/mail-body.txt | 78 +- 13-check_regression/results.compare | 46 +- 13-check_regression/results.compare2 | 89 +- .../{mail-body.txt => results.regressions} | 79 +- 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 80 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 43 + sumfiles/g++.log.xz | Bin 3408192 -> 3377912 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 3014212 -> 3019984 bytes sumfiles/gcc.sum | 4168 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 1033620 -> 1037340 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217540 -> 217572 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 429844 -> 434376 bytes sumfiles/libstdc++.sum | 59 +- 43 files changed, 2448 insertions(+), 2369 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} (73%)