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_gdb/master-arm in repository toolchain/ci/base-artifacts.

discards d1cb4adf5d 254: onsuccess: #132: 1: [TCWG CI] Success after gdb: 2 commits discards 10628921d6 253: force: #131: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards 1a1d9d3469 252: force: #130: 1: [TCWG CI] Success after gdb: 15 commits discards 23704d3435 251: onsuccess: #129: 1: [TCWG CI] Success after linux: 121 commits discards 4e8470f4ea 250: onsuccess: #128: 1: [TCWG CI] Success after glibc: 2 commits discards c94642aaab 249: onsuccess: #127: 1: [TCWG CI] Success after gcc: 98 commits discards a6cfe7425f 248: onsuccess: #121: 1: [TCWG CI] Success after binutils/gc [...] discards 1e04421c12 247: force: #120: 1: [TCWG CI] Success after baseline build: [...] discards 07bb5bf151 246: onsuccess: #118: 1: [TCWG CI] Success after glibc: 7 commits discards eb2252778a 245: onsuccess: #117: 1: [TCWG CI] Success after gcc: 16 commits discards df919a8e10 244: onsuccess: #112: 1: [TCWG CI] Success after binutils/gc [...] discards 3b8d6f4e65 243: onsuccess: #111: 1: [TCWG CI] Success after binutils/gc [...] discards cdc272969b 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits discards 95c0eacaf1 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/gc [...] discards 04cb169312 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/gc [...] discards a6e72f5a00 239: force: #106: 1: [TCWG CI] Success after baseline build: [...] discards 854b6c99a6 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards 360d9612d5 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits discards 3ddeb5a43e 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 22 [...] discards f704a6c0e0 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards 7991046c6e 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards fb238b6d4b 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards e9b8abe42a 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 5010d41529 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits discards a56ef7a854 230: onsuccess: #78: 1: Success after gdb: 2 commits discards e3e9fc8b30 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g4 [...] discards 9cd1374fdd 228: force: #74: 1: Success after gdb: 53 commits discards f5ca058af8 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 95d464ba7a 226: force: #70: 1: Success after baseline build: no new commits discards 840b367e43 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g4 [...] discards 3a7936d10c 224: force: #65: 1: Success after gdb: 50 commits discards 07f232000a 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g2 [...] discards ab8de2012c 222: force: #60: 1: Success after gdb: 16 commits discards 43c97628a3 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g6 [...] discards 481e8cd294 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02ddb [...] discards b617e9b159 219: force: #50: 1: Failure after linux: 2520 commits discards f8098364c4 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g3 [...] discards 130e77ae7e 217: force: #45: 1: Success after linux: 1 commits discards 0c37abf0ec 216: force: #43: : Failure after baseline build: no new commits discards a68f4ee3b4 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g1 [...] discards f2380d92e3 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g1 [...] discards 9c2cac765b 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 271f099dff 212: force: #27: : Failure after baseline build: no new commits discards 2332086def 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 55bafa087f 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 3d26cf621c 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 372cdfecf7 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 597397faeb 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 0b2b34aa7d 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards d5ab65087b 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards ce6e2876ef 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards b775edca73 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 57693c8562 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards a3c5c07e2c 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 7e84b8fae6 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 68becb9b01 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards a13b33795f 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards c7988f7365 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards f26fea9ac8 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 40d1eeb82c 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 3b8c7b90fe 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 91601c4fd9 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards f48784fbac 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards 95bf489b80 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] discards 3e9cfe0603 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards eb97b0790c 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] discards 6ef402ec0a 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] discards 21bfe3f137 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] discards 6ebeace7a9 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] discards 040d137592 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] discards 36ca4dc238 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] discards 6d409ab4c5 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] discards 0da53ef74f 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] discards 2fa9d3d33c 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards 1eeb4621e2 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] discards 564e92cc0f 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] discards 44df017d43 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] discards aa81b289b7 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] discards 52bae7b828 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] discards 0a57180077 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards 1068fbc38d 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards 5ffb263078 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] discards 92ffc99b3a 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] discards 3baff1ac39 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards 1747dcc1b7 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] discards adaa8d7214 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards f832ec949c 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards 73cff71471 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards 8bbdfc2eec 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards 0c356b2641 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards ef0f6ad494 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] discards e888471c0f 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards a2db62ba4e 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards 453acd8375 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] discards bc9f3deb96 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards c1e7092a48 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards 6bff4b0bb4 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards d56e4a54a2 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 9ace95be01 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards 5daa977086 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 43d3d85b52 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] new 3318eb9e45 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] new d4d4ea92bd 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new cb573ed214 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 5f3fa9da73 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new f33ca05f6b 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new d0538719f6 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 28d5403f4c 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new c102170e11 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] new 1296c3ea0f 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new 88ef098a55 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new 81fc8d7545 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] new c4c8fadfa9 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 5c564f3f18 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new 11436dd899 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new 0abdc6f75f 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new 844c8b85a0 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new fc030a3036 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] new 4a4f67c710 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new fb08eba9df 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] new 3277c50c41 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] new 692d7352ee 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new 3a330fd224 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new 9874a220f8 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] new 452888d91f 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] new 53c3a4860d 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] new a23babe28d 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] new 64ce00fb8c 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] new dbde251c9b 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 91c89d1bf0 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] new 9d3993360e 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] new cfc0349e4d 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] new b18c983be1 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] new 589cc636a5 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] new 1d1c8c8ac2 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] new df8f8c225b 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] new 1c4197f6ac 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] new f1e74a4d2c 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new 8a3217bb43 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] new b94d74af11 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new 0ee4a2375e 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new c48e3217ba 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 3f01eff9e2 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new d64f3abf9a 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 7d00f8e1a8 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 0ca143acd1 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new a1bdd9876d 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 34cfcc5bd0 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 90304f44c0 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 0ab634815f 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 9f0d5dff43 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new a7ca11b15d 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 5d49c232ec 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 7b2f11349c 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new fb9dbe955a 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 7ecc0dd9d0 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new ab5f877742 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 7c8167fb6e 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 280a71b023 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 1ca822ccdf 212: force: #27: : Failure after baseline build: no new commits new b63eadfdfa 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 3239716bf2 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g1 [...] new d34374fb55 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g1 [...] new 2ce27be6f9 216: force: #43: : Failure after baseline build: no new commits new 9b55bee159 217: force: #45: 1: Success after linux: 1 commits new 444f3816c8 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g3 [...] new d53381e569 219: force: #50: 1: Failure after linux: 2520 commits new c8ae5546a4 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02ddb [...] new 072a6bcc73 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g6 [...] new 62f7da3f3c 222: force: #60: 1: Success after gdb: 16 commits new d121eff69a 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g2 [...] new 5c9f152eea 224: force: #65: 1: Success after gdb: 50 commits new d8c3afd50c 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g4 [...] new 960bbf6d07 226: force: #70: 1: Success after baseline build: no new commits new 900eab3c7e 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new a21effa4c5 228: force: #74: 1: Success after gdb: 53 commits new f90bdc15f8 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g4 [...] new 58dcb71c90 230: onsuccess: #78: 1: Success after gdb: 2 commits new b74bdf65ba 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits new 3961cca968 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new ea10f0df8e 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new da7083a50f 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new 0fcc2a04f4 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new d9488e9cff 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 22 [...] new 241b887af5 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits new 0ceffd5720 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new 4a0ddcb479 239: force: #106: 1: [TCWG CI] Success after baseline build: [...] new 777061335a 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/gc [...] new f5f0b2cc15 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/gc [...] new 01ac0e444c 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits new 4def15164c 243: onsuccess: #111: 1: [TCWG CI] Success after binutils/gc [...] new 074aac18b7 244: onsuccess: #112: 1: [TCWG CI] Success after binutils/gc [...] new 440e252951 245: onsuccess: #117: 1: [TCWG CI] Success after gcc: 16 commits new 8153b407e2 246: onsuccess: #118: 1: [TCWG CI] Success after glibc: 7 commits new 90f54dfa5a 247: force: #120: 1: [TCWG CI] Success after baseline build: [...] new 56f026dc95 248: onsuccess: #121: 1: [TCWG CI] Success after binutils/gc [...] new 196ac38a10 249: onsuccess: #127: 1: [TCWG CI] Success after gcc: 98 commits new 3e91b6a1fa 250: onsuccess: #128: 1: [TCWG CI] Success after glibc: 2 commits new 1841dbe0fc 251: onsuccess: #129: 1: [TCWG CI] Success after linux: 121 commits new 22cea666f8 252: force: #130: 1: [TCWG CI] Success after gdb: 15 commits new 4b6121e2e7 253: force: #131: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new 1919951ac6 254: onsuccess: #132: 1: [TCWG CI] Success after gdb: 2 commits new 1e310f7695 255: force: #133: 1: [TCWG CI] Success after baseline build: [...]

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 (d1cb4adf5d) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/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 2020 -> 2044 bytes 02-prepare_abe/console.log.xz | Bin 2532 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 49664 -> 49428 bytes 04-build_abe-gcc/console.log.xz | Bin 235996 -> 234428 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8624 -> 8660 bytes 07-build_abe-glibc/console.log.xz | Bin 232772 -> 232212 bytes 08-build_abe-gdb/console.log.xz | Bin 46512 -> 46796 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3808 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4448 -> 4592 bytes 11-check_regression/console.log.xz | Bin 4032 -> 2472 bytes 11-check_regression/results.compare | 18 +- 11-check_regression/results.compare2 | 119 +-------- 12-update_baseline/console.log | 54 ++-- dashboard/dashboard-generate.sh | 2 +- mail/changes-list-long.txt | 4 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 20 +- manifest.sh | 17 +- sumfiles/gdb.log.0.xz | Bin 2890712 -> 2898648 bytes sumfiles/gdb.log.1.xz | Bin 138404 -> 143344 bytes sumfiles/gdb.log.10.xz | Bin 0 -> 9864 bytes sumfiles/gdb.log.11.xz | Bin 0 -> 9988 bytes sumfiles/gdb.log.12.xz | Bin 0 -> 9860 bytes sumfiles/gdb.log.2.xz | Bin 15212 -> 19448 bytes sumfiles/gdb.log.3.xz | Bin 10072 -> 9888 bytes sumfiles/gdb.log.4.xz | Bin 9764 -> 10148 bytes sumfiles/gdb.log.5.xz | Bin 9972 -> 9900 bytes sumfiles/gdb.log.6.xz | Bin 10068 -> 9916 bytes sumfiles/gdb.log.7.xz | Bin 10136 -> 9944 bytes sumfiles/gdb.log.8.xz | Bin 10120 -> 10084 bytes sumfiles/gdb.log.9.xz | Bin 10012 -> 9948 bytes sumfiles/gdb.sum | 23 +- sumfiles/gdb.sum.0 | 29 ++- sumfiles/gdb.sum.1 | 450 ++++++++++++++++++++++------------ sumfiles/{gdb.sum.8 => gdb.sum.10} | 17 +- sumfiles/{gdb.sum.7 => gdb.sum.11} | 19 +- sumfiles/{gdb.sum.6 => gdb.sum.12} | 20 +- sumfiles/gdb.sum.2 | 233 +++++++++++++----- sumfiles/gdb.sum.3 | 14 +- sumfiles/gdb.sum.4 | 42 +++- sumfiles/gdb.sum.5 | 68 +---- sumfiles/gdb.sum.6 | 33 ++- sumfiles/gdb.sum.7 | 56 ++--- sumfiles/gdb.sum.8 | 27 +- sumfiles/gdb.sum.9 | 58 ++++- 46 files changed, 725 insertions(+), 600 deletions(-) create mode 100644 sumfiles/gdb.log.10.xz create mode 100644 sumfiles/gdb.log.11.xz create mode 100644 sumfiles/gdb.log.12.xz copy sumfiles/{gdb.sum.8 => gdb.sum.10} (99%) copy sumfiles/{gdb.sum.7 => gdb.sum.11} (99%) copy sumfiles/{gdb.sum.6 => gdb.sum.12} (99%)