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 4fa65b5ca0 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards 8eda40984e 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards ea6cf69318 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards 03587c7525 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards 943afc2f9b 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards ef48131784 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards 5d7a12c1ab 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards 10e9e100be 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards caf2679cc2 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards 4d1e854066 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards bb63409c1d 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards 72c957acef 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards bf38a51cb7 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards 5987e19d8a 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 07f3acb39c 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards d72fada897 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards aefbf6f661 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards a915c8c1c9 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 1ab31d3386 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards e473d117d4 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards ca55e605f5 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 84433f1953 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 627e110931 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 14962dc62f 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards a0972eaa33 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards d808786bac 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 49355bd33a 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 1adc9d2d31 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards ad81adb0d1 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 41b4fa0a66 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards bb93c37655 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 93f6a5d55e 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 08bf75641b 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards a0eccb1e2e 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 787c178969 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards e0347219a2 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 26f38be945 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards c97b6acd53 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 00fd8d3574 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards ef590169b5 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards ce9f77e8ab 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 0d769c30fa 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 3092a0116e 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards e633cb381c 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards eb4ca3c419 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards ceeba70421 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 72053d3999 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 0b7af02ee8 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards a4ba67d08b 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 3cc1b3ce19 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards d9b02418ed 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards b57b92d735 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 7005ab3d37 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 42a4147555 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 4f0c52f0e5 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 9060e92411 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 895ab8e445 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 0f0803af00 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 3615186f7f 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 2096021a21 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 13fe2b2a5e 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards df730e39d7 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 9a208e9207 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards ae9e9e8019 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 8c8a96318a 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 8216cdd2d8 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 0f0f270235 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 702cdb346c 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards f183fa6fb1 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 49394b127a 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 2010eabca0 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 11bf4a4bae 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards dafbfb21a3 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 9d52ab128b 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 2e20b1c7d5 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 39f246c4f4 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards d942fc5fc1 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards c470b14cbf 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards c8143f39c6 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 8942763e87 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 167ecce2be 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 149fba87c4 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 3c32f121c5 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 8cdb55eba5 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 1c5e36f0fb 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards e914c1de20 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 3ac6d90fc3 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards caa6f75db3 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards d80a533d19 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 177649b73e 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 9b38d215cc 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 897299628b 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards b3da725283 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards a1eceb91b2 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 44dea4c5ec 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 2be0dbd399 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards ee1c76d978 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards abc17db555 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 4359fa3ac1 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards dfce66f4e4 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards eceeaf79a6 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 6be1d38c3c 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 4676461b58 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new c7dd70ae48 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new b2b9ee9b3d 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 28a343891d 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new ce758c04c9 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new aac78a15c3 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new ee3d09cc56 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new aa0f9666b0 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 05de8c03b1 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new d1e8ff7fe1 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 272ae35423 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new c3e5ba2877 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 216fd0f4fb 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new cfc2fbff99 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 83c7391f2b 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new a3c1a2a647 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 84db30bfe2 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 25a7042260 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new d7f43fdf08 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 835130a2cf 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new d4e91f31b7 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new eec7bb47d1 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new e959d1f5b4 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 4be654b87e 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 0903d4a33a 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new f0f24d31d8 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new ec52f082a9 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new a30764d842 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 3951b5a53a 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new b1302a9b71 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 31e97b6805 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new a347659317 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 82e787ff86 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new ffe08a8ad0 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new dc083dbe89 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new a0224d1d01 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 1996f02813 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new b56f931e75 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 896290132f 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new fec87f7d6e 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 155b5798b4 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new a0c4b1cd53 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 2ba900915d 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 7e4624c539 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 69f9404910 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 4751e83642 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 82f9434b92 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new f6e73c05ca 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new bdfc9872ce 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new b4a080873b 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new b10feba84a 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 995df5a574 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 1d7a7aa931 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new acd1477bda 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 8eaddf85f9 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new f3b934e3bc 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 4f0914697d 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 86e24cd5eb 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 2f21f34a86 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 278990ae25 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new b143ee2cb1 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new f5aa2749de 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 4fe2433fc5 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new 181a59a8c5 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 76d7bff09e 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new de9171f195 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new e2d3a0db45 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 02906d8a8c 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 2f9332f7f8 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 3476d0125e 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 5b25be6a72 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 470f99a4b8 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new e2da2297ba 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new f21426991c 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new fdc0bb7c62 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 0afcbcf17c 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new df456bd174 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 23f6268d3d 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 499e16e85f 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 3661e549a9 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new 3456e83d74 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 9d56316034 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new 65afa38cae 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 89d255433e 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 5e42dfaaf9 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new 82d4027f57 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new b5157e0f28 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 56d995ccf8 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 63be9e63b6 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new bcbad0e032 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new d4535b3a1b 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new 09877f171b 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new eb55425e5f 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new a25c4719af 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new 2e6b4365e7 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new 78c9fb6573 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new 6517bd99ea 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new a873b9b0ce 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new a120e06852 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new d4029bb72d 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new 056f5a13fb 404: onsuccess: #2658: 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 (4fa65b5ca0) \ 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 -> 1812 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31040 -> 31044 bytes 04-build_abe-stage1/console.log.xz | Bin 70768 -> 71108 bytes 06-build_abe-linux/console.log.xz | Bin 9040 -> 9040 bytes 07-build_abe-glibc/console.log.xz | Bin 244184 -> 244124 bytes 08-build_abe-stage2/console.log.xz | Bin 202564 -> 202460 bytes 09-build_abe-gdb/console.log.xz | Bin 38820 -> 38848 bytes 10-build_abe-qemu/console.log.xz | Bin 31828 -> 32248 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2740 -> 3104 bytes 13-check_regression/console.log.xz | Bin 5996 -> 6452 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 19 +++++++++ 13-check_regression/mail-body.txt | 39 ++++++++++++++++++ 13-check_regression/results.compare | 34 ++++++++++++---- 13-check_regression/results.compare2 | 56 ++++++++++++++++++++------ 13-check_regression/results.regressions | 39 ++++++++++++++++++ 14-update_baseline/console.log | 68 ++++++++++++++++---------------- 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 | 41 ++++++++++++++++++- mail/mail-subject.txt | 2 +- manifest.sh | 38 +++++++++--------- results | 39 ++++++++++++++++++ sumfiles/g++.log.xz | Bin 3389664 -> 3390124 bytes sumfiles/gcc.log.xz | Bin 3020540 -> 3029792 bytes sumfiles/gcc.sum | 37 +++++++++-------- sumfiles/gfortran.log.xz | Bin 1033552 -> 1040904 bytes sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217596 -> 217620 bytes sumfiles/libgomp.sum | 7 ++-- sumfiles/libitm.log.xz | Bin 2660 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 428988 -> 434552 bytes sumfiles/libstdc++.sum | 49 +++++++++++++++++------ 41 files changed, 371 insertions(+), 114 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