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 cbb5f1c32c2 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] discards 17474b569f4 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 440fed7062c 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] discards 15fa5ded7df 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 8b625421b03 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] discards 13758e27a74 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] discards 6dda4d4a406 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] discards 1095c12f746 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] discards b1438e42f1d 194: onsuccess: #1995: 1: Success after linux: 517 commits discards ec77b6477d8 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 59b9968a306 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] discards a9372dae40b 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] discards b5883ad801c 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] discards f3541dd5d1f 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] discards b2861ef8f66 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] discards e398d880f79 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] discards 7fb00064f33 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] discards 263b5cb982e 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] discards 6af5093eb03 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] discards 68f54c300cd 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] discards 25894cda5db 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] discards 39bc7d06257 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] discards eba8dd08741 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] discards 1499bb51bf7 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] discards 17b78fa8485 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] discards b3adb0b107d 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] discards 8a0a1e1c9dc 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] discards 9adc68a24d6 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] discards 58b056ae106 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] discards f6ac162ab4b 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] discards dcae5eee0dc 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] discards 43a39b642d5 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] discards 9a14ac5f05f 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] discards b5feb252411 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] discards 30f93ad9470 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] discards 1c4bfc73473 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] discards d995b8d084d 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] discards 485296625e8 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] discards 19155c24b29 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] discards 671e9fe4993 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 36ef49cbc64 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] discards 8316868fb5b 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] discards e1f5c58f1dd 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] discards b992503b497 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] discards 1da3935fe0d 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] discards adba4b95b3a 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] discards 67a620fdbcc 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 40c02290eb0 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] discards 31e9fc500e1 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 7098b9782c0 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 9f75153ad90 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] discards 45eea25eb9f 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] discards ec97e3b35e8 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] discards ac097cba221 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] discards 94bc8465b1e 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] discards 9b30af83ec1 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] discards 2d6ffdb618f 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] discards 88e2fd90f91 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] discards b3d6d00ad17 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 54707773b35 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] discards f2a2021df16 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] discards ba91be86ee6 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] discards 7997d232f7b 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] discards 1767c6a9f54 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] discards e5cc52e8c2c 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] discards 6ad428796b0 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards de873e61534 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] discards 97ed4211660 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards eac7ba23f95 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 0bfc64793d2 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] discards dbf609afef8 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] discards 8e5b23ee161 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] discards 2efa1e3611e 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 43df669235b 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] discards 6978ed10ed8 128: onsuccess: #1723: 1: Success after linux: 12 commits discards e917d79e7b5 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] discards e46b79ca1b0 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 1f816d88f95 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] discards c236a351b43 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 71c85e43f94 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] discards 4fc60aad4bd 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] discards 7381cae4877 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] discards 48364baf4ff 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] discards 29a83112cbe 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] discards 17a9ba88a2e 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] discards 5416a9ac356 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] discards 598a98e5413 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] discards 3cf79c22603 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] discards 11a36d413ba 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 757160d175e 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] discards 9a8724250d7 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] discards de5000e68bf 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/ [...] discards eceaf2869d0 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards a0df6f58c7c 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 [...] discards 867a79cc4e4 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 [...] discards 365c23dc9fd 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/ [...] discards 7ed724f2b55 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/ [...] discards 26776d42a58 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38edde [...] discards 6f8dcb3c86f 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 22404093040 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/ [...] discards 2410fca7490 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/ [...] new 9bc7f8037e4 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/ [...] new d5b81a3cca0 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/ [...] new bbf599fc724 104: onsuccess: #1697: 1: Success after gcc: 4 commits new f9d8a00bc1b 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38edde [...] new 55f8cddb17d 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/ [...] new d1a8e808ff8 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/ [...] new 1a4add35a41 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 [...] new 9bc05162427 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 [...] new 2445194b4ea 110: onsuccess: #1703: 1: Success after gcc: 6 commits new f58ea2a7a69 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/ [...] new 63ea3e7faef 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] new 200a5c73be4 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] new 95e6e525678 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 7ffd323b767 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] new d74bdea9a5b 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] new a1b09553ac5 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] new c4bbae0f9f9 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] new ed380184fd9 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] new 32509b2c86a 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] new 52482adb57b 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] new ed20f9156ec 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] new f195fda10d7 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] new ed6053661d2 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new d3fad9acbba 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] new 268ea654e88 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 4ac05586fbb 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] new b62bfb13577 128: onsuccess: #1723: 1: Success after linux: 12 commits new d999b187b57 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] new fe94464f4bc 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new c44d5e8505e 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] new 70ef2165ee3 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] new fd1655e4820 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] new ae5dcc76e82 134: onsuccess: #1730: 1: Success after binutils: 2 commits new d3c0b0c5516 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 128a9ab29f9 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] new 23bf1e78dc6 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 35fa160ef9a 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] new e8aacbf0d8d 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] new d8bce6c323d 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] new 0832e7bafd8 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new 48e5255479f 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] new 5fc8f848f3d 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] new 92a39af8577 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 51833389a24 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] new b39cca58b8f 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] new db05e170540 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] new 67799e29512 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] new 7977de97b36 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] new f44a4acccd9 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] new 1c64a62f765 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] new 35655de883d 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] new fecb5e9e32d 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 279759d98e8 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new ba9c1b44751 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] new b85b9b893e3 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 830c483fa40 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] new da4b78250aa 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] new 2ab3bb8e1be 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] new da36dec5b03 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] new 87f90e512fa 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] new 8d1dceb8872 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] new 4aac7d53d84 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 566ebd2708f 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] new 1af88c67a59 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] new 22c0f8e05a6 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] new a252871ea26 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] new d93b07c912f 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] new 56f204566cc 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] new 79e1aaa8a9f 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] new e7cefe927e8 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] new 6f6f2891be4 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] new 71e13c77a26 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] new 48502d3eb32 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] new 25be8bed68e 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] new 070f9ac152e 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] new aee6538bc02 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] new bf5659de77b 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] new 7627dc38d2c 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] new ee8becc9926 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] new 58f5847462f 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] new feaf06b5c1e 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] new 6aa95f20b9c 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] new 2b1661e804d 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] new f90cf6f7b5f 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] new ccf5fa33a88 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] new e1ad1d133bc 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] new a3b0a674595 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] new ad98271b740 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] new badb7c9feec 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] new ce5f601edc2 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] new a12a9a808f5 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] new b8fd1a9eb1f 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 5793db3a30c 194: onsuccess: #1995: 1: Success after linux: 517 commits new 1f89fb33f89 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] new b674ff1fd2b 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] new f169656c45a 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] new f6b70a11682 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] new 013981500fc 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 20930657385 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] new 78f1b366b5f 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 249b837b538 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] new 5411faeab38 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...]
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 (cbb5f1c32c2) \ 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 1740 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 31668 -> 32168 bytes 04-build_abe-stage1/console.log.xz | Bin 91744 -> 92852 bytes 06-build_abe-linux/console.log.xz | Bin 8608 -> 8672 bytes 07-build_abe-glibc/console.log.xz | Bin 237948 -> 238516 bytes 08-build_abe-stage2/console.log.xz | Bin 225264 -> 227576 bytes 09-build_abe-gdb/console.log.xz | Bin 38964 -> 39424 bytes 10-build_abe-qemu/console.log.xz | Bin 30572 -> 30972 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3876 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2644 -> 3020 bytes 13-check_regression/console.log.xz | Bin 8076 -> 5904 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 86 +- 13-check_regression/results.compare | 38 +- 13-check_regression/results.compare2 | 87 +- 13-check_regression/results.regressions | 49 - 14-update_baseline/console.log | 68 +- 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 | 88 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 49 - sumfiles/g++.log.xz | Bin 2694376 -> 2710896 bytes sumfiles/g++.sum | 44 +- sumfiles/gcc.log.xz | Bin 2312924 -> 2309872 bytes sumfiles/gcc.sum | 2240 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 890136 -> 896484 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213184 -> 213124 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 424852 -> 430584 bytes sumfiles/libstdc++.sum | 2 +- 42 files changed, 1286 insertions(+), 1530 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