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 0e0ee1a67b 261: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 3b271feb37 260: onsuccess: #66: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards e7577fa120 259: onsuccess: #65: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 1dac171be1 258: onsuccess: #64: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards b82e1d0cfb 257: onsuccess: #63: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards c1b2a29710 256: force: #62: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 273602eb36 255: force: #61: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 71b5beea01 254: onsuccess: #58: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 627b54fb76 253: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 12fea2c0a6 252: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards f5eafbb71d 251: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 5ceba146a4 250: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 8a1a57227e 249: onsuccess: #52: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 9b4f7b0337 248: onsuccess: #51: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 1008f05682 247: onsuccess: #50: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 102014abe3 246: onsuccess: #49: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 84977f3025 245: onsuccess: #48: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards d5ee7ffa16 244: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 1982e390bf 243: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 664d7f7e72 242: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards e687f44b9f 241: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards ee5e298d68 240: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 873ac63794 239: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards e8d3d3433b 238: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 20b8223f7e 237: onsuccess: #38: 1: [TCWG CI] Success after binutils/gcc [...] discards b2c1b3c554 236: onsuccess: #37: 1: [TCWG CI] Success after binutils/gcc [...] discards e7772d228a 235: onsuccess: #36: 1: [TCWG CI] Success after binutils/gcc [...] discards 30d9ad01c5 234: onsuccess: #35: 1: [TCWG CI] Success after binutils/gcc [...] discards 59fc5e8c9b 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/gcc [...] discards acc28ddef0 232: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 74917e870a 231: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards cb6496509c 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 15582a0d00 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards caf4d4e112 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] discards 8d5d3a1b8f 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 85d21f66a1 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards ddaae1cfba 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] discards c4eb002b6f 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] discards 8a00889ec8 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 7a1a5d1329 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 99463dbcac 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gdb [...] discards 8ccb7603c6 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] discards 6a661dd124 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 00b88aa008 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards aaa63a9a3d 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 924e60c662 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 6b55078d0b 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards c750ae4e9e 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards c6ea631fd2 213: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] discards 138814fe5d 212: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 135ef035bd 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards 8106da2f96 210: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards d4921a01e3 209: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 4f3344115a 208: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards 5abbfc202c 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb: [...] discards 742d5803f8 206: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 0ea9931bf9 205: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 5f4aa8b499 204: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] discards 1c6005cb2b 203: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards 75a78560cb 202: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] discards 5d6282748b 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] discards 3c17159b62 200: onsuccess: #663: 1: Success after binutils/gcc/linux/gl [...] discards 8b84cb1b3e 199: onsuccess: #662: 1: Success after binutils/gcc/linux/gl [...] discards 35f695dce2 198: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards da30865f4e 197: onsuccess: #660: 1: Success after binutils/gcc/linux/gl [...] discards 0f1b889e88 196: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards ce400e3696 195: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards 6cbb3104f6 194: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards eae63b7bc7 193: onsuccess: #655: 1: Success after binutils/gcc/linux/gd [...] discards 1bb42f7d4a 192: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards 2f6e86f2ee 191: onsuccess: #653: 1: Success after binutils/gcc/linux/gl [...] discards 68d574c1ad 190: onsuccess: #652: 1: Success after binutils/gcc/linux/gl [...] discards 20886bd24f 189: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 3229a23dce 188: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards 42c386ce24 187: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 31bed54ea9 186: onsuccess: #648: 1: Success after binutils/gcc/linux/gd [...] discards b549440d5b 185: onsuccess: #647: 1: Success after binutils/gcc/linux/gd [...] discards 0d67d379fc 184: onsuccess: #646: 1: Success after binutils/gcc/linux/gl [...] discards 58bdeb5ddc 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 203 [...] discards a89e38551d 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 commits discards 9e1157961b 181: onsuccess: #643: 1: Success after binutils/gcc/linux/gl [...] discards 7d13ca4242 180: onsuccess: #642: 1: Success after binutils/gcc/linux/gl [...] discards 57cc927440 179: onsuccess: #641: 1: Success after binutils/gcc/linux/gd [...] discards e4f05a4311 178: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] discards b07ddf67a1 177: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] discards 07cec49f64 176: onsuccess: #638: 1: Success after binutils/gcc/linux/gd [...] discards ef46eca2c8 175: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] discards e10a26e2e4 174: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] discards 8efea24f89 173: onsuccess: #635: 1: Success after binutils/gcc/linux/gl [...] discards c426ca0bb5 172: onsuccess: #634: 1: Success after binutils/gcc/linux/gd [...] discards f50bc534e4 171: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards 49ae67e4d4 170: onsuccess: #632: 1: Success after binutils/gcc/linux/gl [...] discards e60d1f5083 169: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards 034a18fc2e 168: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards a769d4af2c 167: onsuccess: #629: 1: Success after binutils/gcc/linux/gd [...] discards eacf397949 166: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards 78eb3a2788 165: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] discards 1ea8fd876d 164: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 8b49713a96 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/gd [...] discards 6e3f7b12a6 162: onsuccess: #624: 1: Success after linux: 10 commits discards 6d88d378bd 161: onsuccess: #623: 1: Success after glibc: 9 commits new 6b427a742e 161: onsuccess: #623: 1: Success after glibc: 9 commits new f68433c1c0 162: onsuccess: #624: 1: Success after linux: 10 commits new c8a38f4ba3 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/gd [...] new 81fe92ac54 164: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new a35d85d834 165: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] new 6d4e7895b5 166: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 233c8cc025 167: onsuccess: #629: 1: Success after binutils/gcc/linux/gd [...] new 51e32a87da 168: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new 9fbf023b0f 169: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new a47102372a 170: onsuccess: #632: 1: Success after binutils/gcc/linux/gl [...] new 0f61d6b16a 171: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new 2ddde45de5 172: onsuccess: #634: 1: Success after binutils/gcc/linux/gd [...] new 58252d94ec 173: onsuccess: #635: 1: Success after binutils/gcc/linux/gl [...] new e2e4d807f1 174: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] new af6bbf8613 175: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] new 871211327d 176: onsuccess: #638: 1: Success after binutils/gcc/linux/gd [...] new 74bf53443b 177: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] new e6e62a0a67 178: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] new 8c9d4dc915 179: onsuccess: #641: 1: Success after binutils/gcc/linux/gd [...] new bd764c2664 180: onsuccess: #642: 1: Success after binutils/gcc/linux/gl [...] new 164d3cf0a3 181: onsuccess: #643: 1: Success after binutils/gcc/linux/gl [...] new 6506046e5f 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 commits new ea4ce08dd8 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 203 [...] new 61a924b89e 184: onsuccess: #646: 1: Success after binutils/gcc/linux/gl [...] new 69b2bf8a0e 185: onsuccess: #647: 1: Success after binutils/gcc/linux/gd [...] new cf6e8ca701 186: onsuccess: #648: 1: Success after binutils/gcc/linux/gd [...] new 71c974a254 187: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new 24285a3cb4 188: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new aa0f6d57bc 189: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new cb879fcd07 190: onsuccess: #652: 1: Success after binutils/gcc/linux/gl [...] new 320daa96ce 191: onsuccess: #653: 1: Success after binutils/gcc/linux/gl [...] new aeb83a0cea 192: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new 798d809758 193: onsuccess: #655: 1: Success after binutils/gcc/linux/gd [...] new b9426bd172 194: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new 57f21ee16b 195: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new 012e86e714 196: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 08f43204aa 197: onsuccess: #660: 1: Success after binutils/gcc/linux/gl [...] new 9f5ee2d924 198: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new 03334f0bee 199: onsuccess: #662: 1: Success after binutils/gcc/linux/gl [...] new bc815ea03f 200: onsuccess: #663: 1: Success after binutils/gcc/linux/gl [...] new 35361bce85 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new d126f97d5b 202: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] new c71ff37158 203: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new 3e7543a652 204: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] new 3c66f29cf6 205: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 6b9dbdf466 206: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new e0d9edf775 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb: [...] new 17bf0fb1f7 208: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new de2d0c1852 209: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 835e51b012 210: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 3e4aa45273 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new 0e216d9dcd 212: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new a9f79b44ba 213: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] new 0b578be2db 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new a173f53a86 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 420f906d30 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new b973d3a19f 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new a5255687e8 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new 6f08f82ad7 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 767f96d5b1 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] new f757dbdcd9 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gdb [...] new 96a78ee6be 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new fa9219c456 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new cdd493a75b 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] new cd5c7b7b2a 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] new e5e3461314 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new 9aacec2372 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 3ea40a6d90 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new ac54a4eb7f 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 25ad57fdec 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 5d8abe5c97 231: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new c8f05380f0 232: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 27fb4669eb 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/gcc [...] new 7fe2b48980 234: onsuccess: #35: 1: [TCWG CI] Success after binutils/gcc [...] new 6179ab5e07 235: onsuccess: #36: 1: [TCWG CI] Success after binutils/gcc [...] new 3ea2879355 236: onsuccess: #37: 1: [TCWG CI] Success after binutils/gcc [...] new 0ac7ae8c1c 237: onsuccess: #38: 1: [TCWG CI] Success after binutils/gcc [...] new e4b7cdf1eb 238: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 9cce503e43 239: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 25f34207b4 240: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 153401b617 241: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 5b906b2bbe 242: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 66b6f57ae8 243: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new ce8d5f65e3 244: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 95ab49b6ef 245: onsuccess: #48: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 47583ee4d8 246: onsuccess: #49: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 85bf5311e0 247: onsuccess: #50: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 232f79b584 248: onsuccess: #51: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 180ab2adf0 249: onsuccess: #52: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 4cea56ac09 250: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 80d17b4b77 251: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 8e72ef88c3 252: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new e5ef8f33d9 253: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 5e9a7cbdb0 254: onsuccess: #58: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 5ac25d3bb4 255: force: #61: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 5d364ab54f 256: force: #62: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 18644c8e8d 257: onsuccess: #63: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 9dc9e10dc2 258: onsuccess: #64: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 596deb5c09 259: onsuccess: #65: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new c810eacd31 260: onsuccess: #66: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 6c3241e8a1 261: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new d1e8cadba9 262: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...]

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 (0e0ee1a67b) \ 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: 00-sumfiles/g++.log.xz | Bin 2881128 -> 2895348 bytes 00-sumfiles/gcc.log.xz | Bin 2519484 -> 2518548 bytes 00-sumfiles/gfortran.log.xz | Bin 962604 -> 962080 bytes 00-sumfiles/libatomic.log.xz | Bin 2284 -> 2284 bytes 00-sumfiles/libgomp.log.xz | Bin 233908 -> 234036 bytes 00-sumfiles/libitm.log.xz | Bin 2696 -> 2692 bytes 00-sumfiles/libstdc++.log.xz | Bin 479428 -> 479348 bytes 01-reset_artifacts/console.log.xz | Bin 2204 -> 2212 bytes 02-prepare_abe/console.log.xz | Bin 2448 -> 2460 bytes 03-build_abe-binutils/console.log.xz | Bin 49080 -> 49196 bytes 04-build_abe-gcc/console.log.xz | Bin 235276 -> 235040 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8588 -> 8764 bytes 07-build_abe-glibc/console.log.xz | Bin 233832 -> 232544 bytes 08-build_abe-gdb/console.log.xz | Bin 47636 -> 46904 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3808 bytes 10-build_abe-check_gcc/console.log.xz | Bin 7724 -> 7636 bytes 10-build_abe-check_gcc/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 1664 -> 1280 bytes 11-check_regression/results.compare | 18 ++++----- 11-check_regression/results.compare2 | 57 ++++----------------------- 12-update_baseline/console.log | 72 +++++++++++++++++----------------- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 18 ++++----- manifest.sh | 32 +++++++-------- sumfiles/g++.sum | 2 +- sumfiles/gcc.sum | 2 +- sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.sum | 2 +- sumfiles/libitm.sum | 2 +- 36 files changed, 90 insertions(+), 133 deletions(-)