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 9a1248c2c0 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: [...] discards 781102960f 427: onsuccess: #7: 1: Success after linux: 26 commits discards 7a4b8c3886 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards b535239f22 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] discards dff75b2f42 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards 7542529d61 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 4055125e1f 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards e4b1f35ddc 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] discards 5a56874a44 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] discards a70e4724ab 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] discards 4971223e4f 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] discards 9cc63c540e 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] discards 462c28189e 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] discards ed41f9abd9 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] discards 31c0e8987f 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] discards ab9f3adc06 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] discards 7c4f88d19d 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] discards f0337ad6e1 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits discards 13e17decba 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] discards 36aedc8fb6 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] discards 2a7ffb9f73 408: onsuccess: #2662: 1: Success after linux: 11 commits discards d456c9a9e8 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards 0688578b26 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards 177eeb92a8 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards 95e620493c 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards be0ec46098 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards 2a6eb0d4dc 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards c27f2f72cb 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards 8d69ed8a5a 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards 00d6a0f375 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards 888fae473e 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards 262396b716 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards 46b908c559 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards 6881b7bf92 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards 247940020a 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards d60bdb79b6 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards 28947389ef 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards eefd09ed0f 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards 8b8c616cda 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 6433ec03aa 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards 3dab4a6e8e 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards 1cc12b31ee 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards d4b3598876 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards c3a8835e30 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 1663f03fd1 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards fe2f6d96d0 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 9fac46e6d7 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards e9ed60b27d 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards fb3b98e2fd 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards 652ff8bc29 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards dfb4317ff2 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 1468eae967 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards ea10d0ab0e 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 59c8fa9517 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 4f86527aba 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 624f22ad77 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 894d3f518b 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 8bf351845c 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards d275ef46b4 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards fd470cfc07 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards ec01fc0f28 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards b9c9f832f2 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 51b2597f05 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 8a94166aba 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 46edc6238a 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 27da9082e8 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 9cef5d33f2 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 589355984f 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards c22a914b8b 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards a0f6b2010b 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards d08f8980b4 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 012fa81ca0 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards fdbcde75aa 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards bad97df6ba 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 0db89372c3 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards bed22cbf52 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 6698fbb3a9 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 85cd281fb9 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards ceafa82ced 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 573e5e472e 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards d1cb4980be 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards eefc6045e7 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards c2563b3b80 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 0dfedd2d7b 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 2830571484 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 75aa5607b1 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 93484b7484 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 0e29d62d71 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards c078ed343a 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 6a8fd3e7f3 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 83aca06855 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 90fea213ab 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards ef784ab5f6 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards e45ad04347 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards c253367054 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards ddf85b0281 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 0deeb6989a 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 06028fd3ba 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 27e2fe4d8a 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 77624a449b 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 84aab24136 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 6152b100da 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 3148fce04a 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new bb502c2604 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new b8b03e19ee 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 9faca0281c 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new bea1a40512 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 354da1e73b 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 37a497904d 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 2384df65a4 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 35bd3a437d 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new cbfd1ddfde 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new e6c8ba6ef8 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 90bf2a24bf 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 31d3f4e357 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 4f3e663db2 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new c27b1f5518 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new fa1d57244c 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new d25c453c8a 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 80cc09d45e 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 169ad51ff1 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 6161e304bc 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 5da79c76e9 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new a161919364 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new ffaa129de7 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 44f2c888c5 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new fdabbf17c9 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new a0c361ff60 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 6009571fac 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 6397db81a6 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new f73463815f 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 9ed516949a 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new ae60acf975 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new ca881067bc 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new ce8966d66b 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 2e92b7b3ec 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 109a5aaea3 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 7ebbdc7cdb 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 150aa0d05e 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 61f60e6076 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new 6da557fdeb 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new df01d299bf 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new e802500e5b 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 6fe4f8217d 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 0447b904d5 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 4056d0fc1c 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new f43f86b44f 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 21cd395833 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 0d49db71a8 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new ed5dd661e1 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 4ace5134ad 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new b32224c8e2 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 5569661cd7 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 23f3d139d6 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new b627cec669 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 426929867b 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new c8b5b5a65c 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new 3354d5e066 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 22fef3e75a 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new 33d7924fc1 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 99facaa03f 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 9cbec77b03 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new d56446f810 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new 6fd69afc23 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 7509f67d74 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 6774d9652a 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new 6c8d8082a7 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new fb9a95b341 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new e31efee30a 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new 80e32dbfbe 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new 4d674f6ef1 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new a32458923e 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new c5b42c1741 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new 30f304ceaa 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new 72c1f2b1c5 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new b0028a7f83 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new d2ec330fea 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new ad0d22f4fe 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new 2afe847471 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new a0f6a960d5 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new 966c85eeb5 407: onsuccess: #2661: 1: Success after gcc: 7 commits new 16b63a61f5 408: onsuccess: #2662: 1: Success after linux: 11 commits new 57083fa2c9 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] new a183fe76a8 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] new c3de8b6a1e 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits new 64fad77cc8 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] new 155f975ed6 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] new 8d09d3389d 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] new 2bc8054118 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] new aeda0afb53 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] new 98245b0b00 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] new f58d6ec7fd 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] new 460ceeeab0 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] new 4aaa496ba6 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] new 97d4167dbd 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] new d30a143359 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 7495c41ddf 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new f97a67ed27 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new b39f48bd4b 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] new fb544776d9 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 7b943a2216 427: onsuccess: #7: 1: Success after linux: 26 commits new e88986db3e 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: [...] new 15f305dd16 429: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...]
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 (9a1248c2c0) \ 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 1772 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 30844 -> 30964 bytes 04-build_abe-stage1/console.log.xz | Bin 71832 -> 71244 bytes 06-build_abe-linux/console.log.xz | Bin 9612 -> 9436 bytes 07-build_abe-glibc/console.log.xz | Bin 243476 -> 243440 bytes 08-build_abe-stage2/console.log.xz | Bin 203240 -> 202380 bytes 09-build_abe-gdb/console.log.xz | Bin 38808 -> 38968 bytes 10-build_abe-qemu/console.log.xz | Bin 32012 -> 32296 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3816 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3240 -> 2656 bytes 13-check_regression/console.log.xz | Bin 50920 -> 6860 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 26 + 13-check_regression/mail-body.txt | 77 +- 13-check_regression/results.compare | 52 +- 13-check_regression/results.compare2 | 5872 +------------------------------ 13-check_regression/results.regressions | 46 + 14-update_baseline/console.log | 66 +- 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 | 79 +- mail/mail-subject.txt | 2 +- manifest.sh | 44 +- results | 46 + sumfiles/g++.log.xz | Bin 3396336 -> 3392776 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 3021896 -> 3023784 bytes sumfiles/gcc.sum | 48 +- sumfiles/gfortran.log.xz | Bin 1041820 -> 1043972 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2316 -> 2312 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217432 -> 217220 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2680 -> 2684 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 436256 -> 429240 bytes sumfiles/libstdc++.sum | 10 +- 44 files changed, 380 insertions(+), 6018 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