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-aarch64 in repository toolchain/ci/base-artifacts.
discards 5c9d20997d 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards e5d8b751fd 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards c9419ecc98 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 594f04888d 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 3c9f8bfbf1 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 3969b03299 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards ea36108301 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards ba6d78fd06 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 6b0231aa0f 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 4282371eb3 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 7e7699e271 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 7770b1f0c2 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards be9f02cdfd 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards fd044ffdf8 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 5ff2337fbc 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 13a6e30cbf 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 7e3b26952e 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 35f66459ce 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 5fdf77c139 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 54159c8aab 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 3e20326cbe 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards ac9ccf9488 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards ef4a9e8876 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 51a8ea4ad8 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 34113c2d3c 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 54053fe7f4 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 2d23d608e8 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards cb053e8a7f 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 69aa1f5402 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards f78f8b86b7 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards cc6879c6f2 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 10a8807eee 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 06f0d32e71 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 5843a89008 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 4ae5711bb5 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 3e9bf546b0 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 3b17bc6f60 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards dfa5d60d37 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards c26ca1d776 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards d081f176ea 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 2c9b14a62e 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards bb9776e100 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards ff7fc2335e 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 5a314adb80 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 42e93b88c7 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards fc4b7f63bc 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 63b2495edd 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards df1caddcd6 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 312a974dc1 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 59e523b03a 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 87d7a9e90a 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 833488cea7 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 4a617b419f 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards a186329e1b 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards e9b24984f2 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 3babf8ddf4 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 63dcffd6c9 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards a2949d75c3 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 0352d63c33 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 3d330bd0fd 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 29a231287f 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 7100e0b7c3 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 0d988e6c3a 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards d91c4691ac 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 893146a129 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards a1cbe7e662 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards bf8790846c 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards d9ccdc471f 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 8f903ccecf 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 9f88d62461 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards a772384cf0 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards f1bedf6651 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards e7c383f190 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 71ac528a45 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards b7d91e1036 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 86979fe429 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 9ff88b51f2 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards a8fca81ec8 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 3cb53db0e7 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 8a778f129a 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 23aba25f5c 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards ed47d3e0f0 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 8cd96a28a0 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 0ec4eff28f 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 5641970db6 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 180402b8e7 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards fc56c4e339 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards ce37a3b7e1 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 35affe0583 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 0a34ed9ff4 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards d06be9cc37 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards e12abc10fa 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 33443d8750 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 1fb6aacc39 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 45544acbdd 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 82a16a2b46 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards bfa02c1212 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards cf9ef194a4 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 80852b6a3f 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards 11124508ae 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards cecc6f4f55 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 309e8ec90d 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 42d83b60db 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 800076c187 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new f6529c545b 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new 32dc11fed8 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 217a92605f 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new a23fe35794 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 856963efa5 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new fe964ffa65 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new d3c24a9f06 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 29a64d4443 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 8946efc2b1 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 1c1ff13762 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 9411cc2db4 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 0e9b0bdae7 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 03c6a622a9 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new c8b5fc93f8 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new f991ae8b06 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 8c03cd43f3 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 7b83ea5ade 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 56ed2e47c8 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new efcfaf1689 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 7e535dc497 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 6aec412b3d 273: onsuccess: #2521: 1: Success after gcc: 2 commits new f3f467624e 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new af94251a9a 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new d436986042 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 9aff2f9a97 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new dc81ec32ad 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 0997819d77 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 8735c0d080 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new ee1d56e079 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 3fafb0c6bd 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 0b94e20b2e 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new a5e2d7e411 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new d6b18ec2ad 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 366f6b14e0 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 6d0cd45328 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new db069737c7 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 6467057013 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 88d33189f9 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 8a26ef175f 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 45d4bc4d08 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 22c834d466 293: onsuccess: #2542: 1: Success after gcc: 5 commits new fff805ddef 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new a7bd416270 295: onsuccess: #2545: 1: Success after linux: 10 commits new 3b20a3fc9e 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 3c6e956a5c 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new f3fb91cacc 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 52cc56b10c 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 5114b6f754 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new bcf31706d5 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new dca0665df0 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 5101d7850d 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new b8abf31f0a 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 6e224965d6 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 81b5233ebe 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new eb549702ad 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 5bb93b77ba 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 5095dd92a7 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 9306245d0b 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 22d6651bf6 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 03a652974c 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new f31b6c1a79 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 7f81349a67 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new a8aae2fb02 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new eadb72503d 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 9589a00c31 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 57bfcf7dfb 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 3c90f5e8af 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 432f350bb8 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 1edb592498 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new d7a00464a5 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 5ded4d2528 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new dbcc4ace74 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new fa0df10c19 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new b1ee6d5608 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new f1eba7e327 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 1fd88243c7 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 93f2923f18 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 7b997169b7 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new e36e67b94b 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new c8cb704f5c 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 5f499d1a70 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 65995b1b54 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 786401a727 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 7a61c42b91 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 285df86f44 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 9cfb2e8e37 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 55c7d8b8f9 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new f560580368 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 872480bd2f 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 535c9adcea 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 1a7929c3b5 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new a6d1643df1 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new fd2176a8f9 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new a98e1d41c8 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 417d20d9cc 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 04474854ad 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new f966944d49 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new a7d683fedc 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 20d76ba3f8 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...]
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 (5c9d20997d) \ 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 1768 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 31464 -> 31552 bytes 04-build_abe-stage1/console.log.xz | Bin 73548 -> 73720 bytes 06-build_abe-linux/console.log.xz | Bin 8872 -> 8924 bytes 07-build_abe-glibc/console.log.xz | Bin 246892 -> 245984 bytes 08-build_abe-stage2/console.log.xz | Bin 206092 -> 206280 bytes 09-build_abe-gdb/console.log.xz | Bin 38612 -> 38904 bytes 10-build_abe-qemu/console.log.xz | Bin 31756 -> 31800 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3900 -> 3912 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2772 -> 2812 bytes 13-check_regression/console.log.xz | Bin 9204 -> 10432 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 22 +- 13-check_regression/mail-body.txt | 144 +- 13-check_regression/results.compare | 114 +- 13-check_regression/results.compare2 | 686 +++-- 13-check_regression/results.regressions | 109 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 146 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 109 +- sumfiles/g++.log.xz | Bin 3416216 -> 3403384 bytes sumfiles/g++.sum | 109 +- sumfiles/gcc.log.xz | Bin 3032760 -> 3005192 bytes sumfiles/gcc.sum | 4476 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1045088 -> 1036432 bytes sumfiles/gfortran.sum | 22 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214744 -> 214752 bytes sumfiles/libgomp.sum | 15 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 439388 -> 432780 bytes sumfiles/libstdc++.sum | 126 +- 42 files changed, 3230 insertions(+), 2966 deletions(-)