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

discards f7e365f5e3 245: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 091239d456 244: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 3cae55ad9f 243: onsuccess: #50: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards c2c7360cea 242: onsuccess: #49: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 82a1f22b65 241: onsuccess: #48: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards b65f237796 240: onsuccess: #47: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 58d946eb2a 239: onsuccess: #46: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 84942b550e 238: onsuccess: #45: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 125b0c34e8 237: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 4de2b8e67b 236: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 9f31b19055 235: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 646a039aa7 234: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards d617525222 233: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 970025fe7d 232: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards e12abda154 231: onsuccess: #38: 1: [TCWG CI] Success after binutils/gcc [...] discards 9e8b20a9d7 230: onsuccess: #37: 1: [TCWG CI] Success after binutils/gcc [...] discards fa8ead7860 229: onsuccess: #36: 1: [TCWG CI] Success after binutils/gcc [...] discards a9be537073 228: onsuccess: #35: 1: [TCWG CI] Success after binutils/gcc [...] discards 4b569bea64 227: onsuccess: #34: 1: [TCWG CI] Success after binutils/gcc [...] discards 4cfc15b6e0 226: onsuccess: #33: 1: [TCWG CI] Success after binutils/gcc [...] discards 117f49fd57 225: onsuccess: #32: 1: [TCWG CI] Success after binutils/gcc [...] discards 4d5abbe646 224: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 6f361f6460 223: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 34b2ad43bf 222: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards de6301ab5f 221: onsuccess: #27: 1: Success after binutils/gcc/linux/gli [...] discards 6ce2b22c13 220: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards 1bf49c42e2 219: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb [...] discards d7527480ea 218: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] discards 6ee1a4b3be 217: onsuccess: #22: 1: Success after binutils/gcc/linux/gdb [...] discards cf51806f0d 216: onsuccess: #21: 1: Success after binutils/gcc/linux/gdb [...] discards 49cb742a19 215: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 573754e981 214: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards a311e66d72 213: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 36506bac00 212: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards fe18dfb844 211: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 85432993cf 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 0329631841 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 456b699c8c 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 68e86faed1 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 4ce82ac590 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 662a0da717 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 17823f58fd 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards efbcbd171a 203: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 24006db53c 202: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 2a1d71896d 201: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 92050dff8a 200: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 6d213ec92e 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 3bfaeabee8 198: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards a501ea0a6e 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 5ccd36c2cc 196: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards bb5d999117 195: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards 7372a93095 194: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards c223e6360f 193: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards a4ebeb589b 192: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards 89d6d9ac1c 191: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards 18a38cc86a 190: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] discards 5b108ae25b 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 commits discards f82c6afe6c 188: onsuccess: #941: 1: Success after binutils/gcc/linux/gl [...] discards 0edb69f710 187: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] discards 9679d4094c 186: onsuccess: #938: 1: Success after binutils/gcc/linux/gl [...] discards fb9cac04d8 185: onsuccess: #937: 1: Success after binutils/gcc/linux/gd [...] discards f32c130f30 184: onsuccess: #936: 1: Success after binutils/gcc/linux/gl [...] discards 26d9fbc170 183: onsuccess: #935: 1: Success after binutils/gcc/linux/gl [...] discards dbc248eceb 182: onsuccess: #933: 1: Success after binutils/gcc/linux/gl [...] discards 605b98b4ba 181: onsuccess: #932: 1: Success after binutils/gcc/linux/gl [...] discards 3c683805ea 180: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] discards 31658058cb 179: onsuccess: #930: 1: Success after binutils/gcc/linux/gl [...] discards 87d6b49ad1 178: onsuccess: #929: 1: Success after binutils/gcc/linux/gl [...] discards 0901f83e59 177: onsuccess: #928: 1: Success after binutils/gcc/linux/gl [...] discards b16cdc254e 176: onsuccess: #927: 1: Success after binutils/gcc/linux/gl [...] discards 609a85c087 175: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] discards af4e551017 174: onsuccess: #925: 1: Success after binutils/gcc/linux/gd [...] discards 7743d0af6e 173: onsuccess: #924: 1: Success after binutils/gcc/linux/gl [...] discards 9b1772b051 172: onsuccess: #923: 1: Success after binutils/gcc/linux/gd [...] discards 3d6c220d2e 171: onsuccess: #922: 1: Success after binutils/gcc/linux/gl [...] discards ba82fcd215 170: onsuccess: #921: 1: Success after binutils/gcc/linux/gl [...] discards f182738510 169: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards 71ad22a522 168: onsuccess: #919: 1: Success after binutils/gcc/linux/gd [...] discards 9d43717ce6 167: onsuccess: #918: 1: Success after binutils/gcc/linux/gd [...] discards 92013692dc 166: onsuccess: #917: 1: Success after binutils/gcc/linux/gd [...] discards 7d605d3d4d 165: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards a77ede4762 164: onsuccess: #915: 1: Success after binutils/gcc/linux/gl [...] discards 281ada85a9 163: onsuccess: #914: 1: Success after binutils/gcc/linux/gl [...] discards 049344a614 162: onsuccess: #913: 1: Success after binutils/gcc/linux/gl [...] discards 703ccba626 161: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards cb5e22ee0e 160: onsuccess: #911: 1: Success after binutils/gcc/linux/gl [...] discards 1b1752e4fc 159: onsuccess: #910: 1: Success after binutils/gcc/linux/gd [...] discards 4a4cadc18b 158: onsuccess: #909: 1: Success after binutils/gcc/linux/gd [...] discards dd2196d8a3 157: onsuccess: #908: 1: Success after binutils/gcc/linux/gl [...] discards d49e58a471 156: onsuccess: #907: 1: Success after binutils/gcc/linux/gd [...] discards 8470163117 155: onsuccess: #906: 1: Success after binutils/gcc/linux/gl [...] discards e32bfc93b1 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] discards 4b39db2e5f 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] discards b2436ab7d8 152: onsuccess: #903: 1: Success after linux: 22 commits discards a7ddb1dca8 151: onsuccess: #902: 1: Success after glibc: 8 commits discards 42cf5f5ee9 150: onsuccess: #900: 1: Success after gcc: 11 commits discards 3a6262e3b1 149: onsuccess: #899: 1: Success after binutils: 15 commits discards 9ab7a2112e 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] discards 9d583d1867 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] discards 72de749e58 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] discards f54933ed17 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new 1e03b358ae 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new cea5717e2b 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] new 5215cb5e77 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] new 6eb8d54cea 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] new 17afd3e7fc 149: onsuccess: #899: 1: Success after binutils: 15 commits new 9fc922907a 150: onsuccess: #900: 1: Success after gcc: 11 commits new bddced7696 151: onsuccess: #902: 1: Success after glibc: 8 commits new affef3f723 152: onsuccess: #903: 1: Success after linux: 22 commits new 1c08d8afe1 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] new 038b43541e 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] new efa4e63ec1 155: onsuccess: #906: 1: Success after binutils/gcc/linux/gl [...] new 4068350325 156: onsuccess: #907: 1: Success after binutils/gcc/linux/gd [...] new 57c2036b01 157: onsuccess: #908: 1: Success after binutils/gcc/linux/gl [...] new 0d9b9c1644 158: onsuccess: #909: 1: Success after binutils/gcc/linux/gd [...] new 18d6974281 159: onsuccess: #910: 1: Success after binutils/gcc/linux/gd [...] new 5773397562 160: onsuccess: #911: 1: Success after binutils/gcc/linux/gl [...] new 66ddec52e5 161: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new b5e6345620 162: onsuccess: #913: 1: Success after binutils/gcc/linux/gl [...] new c8eaa77776 163: onsuccess: #914: 1: Success after binutils/gcc/linux/gl [...] new c1c969e98d 164: onsuccess: #915: 1: Success after binutils/gcc/linux/gl [...] new eace93a72a 165: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new d282044567 166: onsuccess: #917: 1: Success after binutils/gcc/linux/gd [...] new 17d085ff2c 167: onsuccess: #918: 1: Success after binutils/gcc/linux/gd [...] new 3027987c9e 168: onsuccess: #919: 1: Success after binutils/gcc/linux/gd [...] new b1c954bc40 169: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new 9d96e2fc5c 170: onsuccess: #921: 1: Success after binutils/gcc/linux/gl [...] new 6fcd8325fb 171: onsuccess: #922: 1: Success after binutils/gcc/linux/gl [...] new b3e730887d 172: onsuccess: #923: 1: Success after binutils/gcc/linux/gd [...] new b9d91e59ad 173: onsuccess: #924: 1: Success after binutils/gcc/linux/gl [...] new 7d65f00c78 174: onsuccess: #925: 1: Success after binutils/gcc/linux/gd [...] new 6747055f90 175: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new 515cc77371 176: onsuccess: #927: 1: Success after binutils/gcc/linux/gl [...] new ea43705e31 177: onsuccess: #928: 1: Success after binutils/gcc/linux/gl [...] new 8dff90ceed 178: onsuccess: #929: 1: Success after binutils/gcc/linux/gl [...] new 55bf7264e8 179: onsuccess: #930: 1: Success after binutils/gcc/linux/gl [...] new 4ee9ed2908 180: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new 8308c1ddf4 181: onsuccess: #932: 1: Success after binutils/gcc/linux/gl [...] new a677b2298e 182: onsuccess: #933: 1: Success after binutils/gcc/linux/gl [...] new 54665f1456 183: onsuccess: #935: 1: Success after binutils/gcc/linux/gl [...] new 847119247c 184: onsuccess: #936: 1: Success after binutils/gcc/linux/gl [...] new 7674a5cc53 185: onsuccess: #937: 1: Success after binutils/gcc/linux/gd [...] new 81a1d01844 186: onsuccess: #938: 1: Success after binutils/gcc/linux/gl [...] new 65b27a073c 187: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new a474903995 188: onsuccess: #941: 1: Success after binutils/gcc/linux/gl [...] new 5aa305fa62 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 commits new 7cf1759d47 190: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new f167f5fefc 191: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new 9f9f1c9966 192: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new cb5f4034ac 193: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new 30dbe72084 194: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new 24157029ae 195: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new 7ee5d18ed3 196: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 86e3cba1f0 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new b59e3964dd 198: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new cb1b8d298e 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new cdd0597850 200: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 540c745440 201: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 13256560c7 202: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new c6b131cefb 203: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 373ee16ec7 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 72bf13eaab 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 4343352fa7 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new a6341e51db 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new e61a4f86c1 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 9121178529 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new c4ae7db49a 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 844e020a10 211: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 22824d1508 212: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 112941a51f 213: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 936c0ca45e 214: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new b0176087e7 215: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new b1e40c454a 216: onsuccess: #21: 1: Success after binutils/gcc/linux/gdb [...] new c38b9a3a6e 217: onsuccess: #22: 1: Success after binutils/gcc/linux/gdb [...] new 70242a8c9d 218: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] new 3b98e99080 219: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb [...] new 74f0b29ddb 220: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new a04f97d054 221: onsuccess: #27: 1: Success after binutils/gcc/linux/gli [...] new 02562eace4 222: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 8a3748542d 223: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new ef7a94b4fd 224: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 26c233dfc8 225: onsuccess: #32: 1: [TCWG CI] Success after binutils/gcc [...] new 9038fd755f 226: onsuccess: #33: 1: [TCWG CI] Success after binutils/gcc [...] new 0295df5b91 227: onsuccess: #34: 1: [TCWG CI] Success after binutils/gcc [...] new 85d34193c2 228: onsuccess: #35: 1: [TCWG CI] Success after binutils/gcc [...] new b391cf5b64 229: onsuccess: #36: 1: [TCWG CI] Success after binutils/gcc [...] new 717c4eb242 230: onsuccess: #37: 1: [TCWG CI] Success after binutils/gcc [...] new e5f2820e21 231: onsuccess: #38: 1: [TCWG CI] Success after binutils/gcc [...] new 30ec2b1e78 232: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new bbc59d326d 233: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new a40bb9577f 234: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new fb46450d39 235: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 4416651cff 236: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 5ce8d80749 237: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 3109957596 238: onsuccess: #45: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 109daf6087 239: onsuccess: #46: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new d1ea305a73 240: onsuccess: #47: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 52fbcb64e9 241: onsuccess: #48: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 5baa074a67 242: onsuccess: #49: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 8909167501 243: onsuccess: #50: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 1b0ce3c82c 244: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 3c3c286c85 245: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new b6c45cbd2d 246: onsuccess: #57: 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 (f7e365f5e3) \ 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 0 -> 3700908 bytes 00-sumfiles/gcc.log.xz | Bin 0 -> 3266360 bytes 00-sumfiles/gfortran.log.xz | Bin 0 -> 1085012 bytes 00-sumfiles/libatomic.log.xz | Bin 0 -> 2288 bytes 00-sumfiles/libgomp.log.xz | Bin 0 -> 235400 bytes 00-sumfiles/libitm.log.xz | Bin 0 -> 2680 bytes 00-sumfiles/libstdc++.log.xz | Bin 0 -> 457296 bytes 01-reset_artifacts/console.log.xz | Bin 2024 -> 2200 bytes 02-prepare_abe/console.log.xz | Bin 2444 -> 2444 bytes 03-build_abe-binutils/console.log.xz | Bin 35980 -> 35680 bytes 04-build_abe-gcc/console.log.xz | Bin 204928 -> 204992 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8496 -> 8460 bytes 07-build_abe-glibc/console.log.xz | Bin 241988 -> 241336 bytes 08-build_abe-gdb/console.log.xz | Bin 35648 -> 34940 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3912 -> 3876 bytes 10-build_abe-check_gcc/console.log.xz | Bin 13852 -> 6816 bytes 10-build_abe-check_gcc/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 1276 -> 1672 bytes 11-check_regression/results.compare | 18 +- 11-check_regression/results.compare2 | 35 +- 12-update_baseline/console.log | 64 +- 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++.log.sep.xz | Bin 64236 -> 0 bytes sumfiles/g++.log.xz | Bin 3737168 -> 0 bytes sumfiles/g++.sum | 2 +- sumfiles/g++.sum.sep | 6348 --------------------------------- sumfiles/gcc.log.sep.xz | Bin 121484 -> 0 bytes sumfiles/gcc.log.xz | Bin 3225288 -> 0 bytes sumfiles/gcc.sum | 18 +- sumfiles/gcc.sum.sep | 2128 ----------- sumfiles/gfortran.log.sep.xz | Bin 20984 -> 0 bytes sumfiles/gfortran.log.xz | Bin 1092344 -> 0 bytes sumfiles/gfortran.sum | 2 +- sumfiles/gfortran.sum.sep | 1234 ------- sumfiles/libatomic.log.xz | Bin 2288 -> 0 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 235584 -> 0 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2688 -> 0 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 23904 -> 0 bytes sumfiles/libstdc++.log.xz | Bin 445784 -> 0 bytes sumfiles/libstdc++.sum | 4 +- sumfiles/libstdc++.sum.sep | 111 - 52 files changed, 129 insertions(+), 9905 deletions(-) create mode 100644 00-sumfiles/g++.log.xz create mode 100644 00-sumfiles/gcc.log.xz create mode 100644 00-sumfiles/gfortran.log.xz create mode 100644 00-sumfiles/libatomic.log.xz create mode 100644 00-sumfiles/libgomp.log.xz create mode 100644 00-sumfiles/libitm.log.xz create mode 100644 00-sumfiles/libstdc++.log.xz delete mode 100644 sumfiles/g++.log.sep.xz delete mode 100644 sumfiles/g++.log.xz delete mode 100644 sumfiles/g++.sum.sep delete mode 100644 sumfiles/gcc.log.sep.xz delete mode 100644 sumfiles/gcc.log.xz delete mode 100644 sumfiles/gcc.sum.sep delete mode 100644 sumfiles/gfortran.log.sep.xz delete mode 100644 sumfiles/gfortran.log.xz delete mode 100644 sumfiles/gfortran.sum.sep delete mode 100644 sumfiles/libatomic.log.xz delete mode 100644 sumfiles/libgomp.log.xz delete mode 100644 sumfiles/libitm.log.xz delete mode 100644 sumfiles/libstdc++.log.sep.xz delete mode 100644 sumfiles/libstdc++.log.xz delete mode 100644 sumfiles/libstdc++.sum.sep