This is an automated email from the git hooks/post-receive script.

tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm in repository toolchain/ci/base-artifacts.

discards e3677ec6153 234: onsuccess: #35: 1: [TCWG CI] Success after binutils/gc [...] discards 869c40b9dbe 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/gc [...] discards 4f3e3027f8b 232: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] discards bf1a9fb8d00 231: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards 7fd14320708 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 48927ee63c4 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards eb98b68e5c4 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gl [...] discards 12d0086cd6a 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 1738d4a0087 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] discards 6fbe3e43ccd 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] discards 7fa2c011f50 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] discards e10e93ac16a 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 8175f5916e1 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards cf7565005ae 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] discards 432d51aac0b 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards 602c8956b23 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 34638025133 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards e19512078da 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 59d36a6d418 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 73ec540f7e6 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 314e16ddadf 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards a30c6137a97 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] discards 5131eb5afce 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards e6ff75dd73d 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 1f1055d92b1 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 29d2bc3a950 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards ce9db6ca480 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards c6af5bf6d1d 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] discards 93a50f536b9 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards d76a3e9da52 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards eb3d30040e9 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 7493f993411 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 397f7ad62a7 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 87fc6a54f97 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards bb6d94ffac0 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards bc0089b4860 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 78dc34da735 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 1958e3eea05 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 3a5c5b999ef 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 3e41c1d51f1 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards cd2d61b0de4 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards b7b9b88aba4 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 11418a350bd 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 7e407c7572d 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 1073babf435 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 42b1d95304e 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards dbc417538ef 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 3384df87a85 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 0e41f8feee3 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 49e21b51bfe 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 03e5a5e60dc 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] discards 49f826562a6 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] discards 82b057864d5 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] discards 159fef47084 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards c8c936ef27a 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 3091c27122c 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 24eac83f54c 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 606542c46be 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards f9ede1b7c6c 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards b88b1a39c02 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 3f632b2f411 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 2d610d86cbf 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards bfe8e3f50eb 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards f9d987f43df 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 167dc175e0a 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] discards 3d95f78b25f 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 3d87e3c3fab 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards 6cb9e6018db 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 5411af29ba6 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 006101b57cc 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards d73c4645efb 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 4b6e0a7f5bd 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] discards 7e296c913fd 162: onsuccess: #624: 1: Success after linux: 10 commits discards 83cdded6354 161: onsuccess: #623: 1: Success after glibc: 9 commits discards 5703f5c69ec 160: onsuccess: #621: 1: Success after gcc: 11 commits discards a25070d9c5a 159: onsuccess: #620: 1: Success after binutils: 12 commits discards ed418bdc6a5 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards cca8d074b61 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 0ba231548d9 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards de81e378d61 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 6d2f7a86636 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] discards a5ec309b078 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] discards 9718840f6b0 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] discards 022c177562a 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 55a5bff8056 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards b247b4d4475 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards c4be63bdeae 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards b0bc90fba15 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 6389151274e 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 6ec0b487f40 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 939be1e7c67 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] discards a8674163275 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 2765c62965b 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards b36ff458498 141: onsuccess: #601: 1: Success after linux: 794 commits discards a276bb420e5 140: onsuccess: #600: 1: Success after gcc: 23 commits discards c1ee1381508 139: onsuccess: #599: 1: Success after binutils: 10 commits discards f87ee20bb8c 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards f99826ab06a 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards bba67e9a46f 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 07827391d97 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 4f795db17e8 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 32cb350621c 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 69e3c03d8d9 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new bfe48a1da01 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new c58196750e0 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 924f2f28829 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 91d4aa47989 139: onsuccess: #599: 1: Success after binutils: 10 commits new 2452ec15bfe 140: onsuccess: #600: 1: Success after gcc: 23 commits new 2846746d1a5 141: onsuccess: #601: 1: Success after linux: 794 commits new 45346e3e1c9 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 382f562d3d4 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 0bca5b02127 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] new 8042bd3ceb7 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 80d68080a8f 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 852d99c1a54 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 78c40078902 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new e000600f24d 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 1085ea055cd 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new c120550a9f0 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new b3c85d2bda7 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] new a83c03ec3f7 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] new 7427dbfaf0b 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] new b89264ae2dc 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new f2b2ac17fbe 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new f78db754d34 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new eab0cbc0a66 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new ede9b8ede54 159: onsuccess: #620: 1: Success after binutils: 12 commits new 0aaaaa2c3ae 160: onsuccess: #621: 1: Success after gcc: 11 commits new e4cc66080e3 161: onsuccess: #623: 1: Success after glibc: 9 commits new 20544d61272 162: onsuccess: #624: 1: Success after linux: 10 commits new 3b5c75a14bf 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] new ed2d63f1c23 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new e39a932250e 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 548ab9fd198 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 1b2e3c006e8 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new cf49ad1fb5c 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 4bb4979ca91 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new b5c3823c67c 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] new 91c96d0592f 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new b7a2e151873 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 28024a36726 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new c23b9b15fa8 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new e812be0643a 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new d4513ab4ddb 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 3865bbe7415 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 767f1b979a4 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new dc8a327d31b 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new a76999544a5 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new c36ad3a62a6 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 9a00ae8f14b 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] new 145222bd201 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] new 22a6bd28fdb 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] new 80ea08917aa 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 845cba7390d 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new eeab58f76f8 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 3b35d78a681 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 6050ba87923 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new d6f4d3b9c0f 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new f475d20c4ab 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 2fe55345603 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 28c7b9ab32c 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 0c968301d3a 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 75ecfc11b37 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 14c5968497f 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 39f0ba1abfb 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 4e847c56ba8 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 861bd9bd001 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 2a4718df605 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new c4eb30138ba 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 37e986a844a 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 03242e9effd 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 1f5cf26b212 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 1cbc60a5b9c 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 90f5fc20877 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 9a4c35e5207 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] new dd10e820a44 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 97312ef1a07 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 1f9b1102975 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 360fc012584 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 718bedef2d0 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new f514a528daf 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] new 795fa31a09a 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new dc82e12fb9c 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new e984a0755e5 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new c27b81c15d8 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 9ccee14000d 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 7b502dca606 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 17f0504ce64 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new 8b0e88bc24d 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] new c26b242ebfb 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 2fcb33d0e00 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 38392b1129f 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] new d71493e57e3 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] new a0fc0a8595c 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] new c8e7e04d46a 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 4518d43015a 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gl [...] new c8f5e2468f1 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new cfdcaacce24 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 618e514fe07 231: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new 613e2d03f07 232: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] new 50e8aee765c 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/gc [...] new e7b000de2bd 234: onsuccess: #35: 1: [TCWG CI] Success after binutils/gc [...] new c4c0d05cc38 235: onsuccess: #36: 1: [TCWG CI] Success after binutils/gc [...]

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 (e3677ec6153) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...]

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 2052 -> 2060 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 49328 -> 48976 bytes 04-build_abe-gcc/console.log.xz | Bin 235020 -> 236504 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8380 -> 8684 bytes 07-build_abe-glibc/console.log.xz | Bin 231624 -> 232072 bytes 08-build_abe-gdb/console.log.xz | Bin 46592 -> 46236 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3772 bytes 10-build_abe-check_gcc/console.log.xz | Bin 11352 -> 9972 bytes 11-check_regression/console.log.xz | Bin 5364 -> 6376 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 18 + 11-check_regression/results.compare | 47 +- 11-check_regression/results.compare2 | 162 +- 11-check_regression/results.regressions | 38 + 12-update_baseline/console.log | 62 +- 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/changes-list-long.txt | 56 +- mail/changes-list-short.txt | 2 +- manifest.sh => mail/last_good.sh | 0 manifest.sh | 38 +- results | 38 + sumfiles/g++.log.sep.xz | Bin 97448 -> 57256 bytes sumfiles/g++.log.xz | Bin 2886288 -> 2886584 bytes sumfiles/g++.sum | 37 +- sumfiles/g++.sum.sep | 6524 ++++++++++++++++++++----------- sumfiles/gcc.log.sep.xz | Bin 70252 -> 95756 bytes sumfiles/gcc.log.xz | Bin 2516260 -> 2512344 bytes sumfiles/gcc.sum | 2 +- sumfiles/gcc.sum.sep | 5413 ++++--------------------- sumfiles/gfortran.log.sep.xz | Bin 14496 -> 24016 bytes sumfiles/gfortran.log.xz | Bin 960532 -> 956488 bytes sumfiles/gfortran.sum | 2 +- sumfiles/gfortran.sum.sep | 2359 ++++++----- sumfiles/libatomic.log.xz | Bin 2288 -> 2284 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 233752 -> 230804 bytes sumfiles/libgomp.sum | 27 +- sumfiles/libitm.log.xz | Bin 2684 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 6408 -> 16948 bytes sumfiles/libstdc++.log.xz | Bin 479240 -> 468488 bytes sumfiles/libstdc++.sum | 15 +- sumfiles/libstdc++.sum.sep | 441 ++- 50 files changed, 7022 insertions(+), 8276 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions copy manifest.sh => mail/last_good.sh (100%)