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 525de04ba5 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards f5863b532b 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 0030845b5a 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 5a078f8bbd 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards e1b5c70d18 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards e88b6a6bc0 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 3456a6b40a 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards adaa5b03a5 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards dba6e774a1 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 8677243f1a 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 22a081376b 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 0ef40c2d38 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards b0a2650c7e 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 56d5250fa1 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 25cb3e5820 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards ea35ecac1d 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 02c9e3b3f7 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards e3095b2c56 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards ce97c4c48f 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 967725787f 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 32b01a8f77 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 1a42ab91ec 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards c5767512ea 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 52acf6daa7 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards d68e28045f 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 43470b2000 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 0ecaf4507f 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 4889de4f76 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards bc768c0d7c 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 033aa678d9 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 4fb1cfc7e9 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 5c66a9c93d 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 1fca5c255f 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards e22c32ed86 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards e37e7ca1cf 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 98140d2ef1 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 94c04fc1d6 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards d562f8e938 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 1fe88a2f9b 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 7d7f5fd825 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 98ebc3d4b4 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 0e5e7c2098 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 4271df2bfb 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 242a898c5c 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 52a8b680db 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 591572cd3b 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 5303505a88 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 7e640fde4d 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 3c7aa4ed60 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards c5abc94ecb 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 4aa511b298 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 79c41b6c54 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 3e61241d55 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 50eff09c1c 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 857d44c34f 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards ab39160325 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 440f27a945 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards a21c6d5700 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 70ec56b3cc 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards f8b7671f0a 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards f2c066f1e5 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards bfa646e81b 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 7cd018ab8d 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards bd5249bb3f 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards cf4881b3d5 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 469d8eac8f 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards ef001cedad 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 814c885f99 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards a55e93b460 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 455c7fac61 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards c54e58ec01 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards e59540fd39 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 3452e090ac 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 2c09fa8181 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards e8e2b73816 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards df12553ce8 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 1fff223432 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards ed21f207cb 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 2e12fa79b8 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards c4b2f98aa1 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards b6a4ac595c 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards a98e0dc353 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 83ca896363 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards cc742927e5 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards f8d0f7e073 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 34a7ce2274 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards e079c9bbec 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 4979e373cf 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 1b0a2194d0 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 41e6988bdf 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards d5784f8702 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 18c845a27a 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 06585582ab 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 99de18c246 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 1fa69e8a0b 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 3dbff88de9 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 47f97dec12 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards b184744647 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards b2ab42b0d8 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards d60adcb848 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards bf4aa95da7 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new dfd6a527a3 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 899d6f0585 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 0b82ab6aeb 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new bb3a03b3c0 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 1ba163af1b 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 256bf33486 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new feb29ac76d 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 29f1943275 293: onsuccess: #2542: 1: Success after gcc: 5 commits new b2be406613 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 96763de39e 295: onsuccess: #2545: 1: Success after linux: 10 commits new a7324e7ac6 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 28aa6a585b 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 85d4fd1d89 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 6ec8d88887 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 88ef18368a 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 01c4fbc521 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new a065c57f0d 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new f9dc9db5e2 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new a10c399542 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 55dabc0343 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 1bbc5f29c3 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 8304d170c0 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new cb1e011d9c 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 9a18fd74a2 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 2799535572 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 7757cc2a2c 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 7817a34d75 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new d8041f9735 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new fbd8a0b7f4 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new a03e33b086 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new d41d0091cc 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 7562c0e23f 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 728d2f8de0 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new a1968100ed 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 530198ba5d 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 06b0d6bfcc 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 9b715eace0 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 349d7a3acd 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 42a3470d45 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new d0c28a25d3 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 425a4d04e5 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 9a014f0765 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new a52fa68b52 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new ec07c72d18 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 0e5b061be5 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new b79cf3806a 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new d493319e35 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 7c43f3148a 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 37298c38fc 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 2bc9beb745 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 5281c69cbd 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 90b0e76da9 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 14710234a2 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new a3889ede3a 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 01769e257f 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 30601e3f22 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new d6d80256d6 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 9e354836f6 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 5e97ab0356 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 5890144e72 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new f91caf36a5 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 82e24d5b99 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 85ecd91505 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 600bed0b6a 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 3792b73b1e 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 1b2c50e34b 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 75857dbf29 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new d0c9499def 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 2290c69d19 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new ebd9171b90 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 88cada7f7f 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 4c528e440e 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 43990049b7 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 60cb838655 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 17a30f87fb 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 321b631882 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 339573104a 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 9c7cae1269 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new fe3349b8d0 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new bcb9fe3675 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new dc921f123a 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new b7ffacaf11 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 77d8a41aa9 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 946c0b6990 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 343bd3ed9b 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 12aea3a0de 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 7980a34d4b 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 61d789fe8b 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 0a7e45c2bc 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 126f83dd02 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 0b121544cf 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 5f986987ff 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 156776ccf2 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new dc2a40aefd 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 8800e28b6c 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 3546a75711 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 9b2004e307 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 818a7b68d6 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new cf707acd3b 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 7f522df2a1 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new cf58f3797d 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new f4081000e5 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...]
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 (525de04ba5) \ 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 1760 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31160 -> 31468 bytes 04-build_abe-stage1/console.log.xz | Bin 72792 -> 73116 bytes 06-build_abe-linux/console.log.xz | Bin 8664 -> 8660 bytes 07-build_abe-glibc/console.log.xz | Bin 244716 -> 245268 bytes 08-build_abe-stage2/console.log.xz | Bin 204000 -> 204696 bytes 09-build_abe-gdb/console.log.xz | Bin 38484 -> 38840 bytes 10-build_abe-qemu/console.log.xz | Bin 31368 -> 31980 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3908 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2644 -> 2724 bytes 13-check_regression/console.log.xz | Bin 6336 -> 6024 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 17 - 13-check_regression/mail-body.txt | 68 +- 13-check_regression/results.compare | 41 +- 13-check_regression/results.compare2 | 50 +- 13-check_regression/results.regressions | 51 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 70 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 51 - sumfiles/g++.log.xz | Bin 3395232 -> 3399904 bytes sumfiles/g++.sum | 34 +- sumfiles/gcc.log.xz | Bin 3017024 -> 3026312 bytes sumfiles/gcc.sum | 3464 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1035656 -> 1040708 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217520 -> 217508 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2660 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 431104 -> 435968 bytes sumfiles/libstdc++.sum | 52 +- 42 files changed, 1934 insertions(+), 2092 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