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 3879d3d3f9 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] discards e417387799 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits discards bb7499aa62 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] discards e4689973c7 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] discards a4ed1d8c1b 408: onsuccess: #2662: 1: Success after linux: 11 commits discards 195c553da5 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards 23db05bd37 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards 3c186e7cf4 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards 774a612cbf 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards df9f559f3a 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards 82d91e190c 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards eedbcfe4fd 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards 3eff21f5dd 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards 4ee08d303f 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards 936b49f472 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards 32e16f7a9a 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards 9c25718b71 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards a750d09739 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards c79fae6535 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards 3a50fab05e 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards acf23e3b2a 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards d35fd0079b 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards 99ca9df7e4 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards c1f26eb1ec 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards b86770fa22 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards 28c5eaa9c5 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards 7527795b8e 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards a85a1fc1f1 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards ee374d380c 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 16b62b1d03 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 4bb7373ee8 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 30171e8127 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards fbb3e0b89f 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards c5b438f9e5 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 0d3132791a 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 665d970f27 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards a91e1154d6 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards d93fa33db0 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 172caf9c76 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards e3114ea725 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards a7d191d55e 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 1f6bc5532a 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards ebbd3e6d56 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 0167c5aa95 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 4c38790af0 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards c689893f9b 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 32e07bf7a9 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 349ab79488 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 27f57f5821 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 459c4cd6ce 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 3ac3face3c 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 6cfbf95396 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards e02aa90fcc 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards ee8d70ca94 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 68d2608e0e 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards d3c78271c3 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 72abc47fbb 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 9a0ec30bfa 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 8cee6bbeb1 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards b9c5d807f0 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 04280510a5 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 07e21989d0 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards c8edea2b32 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 2bc8858088 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 5ef2ecdc06 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 52ab28ffec 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 55e9a7f607 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 82ef06744b 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 21300cad80 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards b943077968 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 65e6e41a04 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards eb088f1eb3 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 0eeef60100 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 13f87d5ec0 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 59f8cf07fb 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards ac532dd77f 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 736d20bd1e 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards c0f398cc9c 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 4719c0bca8 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 63ad2c3f79 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 03f5d06ea0 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards d7b0460839 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 886e3d0e16 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 571a3e61f5 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 41b4b892e1 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 4c35596a58 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards ee60894e3e 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards a7249266b3 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 5ff32a09a0 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards e2011df7e2 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 8074fc70c2 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 8de287cc02 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 4e0fbae8f5 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards cf276e66ae 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards e239d91518 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 68632f6b97 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 8c27455dbe 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 24af73460f 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 1bd637b7a6 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards f24356cd31 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 25f93fa1f0 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new ded52edbb1 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new ef94409cb3 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new dd3c3dd51c 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 03bf01ec9b 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 7b7f9b0383 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new c8cddbfc21 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new ca0e4d0eec 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 80ff7a3e7f 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 21b8d72fc0 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 16fd082c38 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 422c69f492 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 6c54f3744f 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 403db35f5f 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 6ce2365668 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 864dfb70c6 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new a6a45047e0 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new bbf939157e 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 7cd32c3584 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 02e767736e 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new ec0c29fae4 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new da9130d608 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new f4604aaebc 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 07cff26065 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new c8f9bf70bb 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new e5bff8b410 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 07802b07bb 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 0153e6ea5c 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new bef11c8508 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 26d2c7bf44 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 60bb3951ac 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 912fc58eb9 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 47225e7121 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 825ceb9b1d 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 5aa69f24c9 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 3621f951d2 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 7f8b27a25b 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 2a89330c67 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new cf2ee5f112 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new e3a585bb01 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new c770466034 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 927f4ba8f3 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new ae1e330745 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new b86a9488af 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 5506659996 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new c46594830a 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new aa509c07ed 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new a7c2c393dc 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 5428e05e6f 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 8c320a9c15 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new e5c358fbb7 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 8f156a1cee 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 0d04b35744 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 67412bfcc3 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 396a4389b9 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 4b31d0e369 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new b29e54c71a 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new f5f2c17f41 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 5ae3f4e574 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new aa9dee9448 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 05ffd41323 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new a2ad273545 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new a1b1782be0 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 15481db8c8 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 68806fe784 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new ba2f6a5be6 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new f5dc1bf985 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new dd49b814e4 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 38deaac385 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new dcaecc5398 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 5739c33e6f 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new f3563f6f0c 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 393000c881 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new fdc2fa2d0f 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 4ca9be20e9 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new abc0b5d074 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 6ce7c53288 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 18c9620482 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new 9f52377ca3 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new ca0ffbcecf 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new e6174c4459 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 20f9a61122 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new 841c0d6f78 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new ae36b1b614 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new 61562ae472 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new 3de90a8866 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new fee311f6fc 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new db2a6ebfe8 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new b52e23b5ae 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new a9184d8736 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new 466f790fbd 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new 7035d111f8 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new 4d071fc879 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new f55842dc44 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new 5f4996322d 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new 67cae52acd 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new 97df60b3eb 407: onsuccess: #2661: 1: Success after gcc: 7 commits new 1306d80083 408: onsuccess: #2662: 1: Success after linux: 11 commits new 69004a422b 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] new 772d3f262a 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] new d6b3d2bb9c 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits new eb439798a5 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] new 15fed7625f 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/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 (3879d3d3f9) \ 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 1816 -> 1824 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 31300 -> 31008 bytes 04-build_abe-stage1/console.log.xz | Bin 70716 -> 70592 bytes 06-build_abe-linux/console.log.xz | Bin 8316 -> 8628 bytes 07-build_abe-glibc/console.log.xz | Bin 243900 -> 243848 bytes 08-build_abe-stage2/console.log.xz | Bin 202336 -> 202084 bytes 09-build_abe-gdb/console.log.xz | Bin 38796 -> 38744 bytes 10-build_abe-qemu/console.log.xz | Bin 32076 -> 31876 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3836 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2708 -> 2576 bytes 13-check_regression/console.log.xz | Bin 8004 -> 7480 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 12 +++ 13-check_regression/mail-body.txt | 70 +++++------- 13-check_regression/results.compare | 33 ++---- 13-check_regression/results.compare2 | 181 +++++++++++++++----------------- 13-check_regression/results.regressions | 32 ++++++ 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 72 +++++-------- mail/mail-subject.txt | 2 +- manifest.sh | 42 ++++---- results | 32 ++++++ sumfiles/g++.log.xz | Bin 3391756 -> 3403324 bytes sumfiles/g++.sum | 14 ++- sumfiles/gcc.log.xz | Bin 3024232 -> 3023692 bytes sumfiles/gcc.sum | 6 +- sumfiles/gfortran.log.xz | Bin 1037580 -> 1044192 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217612 -> 217692 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434176 -> 435424 bytes sumfiles/libstdc++.sum | 100 ++++++++++-------- 44 files changed, 360 insertions(+), 323 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