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 fcbb14bc417 202: onsuccess: #2431: 1: Success after linux: 944 commits discards 100f5a19141 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards 05b39425015 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards 8d225ab0f0d 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/ [...] discards 0e5fd99ef33 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/ [...] discards ad4819f69d5 197: onsuccess: #2348: 1: Success after linux: 190 commits discards 88c75ff9cf0 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 4 [...] discards be77282bc83 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/ [...] discards 4c311457dab 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/ [...] discards d0bc2ade18e 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/ [...] discards 281c8594f69 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/ [...] discards 4367fcbf224 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards 868c4a41346 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/ [...] discards 7d77acce7df 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/ [...] discards b5479ac85ec 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/ [...] discards e526e3380d2 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/ [...] discards 894339973f4 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/ [...] discards 5340def1406 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/ [...] discards 15ad0dba790 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/ [...] discards 72e974d6235 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/ [...] discards 51704db0728 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/ [...] discards f62541f7cd7 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/ [...] discards cc1042f9687 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/ [...] discards 2608e56128f 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/ [...] discards d358f5178d9 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] discards 372e94ad7e3 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards 17702dead97 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] discards e49809f6824 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] discards 83015039ec4 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 2 [...] discards 064b27d7649 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 06f21f29f3b 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] discards 6f8e6ee916b 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/ [...] discards 3d3cb9cb957 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/ [...] discards 28c0ba67e48 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/ [...] discards ca905bc6e98 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/ [...] discards 262052f8f8c 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qem [...] discards 44ef9989806 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards a76abdc7066 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards bea04d0b07a 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/ [...] discards 2cc000fee91 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/ [...] discards 4ae990e2ba4 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/ [...] discards f595bdc2e70 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/ [...] discards 5d01ecf2760 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/ [...] discards b3dc325bc85 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 19 [...] discards b33db31dcc7 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/ [...] discards b0d8b407a0a 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 [...] discards e0b98bb2ea2 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/ [...] discards 624829cabb9 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/ [...] discards c125d99b841 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 1 [...] discards 63e29936377 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 [...] discards b175cdb69e7 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 [...] discards 8ec534d2315 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 6e5ace59035 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 963c3e77efe 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/ [...] discards e9e5c924b6c 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 [...] discards 2eeee54fbb3 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 1 [...] discards f7fe4394c1f 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 8632d154e92 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/ [...] discards aaff7e1f722 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/ [...] discards d0e5647c7f2 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qe [...] discards b38810ab3ee 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 0121f77d5e6 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 [...] discards 7b037f79327 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/ [...] discards b70f25685f3 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 1 [...] discards 92275c018ec 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 [...] discards b1956f277e3 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/ [...] discards 3709bc1e219 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qe [...] discards 74730b26c9a 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 2e60e4ce559 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 1 [...] discards 47b2551e32f 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/ [...] discards 53b6de3245c 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/ [...] discards 509cb5a4acd 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 1 [...] discards 7e04352413c 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 3 [...] discards f85d68f8c23 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/ [...] discards 3ab1664c13a 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 6d385cd435d 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 13d122eca9d 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-2 [...] discards d6b9e56b376 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/ [...] discards 9c563524db7 124: onsuccess: #2159: 1: Success after linux: 23 commits discards b8aa00f6aa6 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-2 [...] discards a3220bd2cdc 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 [...] discards 35fd41f68b4 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/ [...] discards 77a8d48f6e2 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/ [...] discards 6ad82ad16d7 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/ [...] discards d26e81d8ad5 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/ [...] discards 79714924a86 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/ [...] discards 6b9e30140ae 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 [...] discards 49bd5eb0186 115: onsuccess: #2147: 1: Success after binutils/linux/glib [...] discards 1d81038440b 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/ [...] discards cb50ef4e123 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/ [...] discards 358eab84cf8 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/ [...] discards e92826e228a 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/ [...] discards b4cf22132eb 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/ [...] discards 24badee1046 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 61068acc850 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 [...] discards b0659cebe8e 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 [...] discards b3a05f59078 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/ [...] discards e5e5e60f165 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-2 [...] discards 2282c4e2748 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 [...] discards 50ef854d373 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb [...] discards 134d63a3d2b 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint- [...] new aa0498e77d1 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint- [...] new 33d25b39a44 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb [...] new d34237785a8 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 [...] new 3517d302943 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-2 [...] new 65ab3b11b30 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/ [...] new a996b792387 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 [...] new be7625795c2 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 [...] new 3d00af3b607 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new b0b6ff47cb5 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/ [...] new 9e0d701195d 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/ [...] new 27d37cf01b3 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/ [...] new 8c9ebc47131 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/ [...] new 46c1628c4e3 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/ [...] new 5ce6731b099 115: onsuccess: #2147: 1: Success after binutils/linux/glib [...] new 117073bc623 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 [...] new 27ff436ae41 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/ [...] new 76f69edfed7 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/ [...] new c93c3595f1d 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/ [...] new e15888635ff 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/ [...] new 0b6d0bf64ed 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/ [...] new 1b9d41b5b0f 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 [...] new 3dbc2f49a8b 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-2 [...] new 3bd73eddfd3 124: onsuccess: #2159: 1: Success after linux: 23 commits new 8cd4883ddcd 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/ [...] new 2cff43d0cbe 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-2 [...] new 868ea7f6b27 127: onsuccess: #2162: 1: Success after gcc: 9 commits new aa9d34e76c2 128: onsuccess: #2163: 1: Success after linux: 23 commits new a05be50adb2 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/ [...] new e0fbc18a06c 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 3 [...] new f47cdd56743 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 1 [...] new cd497fa93c4 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/ [...] new 1f00d425b7b 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/ [...] new 59c177e5379 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 1 [...] new 9480f74fbd2 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 11a35f69a4e 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qe [...] new 8cfcccea6ba 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/ [...] new 9447b9270d1 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 [...] new 32341c83ec4 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 1 [...] new 09a27ca0557 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/ [...] new 9b25de611c7 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 [...] new f030df8ea6c 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 4cc89a3d2c5 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qe [...] new f7bf8ab6ffb 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/ [...] new 33b6651b407 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/ [...] new ba95a29d883 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 586054cd4ab 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 1 [...] new 91427a49d39 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 [...] new 9c5945b4f81 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/ [...] new 4730e7bde8d 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 7fc77a17cb0 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 00803b8b820 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 [...] new 71d60f5fd61 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 [...] new e16e8281e9e 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 1 [...] new 904e3a871e4 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/ [...] new 6dbfa160ea7 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/ [...] new 15fd556b1c5 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 [...] new 588917013a5 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/ [...] new ea9e90979ea 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 19 [...] new 157616e91fe 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/ [...] new 8b014a2de62 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/ [...] new 7099bb62a63 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/ [...] new e190c65719c 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/ [...] new fa4fc0f706c 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/ [...] new 002f26de660 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new dd42d13aa14 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new 8f22b6c100c 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qem [...] new 06e3df09310 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/ [...] new 9fae99c8f1a 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/ [...] new 818bb748bdf 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/ [...] new f3d71ddbfdc 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/ [...] new dd1cca3fe2e 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] new e68fab3816a 173: onsuccess: #2208: 1: Success after gcc: 10 commits new ffda636cd36 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 2 [...] new d75fe884bfb 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] new 461cfbc59b1 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] new b2be8b5ba77 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new c8a9ea88de8 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] new 09bb8aacad0 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/ [...] new de8a18953c9 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/ [...] new bfd78f913f7 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/ [...] new 7ee93023e49 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/ [...] new a355bf7e5c6 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/ [...] new 57bc53bf248 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/ [...] new fa4d82459b8 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/ [...] new 4b743182f33 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/ [...] new a1829b1a43c 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/ [...] new db3f85a477c 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/ [...] new cbd4d5f1bef 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/ [...] new 0ec75890957 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/ [...] new 1a093e6c512 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new eb6951c86f2 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/ [...] new 7fb55495a2c 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/ [...] new 5a843963738 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/ [...] new 01de8c52146 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/ [...] new c2469e9c859 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 4 [...] new b6a722dc6f2 197: onsuccess: #2348: 1: Success after linux: 190 commits new be2d0b5e8f5 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/ [...] new e8692c10a16 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/ [...] new 499c384350e 200: onsuccess: #2427: 1: Success after binutils: 274 commits new f4e92d06fe3 201: onsuccess: #2430: 1: Success after glibc: 26 commits new 0a8456a5bf6 202: onsuccess: #2431: 1: Success after linux: 944 commits new 96c5f9ac6d9 203: onsuccess: #2433: 1: Success after binutils: 27 commits
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 (fcbb14bc417) \ 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 1804 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2788 bytes 03-build_abe-binutils/console.log.xz | Bin 31864 -> 32308 bytes 04-build_abe-stage1/console.log.xz | Bin 72840 -> 73068 bytes 06-build_abe-linux/console.log.xz | Bin 8420 -> 8528 bytes 07-build_abe-glibc/console.log.xz | Bin 244856 -> 244772 bytes 08-build_abe-stage2/console.log.xz | Bin 205196 -> 204108 bytes 09-build_abe-gdb/console.log.xz | Bin 38128 -> 38040 bytes 10-build_abe-qemu/console.log.xz | Bin 32352 -> 32196 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3960 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2708 -> 2664 bytes 13-check_regression/console.log.xz | Bin 15168 -> 5404 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 17 - 13-check_regression/mail-body.txt | 100 +- 13-check_regression/results.compare | 60 +- 13-check_regression/results.compare2 | 2718 +----------------- 13-check_regression/results.regressions | 68 - 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 102 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 68 - sumfiles/g++.log.xz | Bin 3450900 -> 3453388 bytes sumfiles/g++.sum | 83 +- sumfiles/gcc.log.xz | Bin 3030860 -> 3035492 bytes sumfiles/gcc.sum | 4648 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1038456 -> 1038048 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213372 -> 213460 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2700 -> 2704 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 423128 -> 433688 bytes sumfiles/libstdc++.sum | 10 +- 40 files changed, 2517 insertions(+), 5460 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