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 0840447581 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards d3bf775fb5 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 11760a17b2 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 34a460c177 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 62678f26d9 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 89d1e8f9d2 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards efd79b499c 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 1f95dc670a 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 87beeca53c 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 5b4e8f6d63 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards c7face381f 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards d670588f97 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 55094d37bb 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards a14f2d5550 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 3cc5a5326b 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 2f7b2fc4d7 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 26ef9dc0dc 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards ac431e90cc 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards a79192d7d7 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards e8159a44d5 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 42e80ce474 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 987add3823 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards b39ffa3f17 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 1a84315ba0 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards e23b6d1722 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards dedfc33539 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 1dd06d5d1f 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 765e72c233 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards e30c290459 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 3e5d34533b 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards b13d421dd4 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 67a8902756 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards e5739861d2 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards bf093c6c1f 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 7a7a645e36 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 389b43a69e 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 95d8136b23 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards eb49804060 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 7112f08e89 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 54f9f67f83 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 1dfb5dfdb4 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 85044ff2ff 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 3cfa2446d5 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards ee86b0165d 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards f42b1a485d 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 1c76d6b775 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 4a4062dc28 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 563a75cdcd 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 4314b6250b 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 6aecf7dbd7 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 4a78768d1e 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 33f0d998be 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards c8fa395649 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 825f3765a7 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 42872a3ea3 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards f348a4fe2a 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards d5ce3c1027 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards d8d86a166e 301: onsuccess: #2118: 1: Success after linux: 16 commits discards b618d611f0 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 88c79c3a0d 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 4f4bd56474 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 27babf1cd0 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 5c2b737ab2 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards a8ed4270ae 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 0d7d013b4f 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 61359e4335 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 2c01def14e 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 97bf7f9c18 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 7b41f54ac7 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 05f3a142ad 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 7a04145441 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 6af8f85dd0 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 5a3c2875d6 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards ff194614c3 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 5b2b1dd57c 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 85209cec54 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 3a987386b8 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 71612f6433 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards cb341092d2 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 8b4aab2120 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards cb8e61b3cf 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 0c469d1b57 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 7396127eaf 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 2c29a6e267 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 326de7a567 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 753b37858b 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards ad491315d1 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 806d6e2cfb 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 28fc216d1e 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 14b4b885d2 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 3d013b0cb1 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 3410fb4677 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 361b658ad4 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 0d3c64a22e 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 471bae9582 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 9db7c45f27 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards f7e9755f5f 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 40e5f56e0f 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 5c7c8fdb4d 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 53b0b23e0b 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 3fd3b57af5 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 4effe8857a 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new eb0a842943 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 0ed05debd2 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new f40305fdb8 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new a26c003613 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new b3f559dbdc 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 54e3d6674d 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new c9a70cc790 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new d4bd30c650 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 9f35d9a7a5 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new b27b53b0ed 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new e4dab25e6b 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 2cd68343a6 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 79398e4f13 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 0f87ba29bc 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 1b83abe4df 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new c02e1cd64e 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 43c27b9a9b 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new a94672440b 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new d3b8892f59 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new f90e22adb5 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 588ad90035 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new c152160527 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new f3c7324896 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 65565fc2e7 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 7579277b79 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 384b2f2b94 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 58143e45df 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new fcdd513027 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 96a99440e1 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 8cd6cceb54 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new f44459e6a3 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new eb5a3c02a5 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 52365fa3c4 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 04d91d632e 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 74a94122b3 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new f40b2b5a8a 294: onsuccess: #2110: 1: Success after gcc: 17 commits new f250a315ff 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new b8f86e7f04 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 2a8e1e0411 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 74b22aac2c 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 383dd10d6a 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 1bdc9ae16b 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 4bac395ee2 301: onsuccess: #2118: 1: Success after linux: 16 commits new 26b94625f7 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 2d80ae05f2 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 6112a8d020 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new b5ad702565 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new b1cb93bb2a 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 4e5b55573e 307: onsuccess: #2124: 1: Success after gcc: 2 commits new cb4cc2b8b4 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 515aa4ff32 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 00731ad083 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 070e5eb4cf 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 363bcdc39f 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new f198f254be 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new ec7ee63927 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new bf014e899f 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new ac23fa4398 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new cab2ec0531 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 251e4f8689 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new c08d998088 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 94977fefa4 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 1a73a8b6d4 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new fc29b8a42d 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 15b167b5fe 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 137e0c9870 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new c07d520d7f 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 549657ddd2 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 9c982446cf 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 735e924827 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 4a2dbbd466 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 6d3637d6e7 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new f5cec54a2a 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new bd177d18eb 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 887f0b0df4 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new cad5a524f0 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 0bcb2cd065 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 06cfeba985 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 49219ff2c4 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 6a702ec231 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 4f35db6e07 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 7701a38b8b 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new ab5b0c0c73 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 349a68f21f 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new c01210a35b 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new deeace1ea0 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new bdb4e0d536 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 6c76e8db5d 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 416ef5785a 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 9b59059d9e 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new d87eecd024 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new a9f5237da3 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new ca0d24e2cd 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 7602295ca8 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 6ca3a65fa7 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 1a5d911b65 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new cad056b783 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 48f137eb70 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 9da717b574 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 647f6622b3 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new dcb7c7096d 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/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 (0840447581) \ 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 1760 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2808 bytes 03-build_abe-binutils/console.log.xz | Bin 31624 -> 32196 bytes 04-build_abe-stage1/console.log.xz | Bin 91800 -> 92584 bytes 06-build_abe-linux/console.log.xz | Bin 8604 -> 8640 bytes 07-build_abe-glibc/console.log.xz | Bin 235816 -> 236968 bytes 08-build_abe-stage2/console.log.xz | Bin 228312 -> 229316 bytes 09-build_abe-gdb/console.log.xz | Bin 38936 -> 39220 bytes 10-build_abe-qemu/console.log.xz | Bin 31268 -> 31452 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3904 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2792 -> 2700 bytes 13-check_regression/console.log.xz | Bin 7688 -> 7140 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 17 +- 13-check_regression/mail-body.txt | 68 +- 13-check_regression/results.compare | 29 +- 13-check_regression/results.compare2 | 70 +- 13-check_regression/results.regressions | 29 +- 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 70 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 29 +- sumfiles/g++.log.xz | Bin 2673872 -> 2651380 bytes sumfiles/g++.sum | 24 +- sumfiles/gcc.log.xz | Bin 2198528 -> 2222884 bytes sumfiles/gcc.sum | 2402 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 887492 -> 888796 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214080 -> 214224 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 441636 -> 434720 bytes sumfiles/libstdc++.sum | 24 +- 44 files changed, 1464 insertions(+), 1436 deletions(-)