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-arm in repository toolchain/ci/base-artifacts.

discards 754095659d 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards 5a3e560643 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards 547e5fc905 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards 8d56d63491 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards b678875248 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 6db29434f8 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 62c12bed3d 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards 6d7b9a4b23 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 7e8c98af15 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 9480a0e550 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 97e512ed30 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards 4ae54a95a4 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 5f983d9542 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards e0c8a2313e 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 2b098b6ee8 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards bbdb069afe 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 565d3291a9 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 26689d8dc8 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards b6a08f76c6 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards a1058e9abe 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 23a0406b6e 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards b0f2da243c 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 546f5d9605 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 74cc0588c1 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards d13f464909 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards fd2dc6f573 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards f01d8d5edd 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards dd81d39d1f 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards babc48a1e2 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 472cd87565 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 5984dd3fae 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards b1fdc72bef 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 363f9a15a0 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 2223cf17c4 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 1852e24d06 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards a684610a16 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 3bed398cce 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 33cf38f92f 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 20abf006f4 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 4a86a9ee49 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 044ed1eb22 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards fb64e68c71 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 4649653fe2 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 3190f21832 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards c86df71aed 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards a0fc92c739 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards f6d710097b 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards f311be48c7 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 8ce0b627da 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 4ba04ee382 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 85dfe7186d 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 09265c768b 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 3bb2afabb2 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards a6355b2b8a 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards a30d621cd0 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 2d7ec8abec 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 8255c5ea59 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards b319f17094 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 4425e26b23 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 710ba5d881 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards b5074293df 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 5d5106e3b8 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards a0f3bff082 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards c16148021d 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards ef442a7e18 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 1f9e7c3ee4 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 4fbafd50b8 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards d95d4fcb07 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 8fba49a7e0 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 0efefa4200 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 8c10f217ba 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 90d8637426 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 6bd8598aaf 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards d9ef4c3387 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards f56ded9b34 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 3acfae11f2 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 20a713dd7b 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards aaa6407840 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards f9cdb46fc6 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards d2f4f91b0d 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 22b327b0d3 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 969469477b 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 436edcae49 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards ed8abd484f 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 8c90c2e2e0 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 6cc26a55ac 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards b4ade7121d 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 2e6ec45619 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 5b89dc620d 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 1423e2eada 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 167f7a1890 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 25366b5b2a 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 2d82fb042e 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards ec3849c9ae 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 2775714b54 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 2d3fd18f7b 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 2e063126b4 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards e18e2a28b2 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 2fb3d83e33 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards f9cb4fb389 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 0e4c55cc09 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new a5f7610e97 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new e8c0449d89 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new e7511841d7 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new ec8b6e9a39 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new c7a58edcf0 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 6b3fadbe02 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 57d2585a18 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 33e1e439eb 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 8398a56381 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 358a42cb82 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new ece643567a 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 2b066d4e03 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 47d4a873c2 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 3b7c369e98 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new a2591c2de2 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 239738bf5d 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 43eb55a786 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new f63ce5325d 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new f52888808b 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new bfe88d6b43 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 3081f76b0f 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new e461a6fd7e 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 04845a9b00 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 12f4d07c1d 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new abca6117ab 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 5c14ce10f4 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new a2a1547882 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 4d3b3611a8 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new ada56dbba2 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 643f33ce35 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 0fd57fcd4d 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 24c4218345 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 28a2073b94 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 436ce91ff0 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 672019d509 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new bd95de5c66 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 7dda12e759 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 7c274e877c 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 46a3f5dcf2 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 2b4f2527e4 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 28c0ebff31 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 2eaaabe34d 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new f29e40c6cb 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 95efaf990c 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 294fdab160 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new cad9e7ef11 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 66ffd8fff2 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 2f3af50b5e 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 7206f2c743 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 4d56219d64 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new fd2d92cf25 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new daeb890aa3 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new c2f489b09d 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 3b0b52b9ff 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new ab5a9c632e 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 310b72bcea 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 7423e99178 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new ad1797eb55 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 374ac8e177 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 0a8325f9ca 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 4c379b1d0a 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 70ed6df42d 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 559ab16e67 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new d870ff4f19 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 4dffba4ff1 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 8f8e7cb634 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 8886cc6e80 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 6c3c00a9e1 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new c78a4202ec 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 9ec544647b 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 208c581217 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new a4413ef885 387: onsuccess: #2208: 1: Success after gcc: 2 commits new f614cac966 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new d6625f7caa 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new c91d245792 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 581733dcae 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new b2a642647e 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 9e737c55d1 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 8fee9a8aff 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 85d2e1de60 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 2ced01e739 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 48e03fef17 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 95c431991c 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 1c456d37ff 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new f8b2275618 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 34d3d3ca9b 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new ffa9fdf20a 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 3069ae22a8 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new db76e88697 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new ea75c8757a 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new fd3a548c4c 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new a4e0a9a8f4 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 38e6a924e3 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new d6efe7b817 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 06ed717f3a 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 762c9953e7 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 2768e1964c 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new b682391f6c 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new 70e3f2d5d0 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new 6cb24004e6 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new 4953706ba1 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new b38cd900c1 417: onsuccess: #2238: 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 (754095659d) \ 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 1792 -> 1816 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 31244 -> 31020 bytes 04-build_abe-stage1/console.log.xz | Bin 91924 -> 92040 bytes 06-build_abe-linux/console.log.xz | Bin 8576 -> 8516 bytes 07-build_abe-glibc/console.log.xz | Bin 236788 -> 236656 bytes 08-build_abe-stage2/console.log.xz | Bin 228580 -> 228260 bytes 09-build_abe-gdb/console.log.xz | Bin 38552 -> 38608 bytes 10-build_abe-qemu/console.log.xz | Bin 32456 -> 32548 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2904 -> 2872 bytes 13-check_regression/console.log.xz | Bin 7256 -> 6876 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 9 +- 13-check_regression/results.compare2 | 139 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 60 +- 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 | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 26 - sumfiles/g++.log.xz | Bin 2671256 -> 2637492 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 2194516 -> 2193160 bytes sumfiles/gcc.sum | 2417 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 897864 -> 889312 bytes sumfiles/gfortran.sum | 9 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217036 -> 216948 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2676 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 438900 -> 437868 bytes sumfiles/libstdc++.sum | 38 +- 43 files changed, 1401 insertions(+), 1476 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