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 96c5f9ac6d9 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards 0a8456a5bf6 202: onsuccess: #2431: 1: Success after linux: 944 commits discards f4e92d06fe3 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards 499c384350e 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards e8692c10a16 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/ [...] discards be2d0b5e8f5 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/ [...] discards b6a722dc6f2 197: onsuccess: #2348: 1: Success after linux: 190 commits discards c2469e9c859 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 4 [...] discards 01de8c52146 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/ [...] discards 5a843963738 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/ [...] discards 7fb55495a2c 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/ [...] discards eb6951c86f2 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/ [...] discards 1a093e6c512 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards 0ec75890957 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/ [...] discards cbd4d5f1bef 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/ [...] discards db3f85a477c 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/ [...] discards a1829b1a43c 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/ [...] discards 4b743182f33 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/ [...] discards fa4d82459b8 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/ [...] discards 57bc53bf248 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/ [...] discards a355bf7e5c6 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/ [...] discards 7ee93023e49 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/ [...] discards bfd78f913f7 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/ [...] discards de8a18953c9 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/ [...] discards 09bb8aacad0 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/ [...] discards c8a9ea88de8 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] discards b2be8b5ba77 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards 461cfbc59b1 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] discards d75fe884bfb 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] discards ffda636cd36 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 2 [...] discards e68fab3816a 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards dd1cca3fe2e 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] discards f3d71ddbfdc 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/ [...] discards 818bb748bdf 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/ [...] discards 9fae99c8f1a 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/ [...] discards 06e3df09310 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/ [...] discards 8f22b6c100c 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qem [...] discards dd42d13aa14 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards 002f26de660 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards fa4fc0f706c 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/ [...] discards e190c65719c 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/ [...] discards 7099bb62a63 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/ [...] discards 8b014a2de62 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/ [...] discards 157616e91fe 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/ [...] discards ea9e90979ea 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 19 [...] discards 588917013a5 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/ [...] discards 15fd556b1c5 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 [...] discards 6dbfa160ea7 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/ [...] discards 904e3a871e4 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/ [...] discards e16e8281e9e 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 1 [...] discards 71d60f5fd61 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 [...] discards 00803b8b820 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 [...] discards 7fc77a17cb0 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 4730e7bde8d 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 9c5945b4f81 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/ [...] discards 91427a49d39 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 [...] discards 586054cd4ab 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 1 [...] discards ba95a29d883 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 33b6651b407 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/ [...] discards f7bf8ab6ffb 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/ [...] discards 4cc89a3d2c5 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qe [...] discards f030df8ea6c 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 9b25de611c7 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 [...] discards 09a27ca0557 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/ [...] discards 32341c83ec4 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 1 [...] discards 9447b9270d1 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 [...] discards 8cfcccea6ba 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/ [...] discards 11a35f69a4e 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qe [...] discards 9480f74fbd2 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 59c177e5379 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 1 [...] discards 1f00d425b7b 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/ [...] discards cd497fa93c4 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/ [...] discards f47cdd56743 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 1 [...] discards e0fbc18a06c 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 3 [...] discards a05be50adb2 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/ [...] discards aa9d34e76c2 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 868ea7f6b27 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 2cff43d0cbe 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-2 [...] discards 8cd4883ddcd 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/ [...] discards 3bd73eddfd3 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 3dbc2f49a8b 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-2 [...] discards 1b9d41b5b0f 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 [...] discards 0b6d0bf64ed 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/ [...] discards e15888635ff 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/ [...] discards c93c3595f1d 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/ [...] discards 76f69edfed7 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/ [...] discards 27ff436ae41 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/ [...] discards 117073bc623 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 [...] discards 5ce6731b099 115: onsuccess: #2147: 1: Success after binutils/linux/glib [...] discards 46c1628c4e3 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/ [...] discards 8c9ebc47131 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/ [...] discards 27d37cf01b3 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/ [...] discards 9e0d701195d 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/ [...] discards b0b6ff47cb5 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/ [...] discards 3d00af3b607 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards be7625795c2 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 [...] discards a996b792387 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 [...] discards 65ab3b11b30 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/ [...] discards 3517d302943 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-2 [...] discards d34237785a8 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 [...] discards 33d25b39a44 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb [...] new a5bc2420f65 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb [...] new cf5207785fd 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 [...] new 3a532b49bc3 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-2 [...] new d4a60da9f1c 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/ [...] new 421b9d0bff2 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 [...] new c3bc08f88e9 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 [...] new acd7b7a7113 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 5b43e50aedd 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/ [...] new aec93a1b929 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/ [...] new d54e974fa96 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/ [...] new 79c7785761f 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/ [...] new 564f9e19b04 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/ [...] new 6b99cd744fd 115: onsuccess: #2147: 1: Success after binutils/linux/glib [...] new b4ee1f61c7a 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 [...] new 53bb238384a 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/ [...] new 1e9373cd8b7 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/ [...] new a40e8f7eb41 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/ [...] new 1ca57ab60e2 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/ [...] new d168f3e264e 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/ [...] new d5503a3720d 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 [...] new 21bb5fe8eff 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-2 [...] new 4b5dbfb543f 124: onsuccess: #2159: 1: Success after linux: 23 commits new 3c8b0b89025 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/ [...] new 132a3646f17 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-2 [...] new f82f0629da2 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 11c554e54a5 128: onsuccess: #2163: 1: Success after linux: 23 commits new 6fc779f133c 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/ [...] new 7409722f084 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 3 [...] new 8a3d0627f8f 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 1 [...] new eb345a45b5a 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/ [...] new 748b4579165 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/ [...] new f6363716df5 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 1 [...] new 45bdd10f190 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new aa7cf6f7cd3 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qe [...] new a1a93df2e2e 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/ [...] new 4c0c6b055e5 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 [...] new eee46af5bdf 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 1 [...] new 177a3f722ff 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/ [...] new ee98f8f027f 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 [...] new 0a863f024fb 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 8fa95d6b114 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qe [...] new 813bfe4b773 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/ [...] new 74cd52fa56d 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/ [...] new b3662d079b6 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 0dd3fc20f6e 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 1 [...] new c79ff39c41e 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 [...] new f1fa2dafa32 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/ [...] new 36a08ab901e 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 0f976413000 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 3fcac391c8a 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 [...] new 107e8a430fa 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 [...] new 01a418c495b 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 1 [...] new ef2ce4809c8 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/ [...] new 6b9f25bd7d3 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/ [...] new 349bc35940b 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 [...] new b621cb7fdc4 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/ [...] new ff1d6a94e7a 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 19 [...] new 8eaf39039fc 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/ [...] new 08d1b7e3a4a 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/ [...] new a2daf405875 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/ [...] new 6b14d40ec2e 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/ [...] new 13d0309a67c 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/ [...] new 2cdbc21d36f 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 8617e314fee 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new b30aa8ed548 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qem [...] new 5f601c6dd64 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/ [...] new 8e4d6906938 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/ [...] new c3260ae7ec9 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/ [...] new 405c2a64df0 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/ [...] new 2bdea3a95bf 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] new 0f1ed9a6141 173: onsuccess: #2208: 1: Success after gcc: 10 commits new 2df7e2cf192 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 2 [...] new 0c1a27a7ad8 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] new 638b6995b23 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] new 3edcff888f4 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new 0f9b652fbe0 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] new 1950db90dac 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/ [...] new aa3dc84c21b 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/ [...] new bdad810fb2d 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/ [...] new 1ff1a7ecb71 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/ [...] new 7dfd521236b 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/ [...] new 2349183476c 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/ [...] new 9a2bd22a713 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/ [...] new b85c074263d 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/ [...] new 3250cdf97cf 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/ [...] new 44e5eaacae1 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/ [...] new 57badff52d9 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/ [...] new ffcef0f78d4 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/ [...] new 12196dd4e65 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new a1bc21e7ac0 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/ [...] new 8ce1c39227d 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/ [...] new 9c0a0bf2e28 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/ [...] new 3148d3658bb 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/ [...] new aea90c8abf2 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 4 [...] new 86637352482 197: onsuccess: #2348: 1: Success after linux: 190 commits new 3d85899d641 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/ [...] new bfde681c6eb 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/ [...] new 24732e5dbb8 200: onsuccess: #2427: 1: Success after binutils: 274 commits new ed4488400d8 201: onsuccess: #2430: 1: Success after glibc: 26 commits new a123055250a 202: onsuccess: #2431: 1: Success after linux: 944 commits new 59ff715556a 203: onsuccess: #2433: 1: Success after binutils: 27 commits new 566df4736d4 204: onsuccess: #2435: 1: Success after linux: 3 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 (96c5f9ac6d9) \ 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 1752 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 32308 -> 32132 bytes 04-build_abe-stage1/console.log.xz | Bin 73068 -> 72616 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8528 -> 8704 bytes 07-build_abe-glibc/console.log.xz | Bin 244772 -> 245184 bytes 08-build_abe-stage2/console.log.xz | Bin 204108 -> 204152 bytes 09-build_abe-gdb/console.log.xz | Bin 38040 -> 37984 bytes 10-build_abe-qemu/console.log.xz | Bin 32196 -> 32188 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3960 -> 3948 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2664 -> 2692 bytes 13-check_regression/console.log.xz | Bin 5404 -> 5564 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 103 +- 13-check_regression/results.compare | 51 +- 13-check_regression/results.compare2 | 48 +- 13-check_regression/results.regressions | 41 + 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 105 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 41 + sumfiles/g++.log.xz | Bin 3453388 -> 3456844 bytes sumfiles/g++.sum | 222 +- sumfiles/gcc.log.xz | Bin 3035492 -> 3042844 bytes sumfiles/gcc.sum | 5243 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1038048 -> 1030800 bytes sumfiles/gfortran.sum | 98 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 213460 -> 213660 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2704 -> 2700 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 433688 -> 429980 bytes sumfiles/libstdc++.sum | 20 +- 41 files changed, 3067 insertions(+), 3034 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