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 de16e64744 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] discards b0a1416625 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] discards 8b25d4376f 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] discards 5038399d73 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] discards ecdf92b62a 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits discards dc6d39c79c 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] discards b4174b5fc5 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] discards dae39ce1e5 408: onsuccess: #2662: 1: Success after linux: 11 commits discards cd96086285 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards ad7b62add0 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards 416a44c2dd 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards 6cfa23270c 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards ef1e2dbc75 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards c52eaac16a 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards 5c3dcdc188 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards 6d00f0d1fa 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards 6152fe63e2 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards f5d64da0d6 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards db19a990cc 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards 3a9ec7efb2 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards 35f47f95b6 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards bb5f99e30d 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards 43e55b0822 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards 39b86bd60d 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards 2b6661feb0 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards de46df6408 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 25f9a38846 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards 8125bf078c 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards bea9977bbf 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards f71092aeb0 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 2f1b9b289f 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 700b4382f3 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 1369a1e47c 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 0123a7b507 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 1e5de3c437 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards adf91e580e 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards 0205af0684 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards c792e632b9 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards f722fdb7f7 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards a75f4ae034 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 72d2b40a7b 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 3b8fefe59b 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards bb84f7acf5 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 39a9ce99f2 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 00eb550a16 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 7dbb0af0be 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 6edae7eb53 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards da92000e8b 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards f05d236861 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 5c4953b360 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 63afcbc741 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 2a939e78d2 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards ae604ebc66 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards ee9cd37b29 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards acb013ae03 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards aef425c77a 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards ba46ec3dbe 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards b2c692e888 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 336c1832b2 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 1fe2830107 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards dfa1a6e2f0 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards d5d1c6501d 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 2eb03537e2 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 8f2e9392ff 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards be0823290c 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 0dc5c7c119 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards e912e34350 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards d11c42fe58 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 12a386128a 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 98af61b11f 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 6f0782e86c 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 8badf82386 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 5394e6403c 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 36b4aad41b 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards b41a08a9b7 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 2fc4f991df 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 123d9b88b9 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 5a13aa57ef 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards ab366afac9 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards c29aff7365 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 4a82bbed08 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards b308fc29df 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards a9a36180c9 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 85f5f6f05a 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards e289040be3 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 1e5ec1ca14 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 729a69c91e 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 834cfaabc3 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards b3211d9afa 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 5d6e993abe 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 060413780b 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards b29b4765fc 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 36669e1199 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 5fa54e8b22 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards fa045044a3 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 91f3056174 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards f2f87e7b93 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 6783134a14 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards df1eb825f3 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 1284d402eb 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 1072219997 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 0d3390fba6 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 63a4f45ab6 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new aa364cc98b 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new bbebada1e5 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new dbfbd2558b 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 4d037c2ebb 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 39d9f93f4c 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new df5edb929f 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 68b99df55d 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 8538e900a5 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new c7a7d53c76 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new f626e02fe6 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 149a162ec6 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new b4e6973b89 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 6ce925a697 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new fa8e14414b 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 10cd3f29cf 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 691b30464b 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 81e565a609 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 2e8c7d4232 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 239d9cfbdc 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 4a2f010a5d 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 2a1ccd70e5 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 7eaec06141 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new c991beb4a1 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 095f1b8e3f 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new f2faece2d8 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 15d75bc725 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 39d79a0dcb 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 44ba527335 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 8a383648bd 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new a4e4dc0cd4 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new fe8dcb2e83 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 9dac896e16 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 79bb053f6d 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 243a622d4c 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 602f5e138c 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 7a10bb8d2e 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new ff0c50a551 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 5e66082d9f 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new b88a74fbf8 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new c8c823cb2a 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 1eff922ef5 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 15330c87ae 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 28acbfbb68 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 809f36792d 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new ab9304a3b3 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new a9a4e9c773 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new ed3e596467 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 06fd7f7f90 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new cbb434b18f 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 335faeb356 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new ed3777dd4f 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new dc9a5b2576 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new e05dc7f21b 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 6b7bdbd524 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 403e53be37 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 52063cc77a 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 1548f53a67 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 752486dffd 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 036783bb38 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 203bfd417e 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 81ca39e6c7 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 0da0fb1b80 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 56748e90bd 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new f1f1089cd3 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new a3302c6ae0 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 2aca96cbab 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new c2ea1cb56b 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new 74b6957ce1 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 5d875a5f04 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new 6a90bda5b5 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 6b25b365ba 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 70af3f422a 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new 6e821bce09 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new c790e868a5 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 9444dff09e 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 88fca69f33 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new a158af18cb 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new 734d5e797a 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new 02ca842304 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new 55bd6df1c7 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new 95962042b8 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new c9c73fd546 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new 922c2b827e 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new 4a9992308a 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new a905e2244f 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new bf9609e07e 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new a9238d71ab 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new 55fb6a57d7 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new 1082c7a17a 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new 658f3b9de2 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new bb216d8a26 407: onsuccess: #2661: 1: Success after gcc: 7 commits new 064126874b 408: onsuccess: #2662: 1: Success after linux: 11 commits new 83f8a3393e 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] new 3fde12ff98 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] new e302fe99c5 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits new 0123d84d61 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] new 6cfa83b5a9 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] new c442e18aa7 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] new a918b86a90 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] new 311af1d749 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/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 (de16e64744) \ 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 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 31508 -> 31060 bytes 04-build_abe-stage1/console.log.xz | Bin 70668 -> 70820 bytes 06-build_abe-linux/console.log.xz | Bin 8472 -> 10508 bytes 07-build_abe-glibc/console.log.xz | Bin 243556 -> 243804 bytes 08-build_abe-stage2/console.log.xz | Bin 202616 -> 202352 bytes 09-build_abe-gdb/console.log.xz | Bin 39184 -> 38732 bytes 10-build_abe-qemu/console.log.xz | Bin 31844 -> 31440 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3876 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2688 -> 2732 bytes 13-check_regression/console.log.xz | Bin 6992 -> 6516 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 10 ++++ 13-check_regression/mail-body.txt | 95 ++++++++++------------------- 13-check_regression/results.compare | 50 +++++----------- 13-check_regression/results.compare2 | 103 +++++++++++++++++--------------- 13-check_regression/results.regressions | 30 ++++++++++ 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 | 97 ++++++++++-------------------- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++++++------ results | 30 ++++++++++ sumfiles/g++.log.xz | Bin 3414240 -> 3404600 bytes sumfiles/gcc.log.xz | Bin 3015800 -> 3022024 bytes sumfiles/gfortran.log.xz | Bin 1042308 -> 1040180 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217604 -> 217676 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 436936 -> 435480 bytes sumfiles/libstdc++.sum | 68 ++++++++++----------- 41 files changed, 301 insertions(+), 311 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