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 eb197ece7b 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] discards e938819d9e 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] discards 43c2407d35 408: onsuccess: #2662: 1: Success after linux: 11 commits discards 6e356d97a2 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards 7295524281 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards 76c823ec37 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards b17b0c8b7d 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards 0352032c78 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards 1ba2a7b5d8 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards 4a2c5165ad 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards a6acf73eb3 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards 9450f61c65 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards c6a29d0c1f 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards 2ce9855f77 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards a722eba673 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards 6c515910a5 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards dbbb5e2ea9 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards 6b68c4fb53 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards 97d8dd16df 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards 8db90e421a 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards 690ce18474 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 839bf36ae1 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards a96f6a3c70 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards 8518752b1f 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards 40a235cb5e 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 8d8a0a52df 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 99efbf15fe 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 91f72675b3 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 2c46439540 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 756d04e585 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards c9deac73ff 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards 30fdb97d78 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 17fb9b2f18 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 4c1b1703ff 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 5f7c43bc56 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 932ecfb439 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards c9aa1577f9 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 435f8ac95f 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 325c86ed16 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards f779a4d6fb 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 9bd58c89fe 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 5e96130e72 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 70d52138ac 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 95505b8a5a 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards fb1c76ed15 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 1aee1b9e8b 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 6136e71223 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 36a438e62f 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards ebd39e0eb8 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 1865f58ef8 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 6422e052e4 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 261c9f428d 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards e4fd04410f 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 69cb8bc507 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 17d9a270ae 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards e3d24c611f 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 9e1cbc7c93 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 51a223c08a 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards e4c267bc73 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards af238fc234 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 941bd5d4d1 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 0fdc828143 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 9e0e861d88 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 16d12fd69f 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards d5dc827ad5 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 25970e42b5 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 00a78d2e55 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards bcb5ddb7c8 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 5ad894c32d 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards a0e37a8a5c 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards d67a864d21 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards aa3307d004 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 63275dd9d2 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 8b80612894 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards fa6e678d39 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 1a72120b39 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards fa48d7f261 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 6ee9dd5af3 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards a080c403fd 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards dc8fff733c 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 1e82966a42 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 233a510c37 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards e871d98eb3 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 8d6d652db7 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 74c49c9eac 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 0386d4b588 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 320550dd4c 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 745950a0b7 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 9f8b08c402 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 072fc47d84 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards ef5078afc5 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 6c8f6765c9 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 5245d85976 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards de051418ac 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards bc38bf2e76 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards ffa8c73178 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 5b6fea88a0 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 6fbcf2226a 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 76b2bbe632 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards a8fbaef93e 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 9052b08730 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new a7bebdc345 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 409bd749e7 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 4f929a39e7 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new ccf61bb005 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 8073b86322 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new a304513225 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new ad328d8e80 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new d627a56dcf 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 7776cf7555 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 2833ceb615 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 97e947cc3b 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 1d159693aa 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new aa2326990b 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new bf7bf541d6 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 48b710f3c2 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 1ebe2d68b1 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 51e3943ad6 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new bfcb5bc9fc 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 5e84bce579 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 5fc5c4462b 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 188b14049a 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 2d4ff8bb1a 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new de88c9f452 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new ad056b96d2 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new ecfbdf8b1c 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 8b3b26bcef 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 92845a7b93 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new d9ccb0ffb0 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new ce5049c529 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new d3a658c8ae 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 2b1fc18bad 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new b2f825b1cf 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new f942691e19 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new ee1d6dc361 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 3d5b056afb 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 3e9bfccbc9 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new f82fba0e30 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 6233ee2d94 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 596b3a1b4b 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new ab10529d29 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new a0a357523a 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 07f265dd90 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 0c2344ca96 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 08d25d1e66 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 144fb0beef 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new cd4883ef1f 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new f68c9998d2 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new c94d35de9c 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 061b293641 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 12acaeccb7 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new e2b667e652 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new c48ee111e6 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new c0c0976be0 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 8880a03ccd 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 16d95d2039 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 9686c6ef9a 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 51fa5fff73 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new 6d7692f28d 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new eb22a09bb5 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 037fc15385 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 4d4458b07f 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 4e591b3ab2 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 107a4df7cf 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 2d95bee238 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 3b57819258 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new efa2a82f20 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 2e005cd5f8 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 608c453382 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new dc197999af 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 922e07cac7 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new d87992751e 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 4caeaf6839 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new f1a303d4e9 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 0eb4c1ed02 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new 2c8f28cb33 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 14df94ce1b 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new febe132277 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 14313d8477 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 632e3ed7d7 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new fc78f4b18f 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new a74caf3e20 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 3298c1ab7d 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new ebc607006c 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new 2ca5177c00 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new 9cc9d52749 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new 370d51036e 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new b39289497d 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new 10608841eb 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new 48605ec1c2 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new 59c10d0c61 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new 949e6b5d69 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new 0c07c2f555 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new b8f7407eb1 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new 5817a1f4cf 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new e854b21ff2 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new 0150c3814e 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new ccadea8501 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new adf49b4b92 407: onsuccess: #2661: 1: Success after gcc: 7 commits new 8ac4bada27 408: onsuccess: #2662: 1: Success after linux: 11 commits new f7beeaf4b8 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] new 10c8a13ad1 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] new 8fe8f161da 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits
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 (eb197ece7b) \ 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 1820 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 31092 -> 31276 bytes 04-build_abe-stage1/console.log.xz | Bin 70544 -> 70656 bytes 06-build_abe-linux/console.log.xz | Bin 8336 -> 8340 bytes 07-build_abe-glibc/console.log.xz | Bin 244324 -> 244724 bytes 08-build_abe-stage2/console.log.xz | Bin 201856 -> 202516 bytes 09-build_abe-gdb/console.log.xz | Bin 38984 -> 38920 bytes 10-build_abe-qemu/console.log.xz | Bin 31528 -> 31504 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3824 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2596 -> 2760 bytes 13-check_regression/console.log.xz | Bin 6180 -> 6368 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 28 +++++++++ 13-check_regression/mail-body.txt | 48 +++++++++++++++ 13-check_regression/results.compare | 47 ++++++++++++--- 13-check_regression/results.compare2 | 99 +++++++++++++++++++++++++++---- 13-check_regression/results.regressions | 48 +++++++++++++++ 14-update_baseline/console.log | 68 ++++++++++----------- 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 | 50 +++++++++++++++- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++------ results | 48 +++++++++++++++ sumfiles/g++.log.xz | Bin 3424304 -> 3414740 bytes sumfiles/gcc.log.xz | Bin 3009012 -> 3012376 bytes sumfiles/gfortran.log.xz | Bin 1040824 -> 1036928 bytes sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217724 -> 217652 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 438344 -> 437996 bytes sumfiles/libstdc++.sum | 101 +++++++++++++++++--------------- 39 files changed, 462 insertions(+), 128 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions