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 473e6169a5 432: onsuccess: #12: 1: Success after binutils/gcc/linux/gdb [...] discards 1002e189f7 431: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 03d44b5d55 430: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] discards 80e00ecf1e 429: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] discards d2efce69c9 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: [...] discards f2ee15bdf7 427: onsuccess: #7: 1: Success after linux: 26 commits discards 58117192a5 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 1a445279c3 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] discards 403ef6b233 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards b90d409f54 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards b2233bce87 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 4103a47709 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] discards 37e8e2c4f5 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] discards 50b18e17b3 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] discards a29faa8cea 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] discards 65af398287 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] discards 2c9e6375c6 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] discards b222dffdeb 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] discards a5372b1a44 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] discards 03a5dd0a9a 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] discards 71e5141ec7 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] discards 4efbecda3a 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits discards 999ccf2507 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] discards 66427323b5 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] discards 450b703ba8 408: onsuccess: #2662: 1: Success after linux: 11 commits discards ec0f5879b3 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards dbecf334a2 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards 0c70d8ed2a 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards abbaa1f75f 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards d2c1f1f79e 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards 0cf628458a 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards a1f3fab548 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards 69938bba8b 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards a88a74b6f4 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards 3e6d5cefb6 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards 57b8ebba4c 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards e6ed4ea531 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards c4fded6f01 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards dd45ded5ee 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards d5b2a74b84 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards c6497a5b8b 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards 404ddc756d 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards f0aa267872 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards da66cd9cde 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards c7099c0fe7 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards 595a551358 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards 03bea870d3 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 74e0ec87fe 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 92d7e88064 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 979b6e802b 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 07886e0546 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards e5a4182125 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 9c33f4d4aa 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards b560bb8f6b 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 092de7159d 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards a693b88110 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 41f7d9c704 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 755cc89b25 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 7659483901 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 34c2bf2418 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 916f78a793 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards f70f85c26d 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 6317fb1b44 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 5d36e25e33 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards e33f175749 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 5cb71923ec 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 3ba529414a 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 39e11d8a67 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards bb1f9c1b07 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards a58cf3a7fb 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards a9d2231a21 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 8ec80cfe88 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 4418cb580d 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards ea982dd43f 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards d1104ffea5 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 9a1f6e3c9e 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 62bf46c2a1 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 4050e8bd03 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 61eb573f46 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards e26d1da236 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards d2e51fb382 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 1d5a2ef2ee 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 4206e391bc 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 88c6c1d0e6 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 8c0d75cb4f 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards ddabfae073 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards f9de04b75b 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards cb64606778 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 40e17c5345 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards a8bc4f1db2 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 0597c1735f 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 998976f679 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards baa8ff78ab 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards ab3d52df04 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards ed247b83ef 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 24efa76126 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards fd1f6b8e45 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards ac70dc67e6 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 9b591a8c3c 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 500c21e552 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards fe2be99ecc 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 0c54cb49fe 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 4cc332c981 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 0e4c1d5f6a 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new d135489834 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 2695a61bfa 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 15997a3125 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 6e41d83681 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 7e4322f797 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 15a8e88868 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 430a881a4a 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new b4d21d246d 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 72dfdb46c5 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new df353545c8 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 68f2d67cbf 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 0bd24838e4 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 18464aab62 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 4874501d7e 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new c29067815f 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 432a45f7a6 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new d4f19a6f52 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new ae2387660e 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 3d0087da9b 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new aebb7c7b04 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 5ae8d19b0d 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 2371bca21d 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 01b2517cc8 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 6ecdd9ae5b 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 79c09226da 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 4ee6cb864f 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 94be00917e 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 318e3f5d1b 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new f6e8a1d01c 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 8937eb9ae3 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new ea9b96e69f 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new a5078c342a 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new 3d76069f0e 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 9c6922e32d 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 1bd4ac6c3a 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 54c4a5b2f3 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 1e6e903909 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new ed61f608dd 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 33225c9592 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 8164be8783 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new dcfe948e17 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new a084cc22a5 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 75a249be18 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 800bc4aeab 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 4e3c34c1ba 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 8e12803b63 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 609d263902 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new b02e334a0e 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 7deb91a5dc 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new 59cc67d97e 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 21a849c84d 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new 61768b6d84 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 1e2ed0caca 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 2d6c4b2407 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new a0594dca83 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new 4191225df5 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 143e89a98f 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 2f388a7d74 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new 6b43e29572 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new 7daf085faf 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new 41d403cbd2 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new af514da724 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new e8122e0a2e 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new 0f9318d07a 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new 974f3770a0 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new cceed76721 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new bea442621c 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new 01f08931ce 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new 91b09e62ae 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new 72144c8c3a 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new 5fc92bd462 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new 7f03cc79f1 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new ccc9f07899 407: onsuccess: #2661: 1: Success after gcc: 7 commits new eb9eb23ea0 408: onsuccess: #2662: 1: Success after linux: 11 commits new fe52f9b350 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] new 16efba0969 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] new 8136c88a37 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits new ab9295686a 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] new cde8718ef8 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] new 0a6cffca81 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] new 9527bb06b7 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] new 77acc20588 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] new b3322907be 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] new 4c95549457 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] new 8a9e40a896 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] new f1f9520eb3 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] new ac159b6e99 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] new 69bec33a3c 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new f48dd26b0d 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 4a0d142713 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new 904b74e8ce 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] new b801afe60d 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new bca7f1dc08 427: onsuccess: #7: 1: Success after linux: 26 commits new 2c7fc21731 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: [...] new f7ee7b98f5 429: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] new 7b3b7a1abb 430: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] new b05d58df41 431: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 93d97af5b4 432: onsuccess: #12: 1: Success after binutils/gcc/linux/gdb [...] new e1ad36357e 433: onsuccess: #13: 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 (473e6169a5) \ 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 1812 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2828 -> 2836 bytes 03-build_abe-binutils/console.log.xz | Bin 31028 -> 31244 bytes 04-build_abe-stage1/console.log.xz | Bin 72120 -> 71556 bytes 06-build_abe-linux/console.log.xz | Bin 8496 -> 9020 bytes 07-build_abe-glibc/console.log.xz | Bin 243956 -> 244504 bytes 08-build_abe-stage2/console.log.xz | Bin 202644 -> 202024 bytes 09-build_abe-gdb/console.log.xz | Bin 38972 -> 39060 bytes 10-build_abe-qemu/console.log.xz | Bin 32660 -> 32248 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3816 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3468 -> 3036 bytes 13-check_regression/console.log.xz | Bin 7860 -> 9020 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 91 +++++---- 13-check_regression/results.compare | 56 ++---- 13-check_regression/results.compare2 | 314 ++++++++++++++++---------------- 13-check_regression/results.regressions | 41 +++++ 14-update_baseline/console.log | 40 ++-- 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 | 93 +++++----- mail/mail-subject.txt | 2 +- manifest.sh | 48 ++--- results | 41 +++++ sumfiles/g++.log.xz | Bin 3394644 -> 3416492 bytes sumfiles/g++.sum | 105 +++++++++-- sumfiles/gcc.log.xz | Bin 2998656 -> 3012704 bytes sumfiles/gcc.sum | 30 +-- sumfiles/gfortran.log.xz | Bin 1039120 -> 1038568 bytes sumfiles/gfortran.sum | 5 +- sumfiles/libatomic.log.xz | Bin 2316 -> 2312 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217512 -> 217484 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2684 -> 2680 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 437088 -> 438780 bytes sumfiles/libstdc++.sum | 1 + 45 files changed, 520 insertions(+), 376 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