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 79beaacd5d 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards ccd553c894 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 76434e3a16 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards c75e76bfa4 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards f04b7c92a0 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards a5fb390773 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 7d4923e397 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards fc6b72d36f 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 312dcf2ce3 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 595902a3ea 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards f3b6712baa 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 1c630b57a8 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 0d9bef8d31 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 65a2fccbbe 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 4804f78b2c 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards dce4d14582 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards bcfea0726c 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 3a953276b7 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 531f63517e 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 3ca4a9bd25 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 5e3885129c 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards e5c4956b49 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 1a3e1a6eaf 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 4a3cb181ba 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards d14ef94268 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 1fffd55c86 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 5cdcfd85ff 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 515d2c7625 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards ea67b6d595 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards f65ca16bce 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 8b33a6f632 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards b414f0efd7 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 59c4b8c2bc 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards d2943acebf 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 967d9e11b1 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 56a3d2a6c3 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards ae98a2c683 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 4fff42cca0 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 50774bbb67 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 6c6fed8298 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 7fbc91bd55 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 942de0539f 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 71e9868cc7 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards bd9325fed7 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 7b4d9a5a12 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 4eea484481 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 8d6858d4cf 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards ec26bbf885 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards f3d98f742f 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards b7e75e629f 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 9287166dbf 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 79f116be02 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 862f197c68 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 2d5d513cb8 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards e928054829 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 9208ffe4d3 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards d59505b2ea 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 39d410dd46 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 2b5a8e35ee 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards afdd8c7bf1 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 0adb7f9242 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 6747dead7d 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 12b249cfd0 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards d92d54f90f 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 726094fba6 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 7f227ac6e0 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 43835cc765 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 94e165d4c8 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 60ee51ab4d 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 45296d5da1 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 86d48805fb 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 0b246320b4 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards d1ca4ef6d5 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 02d73d1899 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards d875dc3d9a 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 7501a2742d 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards fa50c4b953 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards ef29d6562d 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards e3fa5e9fc4 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 46b2e1e0ca 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 8104bb9b69 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 8b9bf91f91 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 58d3ed4f70 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 7372e28f92 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 84fd8c4d47 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 9f882c53b5 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards c09fa65225 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 07b6b83ce9 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 5b59c25b0c 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 2ac73c2090 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 5641529fae 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 2c72505bd2 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 34ada3ae3f 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards bf2ebb7cf1 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards a4a69bb087 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 2f59f2c7ae 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards c8a5099a2b 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards b107d44529 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards e2325725b0 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 1b7b2dcff2 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards baee430c07 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 038413977c 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 32f2c41bbe 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new eabd94cb24 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 9a348aeaa3 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 9c13ccbac1 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 66bc828c36 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 7a77a030b1 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 0224a151ff 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 5467601559 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 3da36a5a3b 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 24fa0e96cc 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 4162c9de3f 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new c1094d1de3 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 5bf8229aa3 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new f3498f8963 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 8d9bb98c77 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new c28f06f285 287: onsuccess: #2103: 1: Success after gcc: 9 commits new da395ee036 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 0548eef401 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new a66c0f00d1 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 6b96b8493f 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new f12bc97ac4 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 5f4eef40db 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new aac7773e63 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 50a05ef75e 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 88b0b4664c 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new ceb3294532 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 75a3d6fc72 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new aba6b1a915 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 0b3bb9cb94 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 0e96f6109c 301: onsuccess: #2118: 1: Success after linux: 16 commits new 983aaa2f77 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 81d5c05e2d 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 1cb1f1fcc6 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new bb0eab8f92 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new e49ec9aac2 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 31d022f093 307: onsuccess: #2124: 1: Success after gcc: 2 commits new db870c6366 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 2ac55f9132 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 08aed59823 310: onsuccess: #2129: 1: Success after binutils: 4 commits new e0855443f7 311: onsuccess: #2130: 1: Success after gcc: 4 commits new dd72accb99 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 932786cf0e 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 0c9641b4fd 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 3875232c13 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 49e14a0d00 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 19e4f85514 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 53603d6b4a 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 202ef8e76a 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 6d9f3c858a 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new be626d15d7 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new e5f585b676 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 318c2b2d1b 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 3a32913013 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 755914604f 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 5c99e9c130 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new e1cd40a28d 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new c5289edaa1 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 365a693152 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 29b33bd57e 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 1784b36f10 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 1dce4b70fe 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 221408bc41 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new c1602d9ad2 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new fb6effc426 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 132701facb 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 801ee11150 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new ab0afa5dbc 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 72a93e997c 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new cc985fb26c 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 8f267d3ea9 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 81c56b1e09 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 52d91fc5c7 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 90d8c1b233 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 8e39fe534b 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new aaea98cc7b 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 6aba0cdbc2 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 3ff20669fa 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new ca3670cdf8 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 951f3964bb 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new a924564aa6 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new b75fb9bc1f 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 52ff27e1b5 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 825c484fb6 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 8fd01c88bd 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 647ae7e9db 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 6b54a6b87a 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 4b8adabf28 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new a5a5ec9465 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 2cb6c50aca 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 325b245ec5 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 036da448dc 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new c93f4dc7b2 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 007bdd15f7 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 241e83161e 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new eb538f7ac0 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new b74c5a7fc0 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new aa3456c6d4 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 3ff1f2e51a 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new ada52698e8 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 9aa44f5d69 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new e9424b82f2 372: onsuccess: #2192: 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 (79beaacd5d) \ 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 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 31392 -> 31736 bytes 04-build_abe-stage1/console.log.xz | Bin 91980 -> 92660 bytes 06-build_abe-linux/console.log.xz | Bin 8676 -> 8656 bytes 07-build_abe-glibc/console.log.xz | Bin 236664 -> 238380 bytes 08-build_abe-stage2/console.log.xz | Bin 228408 -> 231564 bytes 09-build_abe-gdb/console.log.xz | Bin 38712 -> 39464 bytes 10-build_abe-qemu/console.log.xz | Bin 31548 -> 30800 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3912 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2872 -> 2952 bytes 13-check_regression/console.log.xz | Bin 6736 -> 8968 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 74 +- 13-check_regression/results.compare | 30 +- 13-check_regression/results.compare2 | 425 +++++- 13-check_regression/results.regressions | 47 - 14-update_baseline/console.log | 70 +- 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 | 76 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 47 - sumfiles/g++.log.xz | Bin 2630796 -> 2651228 bytes sumfiles/g++.sum | 71 +- sumfiles/gcc.log.xz | Bin 2224332 -> 2225968 bytes sumfiles/gcc.sum | 2470 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 893296 -> 894284 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214208 -> 214344 bytes sumfiles/libgomp.sum | 26 +- sumfiles/libitm.log.xz | Bin 2668 -> 2660 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 436572 -> 435220 bytes sumfiles/libstdc++.sum | 34 +- 44 files changed, 1797 insertions(+), 1646 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