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 06fb5d5251 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] discards 78dad5be64 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] discards bc46a27cf0 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] discards 55e6c9345e 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] discards 64b6780846 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] discards 1d01f10d30 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] discards 01e540c87f 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] discards fdc8518c3e 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] discards fdf2fae620 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] discards 4c5279fd41 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits discards 70ee1183c8 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] discards 4d562e5c8d 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] discards 71418ba3cd 408: onsuccess: #2662: 1: Success after linux: 11 commits discards 029ab6b63d 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards f0fbe9e49c 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards 433512e436 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards 7bc3ab5498 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards 606a583d3d 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards 24c9a98a7d 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards 38710be3e5 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards 0edc0431ac 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards 41b2ac9801 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards ce168bb952 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards 00a9e4906d 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards 63eba32b13 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards 8f0a763df3 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards 9f8df93c96 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards 8e7ac065db 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards b80c378f10 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards 75f87a5757 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards 428ef169a2 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards de98903828 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards 6ace25aa29 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards 4be05afbd6 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards 0d5286eee5 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 56e0e79e97 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 98bd245aac 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 74bc05687f 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 11ba274e2f 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 6c1e98644e 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards f44f018dbf 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards 4590fe9856 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards c9318caa9e 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 178d33a502 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 5ef6be61a6 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 5de6aacdf1 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 805cd06210 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 05ed8f1d18 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards d3f27b99ab 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 6547c6bf1c 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 82fd27a386 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards f7df87781f 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards f5e13319ad 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards f2a49610f7 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 30bc5d5eb4 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 3335709be1 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 67b91f0db5 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 7a7440b850 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards d1325acdf2 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 087d8789da 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 1509124099 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards af973885fb 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards a0bbd7f3d0 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards c8b65543d5 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 8e1a352195 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 67ec164931 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 5a8a9cb0d0 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 77922a596b 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 9c446245c5 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 4fc74ced7d 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards d54a515a28 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 17674455ef 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 694a305f66 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 1b39d83494 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 5237888880 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 787ccab955 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards a8640f21cd 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 9a501eac72 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 495c3f8a83 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 7f358cb0bf 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 5b7266e6c0 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 271d85b1ae 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 54158a8a5f 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 5fb48d6c1f 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 811391404c 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 0de2ac6fbb 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 53dc3c55f3 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 3cd6bea7b2 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 4dd435ea5b 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards e64add9813 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 72abb6a489 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards d3cc5f6354 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 32d2726f50 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 6dacf5c3e2 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 51e74bc77b 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards d117da962a 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 0936b0fef7 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 0c08629cd6 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 6edc57f8ff 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards ce2717f106 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 6c3adc4ce7 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 189a0c0378 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 176623f5a1 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 3a1d319207 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 57b219db20 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 8ced08e55b 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 928146b88d 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 496ba47630 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new a93978f53c 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 02fc484e9a 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 4f8c69256b 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 8da61fe281 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new e10372e3e5 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new acbc79be10 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new a1b0a86819 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 23746f258d 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 4d253d0cff 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new e4cf2d35f5 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 1a913192f4 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 4bc3886496 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 1b27c472d2 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 658f5d858d 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new a93f8a0858 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 7715364d9f 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 7cb70fa5dd 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 8956d9dda0 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new a2f910ef3a 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new ba969eb38f 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 164240c209 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new f2570d8285 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 5663681335 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 5abc5dc4cf 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 3c5eef10fb 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new cc88c80970 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 730867856e 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 43717d9de2 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 4c51e53f69 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new ac131c6df8 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new ee5351c3bd 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new ec664de511 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 68dabdd1db 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 3c2cf06757 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 805b5a92ec 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 799cd31d2a 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 2a811df763 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new fe2504d2cb 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new f30bc4f71c 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new ec14fce042 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new aa2153fa5a 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 3f2d5c4140 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new e1689de5c4 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new c262e05e6d 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 3bc792a3f0 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new df8e98f50b 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 7f3022b7f9 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 2c12010d56 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 9a35387fe1 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new f82a0bb044 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new b85a96f983 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 3057d38445 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 371ccdd9bd 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new f554742062 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new b67816071b 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 0903d6dbb7 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 4769b1d2d7 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new c608876498 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 5aad425971 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new 1c9ca4d949 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 808cb8188b 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new f0fa3cc6be 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new 38814089ea 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new 1e8b874310 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 018f834c25 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 7fdc473813 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new 7e6a8b99e2 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new 9aea195a00 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new d0f6df1eef 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new 088a4f4130 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new d784eb02e1 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new 1b2d68b6f1 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new 7c23c9da0f 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new c6bd547ce9 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new dc12357129 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new a69c1914aa 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new 45cfc97969 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new 44750c8708 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new 3662717630 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new 66d0f5fda5 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new 39e9372c89 407: onsuccess: #2661: 1: Success after gcc: 7 commits new 9f2763d776 408: onsuccess: #2662: 1: Success after linux: 11 commits new 40cf35db05 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] new 37fc988255 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] new 6e4bb0fca7 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits new 0403440004 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] new 606ac4c63c 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] new 4f847d243c 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] new d8d1f3f812 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] new babcc87c13 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] new 84a998cfcc 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] new 756870044c 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] new 10338e45f4 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] new 92a801149f 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] new aa32cb908f 421: onsuccess: #1: 1: Success after binutils/gcc/gdb: 20 commits
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 (06fb5d5251) \ 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 1828 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 30892 -> 30936 bytes 04-build_abe-stage1/console.log.xz | Bin 70816 -> 70916 bytes 06-build_abe-linux/console.log.xz | Bin 11844 -> 11864 bytes 07-build_abe-glibc/console.log.xz | Bin 244044 -> 244424 bytes 08-build_abe-stage2/console.log.xz | Bin 202256 -> 202048 bytes 09-build_abe-gdb/console.log.xz | Bin 38552 -> 38640 bytes 10-build_abe-qemu/console.log.xz | Bin 31508 -> 31752 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3844 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2736 -> 2696 bytes 13-check_regression/console.log.xz | Bin 7232 -> 7736 bytes 13-check_regression/fails.sum | 7 +- 13-check_regression/mail-body.txt | 186 +++++++++++++++---------------- 13-check_regression/results.compare | 124 ++++++++++++++++++--- 13-check_regression/results.compare2 | 185 ++++++++++++++++++++++++++---- 13-check_regression/results.regressions | 95 ++++++++++++---- 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 | 188 +++++++++++++++---------------- mail/mail-subject.txt | 2 +- manifest.sh | 32 +++--- results | 95 ++++++++++++---- sumfiles/g++.log.xz | Bin 3396108 -> 3396212 bytes sumfiles/g++.sum | 10 +- sumfiles/gcc.log.xz | Bin 3019196 -> 3025760 bytes sumfiles/gcc.sum | 192 ++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1041292 -> 1038048 bytes sumfiles/libatomic.log.xz | Bin 2312 -> 2312 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217340 -> 217208 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2680 -> 2680 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 437128 -> 424068 bytes sumfiles/libstdc++.sum | 80 +++++-------- 40 files changed, 796 insertions(+), 480 deletions(-)