This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm in repository toolchain/ci/base-artifacts.
discards a52b1f66e2 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 8dfc797e76 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 110752fc8d 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 2b04a22fff 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards c66f8e4bc7 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards fbe98b8660 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards ef4596611b 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards f9f9b67d1b 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 37fd69f877 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 328491ec13 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 883043bcf1 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 5b8c27e5e5 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards f22fe2054c 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards c39d6ebffb 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards d686eefd19 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 28134f495e 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 8c327c5f10 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards ed96c590c9 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 8c8bfe1c92 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 3ee4fbe6bc 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards b3ff3834f6 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 2c36614c11 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 0c9c7eefcb 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards b86fa52a89 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards ad05e4579a 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 0b72214d06 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 372cfda514 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 29a61794e6 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 7a1f83448d 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards c040a0c0e1 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 6443e6cc17 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards ee23b73815 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 4508d531fe 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards b2f0524ad6 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 967305c287 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards b4bb57a4be 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 109a17a70b 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 51650cce3a 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 4ac3cf8e08 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 07b4d2d102 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 9abeb1fa89 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 6f314c6b3b 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards c91c893a79 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards fd7fb263f3 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards f6e89fac9e 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 6e09cde9f6 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 06ba1ec313 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 6e263250b2 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards c236e65d11 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 8466efff97 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 236b8c07f9 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 694e9c6663 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards ab26756596 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 42144c0ba4 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards cd4af6949f 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 8d08998eb5 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards b53602f8c4 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 907d8377ba 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 45f5e58ece 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards bd7a316631 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 31cdda059d 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 11cabaa48e 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards be2564f47c 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 55b76d548b 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 8ada9789a1 301: onsuccess: #2118: 1: Success after linux: 16 commits discards d11a4aa31d 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards e519c5fac7 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 727be8869b 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards ec5467a39f 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 7567290b0a 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 9d045c3bf0 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards c9d63e4458 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards b9bcd98699 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards e2c42ac4cf 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards fbab153259 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards d75222e267 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards c559d78c35 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 2684160d27 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards d04638506d 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 8868eb626e 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards f8c49082ef 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards a6d1d1c77a 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 0d25f781e0 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards ae97c53251 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 0dffc6f951 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 42c0463e55 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 39d4ac335a 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards b7239b0025 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 166530cce6 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards c99bc181e5 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 7f6c71c01e 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 160ffaf875 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 4753129477 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 1fefb8e420 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 8e08ab9daa 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 66252650ff 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards bf89e7ccee 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 10a9084913 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards a5ed0aa61c 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 6463a40d56 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards b4889f05ca 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 48300cccc1 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 9b9716a52d 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new e969c496e0 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 036fb6a964 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new cc8d40f97d 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new d0d10bfd91 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new c49da6b65a 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 5e10982039 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new e3fc9b7514 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 1d29aca61b 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new b1b5bee94e 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new d2f86a3598 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new c455319ddf 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new b0f8139206 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 6f1387b18a 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new e5ecf893d6 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 872b02f320 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new aac0d70e63 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new d7bc5a9bcb 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 02b7c1ef39 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 7b16ca6003 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 843f0eb7b0 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 9ae96bf36e 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 9aa30ad3c0 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 016aa88e34 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 580fe89a30 290: onsuccess: #2106: 1: Success after gcc: 2 commits new b3c33062e0 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 39c26abeaf 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 0aa9c48c5c 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 7fc5a25818 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 9a7abc4bfd 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 94047d3994 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 3ec833bf7b 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 67506bf48a 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 63de68f92a 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new f4afeba4f2 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 1077371d72 301: onsuccess: #2118: 1: Success after linux: 16 commits new d38a9321b2 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 5885aea221 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new ce4bd4ec87 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new b18318821a 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new bff2b65bee 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 17b9d540aa 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 203d3fa6ad 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 3d21c3f8ca 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 8f11681bd8 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 3dfd61f4b9 311: onsuccess: #2130: 1: Success after gcc: 4 commits new ad778c5483 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new f3ab0136b9 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 64bbac606e 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 2d18464607 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 2c8fb32703 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new ca0527f5ac 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 1736deb25d 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 6218a7f212 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new bc32f89780 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 660409d9e3 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 538484bac1 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 0bc01d0eba 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 2524c23226 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new b921f72bb4 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new af0f81c018 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 4cbdda44a5 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new a6975f6f06 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 9130349efa 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new e09b8bdb72 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new acf8e4e5c9 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 6c95789d5f 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 855a082849 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 0f324655b7 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 5cd2a979d9 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 50db1b0d2b 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 28a857e7a8 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new b223798130 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 6513d1b470 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new b2e2b416ea 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new b499252ebc 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 0cd1ac6183 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 2d57cce308 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new d920dd06dc 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 62f77b2519 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new e1905cc602 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 99716a928b 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new e92a625fa7 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 30c5f4695f 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new f9652ec8b6 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new ce1b524a70 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new b21e6feff4 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 1d71d3d69c 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new cfd31f2808 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 30d75b1ba7 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 97c9a6b693 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new b8b3a163c4 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 4f426823b4 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 428ce3196c 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new a48430f123 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 2ed4c3a4b8 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 61cd89b1e9 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 1af3f20256 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 5aa88475b7 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 26e9cfe7d1 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 3ba79d3113 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...]
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 (a52b1f66e2) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...]
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 1776 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31568 -> 31064 bytes 04-build_abe-stage1/console.log.xz | Bin 93708 -> 91904 bytes 06-build_abe-linux/console.log.xz | Bin 8732 -> 8884 bytes 07-build_abe-glibc/console.log.xz | Bin 236924 -> 236432 bytes 08-build_abe-stage2/console.log.xz | Bin 230344 -> 229072 bytes 09-build_abe-gdb/console.log.xz | Bin 38816 -> 38468 bytes 10-build_abe-qemu/console.log.xz | Bin 32380 -> 31256 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2992 -> 2800 bytes 13-check_regression/console.log.xz | Bin 14916 -> 17844 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 9 +- 13-check_regression/mail-body.txt | 147 +- 13-check_regression/results.compare | 242 +- 13-check_regression/results.compare2 | 5008 ++++++++++++++++++------------- 13-check_regression/results.regressions | 109 +- 14-update_baseline/console.log | 66 +- 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 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 149 +- mail/mail-subject.txt | 2 +- manifest.sh | 48 +- results | 109 +- sumfiles/g++.log.xz | Bin 2645804 -> 2626216 bytes sumfiles/g++.sum | 2080 ++++++------- sumfiles/gcc.log.xz | Bin 2199040 -> 2172180 bytes sumfiles/gcc.sum | 3954 ++++++++++++------------ sumfiles/gfortran.log.xz | Bin 891272 -> 895704 bytes sumfiles/gfortran.sum | 16 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213972 -> 214044 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 435840 -> 431832 bytes sumfiles/libstdc++.sum | 36 +- 45 files changed, 6683 insertions(+), 5316 deletions(-)