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 2bcdee863da 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] discards 44cca558cbf 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] discards cf0c9bf79dc 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] discards 56d792239f8 194: onsuccess: #1995: 1: Success after linux: 517 commits discards f599207d8ce 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards cc2609f5af3 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] discards f18989e6697 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] discards 7ea28a9315d 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] discards 0ee51a52b2e 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] discards 5fea1788d78 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] discards 63e4f99a412 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] discards 81baa6ba96c 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] discards 7f711ea4c99 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] discards 7b2bb11e580 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] discards 6e5e3fee99c 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] discards 8ca7583fe54 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] discards 3b6dadc9458 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] discards 0762e76e532 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] discards 3b1ecd7be79 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] discards 2608e3b1985 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] discards 3703805f59f 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] discards 4dcba867065 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] discards 63847162fb4 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] discards a217273bb7a 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] discards d98e621e799 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] discards 53864c27708 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] discards 4a445d2b9a3 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] discards 5347f0e4699 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] discards 27bfc90dab8 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] discards 6dd8972debd 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] discards f8e1922e69d 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] discards 8eb4d6ed6e6 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] discards 4b895379dd0 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] discards 4969cf3772a 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] discards ce0e7047257 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards d0975ad70c5 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] discards fb84a98bf95 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] discards 2e82675f233 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] discards 40d23fa6142 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] discards fd848c7ad9a 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] discards 7a0fed1d0ea 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] discards fcf3d883936 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 5d9ae26c8cf 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] discards f7a3db663f2 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards e41d9356ac6 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards f5f2b96a27b 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] discards fc90cd375fc 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] discards dc9eee4f8db 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] discards 4b4fc547fa5 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] discards 36dbe26324d 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] discards cce665c1137 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] discards a745ce20273 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] discards b0239ff336a 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] discards 0ebb6c92220 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards ac088154b04 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] discards 0cf2c7fa579 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] discards a716f49b8b3 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] discards cd09311aea5 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] discards a016126bbd8 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] discards 9f1fdc54d8c 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] discards 4e70d7d22dd 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards e21a533a3e3 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] discards ff4f0015cbb 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 6178f814f90 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards a32ba9d0e2d 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] discards 2267932f2fc 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] discards 105afd43643 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] discards 0e3b7bcb398 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 180687307c8 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] discards ccad660ec17 128: onsuccess: #1723: 1: Success after linux: 12 commits discards cc734dcd726 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] discards c4ce854aa90 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 05255a5e908 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] discards 2253fb7db09 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards b0daca35d08 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] discards 78c7bc9b584 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] discards a7970700739 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] discards 65bd1d078eb 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] discards 175ac519fd7 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] discards f0dc1b5b31e 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] discards 1f0fc15bb87 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] discards 87f48dc6652 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] discards 0d73f5f2293 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] discards f1a6c7d6c77 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 15ba62e3a98 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] discards e9a1b03d365 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] discards 721e33cb16f 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/ [...] discards 65ad8dcd91f 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards b9599c3de8b 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 [...] discards 09d62dc5e6e 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 [...] discards fd2bc5324af 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/ [...] discards dd33d8a7844 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/ [...] discards bfba5c940b9 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38edde [...] discards 9613449e1e3 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 6ae1b05ef4f 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/ [...] discards 29c4379abf8 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/ [...] discards 9f4901dd513 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 66c2fe7e534 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/ [...] discards 5f871b56bae 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/g [...] discards 710fb33c285 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/g [...] discards b0ab0302447 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/g [...] new c66f369a7c2 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/g [...] new c091ab8ca8a 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/g [...] new 2ea99200348 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/g [...] new a7e7426bafd 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/ [...] new cee42851e27 101: onsuccess: #1693: 1: Success after glibc: 14 commits new ba889c1909c 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/ [...] new d792c88f5a3 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/ [...] new 64014de1951 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 577b516b419 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38edde [...] new 454073c5f2b 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/ [...] new 8ca2f86d7c6 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/ [...] new 2a525389c26 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 [...] new d69f9312579 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 [...] new d5bcf01538a 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 6242bd0bd66 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/ [...] new bfc5834196c 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] new dc099b7411a 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] new 62bce5446f3 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 6845f30ca55 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] new b3b627dd5c1 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] new 2884cb83c98 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] new 17b880f727d 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] new 9fd4b76fe4c 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] new 405c30dec81 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] new 7d819f3af0a 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] new 41e96e9e767 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] new 1313bab9ad2 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] new 43162890e29 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new fc74a0817ce 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] new f13135c0905 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new bd55127d18f 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] new 9fa82276e12 128: onsuccess: #1723: 1: Success after linux: 12 commits new 4880c713c6c 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] new 2922dafeae8 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 05d94f5d8ce 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] new 1921404950d 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] new efcce43f7c5 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] new 78eb666aa9f 134: onsuccess: #1730: 1: Success after binutils: 2 commits new e1cbeb270fc 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 5b09a6d44b0 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] new 7e32ca86e03 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 85b32ba832f 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] new b662f048058 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] new 45b0c604233 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] new a7efcaa32bc 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new 482653bd62c 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] new cad27cc1469 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] new 7355cb6d6ee 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 23aae3495d3 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] new d98b9ae2436 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] new 22845b55b53 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] new 1c3cb0671fa 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] new 52b0cf410c5 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] new e797ba5e677 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] new 513184350a9 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] new 478286d7948 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] new 5b661f072ce 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 52ff82cd718 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new b45f0f7d743 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] new 7d7f9877326 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 57b5e064f81 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] new 3adab5c503b 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] new ad3b428ce51 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] new fa3e8b855ef 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] new 19b90b3e571 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] new d741a753f9a 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] new 2ad1f011b6c 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 35d893d1898 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] new 062a1f94dfb 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] new e90c58108ca 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] new 6b8d67409db 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] new 373c4902c13 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] new 449881c77ef 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] new 9764aba4bd0 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] new e394868434c 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] new 3650cda5000 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] new 5e852d10db0 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] new fd5e4ba4ac3 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] new a2f571fbc9a 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] new 019f91abe02 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] new f477c41cb44 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] new e2a8782a635 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] new 9beeb71c9e1 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] new 7d18b226a85 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] new 93fe9e676f8 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] new 5d8fad9e60f 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] new 4133831a08e 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] new 7d38bdb8dba 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] new e7412ceebb2 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] new f7706978cba 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] new 405a545938b 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] new 6fdf621797b 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] new 6b0f1ce7913 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] new 407a197549f 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] new 416788c91eb 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] new f8764215218 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] new e66ab21c429 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 6dfa701ac89 194: onsuccess: #1995: 1: Success after linux: 517 commits new b395fa884df 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] new 6cfd342e66d 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] new ad92a27093d 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] new b620b20fda7 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...]
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 (2bcdee863da) \ 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 1700 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 31844 -> 31628 bytes 04-build_abe-stage1/console.log.xz | Bin 91544 -> 91552 bytes 06-build_abe-linux/console.log.xz | Bin 8584 -> 8716 bytes 07-build_abe-glibc/console.log.xz | Bin 237096 -> 237036 bytes 08-build_abe-stage2/console.log.xz | Bin 225064 -> 225932 bytes 09-build_abe-gdb/console.log.xz | Bin 38972 -> 38736 bytes 10-build_abe-qemu/console.log.xz | Bin 30432 -> 30648 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2980 -> 2660 bytes 13-check_regression/console.log.xz | Bin 7216 -> 5940 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 7 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 87 +- 13-check_regression/results.compare2 | 195 +-- 13-check_regression/results.regressions | 101 -- 14-update_baseline/console.log | 58 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 101 -- sumfiles/g++.log.xz | Bin 2738084 -> 2711128 bytes sumfiles/g++.sum | 8 +- sumfiles/gcc.log.xz | Bin 2263000 -> 2300524 bytes sumfiles/gcc.sum | 2040 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 891928 -> 894144 bytes sumfiles/gfortran.sum | 10 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213036 -> 213044 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 432808 -> 436184 bytes sumfiles/libstdc++.sum | 2 +- 43 files changed, 1144 insertions(+), 1606 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions