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 5b73b6acf3 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 9bbfb022fe 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 948a2944b0 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards d48f7576c6 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards db62506d0a 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 59bee58524 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards eb89f6e605 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards 3695b749cc 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 5c86163de1 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 8fd7ced69a 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 3907f27b71 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 3d88f38ed7 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards b99a1de220 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 1ef9f1f9dd 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards fa1e8fe655 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 6b4538f577 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards ab9e92c399 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 078f7ae32a 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards cf969470aa 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards b0117ae5da 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 4c57c18d92 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 66066f6589 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 8d58451207 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 95ecfce834 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 1945871c4a 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards a2a2d30f72 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards a1254ff8af 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 35c0934976 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards eff066a7c3 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards d2def8b7d5 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 082883eb24 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 376bc825b7 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 0f8ccda7cc 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 82df26c928 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 8065272ce3 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 6e8f7a801a 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 3454fbd857 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards cc6cbb5dcd 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 4b42efc7b7 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 6fc3e4d9fc 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 1b6e379ef1 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards ed357d0e5d 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards c29a92737b 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards eaef1ff35b 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards fc8ea142e4 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards f6a292813d 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 9c47aa35e8 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 383f269fec 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 3c96ea8913 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 79d897949e 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 4459ed4c5e 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards d0a92f03bf 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 761659b75e 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 5b0418e446 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 13e2e44b99 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards b2a02e7a2f 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 710685e9ae 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards deecbce075 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 3a8a8e78f8 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 2a83fd8c7d 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 5cf0ae1a72 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 1d94f30bb0 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards f7814d7d46 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 25a030b8b8 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards a9d97c90a5 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 8913011ad4 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards eb7b49fca3 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 10c475dad6 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 4d22dd5271 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 02620eacad 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 29eaececfd 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 296f1e27d4 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards ca41fca909 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 7418bb258c 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 8aff8a4da8 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 55ab03f840 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 25faa06a7e 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 67066a3ff9 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards e46dfb4e9b 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 9e5eb54cc3 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 1c72f385bc 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards e0921fe7b5 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 77d749e446 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards c0fa10766f 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 159625ab62 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 3453181405 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 9a458b5164 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 6d3b63fd2a 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 3132c7fd95 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 993a56e741 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards fa87acaf82 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards a8713bf307 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 2ded95e890 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards af6cc0f4c1 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 1cf1ad6ed2 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards b10b3ec19a 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 146e4a5ae4 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 6538052271 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards b1e4219760 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards df03a28bf1 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 1aabe0a561 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 78a2d4af73 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 94a60d551e 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new a8606a03c8 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 856f9d7f7b 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new ee31d9b0cf 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 3c7b676f68 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 254962cf9b 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 947c84b41b 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 612df9ef84 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 8567261b3d 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 7dfa12051a 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 5d3d922042 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 2ddcaed6e4 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new cb4cd42ac6 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 69b44fae06 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 9c83dcdd6b 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 027ee1be94 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 10881d3faa 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new cc330488f0 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 8ff42d4cfc 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 1f0512f272 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new fff92a9816 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new d40c809b01 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 38e59e619a 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new a9ec69b0a3 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new a20a9b7b8f 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 4a02c3f97b 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new afced70025 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new cca804a8ab 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 30617f7b27 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new b06ff8f99c 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 814fdba589 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new f27fb41d14 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 35ec2d387b 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new a55158e15d 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 86f9fc66a5 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new cb7d154a29 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 1a543845d9 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new e9c183ac72 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 4c40747539 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new a6849b0b1c 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new c83fe8b544 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 3762696e76 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 63995d9784 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 1f8d1bbd42 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 91a94ecaf2 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 956fd0a78c 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 3511b6488e 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 17dea70455 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 26865091f9 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 2c03b35cc1 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 67a1ed0e2b 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 13bf34f4b7 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new ffb8dac523 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new e70f829fdb 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new bddfb85140 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 884cf46800 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 1a545c798f 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new d6ca5bc185 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new ae3548d028 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 8e6b45cf63 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 902c887577 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 5fef168acf 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 344d4f262a 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new c339f285b0 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 5d8f51df7e 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 8b9dd2589f 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 3e2e0a519a 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 35979622c3 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 6807333824 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 0d66e781d9 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new d47c635774 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 2b2cebe046 384: onsuccess: #2205: 1: Success after gcc: 2 commits new c44d1f58a9 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 497b4c2dc5 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 413c6451b8 387: onsuccess: #2208: 1: Success after gcc: 2 commits new e401ac942c 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 6598912f4f 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new adb620a082 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 24edc05112 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 95df5c7d5a 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 5445f20672 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new fa5c71c5e6 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 82ce35d603 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 912f2ad519 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 6add782a64 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new c000a1e67e 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 046d88fa8d 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 81666394ef 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 9deb745ebf 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 6126cf6fa3 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 1e794963dd 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new ebb8d71b4c 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 4c76c6eae6 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 202ce47f50 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new d23ba9fbbf 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 651d82c522 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new fb3ee4ac12 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 62df0820a8 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new bde9e726f3 411: onsuccess: #2232: 1: Success after gcc: 3 commits new aa2d387468 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new 4c87ef07ba 413: onsuccess: #2234: 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 (5b73b6acf3) \ 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 1784 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31532 -> 31072 bytes 04-build_abe-stage1/console.log.xz | Bin 91904 -> 92408 bytes 06-build_abe-linux/console.log.xz | Bin 8892 -> 8556 bytes 07-build_abe-glibc/console.log.xz | Bin 236664 -> 236264 bytes 08-build_abe-stage2/console.log.xz | Bin 228120 -> 229112 bytes 09-build_abe-gdb/console.log.xz | Bin 38980 -> 38500 bytes 10-build_abe-qemu/console.log.xz | Bin 32848 -> 32612 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3912 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2744 -> 2968 bytes 13-check_regression/console.log.xz | Bin 6544 -> 6620 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 26 + 13-check_regression/results.compare | 11 +- 13-check_regression/results.compare2 | 61 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 46 +- 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 | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 26 + sumfiles/g++.log.xz | Bin 2644164 -> 2644484 bytes sumfiles/g++.sum | 28 +- sumfiles/gcc.log.xz | Bin 2188520 -> 2202416 bytes sumfiles/gcc.sum | 2266 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 890096 -> 889020 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216984 -> 216956 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 440208 -> 435532 bytes sumfiles/libstdc++.sum | 29 +- 44 files changed, 1348 insertions(+), 1272 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