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 5b77c210ef9 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards d0872b8b5c3 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 84246ebae5a 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] discards ab393a23d93 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] discards d6144d8ce00 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] discards e6aadb22009 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 1fc0af9adb2 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] discards a036fd930e1 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards ca67058717c 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] discards 4a571c5b9a0 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] discards f702996c8d3 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] discards 1f6884d7ef0 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] discards abe30d28952 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 697a3635dd3 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards ecec629462c 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] discards 1fdf9757f26 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] discards 8627c24a74d 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] discards cd1460d1e73 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] discards 169da2d84f6 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] discards 65e1653094c 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] discards f99e31f5fa2 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] discards 3d56458f535 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] discards 9b803965971 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] discards 7a8d2a09baa 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] discards 9058843fd4c 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] discards b8ffd91fb99 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] discards c8a680496e3 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] discards 7fea8274971 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] discards edbc33835bd 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] discards dd6022e9d5e 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] discards de32ed5c803 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] discards 52d91985210 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] discards dfd00286a6d 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] discards 8197145748c 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] discards cc91ba1869e 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] discards 52516763861 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] discards a19c0958dd5 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] discards 6c56ae325e6 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] discards 9632556870a 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] discards 4c8294d8f01 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] discards c6ad8af7a0b 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] discards 0126e22b238 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] discards 9170fbbf3fd 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] discards c2a2b36b28e 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards ed3e3f50d6e 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] discards deb851d7cd7 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] discards d6d51d15a2b 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] discards 699c2dca8fa 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] discards 78c9655542a 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] discards 63e66e1fbb5 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] discards b3c9b2eb5b9 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 8a1b5d4568f 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] discards 46d90509310 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards be1a4fccc82 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 78f8896f5ad 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] discards 82b10b6ae19 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] discards 3454ec0c9e4 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] discards fe1d4c14d8d 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] discards cbe1d7a2c0f 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] discards 0bb7d5c13f6 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] discards 35660647a20 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] discards 422d57710fa 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] discards 778906bb6bf 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards dedc846503d 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] discards 3a9a67872ff 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] discards 137391ee91c 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] discards ed280d3cfb0 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] discards 5ed1cbf2260 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] discards cbf10d472b4 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] discards ab317f72134 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 0a02aacc5a0 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] discards af29062985d 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 5d83e07b4f4 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 2df881c22ae 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] discards c2c6ca79040 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] discards 32f7c567787 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] discards d14d7781bf8 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 12e95a603da 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] discards 8ecb68491cb 128: onsuccess: #1723: 1: Success after linux: 12 commits discards a1f62f77ea3 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] discards a57a20f5e3f 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards dd8c0bca243 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] discards ebd1405f107 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards f3d8abd3e78 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] discards 0a6c596f16a 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] discards 6eb4ca059a5 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] discards e260d468ffc 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] discards b665504af52 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] discards 1c51d419778 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] discards e267fc3a1c3 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] discards f87c18e7f35 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] discards df0e024d3f1 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] discards c01285b152e 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 293f55dd097 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] discards be042351a60 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] discards 1916a539526 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/ [...] discards 80560c18353 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 10ebece9e25 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 [...] discards 797d93dfcda 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 [...] discards a9d54348d23 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/ [...] discards fc6ad1c2827 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/ [...] new f3ee726a057 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/ [...] new 1899aadc51c 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/ [...] new 0af2aecfbad 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 [...] new 8f6fe9fdaff 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 [...] new 3353ebc09fe 110: onsuccess: #1703: 1: Success after gcc: 6 commits new f3f01792338 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/ [...] new a1a090b6f1d 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] new 8dc6e09e4da 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] new d0e85eaec8f 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 53e72ae965b 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] new ffd5093ab9c 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] new 847b15e6d11 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] new 2140975ce18 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] new 2d4ffa77018 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] new b610ece685c 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] new 97fe73335b4 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] new 23a39f2e0d8 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] new 13b39a02351 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] new 5bb4b4919aa 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new b1995d632c6 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] new e77df884d42 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 627c81ad1e3 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] new b610404e806 128: onsuccess: #1723: 1: Success after linux: 12 commits new faa75e76ed2 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] new 47d950db33d 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new aa32ca2ceca 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] new d101b2ec5f8 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] new a4a37b9d193 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] new f61cbf07519 134: onsuccess: #1730: 1: Success after binutils: 2 commits new a0d9b8f7b7a 135: onsuccess: #1733: 1: Success after binutils: 5 commits new e7726d05191 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] new a49ad79b642 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 5d48015ee3c 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] new 02e44c9b4b6 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] new 83d95237431 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] new 8329cb778f5 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new e1c243999f2 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] new 34026b0c753 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] new 80c1fa09cf2 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 4874fb46ba1 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] new ba66bbbb7eb 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] new a9dd265baf8 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] new 89e13b5ada7 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] new dbe665a0dea 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] new 997dfcbd438 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] new f9c9eb7ac49 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] new 91a16c1a749 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] new 83f43769b7a 153: onsuccess: #1754: 1: Success after gcc: 2 commits new f0398411ab4 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 4f6004aeb0c 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] new b297b73da89 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 4335f67f002 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] new 8b2c2592077 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] new 22f73ce6108 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] new d5bd84185c8 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] new a49d292a583 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] new 57d57bba9df 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] new 5705fd5ba5d 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 96df0b6aeb4 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] new 44f1975f011 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] new 7ea7d21734c 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] new 7ca6e060c8a 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] new a232ec810d1 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] new bff427ebd03 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] new 218da5b8270 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] new d60e7cfadc8 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] new ff97dd5228c 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] new c3509cbb6c4 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] new 22b82369931 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] new c0278fdcd80 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] new d6c54ba3ce9 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] new 78aaf0dcce5 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] new 1b6810620ab 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] new 8f215142e8e 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] new c26197969da 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] new 55ae8aa91d8 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] new 5b305fb0345 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] new b68dc154fd8 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] new ddfb95f71e7 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] new a59ead2494f 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] new f0e679cf36c 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] new 2b0526b2811 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] new d62771ca000 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] new 02c3d74fc7f 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] new 9c3a36750e2 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] new 7d3ef72fa39 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] new c64a55f024c 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] new efda9f16848 193: onsuccess: #1992: 1: Success after binutils: 151 commits new ec1ee285035 194: onsuccess: #1995: 1: Success after linux: 517 commits new 9342251788d 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] new 1039b5968ee 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] new 4c37b4f0c64 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] new c7b07e3d8ef 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] new 95214c86b30 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 3e50627e1eb 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] new 8593e5b114e 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new adcd7d27113 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] new ccb29c5f571 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] new 0a5a52836ba 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] new ec9758bd248 205: onsuccess: #2006: 1: Success after gcc: 3 commits new e7be90a2b32 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 003217aef8e 207: onsuccess: #2010: 1: Success after gcc: 4 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 (5b77c210ef9) \ 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 1716 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31668 -> 31808 bytes 04-build_abe-stage1/console.log.xz | Bin 92916 -> 91632 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8760 -> 8888 bytes 07-build_abe-glibc/console.log.xz | Bin 238580 -> 237640 bytes 08-build_abe-stage2/console.log.xz | Bin 227828 -> 225308 bytes 09-build_abe-gdb/console.log.xz | Bin 38668 -> 38868 bytes 10-build_abe-qemu/console.log.xz | Bin 30300 -> 31136 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3892 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2840 -> 2464 bytes 13-check_regression/console.log.xz | Bin 5848 -> 5140 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 74 +- 13-check_regression/results.compare | 49 +- 13-check_regression/results.compare2 | 70 +- 13-check_regression/results.regressions | 42 - 14-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 76 +- mail/mail-subject.txt | 2 +- manifest.sh | 29 +- results | 42 - sumfiles/g++.log.xz | Bin 2713012 -> 2736252 bytes sumfiles/g++.sum | 124 +- sumfiles/gcc.log.xz | Bin 2307644 -> 2276584 bytes sumfiles/gcc.sum | 2444 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 892524 -> 894432 bytes sumfiles/gfortran.sum | 110 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 213108 -> 213064 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 429696 -> 438576 bytes sumfiles/libstdc++.sum | 10 +- 41 files changed, 1473 insertions(+), 1698 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