Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[binutils-gdb] branch master updated (7dce788191b -> 478fced3a89)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from 7dce788191b gdb: make target_auxv_parse static and rename new 478fced3a89 Automatic date update in version.in The 1 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: bfd/version.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[binutils-gdb] branch gdb-12-branch updated (cb6780e38d0 -> 8a8906debf2)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch gdb-12-branch in repository binutils-gdb. from cb6780e38d0 Automatic date update in version.in new 8a8906debf2 Automatic date update in version.in The 1 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: bfd/version.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[binutils-gdb] branch master updated (31282a84910 -> 7dce788191b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from 31282a84910 gdb: constify target_stack::is_pushed new 3fe639b81b4 gdb: constify auxv parse functions new e2df8050fe7 gdb: make fprint_target_auxv static new 7dce788191b gdb: make target_auxv_parse static and rename The 3 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: gdb/auxv.c | 38 +++++++++++++++++++++----------------- gdb/auxv.h | 18 ++++-------------- gdb/gdbarch-components.py | 4 ++-- gdb/gdbarch-gen.h | 4 ++-- gdb/gdbarch.c | 2 +- gdb/ppc-linux-nat.c | 10 +++++----- gdb/s390-linux-nat.c | 10 +++++----- gdb/target-debug.h | 2 +- gdb/target-delegates.c | 14 +++++++------- gdb/target.h | 4 ++-- 10 files changed, 50 insertions(+), 56 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-arm updated (6a022d49e5 -> 0889e07cff)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/master-arm in repository toolchain/ci/base-artifacts. discards 6a022d49e5 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits discards 8a223eea03 142: onsuccess: #1761: 1: Success after gcc: 83 commits discards 9b4b8a0654 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] discards 016b534924 140: onsuccess: #1756: 1: Success after binutils: 3 commits discards 2b2b52ae3d 139: onsuccess: #1753: 1: Success after binutils: 5 commits discards c0dc7d1a75 138: onsuccess: #1749: 1: Success after binutils: 5 commits discards b544907fb9 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] discards de534df5c9 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] discards 4c7e030302 135: onsuccess: #1739: 1: Success after binutils: 4 commits discards ff513637c4 134: onsuccess: #1736: 1: Success after binutils: 3 commits discards c33d2c2a63 133: onsuccess: #1733: 1: Success after binutils: 3 commits discards 98e8bd2b7b 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits discards 179e169a47 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits discards 1e51d252d9 130: onsuccess: #1729: 1: Success after gcc: 9 commits discards b9b941a779 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] discards 15e72ab216 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits discards 11af53125f 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] discards 380e702b19 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits discards 9e029a4ff8 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits discards d9a4d7b466 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits discards 1438bb666d 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits discards 59d5c93d22 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits discards cbf60bca33 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits discards 5d2f96ae39 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits discards 02c029038d 119: onsuccess: #1715: 1: Success after binutils: 4 commits discards 03777dc691 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits discards e090efb768 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits discards 043da64d15 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits discards c051c06ee7 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits discards 6d73c9436b 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits discards d5875380d9 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits discards 19f2b5f764 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits discards e63306b7c8 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits discards 789a0ab95a 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits discards 07fef55645 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] discards 44db8d1d74 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits discards 97d5478457 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] discards 894a8717de 106: onsuccess: #1702: 1: Success after gcc: 4 commits discards 934869152b 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits discards fcfe412cac 104: onsuccess: #1700: 1: Success after gcc: 2 commits discards 3a65007a1b 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits discards 03b56eb9c6 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits discards b1c6a70164 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits discards 8039816ee8 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] discards 9ee049fd21 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits discards dd63bd87fc 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits discards 7c69f09a2e 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits discards 5b32e9d05e 96: onsuccess: #1654: 1: Success after gcc: 5 commits discards 69ea81c57d 95: onsuccess: #1653: 1: Success after gcc: 13 commits discards a76cba07ef 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits discards 6b3ddc0b14 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] discards 792a114432 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits discards 692051cd4b 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] discards 751ea9e531 90: onsuccess: #1645: 1: Success after gcc: 2 commits discards 15a009adcb 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] discards b4ab9d0d21 88: onsuccess: 1: Success after binutils/gcc: 2 commits discards c8819e4116 87: onsuccess: 1: Success after gcc: 6 commits discards 95e7aea5f1 86: onsuccess: 1: Success after binutils/gcc: 8 commits discards 2deeafcd4b 85: onsuccess: 1: Success after binutils/gcc: 19 commits discards 4ba68d2c76 84: onsuccess: 1: Success after binutils/gcc: 2 commits discards ee2a6558ec 83: onsuccess: 1: Success after gcc: 14 commits discards 1147809744 82: onsuccess: 1: Success after binutils/gcc: 9 commits discards 6e72cb2073 81: onsuccess: 1: Success after binutils/gcc: 8 commits discards 534bcd4755 80: onsuccess: 1: Success after binutils/gcc: 8 commits discards cd6fe990ef 79: onsuccess: 1: Success after binutils/gcc: 23 commits discards 4f55ca33a1 78: onsuccess: 1: Success after binutils/gcc: 17 commits discards f7537dec36 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards f120bd9e83 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 53e28af672 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards dabcef4c00 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits discards 585e7db8a0 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 21be102a2a 72: onsuccess: 1: Successful build after baseline build: no [...] discards fcb8bd9b77 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards da7db1f3f2 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards e866b1e60f 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] discards 1781f3d758 68: onsuccess: 1: Successful build after gcc: 2 commits discards a8e887bd1c 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 2b3975d7a9 66: onsuccess: 1: Successful build after gcc: 4 commits discards 22998ab31e 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards 1cb7276e1e 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards 487e376b52 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards ad3989d46c 62: onsuccess: 1: Successful build after gcc: 4 commits discards c86a6000cb 61: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 06a05631f6 60: onsuccess: 1: Successful build after binutils/gcc: 12 commits discards ffa3ec5a9b 59: onsuccess: 1: Successful build after binutils/gcc: 29 commits discards 05745f58d0 58: onsuccess: 1: Successful build after binutils: ld: pe: M [...] discards b5ebcbdf28 57: onsuccess: 1: Successful build after binutils: 2 commits discards da969bcdca 56: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards 4c49ed91fe 55: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 9022ff14cb 54: onsuccess: 1: Successful build after gcc: 5 commits discards 30a7cc80b5 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards 0bdff4d010 52: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 099f703940 51: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 44ae5834b0 50: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 0ea1c75d72 49: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards b374faf2ac 48: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 2e824645c2 47: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 46e1a43e22 46: onsuccess: 1: Successful build after baseline build: no [...] discards a42e62937f 45: onsuccess: 1: Successful build after binutils: Fix crash [...] discards b62aa8e3d9 44: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards cae11cdc1c 43: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 1d5c01bf8d 43: onsuccess: 1: Successful build after binutils/gcc: 3 commits new df4b827e66 44: onsuccess: 1: Successful build after binutils/gcc: 2 commits new e78923c6c3 45: onsuccess: 1: Successful build after binutils: Fix crash [...] new 12913f6489 46: onsuccess: 1: Successful build after baseline build: no [...] new a67312b45f 47: onsuccess: 1: Successful build after binutils/gcc: 4 commits new c4f7d226da 48: onsuccess: 1: Successful build after binutils/gcc: 6 commits new cbd423ef79 49: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 58684b956f 50: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 86c2d12dd5 51: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 03f7cb9bf8 52: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 5d43eed341 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits new dfc35b6d82 54: onsuccess: 1: Successful build after gcc: 5 commits new 89549cfb56 55: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 2bb278ac9a 56: onsuccess: 1: Successful build after binutils/gcc: 7 commits new dd87b2d452 57: onsuccess: 1: Successful build after binutils: 2 commits new 2df46c6552 58: onsuccess: 1: Successful build after binutils: ld: pe: M [...] new 25e2ebb297 59: onsuccess: 1: Successful build after binutils/gcc: 29 commits new f17bd15d94 60: onsuccess: 1: Successful build after binutils/gcc: 12 commits new ba89b5c71d 61: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 1fd2a1c781 62: onsuccess: 1: Successful build after gcc: 4 commits new 8e5eb8e43c 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 4dd572a67a 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits new e226eb64d3 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits new c0ea2d0070 66: onsuccess: 1: Successful build after gcc: 4 commits new 633bd3f95a 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new a4b70f1570 68: onsuccess: 1: Successful build after gcc: 2 commits new db88ab3311 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] new df0f732ddd 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 5d96515645 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] new bc16527546 72: onsuccess: 1: Successful build after baseline build: no [...] new 79ca94026d 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits new 594442a583 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits new 6d0b61ce1e 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 1bfdcaf087 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits new a52d3dd13c 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 6d3bbbcca6 78: onsuccess: 1: Success after binutils/gcc: 17 commits new 858e1a4a87 79: onsuccess: 1: Success after binutils/gcc: 23 commits new efe2f3e556 80: onsuccess: 1: Success after binutils/gcc: 8 commits new 9d3c6f1369 81: onsuccess: 1: Success after binutils/gcc: 8 commits new 1d83dc624f 82: onsuccess: 1: Success after binutils/gcc: 9 commits new 780a708bd2 83: onsuccess: 1: Success after gcc: 14 commits new fd3716ef28 84: onsuccess: 1: Success after binutils/gcc: 2 commits new 98e329f9e9 85: onsuccess: 1: Success after binutils/gcc: 19 commits new af9ee7efbb 86: onsuccess: 1: Success after binutils/gcc: 8 commits new 8950595aeb 87: onsuccess: 1: Success after gcc: 6 commits new 9b811372b9 88: onsuccess: 1: Success after binutils/gcc: 2 commits new 5a048027b9 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] new dbfb19c43b 90: onsuccess: #1645: 1: Success after gcc: 2 commits new e9d5efaeca 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] new 42add4f1ad 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits new 188d338a54 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] new 3fa946b9eb 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits new 8df32b9b7d 95: onsuccess: #1653: 1: Success after gcc: 13 commits new 6e8f8b015c 96: onsuccess: #1654: 1: Success after gcc: 5 commits new e0e4c740a2 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits new a46042ef9a 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits new e0195304e1 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits new 3cbdb623ac 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] new f6c174ca5e 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits new b39403d772 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits new c4b4ae4d5f 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits new c329d60511 104: onsuccess: #1700: 1: Success after gcc: 2 commits new b86c0a087e 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits new f636ee9dc3 106: onsuccess: #1702: 1: Success after gcc: 4 commits new 2b4ff61d97 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] new 905b3336df 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits new c5d43a6a4c 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] new bade91755d 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits new 2ad2f26943 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits new 74f2ef03c4 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits new 63fb595f2f 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits new 9253f2b07d 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits new 1f769f7ca5 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits new d29bb678c1 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits new c43e28f133 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits new 614c0d5fb6 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits new e5b95566b4 119: onsuccess: #1715: 1: Success after binutils: 4 commits new 460bc72f2c 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits new d876abd8dc 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits new ebbaee5e46 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits new eef05ee72f 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits new 10a12d5fa0 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits new 491ff368bd 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits new a0266a154e 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits new b47d51ca2f 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] new b05a37d6f9 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits new 2396109580 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] new d41aeafc1c 130: onsuccess: #1729: 1: Success after gcc: 9 commits new ce23e6ba9a 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits new 9aff1cde80 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits new 9296b80cd5 133: onsuccess: #1733: 1: Success after binutils: 3 commits new 1f2fc460dd 134: onsuccess: #1736: 1: Success after binutils: 3 commits new 47eaee5e3d 135: onsuccess: #1739: 1: Success after binutils: 4 commits new 68d1834fd3 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] new e94ed7158d 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] new ea203aef55 138: onsuccess: #1749: 1: Success after binutils: 5 commits new 84b4480c3d 139: onsuccess: #1753: 1: Success after binutils: 5 commits new bc00ac19dd 140: onsuccess: #1756: 1: Success after binutils: 3 commits new 6258b223aa 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] new 936ea7de6d 142: onsuccess: #1761: 1: Success after gcc: 83 commits new 5c7dced54b 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits new 0889e07cff 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 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 (6a022d49e5) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (08 [...] 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 1676 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 51132 -> 51064 bytes 04-build_abe-gcc/console.log.xz | Bin 235108 -> 233100 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3808 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2412 -> 2592 bytes 07-check_regression/console.log.xz | Bin 5956 -> 5452 bytes 07-check_regression/extra-bisect-params | 1 - 07-check_regression/fails.sum | 13 - 07-check_regression/mail-body.txt | 22 +- 07-check_regression/results.compare | 34 +- 07-check_regression/results.compare2 | 204 +- 07-check_regression/results.regressions | 33 - 08-update_baseline/console.log | 46 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 24 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 33 - sumfiles/g++.log.xz | Bin 2776684 -> 2798148 bytes sumfiles/g++.sum | 154 +- sumfiles/gcc.log.xz | Bin 2375608 -> 2347388 bytes sumfiles/gcc.sum | 4546 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 905128 -> 908900 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2180 -> 2160 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 204556 -> 204380 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2532 -> 2548 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 464288 -> 462528 bytes sumfiles/libstdc++.sum | 10 +- 36 files changed, 2536 insertions(+), 2678 deletions(-) delete mode 100644 07-check_regression/extra-bisect-params delete mode 100644 07-check_regression/fails.sum delete mode 100644 07-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (559efce74e -> ca61c02b45)

by git＠git.linaro.org

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 559efce74e 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 63c1f018a9 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 176c309d2d 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 5d542afd47 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 1cbfaacdfe 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 8d0e41657b 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 0aaa1ab8aa 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards b220e4083f 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards c601643a25 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards ab47990f00 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 2546f96474 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards a67877bbc1 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 8a4ebec102 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards d81eab13c0 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 5a5872fa27 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards ae05f3b4b4 128: onsuccess: #2163: 1: Success after linux: 23 commits discards bfb1bfc0c9 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 9543eb0159 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards a6b098c118 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards ac20a348e6 124: onsuccess: #2159: 1: Success after linux: 23 commits discards da46ab2e3a 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 92150ed192 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 2bcef82760 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards d4b22b51a9 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 7f4431c9c8 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards d6db996dad 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 32f8f2f378 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 3365ff707f 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 85293038a6 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 07dbed5b69 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 478825db2a 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards bd98e208d9 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 308183741a 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards f528c4fd66 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 621013332d 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 8a20128be9 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards c81b8c2da0 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 4f348016c6 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 720167d837 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 17e024b2b9 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards a0f4b39dcf 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards dafbbe4143 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 77bf577d27 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 0f9db10030 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 594505c342 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 0b6afd01ba 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards d7e61d54c0 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 5072d07e29 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 081b59a9e8 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards c6c5c9877b 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 2d3b9337ca 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 713e9c0c0b 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 1533711e42 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 7d19540397 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 083e10cb01 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 4160c37d91 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 0aac634ee5 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 5ef1cce5bb 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 348b38e222 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards d5fcdf90be 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 95b06ad7db 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards e20d0c88c5 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 40cc24895d 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards d4c4383191 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ecd34921a3 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 3ea87441ae 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards ca0f783001 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 62e4dedefe 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 87e757f75f 75: onsuccess: 1: Successful build after linux: 44 commits discards 7b7cc76188 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards f657699241 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3e81242408 72: onsuccess: 1: Successful build after linux: 12 commits discards efa699ba65 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards fbf6dcca5f 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 089a7423a8 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards a632f57e6f 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 03e9305e26 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards b147fcc4f8 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 6c2756e778 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8148c1e84f 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 060affc95c 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards af334d65f8 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 7cca21bd1d 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 7a43f08e5a 60: onsuccess: 1: Successful build after glibc: 2 commits discards a0393d2280 59: onsuccess: 1: Successful build after binutils: 2 commits discards 51c303aefb 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 06c8e6513c 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 5718f2ca00 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6c5d5ad949 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 6914ef00c8 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 2ddd6b907e 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 7b1207843b 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards deea8520da 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 98c848a442 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards f28c6a17eb 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards f8dc24ae5c 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9edb09341d 47: onsuccess: 1: Successful build after linux: 10 commits discards a1ad0cf0bf 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 052647061a 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7094c1ed0d 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 1e87609169 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 1dc07fe92b 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 4c8e64bfeb 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 7d1aa79ddb 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b794509600 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new e4c56ea6b4 47: onsuccess: 1: Successful build after linux: 10 commits new 5f56201ca0 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new df07fe6b22 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new a578111d8c 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 9cff3a5581 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 84c7016f0c 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 0dd6c6a1e4 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new ec9b5c2ef3 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 633b3506cd 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 2447fe8794 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7db3f0324b 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 075b818817 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new ef01651b3e 59: onsuccess: 1: Successful build after binutils: 2 commits new 82b15dd902 60: onsuccess: 1: Successful build after glibc: 2 commits new 823a585d85 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 802563cbad 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new c8e9e63db1 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 92b2d448a6 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 17ff15c2e2 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0a60a8b8c4 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 75337e0acc 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 8811920845 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 28d74518b4 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 42c40d7b79 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 834dc23130 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 81f8ea66b9 72: onsuccess: 1: Successful build after linux: 12 commits new 011ba2bf59 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 37c4d2042d 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new ae4a06046b 75: onsuccess: 1: Successful build after linux: 44 commits new e73bd2505d 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d22e298b04 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 013ac56063 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new cce1c8d871 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a65a0159e7 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4e7908b3dd 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 49a8ec890d 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 7324229d23 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 4dcb0ee794 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new d6e8ec44b0 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new b99ae2b216 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 3699c9ad8b 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new dfb04e6904 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 720824ce7b 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new c44754c976 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 23e74b3960 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new d35d9af008 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new c97fbaadcd 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new bc7fb63495 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 4924a09012 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 8b0d4129a9 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new b8ece9096a 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 82c202a2f2 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new ed58ee5769 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 7429d6df35 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 56200baf9a 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 0ed4e327ce 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 7c8abf8148 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new e7101e1f17 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 329ac8f71e 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new e8dbe7945c 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new df0a126fbd 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 1147a614ed 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 0572a129ac 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 732109ff19 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 333549c8e3 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new cc71706965 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new b29cab3f3b 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 40ce0eb38a 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 0aab5795a1 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 6698a29ca8 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 1d05e93568 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 9353fd2f1c 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new de494da3aa 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 3a36c6c046 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 889a2782ef 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 4f791791b7 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new dacf19a3c3 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 19fde11b1a 124: onsuccess: #2159: 1: Success after linux: 23 commits new db63b028b7 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 104d0201e7 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 139b987915 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 34c525236c 128: onsuccess: #2163: 1: Success after linux: 23 commits new 57a86c5120 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 5dcfcdc07e 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 072bb16431 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new af8166c7d5 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new d8bae3f689 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 863e5c781a 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new ce45154710 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 776c75ef77 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new dd2518f5f9 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 3d3d6ad826 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 6ff51d2f77 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new c1c9e285a3 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 098c778525 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 4a5f7126a3 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 716e75cfe3 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new ca61c02b45 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] 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 (559efce74e) \ 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 1736 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30264 -> 30200 bytes 04-build_abe-stage1/console.log.xz | Bin 72448 -> 72464 bytes 06-build_abe-linux/console.log.xz | Bin 8716 -> 9288 bytes 07-build_abe-glibc/console.log.xz | Bin 239660 -> 240172 bytes 08-build_abe-stage2/console.log.xz | Bin 202688 -> 202948 bytes 09-build_abe-gdb/console.log.xz | Bin 37300 -> 37528 bytes 10-build_abe-qemu/console.log.xz | Bin 32124 -> 31820 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3876 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2628 -> 2660 bytes 13-check_regression/console.log.xz | Bin 11884 -> 7032 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 17 +- 13-check_regression/mail-body.txt | 73 +- 13-check_regression/results.compare | 615 +---- 13-check_regression/results.compare2 | 804 +----- 13-check_regression/results.regressions | 98 +- 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 | 75 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 98 +- sumfiles/g++.log.xz | Bin 3419800 -> 3413944 bytes sumfiles/g++.sum | 116 +- sumfiles/gcc.log.xz | Bin 3028080 -> 3024756 bytes sumfiles/gcc.sum | 4429 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1035388 -> 1028436 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202004 -> 202196 bytes sumfiles/libgomp.sum | 12 +- sumfiles/libitm.log.xz | Bin 2656 -> 2660 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 431248 -> 424008 bytes sumfiles/libstdc++.sum | 6 +- 43 files changed, 2570 insertions(+), 3893 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm updated (5238701a0c -> 8ce5d3dbb3)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm in repository toolchain/ci/base-artifacts. from 5238701a0c 51: onsuccess: #493: 1: Success after binutils: 13 commits new 8ce5d3dbb3 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] The 1 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 1720 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2700 bytes 03-build_abe-binutils/console.log.xz | Bin 51396 -> 50336 bytes 04-build_abe-gcc/console.log.xz | Bin 231368 -> 232820 bytes 06-build_abe-linux/console.log.xz | Bin 8384 -> 8396 bytes 07-build_abe-glibc/console.log.xz | Bin 232228 -> 232484 bytes 08-build_abe-gdb/console.log.xz | Bin 48320 -> 49464 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3804 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2872 -> 2612 bytes 11-check_regression/console.log.xz | Bin 4808 -> 11176 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 13 + 11-check_regression/mail-body.txt | 73 + 11-check_regression/results.compare | 56 +- 11-check_regression/results.compare2 | 1049 +++++++- 11-check_regression/results.regressions | 73 + dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 75 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 73 + sumfiles/g++.log.xz | Bin 2841308 -> 2859104 bytes sumfiles/g++.sum | 767 +++++- sumfiles/gcc.log.xz | Bin 2495060 -> 2478164 bytes sumfiles/gcc.sum | 4465 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 946936 -> 946060 bytes sumfiles/gfortran.sum | 12 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217640 -> 218068 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2676 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 464164 -> 466944 bytes sumfiles/libstdc++.sum | 30 +- 41 files changed, 4475 insertions(+), 2268 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[gcc] branch master updated (7ea258a13a1 -> 3a3516bc4a0)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 7ea258a13a1 Process unsigned overflow relations for plus and minus is r [...] new 3a3516bc4a0 c: C2x noreturn attribute The 1 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: gcc/c-family/c-lex.cc | 3 ++ gcc/c/c-decl.cc | 25 ++++++++++ gcc/testsuite/gcc.dg/c2x-attr-noreturn-1.c | 56 ++++++++++++++++++++++ gcc/testsuite/gcc.dg/c2x-attr-noreturn-2.c | 72 ++++++++++++++++++++++++++++ gcc/testsuite/gcc.dg/c2x-attr-noreturn-3.c | 11 +++++ gcc/testsuite/gcc.dg/c2x-has-c-attribute-2.c | 16 +++++++ 6 files changed, 183 insertions(+) create mode 100644 gcc/testsuite/gcc.dg/c2x-attr-noreturn-1.c create mode 100644 gcc/testsuite/gcc.dg/c2x-attr-noreturn-2.c create mode 100644 gcc/testsuite/gcc.dg/c2x-attr-noreturn-3.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allyesconfig updated (17c77c4c00 -> 4677e6fa72)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allyesconfig in repository toolchain/ci/base-artifacts. from 17c77c4c00 20: force: #495: 37: Failure after llvmorg-16-init-5673-ge07 [...] new 4677e6fa72 21: onsuccess: #496: 37: Success after llvm: 180 commits The 1 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 1640 -> 1996 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30620 -> 30732 bytes 04-build_kernel_llvm/console.log.xz | Bin 63608 -> 63808 bytes 05-build_abe-qemu/console.log.xz | Bin 32160 -> 32396 bytes 06-build_linux/console.log.xz | Bin 4084 -> 4508 bytes 08-check_regression/console.log.xz | Bin 3776 -> 3016 bytes 08-check_regression/jira-body.txt | 2 +- 08-check_regression/mail-body.txt | 24 +- 08-check_regression/mail-subject.txt | 2 +- 08-check_regression/results.regressions | 9 - 08-check_regression/trigger-bisect | 2 - 08-check_regression/trigger-notify | 0 09-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/llvm_rev | 2 +- jenkins/jira-status.draft | 4 - jenkins/mail-body.draft | 444 -------------------------------- jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/jira-body.txt | 2 +- mail/mail-body.txt | 24 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 9 - 26 files changed, 36 insertions(+), 513 deletions(-) delete mode 100644 08-check_regression/results.regressions delete mode 100644 08-check_regression/trigger-bisect delete mode 100644 08-check_regression/trigger-notify delete mode 100644 jenkins/jira-status.draft delete mode 100644 jenkins/mail-body.draft delete mode 100644 jenkins/mail-recipients.draft delete mode 100644 jenkins/mail-subject.draft delete mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[gcc] branch master updated (c2ee70f20de -> 7ea258a13a1)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from c2ee70f20de c++: implicit lookup of std::initializer_list [PR102576] new 845ee38e9b4 Remove undefined behaviour from testscase. new ef9bc3626ce Audit op1_range and op2_range for undefined LHS. new cfa7434c4b0 Move class value_relation the header file. new 431cdfbea1f Track value_relations in GORI. new 67166c9ec35 Refine ranges using relations in GORI. new 7ea258a13a1 Process unsigned overflow relations for plus and minus is r [...] The 6 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: gcc/gimple-range-gori.cc | 188 +++++++++++++++++++++++++++++--- gcc/gimple-range-gori.h | 17 ++- gcc/gimple-range-op.cc | 12 +- gcc/gimple-range-op.h | 6 +- gcc/range-op.cc | 150 ++++++++++++++++++++++++- gcc/testsuite/gcc.dg/pr102892-1.c | 2 +- gcc/testsuite/gcc.dg/tree-ssa/pr79095.c | 6 +- gcc/value-relation.cc | 55 ---------- gcc/value-relation.h | 59 ++++++++++ 9 files changed, 403 insertions(+), 92 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allyesconfig updated (7756d0d351 -> 17c77c4c00)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allyesconfig in repository toolchain/ci/base-artifacts. from 7756d0d351 19: force: #494: all: Success after llvm: 81 commits new 17c77c4c00 20: force: #495: 37: Failure after llvmorg-16-init-5673-ge07 [...] The 1 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 1872 -> 1640 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30572 -> 30620 bytes 04-build_kernel_llvm/console.log.xz | Bin 63604 -> 63608 bytes 05-build_abe-qemu/console.log.xz | Bin 32240 -> 32160 bytes 06-build_linux/console.log.xz | Bin 3408 -> 4084 bytes 07-boot_linux/console.log.xz | Bin 576 -> 0 bytes 08-check_regression/console.log.xz | Bin 2972 -> 3776 bytes 08-check_regression/jira-body.txt | 2 +- 08-check_regression/mail-body.txt | 15 +- 08-check_regression/mail-subject.txt | 2 +- 08-check_regression/results.regressions | 9 + 08-check_regression/trigger-bisect | 2 + 08-check_regression/trigger-notify | 0 dashboard/dashboard-generate.sh | 2 +- git/llvm_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 444 ++++++++++++++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 15 +- mail/mail-subject.txt | 2 +- manifest.sh | 12 +- results | 13 +- 26 files changed, 508 insertions(+), 23 deletions(-) delete mode 100644 07-boot_linux/console.log.xz create mode 100644 08-check_regression/results.regressions create mode 100644 08-check_regression/trigger-bisect create mode 100644 08-check_regression/trigger-notify create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits September 2022