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 38655a7740 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 26eaa08510 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards a08eda2827 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 0e12df336b 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 72276f6ee1 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 643545267c 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards d21f25df8c 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 3b10dd90ce 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 43aa0ffed4 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 66816b67f9 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards e3b03f7972 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 6ff195c5af 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards afa20008d5 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 3d0efb8b66 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 013328890b 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards ea6d004bee 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 5b0cd4958c 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 82f6fc9a80 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 719bc3dac5 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards c8e952dbf0 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 0cadbd4524 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards aad22b63b6 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards e27f1105f2 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards aecb902e8c 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 3359bc65ed 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 6369b2185e 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards ae249676d7 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 77197bbe17 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 8356ca62d7 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards ad922212ac 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 3b68de234f 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards f76f2aabc5 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 018bd2dc85 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards e2459a1026 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards e4a4b4cb6a 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 582ba1406d 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 04a3838b4f 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 032f5fd234 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards f0bf401f75 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 494ce86fa3 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards deb45ce93c 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 0c85b7f929 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 6f04cd1193 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 7fdd3ca6e7 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards f9dc6e735c 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 183c36c23c 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards eec1af9e15 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 90868cd7ff 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards c87b00923c 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 12dcc36b38 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards c11a71649b 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 5b1a210576 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 80defc3d27 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 5b07969f60 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 04b6e6ede2 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards fc4414f8e5 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 45d8edc0c6 301: onsuccess: #2118: 1: Success after linux: 16 commits discards fc20bad8f7 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 360b5436ca 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 15ecec403e 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 726d8d4d00 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 35cc1472a4 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards fa03461db7 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 020b440d6c 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 5839e8ed3d 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 337ea23a0f 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 3d5fbf86c0 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards de73d89eab 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 5cae7cda4e 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 12798a45db 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 90c5f030c0 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 8c3aa9f6a3 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 9fa84d395e 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 148b817cce 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 3b5d10ded9 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards f025fdb98a 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 435445f1b2 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 8009d2d4f4 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 4f50fa3115 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 22ddcf94d7 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 02ae1a9245 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 9574f27c6b 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 2c8c59e75d 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 78f985b6b5 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards bffa0e848e 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 06b18ab60d 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards f1d26d5bda 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards c4f194b8ce 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards ff77288694 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 01ee002f1e 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 350e653f5d 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 5bf3b8cdfb 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 2680cf7015 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards b4347fd24f 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 52d68d9942 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 8c64f6a73f 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 8e35155be1 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 145eec3e8e 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 1e09048354 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards cea3433b52 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards fd960b4f27 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 855e7b3ab4 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 3fd3b57af5 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 53b0b23e0b 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 5c7c8fdb4d 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 40e5f56e0f 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new f7e9755f5f 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 9db7c45f27 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 471bae9582 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 0d3c64a22e 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 361b658ad4 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 3410fb4677 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 3d013b0cb1 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 14b4b885d2 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 28fc216d1e 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 806d6e2cfb 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new ad491315d1 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 753b37858b 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 326de7a567 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 2c29a6e267 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 7396127eaf 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 0c469d1b57 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new cb8e61b3cf 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 8b4aab2120 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new cb341092d2 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 71612f6433 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 3a987386b8 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 85209cec54 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 5b2b1dd57c 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new ff194614c3 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 5a3c2875d6 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 6af8f85dd0 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 7a04145441 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 05f3a142ad 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 7b41f54ac7 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 97bf7f9c18 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 2c01def14e 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 61359e4335 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 0d7d013b4f 294: onsuccess: #2110: 1: Success after gcc: 17 commits new a8ed4270ae 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 5c2b737ab2 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 27babf1cd0 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 4f4bd56474 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 88c79c3a0d 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new b618d611f0 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new d8d86a166e 301: onsuccess: #2118: 1: Success after linux: 16 commits new d5ce3c1027 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new f348a4fe2a 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 42872a3ea3 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 825f3765a7 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new c8fa395649 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 33f0d998be 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 4a78768d1e 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 6aecf7dbd7 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 4314b6250b 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 563a75cdcd 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 4a4062dc28 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 1c76d6b775 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new f42b1a485d 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new ee86b0165d 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 3cfa2446d5 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 85044ff2ff 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 1dfb5dfdb4 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 54f9f67f83 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 7112f08e89 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new eb49804060 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 95d8136b23 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 389b43a69e 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 7a7a645e36 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new bf093c6c1f 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new e5739861d2 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 67a8902756 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new b13d421dd4 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 3e5d34533b 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new e30c290459 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 765e72c233 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 1dd06d5d1f 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new dedfc33539 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new e23b6d1722 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 1a84315ba0 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new b39ffa3f17 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 987add3823 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 42e80ce474 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new e8159a44d5 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new a79192d7d7 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new ac431e90cc 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 26ef9dc0dc 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 2f7b2fc4d7 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 3cc5a5326b 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new a14f2d5550 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 55094d37bb 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new d670588f97 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new c7face381f 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 5b4e8f6d63 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 87beeca53c 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 1f95dc670a 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new efd79b499c 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 89d1e8f9d2 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 62678f26d9 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 34a460c177 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 11760a17b2 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new d3bf775fb5 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 0840447581 358: onsuccess: #2178: 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 (38655a7740) \ 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 1824 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 32036 -> 31624 bytes 04-build_abe-stage1/console.log.xz | Bin 92584 -> 91800 bytes 06-build_abe-linux/console.log.xz | Bin 9152 -> 8604 bytes 07-build_abe-glibc/console.log.xz | Bin 237348 -> 235816 bytes 08-build_abe-stage2/console.log.xz | Bin 230600 -> 228312 bytes 09-build_abe-gdb/console.log.xz | Bin 39352 -> 38936 bytes 10-build_abe-qemu/console.log.xz | Bin 32316 -> 31268 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3876 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2908 -> 2792 bytes 13-check_regression/console.log.xz | Bin 7220 -> 7688 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 19 + 13-check_regression/mail-body.txt | 140 +- 13-check_regression/results.compare | 34 +- 13-check_regression/results.compare2 | 91 +- 13-check_regression/results.regressions | 39 + 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 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 142 +- mail/mail-subject.txt | 2 +- manifest.sh | 46 +- results | 39 + sumfiles/g++.log.xz | Bin 2674380 -> 2673872 bytes sumfiles/g++.sum | 18 +- sumfiles/gcc.log.xz | Bin 2245532 -> 2198528 bytes sumfiles/gcc.sum | 2228 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 903128 -> 887492 bytes sumfiles/gfortran.sum | 12 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214088 -> 214080 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2672 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 441208 -> 441636 bytes sumfiles/libstdc++.sum | 19 +- 45 files changed, 1460 insertions(+), 1458 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