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 4f0903309080 462: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] discards 3f6831ff2870 461: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] discards 972d2450bb53 460: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards 4161e76c8cdd 459: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards ff9681f0416c 458: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] discards 073e2bdf68b5 457: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] discards df8c718786a9 456: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards 421be7375660 455: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards 5e233fe05813 454: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards bce5b7078e5c 453: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards 581f85aefa8f 452: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards acf21b7048f4 451: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards a9f58468ed4a 450: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards 43b91e93bdcc 449: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards add21554d60c 448: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards 45d5dd1e7d44 447: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards c9a5fed0fd63 446: onsuccess: #26: 1: Success after binutils/gcc/linux/g [...] discards 7d6d7090f21f 445: onsuccess: #25: 1: Success after binutils/gcc/linux/g [...] discards 8eb1c17cda1d 444: onsuccess: #24: 1: Success after binutils/gcc/linux/g [...] discards 90a5bb936f01 443: onsuccess: #23: 1: Success after binutils/gcc/linux/g [...] discards c4f2d885aaf1 442: onsuccess: #22: 1: Success after binutils/gcc/linux/g [...] discards bfa36658c9bf 441: onsuccess: #21: 1: Success after binutils/gcc/linux/g [...] discards 33ce355f115d 440: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards 9ddf1b7902a4 439: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards 4f81103bd698 438: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 235180e8bdf4 437: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards 97cf013970f9 436: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 286a809d03cf 435: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards cddc119b26d3 434: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards a003ffbb3d1b 433: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards 007e84bcc9cc 432: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards ccbc33ae308a 431: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards e2163f99914d 430: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 330d12b72975 429: onsuccess: #9: 1: Success after binutils/gcc/linux/gl [...] discards ecf94ed3fab3 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gd [...] discards 44f1908f0f95 427: onsuccess: #7: 1: Success after linux: 26 commits discards feb6e73613d7 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gd [...] discards 3b8b193380da 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gd [...] discards 50d9823a97bb 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu [...] discards 13894bec6c37 423: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 1a326fa2785b 422: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] discards 6eb7b3592770 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: [...] discards 4446a91f3dca 420: onsuccess: #2675: 1: Success after binutils/gcc/linux [...] discards f17b3058bd37 419: onsuccess: #2674: 1: Success after binutils/gcc/linux [...] discards 2d5b833afe59 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: [...] discards da221df6b303 417: onsuccess: #2672: 1: Success after binutils/gcc/linux [...] discards f568236b5bd1 416: onsuccess: #2671: 1: Success after binutils/gcc/linux [...] discards cf6cf92f7fd3 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/q [...] discards 2387d83399bb 414: onsuccess: #2669: 1: Success after binutils/gcc/linux [...] discards be918c56aebe 413: onsuccess: #2667: 1: Success after binutils/gcc/linux [...] discards a75124e66d83 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc [...] discards 32d564186150 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: [...] discards b03a09985323 410: onsuccess: #2664: 1: Success after binutils/gcc/linux [...] discards 97749bb19854 409: onsuccess: #2663: 1: Success after binutils/gcc/linux [...] discards f2a0d9c95ec1 408: onsuccess: #2662: 1: Success after linux: 11 commits discards 61daa4fcca96 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards 916180229ea6 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards ce18abeb1f83 405: onsuccess: #2659: 1: Success after binutils/gcc/linux [...] discards 1a4deb0dca0e 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc [...] discards 56ea061f31c6 403: onsuccess: #2657: 1: Success after binutils/gcc/linux [...] discards f7376bf5581e 402: onsuccess: #2656: 1: Success after binutils/gcc/linux [...] discards 2498067643ea 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/q [...] discards 808470c58333 400: onsuccess: #2652: 1: Success after binutils/gcc/linux [...] discards 3617048dc972 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc [...] discards a20941717ea3 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: [...] discards 69eb237940c5 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: [...] discards 7a5c2a7a0dd1 396: onsuccess: #2648: 1: Success after binutils/gcc/linux [...] discards 44c897bcb75a 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc [...] discards e2b3ad19cdc0 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc [...] discards d33d40510a2f 393: onsuccess: #2645: 1: Success after binutils/gcc/linux [...] discards 40303c8f94a6 392: onsuccess: #2643: 1: Success after binutils/gcc/linux [...] discards 43584f42755a 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: [...] discards 87efbc738849 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: [...] discards b57afe1d93f0 389: onsuccess: #2640: 1: Success after binutils/gcc/linux [...] discards dbd6c5224daf 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards cc68a7c8888f 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: [...] discards 262e48020f76 386: onsuccess: #2637: 1: Success after binutils/gcc/linux [...] discards f871684221d8 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: [...] discards 73ad7d9161eb 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: [...] discards b8f9776bd4b2 383: onsuccess: #2634: 1: Success after binutils/gcc/linux [...] discards bae3bf5face5 382: onsuccess: #2633: 1: Success after binutils/gcc/linux [...] discards 344848f49a09 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/q [...] discards 80b3b8c68c1c 380: onsuccess: #2631: 1: Success after binutils/gcc/linux [...] discards dab822392df5 379: onsuccess: #2630: 1: Success after binutils/gcc/linux [...] discards 0ae9a8b970de 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc [...] discards 62b022f6b823 377: onsuccess: #2627: 1: Success after basepoints/gcc-13- [...] discards 3f170a09633a 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc [...] discards 6aca343497c9 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/q [...] discards fb58995b25e6 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: [...] discards edf839765e98 373: onsuccess: #2623: 1: Success after binutils/gcc/linux [...] discards 3a5420fc59c5 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc [...] discards f1757f588fe6 371: onsuccess: #2621: 1: Success after binutils/gcc/linux [...] discards a4318f9bc892 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc [...] discards 720b7fc7dae5 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/q [...] discards 0c75903f2a1b 368: onsuccess: #2618: 1: Success after binutils/gcc/linux [...] discards fc05f6b40e77 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 10 [...] discards 5a7af67c3506 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17 [...] discards 7393e350bbdd 365: onsuccess: #2615: 1: Success after binutils/gcc/linux [...] discards 54d2b9d195be 364: onsuccess: #2614: 1: Success after binutils/gcc/linux [...] discards ccabc856b78c 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/q [...] discards d2c19c046ebd 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: [...] new 8086be5ae301 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: [...] new 1e35d56487f2 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/q [...] new 92d546c5c250 364: onsuccess: #2614: 1: Success after binutils/gcc/linux [...] new 2d2b4898786c 365: onsuccess: #2615: 1: Success after binutils/gcc/linux [...] new 422431a59ef0 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17 [...] new 8146da76a1cc 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 10 [...] new ba5106eacdbc 368: onsuccess: #2618: 1: Success after binutils/gcc/linux [...] new 0909f5fd9615 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/q [...] new 4e510d8b91ff 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc [...] new 0be66bb91d1a 371: onsuccess: #2621: 1: Success after binutils/gcc/linux [...] new e754e3325b00 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc [...] new 6c05cbbe8bdc 373: onsuccess: #2623: 1: Success after binutils/gcc/linux [...] new 0b619f15897a 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: [...] new 75d961de994a 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/q [...] new 67c691d760f1 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc [...] new e81d7b954c8b 377: onsuccess: #2627: 1: Success after basepoints/gcc-13- [...] new 96a7f7af7f5f 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc [...] new 41c32192b146 379: onsuccess: #2630: 1: Success after binutils/gcc/linux [...] new aee0f5fc95d9 380: onsuccess: #2631: 1: Success after binutils/gcc/linux [...] new 654de2c1a1cf 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/q [...] new ecb435926bf6 382: onsuccess: #2633: 1: Success after binutils/gcc/linux [...] new 98d06db41deb 383: onsuccess: #2634: 1: Success after binutils/gcc/linux [...] new 6d4eb0534fe8 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: [...] new 3c0293bc00ac 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: [...] new 5c48c8acb848 386: onsuccess: #2637: 1: Success after binutils/gcc/linux [...] new e4276110543d 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: [...] new f9bf255338d5 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new 1ade408fe347 389: onsuccess: #2640: 1: Success after binutils/gcc/linux [...] new d85886ae5788 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: [...] new c7a038d9c670 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: [...] new dce9a75b5186 392: onsuccess: #2643: 1: Success after binutils/gcc/linux [...] new 671cbbcb6048 393: onsuccess: #2645: 1: Success after binutils/gcc/linux [...] new 75e4e20e8e8c 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc [...] new ac0eaba0c9d5 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc [...] new 5e8192b10011 396: onsuccess: #2648: 1: Success after binutils/gcc/linux [...] new b25d3c38041c 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: [...] new 0be6a2d02542 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: [...] new b23aa26801a0 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc [...] new 88c54b7576b0 400: onsuccess: #2652: 1: Success after binutils/gcc/linux [...] new 9bea798dc76e 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/q [...] new cd5a4a750970 402: onsuccess: #2656: 1: Success after binutils/gcc/linux [...] new 646b7b044c3b 403: onsuccess: #2657: 1: Success after binutils/gcc/linux [...] new 57c1f5ec40f2 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc [...] new 3aea70c01ad8 405: onsuccess: #2659: 1: Success after binutils/gcc/linux [...] new fcda9a2d2302 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new af3507171235 407: onsuccess: #2661: 1: Success after gcc: 7 commits new 77adaa262f26 408: onsuccess: #2662: 1: Success after linux: 11 commits new ab63964411c7 409: onsuccess: #2663: 1: Success after binutils/gcc/linux [...] new 3ee81f614cd7 410: onsuccess: #2664: 1: Success after binutils/gcc/linux [...] new 4a003288b888 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: [...] new 0362de17d3bf 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc [...] new cba3adffa528 413: onsuccess: #2667: 1: Success after binutils/gcc/linux [...] new e382f8e90853 414: onsuccess: #2669: 1: Success after binutils/gcc/linux [...] new 3ccd964e215a 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/q [...] new a9212b726180 416: onsuccess: #2671: 1: Success after binutils/gcc/linux [...] new 6ee699323692 417: onsuccess: #2672: 1: Success after binutils/gcc/linux [...] new b67a8be1e97f 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: [...] new ceb9364cd7b6 419: onsuccess: #2674: 1: Success after binutils/gcc/linux [...] new 23ddc8441ec8 420: onsuccess: #2675: 1: Success after binutils/gcc/linux [...] new a9bc17a8564c 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: [...] new debd34493970 422: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] new d39a0b319f57 423: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new e81433468e0c 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu [...] new 7bea2b16dd16 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gd [...] new 226ede9661ec 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gd [...] new ad559c8b462b 427: onsuccess: #7: 1: Success after linux: 26 commits new 258518826168 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gd [...] new c30457922f72 429: onsuccess: #9: 1: Success after binutils/gcc/linux/gl [...] new 65155e2414fa 430: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new 5db7e51d4d66 431: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new 6908329c2701 432: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new a1b05e9f1203 433: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new 25f95498813b 434: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new ed1e1f4608de 435: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new d2bba31dff27 436: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new da32230651fa 437: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 9d57148b43ce 438: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new d7a7308d40db 439: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 7607ec5f3621 440: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new dcff45a10ebe 441: onsuccess: #21: 1: Success after binutils/gcc/linux/g [...] new 16fd87b9a5fb 442: onsuccess: #22: 1: Success after binutils/gcc/linux/g [...] new 88194b0756c8 443: onsuccess: #23: 1: Success after binutils/gcc/linux/g [...] new af021dc1dedc 444: onsuccess: #24: 1: Success after binutils/gcc/linux/g [...] new 1fac4a82b772 445: onsuccess: #25: 1: Success after binutils/gcc/linux/g [...] new f4fa4f1b8ed1 446: onsuccess: #26: 1: Success after binutils/gcc/linux/g [...] new 4760f45ab288 447: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new 5583231fde10 448: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new 71b2a0b207bb 449: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new de06a1160443 450: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new de568fa3dfe8 451: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new 7dccffb4fc29 452: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new 2e81c605f90f 453: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new 3b42784fc537 454: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new 18d300b03b83 455: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new e60b759bf134 456: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new ca25e1b2758d 457: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] new f556a103d51c 458: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] new d3a993125d0e 459: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new 722d4d7b7887 460: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new 50785573cc3c 461: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] new 5e4cb7831d0e 462: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] new aa376de8c96a 463: onsuccess: #44: 1: [TCWG CI] Success after binutils/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 (4f0903309080) \ 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 2124 -> 2100 bytes 02-prepare_abe/console.log.xz | Bin 2552 -> 2528 bytes 03-build_abe-binutils/console.log.xz | Bin 27936 -> 27300 bytes 04-build_abe-stage1/console.log.xz | Bin 71560 -> 71040 bytes 06-build_abe-linux/console.log.xz | Bin 8736 -> 8504 bytes 07-build_abe-glibc/console.log.xz | Bin 240468 -> 240644 bytes 08-build_abe-stage2/console.log.xz | Bin 202268 -> 201252 bytes 09-build_abe-gdb/console.log.xz | Bin 35500 -> 34884 bytes 10-build_abe-qemu/console.log.xz | Bin 32484 -> 32500 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3836 bytes 12-build_abe-check_gcc/console.log.xz | Bin 6752 -> 6232 bytes 13-check_regression/console.log.xz | Bin 5696 -> 5520 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 12 + 13-check_regression/results.compare | 28 +- 13-check_regression/results.compare2 | 114 +- 13-check_regression/results.regressions | 46 + 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 32 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 38 +- manifest.sh | 38 +- results | 46 + sumfiles/g++.log.sep.xz | Bin 219204 -> 184284 bytes sumfiles/g++.log.xz | Bin 3406756 -> 3402172 bytes sumfiles/g++.sum | 2 +- sumfiles/g++.sum.sep | 6456 +++++++----- sumfiles/gcc.log.sep.xz | Bin 147120 -> 129068 bytes sumfiles/gcc.log.xz | Bin 3035136 -> 3029564 bytes sumfiles/gcc.sum | 16 +- sumfiles/gcc.sum.sep | 16433 ++++++++++++++++++------------ sumfiles/gfortran.log.sep.xz | Bin 164264 -> 57536 bytes sumfiles/gfortran.log.xz | Bin 1046096 -> 1045840 bytes sumfiles/gfortran.sum | 2 +- sumfiles/gfortran.sum.sep | 5564 ++++++---- sumfiles/libatomic.log.xz | Bin 2316 -> 2316 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217204 -> 217224 bytes sumfiles/libgomp.sum | 8 +- sumfiles/libitm.log.xz | Bin 2680 -> 2676 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 25220 -> 12148 bytes sumfiles/libstdc++.log.xz | Bin 432976 -> 438136 bytes sumfiles/libstdc++.sum.sep | 928 +- 49 files changed, 17693 insertions(+), 12157 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