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 36a4e8a2bc 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards ec0284625d 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards d49babffbf 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards 136d453cde 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards 01e4fec750 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards 5d2ebd3d9a 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards 3324bcec01 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards 6e560ed475 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards 4c6a79223f 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards 054e796787 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 5c987c129e 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards 8198c7d578 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards bdf4cb24fc 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards 38620a34e8 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 97b95e301e 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards fcd02a0809 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 175859de38 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 880a87c07c 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards ef96c2f7ac 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 984d3abd5a 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards b0f21c4406 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 2aebafadf5 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards d96dea2b5e 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 3e9448cd69 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 9ce71fa571 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 10caeb01cb 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards d9a59f2fc1 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 1e7bfcdd6c 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 4078d2cab7 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 03a32f9756 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards bcd7c3e6cc 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 1cd8059c76 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards e87788d79d 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards fd28afb5cf 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 5610383ad7 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 9bcc56bd07 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 2a711a179a 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 1a8fae9133 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards ecbda21738 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards eb45fac52d 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards d7d795e477 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards f61c09efd2 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 358db94bc1 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards ff7c0bff39 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 371b508e55 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards f6615274ba 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards fdee99b3de 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards d6e5dd18ea 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 0566901e34 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 62dcfd1e8d 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards e9e83e7d28 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 95c1212440 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards d52a1cd7b3 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards d94e21dd08 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards fefaba2e35 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 20a3b5ffc2 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 4dce0426d5 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 8a913c7331 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 15d53578ea 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 3a50c80ab1 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 95c2fa8bbe 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 9d7e918fd3 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards b62a615e8c 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 9b3ad20b65 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 61fe2ed06e 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 766eebd72e 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 3216d3fc8f 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 4ff1800489 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards e8712570c8 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards a1b79245ef 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 5dfdcd4299 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 3110bac292 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 11fa69a179 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards eaf1f31318 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 55e9f2dcfb 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards e32e7b4258 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 8d224bab0e 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards f7021b4f94 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 458fe15179 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 581cbddfcf 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 487ecf9170 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards cf46e46cbb 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 34b35ae666 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 2dfd44be1a 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 22287ff669 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 9aaa370798 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards caeeea0814 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 94848b6ac8 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 0fa768fffe 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards d6762a2eaa 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 548d4adacd 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 044f5a6d6c 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 018a7f512b 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 4e35a0a146 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards ba01b1c6f8 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 95ec0ce8ff 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 7a6cd171f4 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards ca6ae5f3af 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 6d1f3f8998 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 18f718242e 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 88ee22c181 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 89d45222cf 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new b3af950b09 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new ec8db2ed33 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new ba509a0aea 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new b7426d8493 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 82581a8ad9 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 410c5b0a79 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 183fb2756b 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 41a514b4de 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 6e69c83fb4 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 6ead5b0b36 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 5fdfb14b0e 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 5cc620c9ec 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 6025b53554 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new a3b213c5df 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new db0bf588e1 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 2c7c443d8c 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new a079564b7e 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 6e38069455 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 292e5d1f76 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 30874ae96a 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new a5a7fad9fe 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new ff2db0c93b 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new ee0804fda5 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 12e1d18f3d 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 3aa9c88c45 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 374b1450fd 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 9e0d939a83 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new bf83de0d40 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 26a77d2666 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 08ed1a2924 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new f958afbdf6 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new afb23ab641 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new bc21a310c3 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 9b5657c042 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 20f9c0d521 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 327ab75d15 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 20c80aac8c 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 4413a7aa51 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 57bd68791f 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 70ba68e55e 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 2f1a1a6260 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 61567924d3 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 5f28add259 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new f83aadbf4c 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 42e726516a 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 1295660363 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new ed58bddbc2 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new a34d12de3d 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 5d83e629d7 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 2f82fadbdb 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 047ac1963e 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new ec1c07fda1 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new c2f88eedd5 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new c646ca9ec8 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new c47f2508cd 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new e3f8463003 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 50949b16eb 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 70b7425068 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 98da2862ab 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 78d8e557eb 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 6041a5aef1 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 0688d330a1 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 32e898ce4c 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 8d63608c5c 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 98fbe6fc0b 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 0edb13cd84 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 6ae903aba2 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new d8c7493374 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new e0a3f3ccd8 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 2a686722bb 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 8936368e56 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 362dd7062a 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 1344e35b2f 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new e917404bff 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 0df0fb916d 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 8dcdf4d605 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 143d7240ef 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 8e153cbb34 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 1f54a2a12f 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 4a5f413f57 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 003a46a308 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 4dcc73ede5 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 906b75fe53 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 6162f7439e 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new caf751f996 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 600ffecd09 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new 4374de3f2f 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 4f0c281a3f 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new f41bf4f9e7 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new 034bbee0d5 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new 551b5e2caa 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 0f68e86818 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 6056ea2da8 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new 959ec8d079 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new 723f389fb8 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new c16f7eb6fd 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new 27030e8dc0 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new d5f5d94183 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new 0def9affea 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new 57aa2c022a 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new 12b6fe4b07 400: onsuccess: #2652: 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 (36a4e8a2bc) \ 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 1808 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 32528 -> 31120 bytes 04-build_abe-stage1/console.log.xz | Bin 73576 -> 73488 bytes 06-build_abe-linux/console.log.xz | Bin 8604 -> 8516 bytes 07-build_abe-glibc/console.log.xz | Bin 244824 -> 244100 bytes 08-build_abe-stage2/console.log.xz | Bin 205272 -> 204988 bytes 09-build_abe-gdb/console.log.xz | Bin 39840 -> 38644 bytes 10-build_abe-qemu/console.log.xz | Bin 32848 -> 32488 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3956 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3036 -> 3576 bytes 13-check_regression/console.log.xz | Bin 7164 -> 6760 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 20 + 13-check_regression/mail-body.txt | 40 + 13-check_regression/results.compare | 39 +- 13-check_regression/results.compare2 | 93 +- 13-check_regression/results.regressions | 40 + 14-update_baseline/console.log | 68 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 42 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 40 + sumfiles/g++.log.xz | Bin 3406560 -> 3404084 bytes sumfiles/g++.sum | 4 +- sumfiles/gcc.log.xz | Bin 3024784 -> 3021872 bytes sumfiles/gcc.sum | 4438 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1032432 -> 1036028 bytes sumfiles/gfortran.sum | 11 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217628 -> 217656 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 429096 -> 430088 bytes sumfiles/libstdc++.sum | 34 +- 43 files changed, 2555 insertions(+), 2373 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