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 274c65212c8d 461: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] discards 96fdb61319c8 460: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards b3755bcdbd05 459: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards 3dd19d64d4c1 458: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] discards 8120154ef4f8 457: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] discards bade1e6b3ec6 456: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards 2f235f874c43 455: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards de62ecc5a21c 454: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards a339e9886464 453: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards e0353036c1ea 452: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards 9f9ccf567706 451: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards 73d0c829e66e 450: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards 53cfaff88dc7 449: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards 289662e6aef9 448: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards b9f8deb3f6a0 447: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards 07735c0b5934 446: onsuccess: #26: 1: Success after binutils/gcc/linux/g [...] discards 93221034fab8 445: onsuccess: #25: 1: Success after binutils/gcc/linux/g [...] discards a43b1844d680 444: onsuccess: #24: 1: Success after binutils/gcc/linux/g [...] discards cd1ba71c7e89 443: onsuccess: #23: 1: Success after binutils/gcc/linux/g [...] discards a3348a6566e9 442: onsuccess: #22: 1: Success after binutils/gcc/linux/g [...] discards 594a55e57c64 441: onsuccess: #21: 1: Success after binutils/gcc/linux/g [...] discards 9093671f83fc 440: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards a706e5175487 439: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards d1b6d31976f6 438: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 0c666a16a78c 437: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards 8f0abb803805 436: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 5ed90eaa7570 435: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards a2d07d86fd69 434: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 96dcc188d26f 433: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards 9955c6330061 432: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards cc6e7454bea8 431: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards 31625dde08b4 430: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards b44f55477f43 429: onsuccess: #9: 1: Success after binutils/gcc/linux/gl [...] discards 499c15f30464 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gd [...] discards 1c179ca1da31 427: onsuccess: #7: 1: Success after linux: 26 commits discards f230b74b25d8 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gd [...] discards eed58851472b 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gd [...] discards 31f4e32ab133 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu [...] discards a70dfd8fd97d 423: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 49faa19da98b 422: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] discards ff54737cbdb8 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: [...] discards 470e800e621a 420: onsuccess: #2675: 1: Success after binutils/gcc/linux [...] discards e532204ac669 419: onsuccess: #2674: 1: Success after binutils/gcc/linux [...] discards d70ab582f053 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: [...] discards c651a551779e 417: onsuccess: #2672: 1: Success after binutils/gcc/linux [...] discards d8fcf60c4c04 416: onsuccess: #2671: 1: Success after binutils/gcc/linux [...] discards 7de960adda6a 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/q [...] discards 460efbc1d4dd 414: onsuccess: #2669: 1: Success after binutils/gcc/linux [...] discards a29a2923d133 413: onsuccess: #2667: 1: Success after binutils/gcc/linux [...] discards 0faee8ea069a 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc [...] discards 81f548e5c8d6 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: [...] discards 67c028740e8b 410: onsuccess: #2664: 1: Success after binutils/gcc/linux [...] discards 3df2e5f01b83 409: onsuccess: #2663: 1: Success after binutils/gcc/linux [...] discards 591daf70b4b6 408: onsuccess: #2662: 1: Success after linux: 11 commits discards 0ff82d2cc9ef 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards b05eb38639e2 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards 552a92a82984 405: onsuccess: #2659: 1: Success after binutils/gcc/linux [...] discards 0cbd2c53d3c9 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc [...] discards 4a028076f107 403: onsuccess: #2657: 1: Success after binutils/gcc/linux [...] discards 48efad7b4432 402: onsuccess: #2656: 1: Success after binutils/gcc/linux [...] discards e5ae5572aa1d 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/q [...] discards 13e6a25743ca 400: onsuccess: #2652: 1: Success after binutils/gcc/linux [...] discards 0503eb65da6e 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc [...] discards dc058b2737af 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: [...] discards a2458bd2e309 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: [...] discards f66711732d6b 396: onsuccess: #2648: 1: Success after binutils/gcc/linux [...] discards f9c6e85b7c31 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc [...] discards 4c1ee113e273 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc [...] discards 9561ab53c2d0 393: onsuccess: #2645: 1: Success after binutils/gcc/linux [...] discards f396e601fb63 392: onsuccess: #2643: 1: Success after binutils/gcc/linux [...] discards f761420256c8 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: [...] discards b1c1421a6935 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: [...] discards 122e1d1751c2 389: onsuccess: #2640: 1: Success after binutils/gcc/linux [...] discards 6e1991b32446 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards 32f35217b762 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: [...] discards 29549028b88c 386: onsuccess: #2637: 1: Success after binutils/gcc/linux [...] discards 6a0ab0e5fa74 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: [...] discards bcb36228d516 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: [...] discards 27e083be9fdd 383: onsuccess: #2634: 1: Success after binutils/gcc/linux [...] discards 945afa235972 382: onsuccess: #2633: 1: Success after binutils/gcc/linux [...] discards cb8a2a27ebe0 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/q [...] discards 80ddaab99cc6 380: onsuccess: #2631: 1: Success after binutils/gcc/linux [...] discards 69e528f4b0ec 379: onsuccess: #2630: 1: Success after binutils/gcc/linux [...] discards 94c2adac806c 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc [...] discards 51ae39c2ccac 377: onsuccess: #2627: 1: Success after basepoints/gcc-13- [...] discards 67a376389d5f 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc [...] discards 72e072b66d47 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/q [...] discards e8d661e1659d 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: [...] discards 394d4f38c776 373: onsuccess: #2623: 1: Success after binutils/gcc/linux [...] discards 5aa82d960a94 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc [...] discards bef128e822a2 371: onsuccess: #2621: 1: Success after binutils/gcc/linux [...] discards 3f476285db10 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc [...] discards 189a66e93947 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/q [...] discards fa45438cc3e3 368: onsuccess: #2618: 1: Success after binutils/gcc/linux [...] discards 8dc3d3c654d5 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 10 [...] discards ae73f5f2a833 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17 [...] discards bf09c9d58d0e 365: onsuccess: #2615: 1: Success after binutils/gcc/linux [...] discards 6d6327da2273 364: onsuccess: #2614: 1: Success after binutils/gcc/linux [...] discards 253877f68b77 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/q [...] discards 282528bd7673 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: [...] discards 74c5aff19939 361: onsuccess: #2611: 1: Success after binutils/gcc/linux [...] new e552015d3659 361: onsuccess: #2611: 1: Success after binutils/gcc/linux [...] new d2c19c046ebd 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: [...] new ccabc856b78c 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/q [...] new 54d2b9d195be 364: onsuccess: #2614: 1: Success after binutils/gcc/linux [...] new 7393e350bbdd 365: onsuccess: #2615: 1: Success after binutils/gcc/linux [...] new 5a7af67c3506 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17 [...] new fc05f6b40e77 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 10 [...] new 0c75903f2a1b 368: onsuccess: #2618: 1: Success after binutils/gcc/linux [...] new 720b7fc7dae5 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/q [...] new a4318f9bc892 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc [...] new f1757f588fe6 371: onsuccess: #2621: 1: Success after binutils/gcc/linux [...] new 3a5420fc59c5 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc [...] new edf839765e98 373: onsuccess: #2623: 1: Success after binutils/gcc/linux [...] new fb58995b25e6 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: [...] new 6aca343497c9 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/q [...] new 3f170a09633a 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc [...] new 62b022f6b823 377: onsuccess: #2627: 1: Success after basepoints/gcc-13- [...] new 0ae9a8b970de 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc [...] new dab822392df5 379: onsuccess: #2630: 1: Success after binutils/gcc/linux [...] new 80b3b8c68c1c 380: onsuccess: #2631: 1: Success after binutils/gcc/linux [...] new 344848f49a09 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/q [...] new bae3bf5face5 382: onsuccess: #2633: 1: Success after binutils/gcc/linux [...] new b8f9776bd4b2 383: onsuccess: #2634: 1: Success after binutils/gcc/linux [...] new 73ad7d9161eb 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: [...] new f871684221d8 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: [...] new 262e48020f76 386: onsuccess: #2637: 1: Success after binutils/gcc/linux [...] new cc68a7c8888f 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: [...] new dbd6c5224daf 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new b57afe1d93f0 389: onsuccess: #2640: 1: Success after binutils/gcc/linux [...] new 87efbc738849 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: [...] new 43584f42755a 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: [...] new 40303c8f94a6 392: onsuccess: #2643: 1: Success after binutils/gcc/linux [...] new d33d40510a2f 393: onsuccess: #2645: 1: Success after binutils/gcc/linux [...] new e2b3ad19cdc0 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc [...] new 44c897bcb75a 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc [...] new 7a5c2a7a0dd1 396: onsuccess: #2648: 1: Success after binutils/gcc/linux [...] new 69eb237940c5 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: [...] new a20941717ea3 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: [...] new 3617048dc972 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc [...] new 808470c58333 400: onsuccess: #2652: 1: Success after binutils/gcc/linux [...] new 2498067643ea 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/q [...] new f7376bf5581e 402: onsuccess: #2656: 1: Success after binutils/gcc/linux [...] new 56ea061f31c6 403: onsuccess: #2657: 1: Success after binutils/gcc/linux [...] new 1a4deb0dca0e 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc [...] new ce18abeb1f83 405: onsuccess: #2659: 1: Success after binutils/gcc/linux [...] new 916180229ea6 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new 61daa4fcca96 407: onsuccess: #2661: 1: Success after gcc: 7 commits new f2a0d9c95ec1 408: onsuccess: #2662: 1: Success after linux: 11 commits new 97749bb19854 409: onsuccess: #2663: 1: Success after binutils/gcc/linux [...] new b03a09985323 410: onsuccess: #2664: 1: Success after binutils/gcc/linux [...] new 32d564186150 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: [...] new a75124e66d83 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc [...] new be918c56aebe 413: onsuccess: #2667: 1: Success after binutils/gcc/linux [...] new 2387d83399bb 414: onsuccess: #2669: 1: Success after binutils/gcc/linux [...] new cf6cf92f7fd3 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/q [...] new f568236b5bd1 416: onsuccess: #2671: 1: Success after binutils/gcc/linux [...] new da221df6b303 417: onsuccess: #2672: 1: Success after binutils/gcc/linux [...] new 2d5b833afe59 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: [...] new f17b3058bd37 419: onsuccess: #2674: 1: Success after binutils/gcc/linux [...] new 4446a91f3dca 420: onsuccess: #2675: 1: Success after binutils/gcc/linux [...] new 6eb7b3592770 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: [...] new 1a326fa2785b 422: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] new 13894bec6c37 423: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new 50d9823a97bb 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu [...] new 3b8b193380da 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gd [...] new feb6e73613d7 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gd [...] new 44f1908f0f95 427: onsuccess: #7: 1: Success after linux: 26 commits new ecf94ed3fab3 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gd [...] new 330d12b72975 429: onsuccess: #9: 1: Success after binutils/gcc/linux/gl [...] new e2163f99914d 430: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new ccbc33ae308a 431: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new 007e84bcc9cc 432: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new a003ffbb3d1b 433: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new cddc119b26d3 434: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 286a809d03cf 435: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new 97cf013970f9 436: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 235180e8bdf4 437: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 4f81103bd698 438: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 9ddf1b7902a4 439: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 33ce355f115d 440: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new bfa36658c9bf 441: onsuccess: #21: 1: Success after binutils/gcc/linux/g [...] new c4f2d885aaf1 442: onsuccess: #22: 1: Success after binutils/gcc/linux/g [...] new 90a5bb936f01 443: onsuccess: #23: 1: Success after binutils/gcc/linux/g [...] new 8eb1c17cda1d 444: onsuccess: #24: 1: Success after binutils/gcc/linux/g [...] new 7d6d7090f21f 445: onsuccess: #25: 1: Success after binutils/gcc/linux/g [...] new c9a5fed0fd63 446: onsuccess: #26: 1: Success after binutils/gcc/linux/g [...] new 45d5dd1e7d44 447: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new add21554d60c 448: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new 43b91e93bdcc 449: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new a9f58468ed4a 450: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new acf21b7048f4 451: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new 581f85aefa8f 452: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new bce5b7078e5c 453: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new 5e233fe05813 454: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new 421be7375660 455: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new df8c718786a9 456: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new 073e2bdf68b5 457: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] new ff9681f0416c 458: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] new 4161e76c8cdd 459: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new 972d2450bb53 460: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new 3f6831ff2870 461: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] new 4f0903309080 462: onsuccess: #43: 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 (274c65212c8d) \ 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 2108 -> 2124 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2552 bytes 03-build_abe-binutils/console.log.xz | Bin 27316 -> 27936 bytes 04-build_abe-stage1/console.log.xz | Bin 70740 -> 71560 bytes 06-build_abe-linux/console.log.xz | Bin 8524 -> 8736 bytes 07-build_abe-glibc/console.log.xz | Bin 241076 -> 240468 bytes 08-build_abe-stage2/console.log.xz | Bin 201016 -> 202268 bytes 09-build_abe-gdb/console.log.xz | Bin 34912 -> 35500 bytes 10-build_abe-qemu/console.log.xz | Bin 31980 -> 32484 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3848 bytes 12-build_abe-check_gcc/console.log.xz | Bin 6184 -> 6752 bytes 13-check_regression/console.log.xz | Bin 7000 -> 5696 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 36 - 13-check_regression/results.compare | 68 +- 13-check_regression/results.compare2 | 162 +- 13-check_regression/results.regressions | 74 - 14-update_baseline/console.log | 74 +- 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 | 49 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 46 +- manifest.sh | 38 +- results | 74 - sumfiles/g++.log.sep.xz | Bin 198828 -> 219204 bytes sumfiles/g++.log.xz | Bin 3406104 -> 3406756 bytes sumfiles/g++.sum | 47 +- sumfiles/g++.sum.sep | 7244 +++++++-------- sumfiles/gcc.log.sep.xz | Bin 110480 -> 147120 bytes sumfiles/gcc.log.xz | Bin 3038324 -> 3035136 bytes sumfiles/gcc.sum | 24 +- sumfiles/gcc.sum.sep | 14535 ++++++++++++++---------------- sumfiles/gfortran.log.sep.xz | Bin 16360 -> 164264 bytes sumfiles/gfortran.log.xz | Bin 1043864 -> 1046096 bytes sumfiles/gfortran.sum | 2 +- sumfiles/gfortran.sum.sep | 5346 ++++------- sumfiles/libatomic.log.xz | Bin 2316 -> 2316 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217156 -> 217204 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2680 -> 2680 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 14724 -> 25220 bytes sumfiles/libstdc++.log.xz | Bin 439828 -> 432976 bytes sumfiles/libstdc++.sum.sep | 1036 ++- 49 files changed, 12751 insertions(+), 16123 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