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 1dd450c2ce8 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards e94590712f6 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 3b4568fd7b0 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] discards 7a9a3688307 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards e75ece85b14 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 99275e3e0ef 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards c2eabd0481c 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 272c4eb97c9 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards fe05529bc1a 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 30277fa674f 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards bfba3c08960 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] discards 0948f813ce4 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards c92eb3b9ed1 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards c039be724a7 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards d308831038e 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards ae90ebc512b 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 43ff048c4b9 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] discards 9bcb7aba988 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 8c37adb2a1a 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards c8c7263767c 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards e02d23ec5d6 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 927e5f86ec9 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 667a68aa205 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 45b3e6bd8a7 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 82521605e6a 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 97ff58700ec 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 2ecfbc9d9d7 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 30562c0e053 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 5602d749c62 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 214141c63da 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards d261fefe830 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 1588343fb2a 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 142910dd5f3 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 5bd14a66e81 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 1ddecba8948 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards f353798c2da 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 248a05b9447 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards efba8e5f5e0 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 4aefe0c7d76 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 9c2fd1f5851 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] discards bae6c52233d 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] discards d3962f34350 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] discards 28e30f9ec1b 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 9f4a783d2d2 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards d5ac15c2fa0 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards a32d0f269fe 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 112174d4f30 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 191487bf84b 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 1426fb4af56 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards b0853fb2ad6 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards f85f858756e 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 7b5d09bc756 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards f1ec5cfaa27 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 9921f673c83 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] discards a7173375805 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 61088a58155 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards cd2b51f981a 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 0e0756ed483 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards a5a00bb5511 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 873e75be9a3 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards c8c9c90772b 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] discards ff0b2bb86e3 162: onsuccess: #624: 1: Success after linux: 10 commits discards c64ffc29cf9 161: onsuccess: #623: 1: Success after glibc: 9 commits discards 8f9fc832434 160: onsuccess: #621: 1: Success after gcc: 11 commits discards bffcf1b9633 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 4c9c050f425 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards d0c65817654 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 7c9d628bfbb 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards a39c66e3cf9 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 4a1bc64dddf 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] discards 1cd0321e212 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] discards d41153dbba3 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] discards f9cbb2c0170 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 4faf5536884 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 64b2b02b209 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 4777afde368 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 5e5230b685e 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards de40426b303 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards aaa5239b48d 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 7cd64ab1173 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] discards 3d27b53d3f6 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 56a41c2b492 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards ea98a1bec4f 141: onsuccess: #601: 1: Success after linux: 794 commits discards 041851a1a6e 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 4e2b110ea42 139: onsuccess: #599: 1: Success after binutils: 10 commits discards 2760b5f4abc 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 46ec225dc59 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards e113a165873 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 657ae8d88c4 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards accc204209b 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 4b16e0ca744 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 496bddbe3e8 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 55ec7dea78c 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 5b16d51db8f 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards e8fc4fc6b2f 129: onsuccess: #588: 1: Success after linux: 4 commits discards 540551faade 128: onsuccess: #586: 1: Success after binutils: 22 commits discards 1c8fa199d44 127: onsuccess: #584: 1: Success after linux: 21 commits discards e9d0e19e197 126: onsuccess: #582: 1: Success after gcc: 9 commits discards 4c9fd078263 125: onsuccess: #581: 1: Success after binutils: 4 commits discards a50ece7f311 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards 823fc82ff67 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] new 36cf95c91ce 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] new 416405df1f6 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new 839bd96310a 125: onsuccess: #581: 1: Success after binutils: 4 commits new 47ffcd92972 126: onsuccess: #582: 1: Success after gcc: 9 commits new 0fce03a6d29 127: onsuccess: #584: 1: Success after linux: 21 commits new fd499531662 128: onsuccess: #586: 1: Success after binutils: 22 commits new 327edbf3d7b 129: onsuccess: #588: 1: Success after linux: 4 commits new 879eb8297da 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 13a033dc258 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 55655a0a99d 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 2e7373f2aa5 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new b2fdafd7e74 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 83872d7cf5f 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 98c8346961b 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new d60936a1b21 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 14aa0ffc5a8 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 7938f9c60b0 139: onsuccess: #599: 1: Success after binutils: 10 commits new dd0844a7407 140: onsuccess: #600: 1: Success after gcc: 23 commits new 3771d2600fb 141: onsuccess: #601: 1: Success after linux: 794 commits new 0f7bf2e1b06 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 8bf5afae346 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 386d9efd347 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] new 55e2f5a0982 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new f07b18ca1b9 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new a84c0801081 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 0bcd1ba5d97 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new c363ca3fb83 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new ad8ad714176 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new dda41f372e9 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 0ade9b61d9b 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] new 9986fcc1c81 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] new 5f42f799659 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] new 353f117449b 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 9717cbedb50 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 38f32c4b220 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new bed21b29ed3 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 279a16dd072 159: onsuccess: #620: 1: Success after binutils: 12 commits new 2efe18ce2f6 160: onsuccess: #621: 1: Success after gcc: 11 commits new de0882c8973 161: onsuccess: #623: 1: Success after glibc: 9 commits new c24e61cac1e 162: onsuccess: #624: 1: Success after linux: 10 commits new 8f06035bc22 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] new be948348c18 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 1915295aa61 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 806a5e08602 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 0030b54f92e 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new d7679794bab 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new bcd5bb2c8c3 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new c1097a1735e 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] new 3a6fc9193a5 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new de653d9f6c8 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 36a63586a5a 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 1184e09a5f0 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 4726d48c68b 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 9c361e80c5a 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 9730829275e 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new c807a12e194 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 02e272388d0 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new a6dea916dce 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new c71028aba69 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new c35075da0ba 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] new 7ee23980e48 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] new 48cbc18d279 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] new 311fa4f09a6 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 1b40efaac74 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new d718d5ebd12 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 8f508d2f806 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new cb6275697aa 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 57e4c678335 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new ca13cf83326 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new ec76eb35ffb 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 81ac52d7efa 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new abc74fdcfb9 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 5b117a27f67 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new b30dbd3a6fd 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 6170a63d94c 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 1f063b8567f 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 3b47b4e2093 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 5784d49d295 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 8b63d7bca9b 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new ff98bf20959 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new bc13254ed70 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 77e9dab8637 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new cf75e581aef 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 44abc7bc99c 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 8c69fc72510 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] new e57f54f1611 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 27967a7ac91 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new bde9de2ec1e 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 66567442aa9 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 682a7d5bef6 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new b7c34cc5f03 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] new 0bd382ef63d 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 4e801db61f0 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 7ab497e3d91 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new ee3360b6e64 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 44a721d9b0a 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 371173b0332 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 5dd254efbf1 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new 6ec5f7264d7 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] new 6201b197191 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 72ee566fe0a 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new c0524872d36 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...]

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 (1dd450c2ce8) \ 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 1756 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 3444 bytes 03-build_abe-binutils/console.log.xz | Bin 52912 -> 52780 bytes 04-build_abe-gcc/console.log.xz | Bin 239128 -> 238020 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8640 -> 9048 bytes 07-build_abe-glibc/console.log.xz | Bin 237464 -> 235800 bytes 08-build_abe-gdb/console.log.xz | Bin 51628 -> 50296 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3792 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2956 -> 9508 bytes 11-check_regression/console.log.xz | Bin 7216 -> 6288 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 9 + 11-check_regression/mail-body.txt | 43 +- 11-check_regression/results.compare | 36 +- 11-check_regression/results.compare2 | 211 +- .../{mail-body.txt => results.regressions} | 44 +- 12-update_baseline/console.log | 50 +- 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 | 45 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 29 + sumfiles/g++.log.sep.xz | Bin 0 -> 82832 bytes sumfiles/g++.log.xz | Bin 2890876 -> 2913932 bytes sumfiles/g++.sum | 188 +- sumfiles/g++.sum.sep | 6610 ++++++++++++++++++++ sumfiles/gcc.log.sep.xz | Bin 0 -> 74636 bytes sumfiles/gcc.log.xz | Bin 2472616 -> 2459192 bytes sumfiles/gcc.sum | 352 +- sumfiles/gcc.sum.sep | 1197 ++++ sumfiles/gfortran.log.sep.xz | Bin 0 -> 25860 bytes sumfiles/gfortran.log.xz | Bin 957292 -> 953864 bytes sumfiles/gfortran.sum | 38 +- sumfiles/gfortran.sum.sep | 1391 ++++ sumfiles/libatomic.log.xz | Bin 2276 -> 2276 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 233976 -> 234004 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2692 -> 2696 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.sep.xz | Bin 0 -> 13828 bytes sumfiles/libstdc++.log.xz | Bin 470568 -> 465792 bytes sumfiles/libstdc++.sum | 13 +- sumfiles/libstdc++.sum.sep | 16 + 51 files changed, 9817 insertions(+), 536 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum copy 11-check_regression/{mail-body.txt => results.regressions} (70%) create mode 100644 sumfiles/g++.log.sep.xz create mode 100644 sumfiles/g++.sum.sep create mode 100644 sumfiles/gcc.log.sep.xz create mode 100644 sumfiles/gcc.sum.sep create mode 100644 sumfiles/gfortran.log.sep.xz create mode 100644 sumfiles/gfortran.sum.sep create mode 100644 sumfiles/libstdc++.log.sep.xz create mode 100644 sumfiles/libstdc++.sum.sep