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 91f84f3ea7 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards da700b93b9 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] discards 7d91cdc513 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] discards 35f3f9b01b 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] discards 39fbcb505d 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] discards 2a3c7b5aa4 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] discards 8d972aed5b 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] discards c4fab9b818 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] discards 8a15fea837 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] discards 974a45815f 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] discards 1c0f971b49 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] discards 2df9886113 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits discards 7a12cc7519 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] discards bf972d6dca 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] discards d3ddb2245f 408: onsuccess: #2662: 1: Success after linux: 11 commits discards 9a232fcd6c 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards 166869255d 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards 4eec29cfcf 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards e80a4459bb 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards 766506dddb 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards be4bb5408e 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards 30089a18b3 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards 80be16c2ee 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards 31bc72e893 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards 966c19be5a 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards ff23c12391 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards 2917267ac4 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards fe4d18c745 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards 205f8c2079 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards 6716033bbb 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards 615e921cf1 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards 0c036a6c07 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards b67ae9839d 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 8d34d97e00 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards 1c0d59bd77 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards b1ad10ceb6 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards b7b2df4750 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 6d7e4ef183 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 143681b731 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 6c995bc975 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 372dcb6b9d 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 5fa9d008dd 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards df37681bc5 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards b8ac69755e 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 9013a1bd49 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards f2112d4bb2 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 0d8464a2ec 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 6ec9e631ab 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 36cf240a9c 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 02c1ffd864 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 79e95f0b67 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 426234ef57 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 46c96e2f15 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 328573083e 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards bb7e7e439e 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 856b4ea2cd 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 2b045c4145 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 058aba3cfe 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 20013d02ab 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 1d84bd2899 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards a28d276689 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards fd7bfaf46c 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 45a1388288 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 7d3fb62e2d 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 6d3d59c20f 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards d3042bf845 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 716e806c3e 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 2f4a5083c4 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 46ba08ba2d 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards b4b8325d9e 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards be40e5811f 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 09766ec37d 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 04ee183570 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards b650bc5f48 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards db8131f8db 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards ea415aa729 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards e8b80290c8 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 70afb6bf49 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards f6178d650b 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 9ce283c486 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards d90b04efc0 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 680ddef5af 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 8de157578f 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards c65387fa50 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards b6db5c5b09 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards d650fc1f1d 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards b20ecddada 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards ef3d973b5b 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 4490a1c0dc 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 5757bdfe2d 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards ea2ab843b6 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 31568ec480 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards bcf1763aa3 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 912d17d700 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards a0adbdc08b 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards f00ed4699a 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards e1db4b2bea 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards d7f9889c09 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards cfaf415d7d 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards a579f644bf 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 196421b199 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new b9e2b9d4ea 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new cfbd68f127 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new fa20d03c94 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new f2a103bb8c 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 336507aca6 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new c27ff240bb 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new e6bdd84595 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 4994bd79f9 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 60fbdb5d6a 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 60dfcad5b7 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 4b11f260a1 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 1dcf95ec62 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new f9067477b2 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 3334ab4b1c 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 64de7fd0c2 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 6e33869bfc 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new c2e8e36002 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new dcc0652a29 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new cfaa72e4ed 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 954bdfa55c 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 393be1347c 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 93b13c52c8 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 941e28bae8 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 703e545a89 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 9964649566 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new bdb7090beb 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new e7e61316f1 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 90c12ba3da 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 54fd19154a 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 503266f1c7 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 3817d71b09 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 35d846cecf 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 5660850f39 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 1e2629106f 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new dd51ed5746 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 763512c3ab 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new f8c3beff30 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new d5856351aa 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 20b131be91 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new b0ffe15e56 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 36387b1380 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 936b15a194 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 152c832cf2 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 8300fdd0d9 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 44fd02d617 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new 38e3ca5900 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 8ed7d78901 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 03f8d1e212 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 850fa35596 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 7cd413c9fa 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new afcbd9412b 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 5ebb63597e 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 01c42e0d54 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 683b94ea1b 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 2621c5f6b4 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 1849633438 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 4ba6995942 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 390f55dd78 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 696f0b491a 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 0a0b572678 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 77cd57896f 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 57f599e341 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new 37c7952159 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 0980a17a53 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new a784de5623 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new a3237481d3 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 7a34aff2fa 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new 77a07eda7f 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new c610c6cbab 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new f4aaf58d43 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new eab9133131 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new 07479fb00e 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new 06bba9b59f 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new 7714e1fbf1 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new 53bb1875e9 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new 7ec60414de 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new d25fae019b 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new f839ee4073 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new 9015a03360 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new b0db6dd9f9 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new 7c1d8a3eee 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new ffc9d743d2 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new 238cf5ea02 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new e6ecd3fb5a 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new 4e978b81d1 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new 1e5910a8ee 407: onsuccess: #2661: 1: Success after gcc: 7 commits new ab254c7ae1 408: onsuccess: #2662: 1: Success after linux: 11 commits new 0d043194dc 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] new 7616b46348 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] new b0ba5b81a7 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits new d101983982 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] new 0cb78d59d2 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] new ed735ba84c 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] new 9207bf2e10 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] new 1a88ae4a78 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] new 83faa3287b 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] new f69b4f9afc 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] new d348251507 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] new 408f4d978a 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] new 7d01797fe4 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] new b89846a51e 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new d9393fd5a6 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...]
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 (91f84f3ea7) \ 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 -> 1812 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 30964 -> 31100 bytes 04-build_abe-stage1/console.log.xz | Bin 70512 -> 71056 bytes 06-build_abe-linux/console.log.xz | Bin 9180 -> 9180 bytes 07-build_abe-glibc/console.log.xz | Bin 244340 -> 243964 bytes 08-build_abe-stage2/console.log.xz | Bin 201800 -> 202180 bytes 09-build_abe-gdb/console.log.xz | Bin 38544 -> 38644 bytes 10-build_abe-qemu/console.log.xz | Bin 31448 -> 31772 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3824 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2592 -> 2744 bytes 13-check_regression/console.log.xz | Bin 7940 -> 8204 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 7 -- 13-check_regression/mail-body.txt | 139 +++++-------------------------- 13-check_regression/results.compare | 54 ++++++------ 13-check_regression/results.compare2 | 139 ++++++++++++------------------- 13-check_regression/results.regressions | 45 ---------- 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 | 141 +++++--------------------------- mail/mail-subject.txt | 2 +- manifest.sh | 48 +++++------ results | 45 ---------- sumfiles/g++.log.xz | Bin 3392444 -> 3422708 bytes sumfiles/g++.sum | 11 ++- sumfiles/gcc.log.xz | Bin 3021676 -> 3020620 bytes sumfiles/gcc.sum | 48 ++++------- sumfiles/gfortran.log.xz | Bin 1041532 -> 1044040 bytes sumfiles/libatomic.log.xz | Bin 2312 -> 2312 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217404 -> 217388 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2680 -> 2684 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434620 -> 434196 bytes sumfiles/libstdc++.sum | 96 +++++++++------------- 44 files changed, 255 insertions(+), 607 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions