Tcwg-commits January 2023

tcwg-commits@lists.linaro.org

5 participants
4127 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (7bc763ee21 -> 8814c231be)

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-arm in repository toolchain/ci/base-artifacts. discards 7bc763ee21 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards bdcddcca28 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 3ddfc806b3 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards d21483c01c 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards c242bc8336 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards a68aab3d3f 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards a633e0c1fb 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards df6b79428e 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards c55887bd70 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 22adbce366 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 14f5bc69ee 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards d89e2980a6 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards f6a62c895f 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 3271690b8b 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 9a0719b996 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 601d1c1943 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 350082c777 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 67bcadc2c4 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 9c893c28b8 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 2c30e3dc63 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards d2d45aefdd 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 7e4bd53340 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards cd1b460e84 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 026ab31667 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 37b0ac18aa 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards d4770e882d 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 6ec5f0f8cc 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards b318dda81d 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards d4cdf146d0 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 1962211de5 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 4306eb3976 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 95e5091d66 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 1036498a9f 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards a39f50a361 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 32749529fb 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 9ba2c9f3b5 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards c454ab3588 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 9cc3adce5a 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 7f1214cff2 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 8e95001a83 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards a2780b4fc3 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards ff02c4a303 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 234fa3c882 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 0211b7d030 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards ac4691a4ee 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 770c1f5efc 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 30f5c244ed 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 7f697d67aa 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 24a2ff792c 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 5193f1a616 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards e66f63ee73 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 33a664c6ad 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 6d8a98bc4e 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 6d22bcb86f 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 0b0b470d36 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 5ac0b60a9f 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 2189ec8002 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 2f03a3296f 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 474269801a 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 786e51ef9c 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 519c6822f3 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 5fa206c888 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 02848c1dc5 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 2eb7c56023 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards c13390586a 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 6441c48d73 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 8da040aa78 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 6723929448 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards d5f95a3985 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 158ea4a86d 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 555e52b030 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards dbe32509b5 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards a47d3ff5c5 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 6b9b1890ea 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 57f78eb158 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 58c5f9a607 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 59813fe789 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 7c86a854f8 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 1f434da895 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards b6ed2a187b 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards ed73d9c698 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 0ed8eaf04e 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 21ec6a9c7f 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 6afdcc296d 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 1431c8a4fd 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 566cd6ddab 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards e6402fb90f 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 62b1d64034 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards ccb70fc398 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 7f3b3b4020 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 52177740d8 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards a8fc523fc7 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards e830270b72 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards bd2c0abf9e 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 95ac7c0483 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 96d84601f8 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards f9982b9c4d 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 01080bb874 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 3f707f7385 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 6f07448658 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards cefa8ddd1f 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new 2291bacdce 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new 4d42e7f695 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 6076050cbe 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 27a049f1f3 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 6d9eb76708 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 434610c259 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 1f04812c80 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new a2db70e6e6 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 394b9defc4 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new d903fa451d 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 8a90e9864f 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 0235ee01f0 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 46da6b42ec 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new b74e17af35 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 57d68e49ff 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 2eaab2bae4 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 04b00c5752 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 84d456b246 259: onsuccess: #2075: 1: Success after glibc: 2 commits new d4232b0c93 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new dafb365c7b 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 70e3aeee58 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 8b930ad75d 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 970eb63c12 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 5890bf8cc7 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 3ab0a4a5a3 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new cb8857245a 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new e22d3e6cdf 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 99a647a865 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 9804567c88 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 265a22f6e7 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new d280e86226 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new eaf7aa629e 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new cd1492e873 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 280b1636be 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 4979046725 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new cfcc3dc229 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new f279d32f14 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 53cc5b7046 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 771d2cdc17 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 0ea48c59f4 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 75239af78d 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new b6a6e4f90c 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 071eede2b0 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new f417a2bb37 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new a5e7312561 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 76b7ec9f94 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 54999114c8 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new ec2039f851 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new d4028c7c39 290: onsuccess: #2106: 1: Success after gcc: 2 commits new ad78cff61c 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 22a4034027 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new a01e99dbf0 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new a23b7f9db2 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 11f2a7d560 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 32d8b1c36e 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new a751ebbfb6 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 087da8064f 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 99224ce984 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 66ebee1e9d 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new ce208149e5 301: onsuccess: #2118: 1: Success after linux: 16 commits new 0ed9e52e6b 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 7209e15d85 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 264b6070c8 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 7d6709ac80 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 6e1406bade 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 2304408033 307: onsuccess: #2124: 1: Success after gcc: 2 commits new fc6751a62e 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new b3a983375f 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new d4ef755e61 310: onsuccess: #2129: 1: Success after binutils: 4 commits new ce10c6d2d0 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 03fd1c1649 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new f15708bf6f 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 100a6b30a8 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 948e22ece1 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new a0ad344cae 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new c33337cbcb 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 58d1326417 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 01f1e772ea 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 5af9de8091 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new e3406b279b 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new bd06e55048 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 6a6acdf150 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 8d54374ec8 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 6554c83ff7 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 07b4f79657 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new b81883f0f8 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 4995faaa82 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new d5f098d983 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 324c1483c9 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new c975db6f7b 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 0877834bc7 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new bf59315026 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new cfd2c49ec7 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 5ce507b6dd 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 6052990780 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 61b1367c96 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 2f3bccb9d3 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 13f9370e7c 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 7e1dcee376 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 18cdca8537 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new c6870c9a7a 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 8814c231be 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 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 (7bc763ee21) \ 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 1752 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31636 -> 31956 bytes 04-build_abe-stage1/console.log.xz | Bin 91496 -> 91504 bytes 06-build_abe-linux/console.log.xz | Bin 9284 -> 9296 bytes 07-build_abe-glibc/console.log.xz | Bin 236100 -> 236396 bytes 08-build_abe-stage2/console.log.xz | Bin 227956 -> 228052 bytes 09-build_abe-gdb/console.log.xz | Bin 39388 -> 39268 bytes 10-build_abe-qemu/console.log.xz | Bin 31124 -> 31476 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2484 -> 2624 bytes 13-check_regression/console.log.xz | Bin 6952 -> 5212 bytes 13-check_regression/results.compare2 | 82 +- 14-update_baseline/console.log | 66 +- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.xz | Bin 2687528 -> 2692244 bytes sumfiles/g++.sum | 18 +- sumfiles/gcc.log.xz | Bin 2249912 -> 2252124 bytes sumfiles/gcc.sum | 2572 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 896548 -> 899100 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214056 -> 214192 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 438696 -> 437496 bytes sumfiles/libstdc++.sum | 2 +- 36 files changed, 1364 insertions(+), 1432 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (f06ffa8554 -> e0931ecd73)

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_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards f06ffa8554 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards 27c47fd085 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] discards 1c6866e30d 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] discards f154a5a8e8 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits discards 5b70a2f08f 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] discards fcae6ad58a 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] discards 80b9d7f9f2 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] discards 54d7706576 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits discards ae88cea759 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] discards 40958001cf 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] discards 6e2316b6d8 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] discards 0d82b4cb5a 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] discards 82f9117d45 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits discards 3b286fa729 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] discards d3687a39e5 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits discards a48cf88fec 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits discards 65d79b21a1 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] discards f39d3dd4b3 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] discards c8f290f4d5 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] discards 24811643b6 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] discards 99ad64cd34 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] discards 8c052ba1bc 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] discards 7609ef7344 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits discards 199786afd8 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] discards 00fc12605b 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] discards ff2dbe3956 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards 9f22167ff7 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] discards 8f39ab53c3 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] discards e97636159e 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards d70fa9d32e 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] discards 870e4994aa 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] discards 2a7d42fd87 305: force: #2006: 7: Success after gdb: 2 commits discards d1533be7c0 304: onsuccess: #2002: 7: Success after gcc: 4 commits discards 8f5ecf1e0d 303: onsuccess: #2001: 7: Success after binutils: 4 commits discards 77728e3e88 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] discards 625369984a 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits discards c8ee68a97e 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] discards dc7218b635 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] discards d4753aaa14 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits discards 7a1f3114ae 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits discards 9d3f35e503 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] discards 3e9361b5ac 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits discards 6ab0d7e811 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits discards 6446c35e8f 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] discards 5941904c16 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits discards cbeec0e303 291: onsuccess: #1988: 7: Success after binutils/gcc/gdb: 5 commits discards 67368b41c8 290: onsuccess: #1987: 7: Success after gcc/linux: 26 commits discards 52a13195eb 289: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] discards 54b74ca03c 288: onsuccess: #1985: 7: Success after gcc: 17 commits discards e219568d6d 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits discards 649f9066b6 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits discards 2b4a2af5c6 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits discards f1a413f2c9 284: onsuccess: #1981: 7: Success after gcc: 2 commits discards 20435a1416 283: onsuccess: #1980: 7: Success after binutils/gcc/gdb: 6 commits discards c34f079408 282: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 18 [...] discards b152ff8508 281: onsuccess: #1978: 7: Success after basepoints/gcc-13-48 [...] discards 38d2d40441 280: onsuccess: #1977: 7: Success after binutils/gdb: 18 commits discards 48b7f8d209 279: onsuccess: #1976: 7: Success after binutils/gcc/gdb: 5 commits discards 1df6c74323 278: onsuccess: #1975: 7: Success after basepoints/gcc-13-48 [...] discards 7b4d5f64c5 277: onsuccess: #1974: 7: Success after binutils/gdb: 4 commits discards 6e783ebe40 276: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] discards 5bae71ad38 275: onsuccess: #1972: 7: Success after binutils/gcc/gdb: 23 [...] discards 8f4f3af4b1 274: onsuccess: #1971: 7: Success after binutils/gcc/gdb: 21 [...] discards 7a7e380367 273: onsuccess: #1970: 7: Success after binutils/gcc/gdb: 5 commits discards d0b583be0e 272: onsuccess: #1969: 7: Success after binutils/gcc/linux/g [...] discards 6b7d61442e 271: onsuccess: #1968: 7: Success after binutils/gcc/linux/g [...] discards f651157cf1 270: onsuccess: #1967: 7: Success after binutils/gcc/gdb: 71 [...] discards 838ec74a37 269: onsuccess: #1966: 7: Success after binutils/gcc/gdb: 43 [...] discards 936e7f761d 268: onsuccess: #1965: 7: Success after binutils/gcc/linux/g [...] discards 996acea872 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] discards b091a5a546 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] discards ad0fc150a9 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] discards c8e6b6f067 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] discards de6b06bd4a 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] discards 24a4794cbd 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] discards 4966720a86 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] discards d38949820e 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits discards 84fd6577cb 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] discards 234a2d9a94 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits discards 2aea965c14 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits discards d99325181d 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] discards 4ee5f60437 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] discards 772d0d4fe4 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] discards fe4a322f7d 253: onsuccess: #1950: 7: Success after glibc: 2 commits discards bbc632bba4 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] discards 7542757d20 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] discards 11ef6bce53 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits discards 6b9156d903 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits discards 5992c146a9 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] discards 8d07a4a914 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits discards 2f377a5bdc 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits discards b05da83d96 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] discards aca0a34cc2 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] discards 7378aaa41c 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] discards 2eaca4bd62 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] discards e4924243ca 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] discards b54eafb9d1 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] discards 672f808ac8 239: onsuccess: #1936: 7: Success after binutils/gcc/linux/g [...] discards 0ac39ea7c4 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/qem [...] discards 1fcbfbf326 237: onsuccess: #1934: 7: Success after basepoints/gcc-13-47 [...] discards f512d6b369 236: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] new ac23957b4c 236: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] new 20157f0038 237: onsuccess: #1934: 7: Success after basepoints/gcc-13-47 [...] new e5b58aefab 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/qem [...] new 703c274352 239: onsuccess: #1936: 7: Success after binutils/gcc/linux/g [...] new dc676e3e1c 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] new 6ccbf5b5b7 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] new a53f0a1896 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] new ebdf4eb6da 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] new 06f45319fe 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] new c549ebc5a7 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] new 8e43a0456f 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits new acfc1dbfcd 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits new 1537c40968 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] new 9a9e373195 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits new 3fc2208b11 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits new db7dc7395e 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] new c894907620 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] new 7c780714d3 253: onsuccess: #1950: 7: Success after glibc: 2 commits new 261394c302 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] new aea0c5e647 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] new b7335dcb94 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] new afe015f9ab 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits new bfa13434e8 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits new 5d0734a8da 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] new 01afb3c082 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits new b65425a23f 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] new 8f2e2b5ab3 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] new fd9fa63f3f 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] new fd813673e7 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] new cfed29d560 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] new 9577f37408 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] new e7f8e26ee7 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] new e0e00ae19b 268: onsuccess: #1965: 7: Success after binutils/gcc/linux/g [...] new d528ef0121 269: onsuccess: #1966: 7: Success after binutils/gcc/gdb: 43 [...] new 5f37b873cd 270: onsuccess: #1967: 7: Success after binutils/gcc/gdb: 71 [...] new 415ae4f630 271: onsuccess: #1968: 7: Success after binutils/gcc/linux/g [...] new 70911323d4 272: onsuccess: #1969: 7: Success after binutils/gcc/linux/g [...] new 2399726051 273: onsuccess: #1970: 7: Success after binutils/gcc/gdb: 5 commits new 6a02263af1 274: onsuccess: #1971: 7: Success after binutils/gcc/gdb: 21 [...] new 6e56b91a98 275: onsuccess: #1972: 7: Success after binutils/gcc/gdb: 23 [...] new ff3a496c72 276: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] new 8b5cbfe5ad 277: onsuccess: #1974: 7: Success after binutils/gdb: 4 commits new 974e3dc0d3 278: onsuccess: #1975: 7: Success after basepoints/gcc-13-48 [...] new c59a26dd0e 279: onsuccess: #1976: 7: Success after binutils/gcc/gdb: 5 commits new a21ac4575c 280: onsuccess: #1977: 7: Success after binutils/gdb: 18 commits new c14964d07d 281: onsuccess: #1978: 7: Success after basepoints/gcc-13-48 [...] new 211a071c95 282: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 18 [...] new cf28de14e8 283: onsuccess: #1980: 7: Success after binutils/gcc/gdb: 6 commits new 176bc5a273 284: onsuccess: #1981: 7: Success after gcc: 2 commits new fd045c1298 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits new 98567a53e9 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits new 1991fab672 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits new de66aedd14 288: onsuccess: #1985: 7: Success after gcc: 17 commits new 8b383f4859 289: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] new e737cdada5 290: onsuccess: #1987: 7: Success after gcc/linux: 26 commits new acd14b0c44 291: onsuccess: #1988: 7: Success after binutils/gcc/gdb: 5 commits new edcb812b49 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits new 25cb736d9a 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] new e8b18eae66 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits new 0b5a7d7ff0 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits new 21f708f99e 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] new c330e05273 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits new 36f9fdd3cc 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits new 5dcf9c2683 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] new 387611ca67 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] new 29cfa9374b 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits new 028ca9a534 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] new 65b2a6b60d 303: onsuccess: #2001: 7: Success after binutils: 4 commits new c19997b5f1 304: onsuccess: #2002: 7: Success after gcc: 4 commits new 41f1b83863 305: force: #2006: 7: Success after gdb: 2 commits new c10eeee877 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] new 1ff4fa5851 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] new d3aee459cd 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new 6e5b5c2bde 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] new a9b8aaa03a 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] new 9235cffb87 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new 059c6b4d08 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] new 0e8aec3a7a 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] new e921f334d3 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits new b7ea7719cc 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] new 4eea7759db 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] new ba04c93273 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] new 645e6be2c9 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] new 0de0f81515 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] new d8f02b819d 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] new c19efd55be 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits new d540dcd1b7 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits new 654f65019e 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] new 25c6af9c8e 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits new 05545c0dd1 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] new 32c4edff7d 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] new aa6e0aae52 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] new 9c854fc38e 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] new c1f54b0762 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits new 87a80e7e82 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] new b0bc7337e3 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] new fff7d18649 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] new 60e7c75468 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits new 3d73508174 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] new fbeea36e66 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] new 0488b8a225 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new e0931ecd73 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 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 (f06ffa8554) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] 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 1732 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2796 bytes 04-build_abe-binutils/console.log.xz | Bin 31956 -> 32760 bytes 05-build_abe-stage1/console.log.xz | Bin 73048 -> 74032 bytes 07-build_abe-linux/console.log.xz | Bin 9260 -> 9248 bytes 08-build_abe-glibc/console.log.xz | Bin 244576 -> 245328 bytes 09-build_abe-stage2/console.log.xz | Bin 204444 -> 206404 bytes 10-build_abe-gdb/console.log.xz | Bin 39448 -> 40116 bytes 11-build_abe-qemu/console.log.xz | Bin 31528 -> 31656 bytes 12-check_regression/console.log.xz | Bin 4548 -> 3580 bytes 13-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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++--------- 19 files changed, 58 insertions(+), 58 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (1c0649c1d2 -> 36cfa1b00b)

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 1c0649c1d2 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards d7021cc92f 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 12bdeb200e 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards ce68b1549f 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 5117a0980c 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 7516316d59 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 5d45c8579e 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 4503f477d1 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 14ee114b59 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards c9fe10e398 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards bd3053ec36 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 9c6e399152 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 5b7b5dca55 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 6aec33eb4b 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 3e6b99bb41 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards bf7ebdde55 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 52663ea04c 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 1877909579 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards b1e244a64a 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 974215bcd0 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 414b5a008b 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 2be6b063a7 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards de44faabd7 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards c5822a8d3f 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards e23ef3aec6 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards fd34d01c77 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 8596b2f45a 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 734f3fdbce 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 94f40c519a 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards dcf0a1d5ec 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 16a5bf8ab7 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 6656774083 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 4751096282 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 496961d3bc 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 9c21701509 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards cd9957a0fb 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards fc7dc0b2f4 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 2c1b851133 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 3d50d3feae 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards d089108249 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards a1be1387cd 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 9f62ff45d8 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 3fee537586 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 9a2deeff4d 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 9b39cc4aa5 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards b920ebf524 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 5346be2432 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 39d8dd2f66 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards f234d69768 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 941b1e0c4a 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards ee06f9e451 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 6a4e4a5b4b 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 719920ce3e 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 077aadada5 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 29ba47f0e0 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards b0f8ae43f6 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 1ce4b9eb73 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 317c7c7e78 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 3749d26408 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards fda6fa6c64 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards ab21c1662e 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 49b7d51849 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 87d03bea97 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 68fa86bdac 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards b00b62fb93 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards 7d73ca49fa 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 0df78ef254 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 82b4051137 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 7fc231502f 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards a18dfcf51a 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards dc6f04f8ac 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards d3dc4b2504 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 85f0de70f3 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards cc1c516521 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 993a60fde9 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards a5652e9f41 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards 4e21a5689d 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards 1c453a55e8 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards a8aff9b7a5 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards a9c7b19c82 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards 360a45e8fe 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards 4075cd1f00 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards 10beb326c0 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards 50b79bcd0a 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards d1a1f03af5 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards e6bc7df1d1 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards 90be17bb48 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards e79bae8a54 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards 6e60c4b102 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 3c94ac29b6 235: onsuccess: #2483: 1: Success after linux: 108 commits discards a08ce2e078 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards 32c06a3851 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards f10347519a 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards 3994fcc3e4 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards 3aabddf05a 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards 5a1b2ce1c8 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards 3a62b9fb72 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards 9e85f37298 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards ab5e3e3f59 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] discards 2a5e2c7e75 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards 25761c1e6b 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] new ddf92e44cf 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] new a4f92177d2 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new f202c37339 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] new 263aecb449 227: onsuccess: #2474: 1: Success after gcc: 2 commits new a5689c90c7 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new b20bb18afb 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new 4325e404d5 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new 549308063d 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new 56bef199d8 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new 3b850ae116 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new 43e85b808f 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 0b57f13626 235: onsuccess: #2483: 1: Success after linux: 108 commits new cd55431752 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 4747a23089 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new f198cf690e 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new bc0ee45a8d 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new b0653a8ee4 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new eee0dab848 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new f7289ff30e 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new b3ada949dd 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new 20f2aa4199 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new 82320302a8 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 628c84e83d 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new 97f81884a7 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new 48a24fe00f 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 6917b16ec4 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new 7835021bc6 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new d7c464c4d9 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new afa8d1a31a 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new b8411463c8 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new f957794bab 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 88360f9e9e 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new 9beb489306 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 80e868a7b8 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new e5fb7141ef 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new 17dc9059ea 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new cebb3b0498 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new c9814a1980 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new e644a5293e 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 9674fd3ded 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 211e19e89a 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new a788b055da 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 29dfd2ea9b 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 08c14511fa 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 7f679a3dae 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 47de16100a 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 8f604c4815 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new fd36383a4d 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 32f708d22f 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new e6f2586f57 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 449cb4aa55 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 301ed1de17 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 13a4d22231 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 1db3cc12c6 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 82c5b36cd5 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new db16f3a64a 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 35d4855c0e 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 99c8bc18d3 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 036a27714d 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new f3b2fad74b 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new ca6aa61532 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 3e521941c3 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new ba41f23de4 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 2543534b04 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 376484ec99 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 3382c1925b 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 88c70a963f 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new dea006291f 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new f61c552e1f 292: onsuccess: #2541: 1: Success after binutils: 13 commits new c4a395e5f5 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 3668bd2b74 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 76fbe4f699 295: onsuccess: #2545: 1: Success after linux: 10 commits new 49453f2975 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 8830fe3752 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 7fb43b1662 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new a3a4a6c071 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new b1f187d706 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 8f87bdd85d 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new c5a3d2dc5c 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new fc259fdf9f 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 16f0f946c3 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 7d9390e62c 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 5ba9f92744 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new f533c5f2f0 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 13435bec89 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 2a73014c1e 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new da59dd0991 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new e5299cc6f2 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 77b21247bc 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 8db2f7a7e9 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 611646f3fc 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new ab8fa00b59 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 1253b6bc57 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new ed1ce708e6 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 7cf439d7f6 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new ce32c8b7b0 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 2acb8fd689 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new a32a0d9365 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 15268d6ece 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new c7a2e2c306 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new a7e7725213 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 36cfa1b00b 325: onsuccess: #2575: 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 (1c0649c1d2) \ 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 1792 -> 1836 bytes 02-prepare_abe/console.log.xz | Bin 2808 -> 2796 bytes 03-build_abe-binutils/console.log.xz | Bin 32644 -> 32320 bytes 04-build_abe-stage1/console.log.xz | Bin 74536 -> 73748 bytes 06-build_abe-linux/console.log.xz | Bin 8628 -> 9272 bytes 07-build_abe-glibc/console.log.xz | Bin 247696 -> 246560 bytes 08-build_abe-stage2/console.log.xz | Bin 208764 -> 207904 bytes 09-build_abe-gdb/console.log.xz | Bin 40508 -> 40200 bytes 10-build_abe-qemu/console.log.xz | Bin 31948 -> 31988 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3948 -> 3916 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3128 -> 2836 bytes 13-check_regression/console.log.xz | Bin 7164 -> 7516 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 17 +- 13-check_regression/mail-body.txt | 108 +- 13-check_regression/results.compare | 46 +- 13-check_regression/results.compare2 | 145 +- 13-check_regression/results.regressions | 46 +- 14-update_baseline/console.log | 70 +- 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 | 110 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 46 +- sumfiles/g++.log.xz | Bin 3411448 -> 3424336 bytes sumfiles/g++.sum | 32 +- sumfiles/gcc.log.xz | Bin 3036292 -> 3029484 bytes sumfiles/gcc.sum | 4670 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1042504 -> 1041352 bytes sumfiles/gfortran.sum | 8 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214596 -> 214584 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2696 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 432092 -> 436184 bytes sumfiles/libstdc++.sum | 28 +- 43 files changed, 2708 insertions(+), 2678 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch devel/rust/master updated (0152926ab36 -> 0030bead12e)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch devel/rust/master in repository gcc. from 0152926ab36 Merge #1706 new 2f36f380542 rust: add bound parsing in parse_generic_arg. new 8742e540523 Merge #1716 new 5918059fd3a Check for mutable references in const functions new fc72441e83f Merge #1709 new aa7698dca97 unsafe: check use of `target_feature` attribute new 68b0212c81a Merge #1711 new 5bbbe70df98 fatal_error_flag: Fix typo in error message new fd25c4fa72f format: Fix git whitespace errors new 48d32bc9cb0 Merge #1707 #1717 new 9e5769cf45c Implement declarative macro 2.0 parser Signed-off-by: Raiki [...] new 3290293e16f Merge #1708 new 23593204273 Add name resolution to generic argument associated item bindings new ed6718d979e Support associated type bound arguments new b6fcee808fd Merge #1724 new 97c1308bec6 Reuse TypeCheckPattern on LetStmt's new 59cbecb75d3 Merge #1730 new 84009909526 Add get_locus function for abstract class MetaItemInner. new 0030bead12e Merge #1734 The 18 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: CONTRIBUTING.md | 20 +- README.md | 20 +- gcc/rust/ast/rust-ast-full-decls.h | 1 - gcc/rust/ast/rust-ast-full-test.cc | 1 + gcc/rust/ast/rust-ast.h | 7 +- gcc/rust/ast/rust-expr.h | 8 + gcc/rust/ast/rust-item.h | 2 - gcc/rust/ast/rust-macro.h | 77 ++++-- gcc/rust/checks/errors/rust-const-checker.cc | 8 +- gcc/rust/checks/errors/rust-unsafe-checker.cc | 29 ++- gcc/rust/checks/errors/rust-unsafe-checker.h | 5 + gcc/rust/hir/tree/rust-hir-path.h | 4 +- gcc/rust/lang.opt | 4 +- gcc/rust/lex/rust-token.h | 4 +- gcc/rust/parse/rust-parse-impl.h | 275 +++++++++++++++++----- gcc/rust/parse/rust-parse.h | 3 +- gcc/rust/resolve/rust-ast-resolve-type.cc | 5 + gcc/rust/rust-session-manager.cc | 2 +- gcc/rust/typecheck/rust-hir-path-probe.h | 3 +- gcc/rust/typecheck/rust-hir-trait-resolve.cc | 11 +- gcc/rust/typecheck/rust-hir-type-check-expr.cc | 12 +- gcc/rust/typecheck/rust-hir-type-check-stmt.cc | 14 +- gcc/rust/typecheck/rust-tyty-bounds.cc | 89 ++++++- gcc/rust/typecheck/rust-tyty.cc | 73 +++++- gcc/rust/typecheck/rust-tyty.h | 48 +++- gcc/rust/util/rust-attributes.cc | 3 + gcc/testsuite/rust/compile/bounds.rs | 12 + gcc/testsuite/rust/compile/const10.rs | 3 + gcc/testsuite/rust/compile/decl_macro1.rs | 2 + gcc/testsuite/rust/compile/decl_macro2.rs | 2 + gcc/testsuite/rust/compile/decl_macro3.rs | 4 + gcc/testsuite/rust/compile/decl_macro4.rs | 5 + gcc/testsuite/rust/compile/decl_macro5.rs | 5 + gcc/testsuite/rust/compile/decl_macro6.rs | 5 + gcc/testsuite/rust/compile/decl_macro7.rs | 4 + gcc/testsuite/rust/compile/unsafe11.rs | 8 + gcc/testsuite/rust/execute/torture/decl_macro1.rs | 8 + gcc/testsuite/rust/execute/torture/decl_macro2.rs | 8 + gcc/testsuite/rust/execute/torture/decl_macro3.rs | 15 ++ gcc/testsuite/rust/execute/torture/decl_macro4.rs | 15 ++ gcc/testsuite/rust/execute/torture/issue-1720.rs | 26 ++ 41 files changed, 689 insertions(+), 161 deletions(-) create mode 100644 gcc/testsuite/rust/compile/bounds.rs create mode 100644 gcc/testsuite/rust/compile/const10.rs create mode 100644 gcc/testsuite/rust/compile/decl_macro1.rs create mode 100644 gcc/testsuite/rust/compile/decl_macro2.rs create mode 100644 gcc/testsuite/rust/compile/decl_macro3.rs create mode 100644 gcc/testsuite/rust/compile/decl_macro4.rs create mode 100644 gcc/testsuite/rust/compile/decl_macro5.rs create mode 100644 gcc/testsuite/rust/compile/decl_macro6.rs create mode 100644 gcc/testsuite/rust/compile/decl_macro7.rs create mode 100644 gcc/testsuite/rust/compile/unsafe11.rs create mode 100644 gcc/testsuite/rust/execute/torture/decl_macro1.rs create mode 100644 gcc/testsuite/rust/execute/torture/decl_macro2.rs create mode 100644 gcc/testsuite/rust/execute/torture/decl_macro3.rs create mode 100644 gcc/testsuite/rust/execute/torture/decl_macro4.rs create mode 100644 gcc/testsuite/rust/execute/torture/issue-1720.rs -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_O3 updated (80d6fd062b -> f773e57499)

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_bootstrap/master-arm-bootstrap_O3 in repository toolchain/ci/base-artifacts. discards 80d6fd062b 159: onsuccess: #592: 2: Success after binutils/gcc: 131 commits discards cf38cd5c21 158: onsuccess: #588: 2: Success after binutils/gcc: 6 commits discards 90846f39e0 157: onsuccess: #587: 2: Success after binutils/gcc: 16 commits discards 32f7e2983b 156: onsuccess: #586: 2: Success after binutils/gcc: 55 commits discards 146d586b19 155: onsuccess: #585: 2: Success after binutils/gcc: 36 commits discards 1cc3ef0b29 154: onsuccess: #584: 2: Success after binutils/gcc: 36 commits discards dc6d6517f3 153: onsuccess: #583: 2: Success after binutils/gcc: 45 commits discards 0b507cb845 152: onsuccess: #582: 2: Success after binutils/gcc: 25 commits discards dab88caed5 151: onsuccess: #581: 2: Success after binutils/gcc: 12 commits discards 3bf4ebc807 150: onsuccess: #580: 2: Success after binutils/gcc: 19 commits discards 4cfada763d 149: onsuccess: #579: 2: Success after binutils/gcc: 20 commits discards 306cf3bfd5 148: onsuccess: #578: 2: Success after binutils/gcc: 7 commits discards 1e28a39ce3 147: onsuccess: #577: 2: Success after binutils/gcc: 22 commits discards fea81ecffd 146: onsuccess: #576: 2: Success after binutils/gcc: 16 commits discards 1fbd3c5b48 145: onsuccess: #575: 2: Success after binutils/gcc: 6 commits discards 0baf52d62a 144: onsuccess: #574: 2: Success after binutils/gcc: 26 commits discards fbc3bc6b8e 143: onsuccess: #573: 2: Success after binutils/gcc: 35 commits discards 6dd3a7ec0f 142: onsuccess: #572: 2: Success after binutils/gcc: 74 commits discards a612748fa3 141: onsuccess: #571: 2: Success after binutils/gcc: 43 commits discards 9dea774a36 140: onsuccess: #570: 2: Success after binutils/gcc: 56 commits discards 46ca413293 139: onsuccess: #569: 2: Success after binutils/gcc: 42 commits discards 02b6b5ebd9 138: onsuccess: #568: 2: Success after binutils/gcc: 22 commits discards 41fd5084bb 137: onsuccess: #567: 2: Success after binutils/gcc: 10 commits discards ab60cbc724 136: onsuccess: #566: 2: Success after binutils/gcc: 37 commits discards 7bf6b9d44e 135: onsuccess: #565: 2: Success after binutils/gcc: 40 commits discards aba75e3ac1 134: onsuccess: #564: 1: Success after binutils/gcc: 30 commits discards 2020339a21 133: onsuccess: #563: 1: Success after binutils/gcc: 108 commits discards c234efb288 132: onsuccess: #562: 1: Success after baseline build: no ne [...] discards b6e72e3120 131: force: #561: 1: Failure after gdb-12-branchpoint-3046-g [...] discards 46ba9cf9ce 130: force: #560: 2: Success after binutils: 21 commits discards 4f908198e2 129: onsuccess: #556: 2: Success after binutils/gcc: 23 commits discards acf74546bb 128: onsuccess: #555: 2: Success after binutils/gcc: 4 commits discards dfd18eb53d 127: onsuccess: #554: 2: Success after binutils/gcc: 20 commits discards 3e9247d9c1 126: onsuccess: #553: 2: Success after binutils/gcc: 36 commits discards ba36e4e796 125: onsuccess: #552: 2: Success after binutils/gcc: 25 commits discards c30d3b6483 124: onsuccess: #551: 2: Success after binutils/gcc: 41 commits discards 84f337c435 123: onsuccess: #550: 2: Success after binutils/gcc: 40 commits discards 4eb21965d0 122: onsuccess: #549: 2: Success after binutils/gcc: 20 commits discards f7d16bc416 121: onsuccess: #548: 2: Success after binutils/gcc: 9 commits discards e1d878b860 120: onsuccess: #547: 2: Success after binutils/gcc: 17 commits discards 16f5f0e3cf 119: onsuccess: #546: 2: Success after binutils/gcc: 47 commits discards 350f7cd351 118: onsuccess: #545: 2: Success after binutils/gcc: 48 commits discards c9c76b0e45 117: onsuccess: #544: 2: Success after binutils/gcc: 31 commits discards f052775194 116: onsuccess: #543: 2: Success after binutils/gcc: 73 commits discards 0e13aaca2c 115: onsuccess: #542: 1: Success after binutils/gcc: 58 commits discards 03efb411f2 114: onsuccess: #541: 1: Success after binutils/gcc: 8 commits discards 0ed947fb57 113: onsuccess: #540: 1: Success after binutils/gcc: 11 commits discards 2d041b063c 112: onsuccess: #539: 1: Success after binutils/gcc: 31 commits discards b7b9feff09 111: onsuccess: #538: 1: Success after binutils/gcc: 39 commits discards a1d4c3ce33 110: onsuccess: #537: 1: Success after binutils/gcc: 51 commits discards 53ddd4a638 109: onsuccess: #536: 1: Success after gcc: 2 commits discards 0c451bcfdc 108: force: #535: 1: Failure after basepoints/gcc-13-4227-g0 [...] discards dd64c07613 107: force: #534: 2: Success after gcc: 26 commits discards ed7160eb64 106: onsuccess: #532: 2: Success after binutils: 12 commits discards 4ed9b95999 105: onsuccess: #530: 2: Success after binutils/gcc: 32 commits discards 4c92ad4cc2 104: onsuccess: #529: 2: Success after binutils/gcc: 11 commits discards 7f8bf1aacb 103: onsuccess: #528: 2: Success after binutils/gcc: 40 commits discards 83b6259f1b 102: onsuccess: #527: 2: Success after binutils/gcc: 32 commits discards f3897ece42 101: onsuccess: #526: 2: Success after binutils/gcc: 52 commits discards e14968e1a8 100: onsuccess: #525: 2: Success after binutils/gcc: 128 commits discards 15a16a8786 99: onsuccess: #523: 2: Success after binutils/gcc: 84 commits discards f2aeff2b76 98: onsuccess: #522: 1: Success after gcc: 11 commits discards 0792b5c88c 97: force: #521: 1: Failure after basepoints/gcc-13-3918-gba [...] discards 17add09e3d 96: force: #520: 2: Success after gcc: 24 commits discards 651095bc0f 95: onsuccess: #518: 2: Success after binutils: 10 commits discards 56d581016b 94: onsuccess: #516: 2: Success after binutils/gcc: 58 commits discards 6c93d2ef32 93: onsuccess: #515: 2: Success after binutils/gcc: 47 commits discards cfde7d0b09 92: onsuccess: #514: 2: Success after binutils/gcc: 58 commits discards 3e656e07ac 91: onsuccess: #513: 2: Success after binutils/gcc: 71 commits discards 3fa99c647a 90: onsuccess: #512: 2: Success after binutils/gcc: 50 commits discards cf60a43ebc 89: onsuccess: #511: 2: Success after binutils/gcc: 20 commits discards 791758b948 88: onsuccess: #510: 2: Success after binutils/gcc: 55 commits discards 8d1bd2d5ee 87: onsuccess: #509: 2: Success after binutils/gcc: 58 commits discards 4be8f9b1ca 86: onsuccess: #508: 2: Success after binutils/gcc: 29 commits discards 6b1ea95d94 85: onsuccess: #507: 2: Success after binutils/gcc: 27 commits discards 4ed3e3482e 84: onsuccess: #506: 2: Success after binutils/gcc: 37 commits discards 474df5b807 83: onsuccess: #505: 2: Success after binutils/gcc: 15 commits discards bea23e9a29 82: onsuccess: #504: 2: Success after binutils/gcc: 6 commits discards c96f47c585 81: onsuccess: #503: 2: Success after binutils/gcc: 38 commits discards d8be603412 80: onsuccess: #502: 2: Success after binutils/gcc: 31 commits discards 4ebe8c585d 79: onsuccess: #501: 2: Success after binutils/gcc: 28 commits discards 6829516f1e 78: onsuccess: #500: 2: Success after binutils/gcc: 37 commits discards 136c7d763e 77: onsuccess: #499: 2: Success after binutils/gcc: 48 commits discards cd66fa38fe 76: onsuccess: #498: 2: Success after binutils/gcc: 16 commits discards e42c67471e 75: onsuccess: #497: 2: Success after binutils/gcc: 5 commits discards 3e00d6137e 74: onsuccess: #496: 2: Success after binutils/gcc: 15 commits discards cabcb8f740 73: onsuccess: #495: 2: Success after binutils/gcc: 50 commits discards 25c60bea97 72: onsuccess: #494: 2: Success after binutils/gcc: 54 commits discards 449a1d7398 71: onsuccess: #493: 2: Success after binutils/gcc: 50 commits discards 3286971b27 70: onsuccess: #492: 2: Success after binutils/gcc: 42 commits discards 509239da69 69: onsuccess: #491: 2: Success after binutils/gcc: 19 commits discards c6f56e9145 68: onsuccess: #490: 2: Success after binutils/gcc: 8 commits discards 022e8b15ab 67: onsuccess: #489: 2: Success after binutils/gcc: 23 commits discards 46877b35a3 66: onsuccess: #488: 2: Success after binutils/gcc: 51 commits discards 57c2f13123 65: onsuccess: #487: 2: Success after binutils/gcc: 35 commits discards cee61fabca 64: onsuccess: #486: 1: Success after binutils/gcc: 48 commits discards 4053e569de 63: onsuccess: #485: 1: Success after binutils/gcc: 55 commits discards 58bbfead87 62: onsuccess: #484: 1: Success after binutils/gcc: 31 commits discards 5db25b3683 61: onsuccess: #483: 1: Success after gcc: 3 commits discards 6ce86b8b69 60: force: #482: 1: Failure after basepoints/gcc-13-3172-gf3 [...] discards df87e3e1b4 59: force: #481: 2: Success after gcc: 41 commits new 7d3ff2f50f 59: force: #481: 2: Success after gcc: 41 commits new 8d0f86ae2a 60: force: #482: 1: Failure after basepoints/gcc-13-3172-gf3 [...] new d56cc32ffb 61: onsuccess: #483: 1: Success after gcc: 3 commits new 3dcb369aa3 62: onsuccess: #484: 1: Success after binutils/gcc: 31 commits new 5567a81c73 63: onsuccess: #485: 1: Success after binutils/gcc: 55 commits new 50e5f4be47 64: onsuccess: #486: 1: Success after binutils/gcc: 48 commits new a0491bb48c 65: onsuccess: #487: 2: Success after binutils/gcc: 35 commits new 26b0287fdd 66: onsuccess: #488: 2: Success after binutils/gcc: 51 commits new d6825f8e02 67: onsuccess: #489: 2: Success after binutils/gcc: 23 commits new 8edcf8f9ed 68: onsuccess: #490: 2: Success after binutils/gcc: 8 commits new fa28769eb4 69: onsuccess: #491: 2: Success after binutils/gcc: 19 commits new fd2953050e 70: onsuccess: #492: 2: Success after binutils/gcc: 42 commits new 091be228e3 71: onsuccess: #493: 2: Success after binutils/gcc: 50 commits new d78b389b62 72: onsuccess: #494: 2: Success after binutils/gcc: 54 commits new 3afd43e420 73: onsuccess: #495: 2: Success after binutils/gcc: 50 commits new 4cf1845190 74: onsuccess: #496: 2: Success after binutils/gcc: 15 commits new 9238ee1b94 75: onsuccess: #497: 2: Success after binutils/gcc: 5 commits new 93a5f13336 76: onsuccess: #498: 2: Success after binutils/gcc: 16 commits new cd1104e4e6 77: onsuccess: #499: 2: Success after binutils/gcc: 48 commits new 9256c90eda 78: onsuccess: #500: 2: Success after binutils/gcc: 37 commits new 5af7a46626 79: onsuccess: #501: 2: Success after binutils/gcc: 28 commits new 499f10bb66 80: onsuccess: #502: 2: Success after binutils/gcc: 31 commits new 0b83387edb 81: onsuccess: #503: 2: Success after binutils/gcc: 38 commits new d12303f67e 82: onsuccess: #504: 2: Success after binutils/gcc: 6 commits new c244cb55e9 83: onsuccess: #505: 2: Success after binutils/gcc: 15 commits new 728fce0191 84: onsuccess: #506: 2: Success after binutils/gcc: 37 commits new a68f219829 85: onsuccess: #507: 2: Success after binutils/gcc: 27 commits new 735ecabe2f 86: onsuccess: #508: 2: Success after binutils/gcc: 29 commits new 24d7eff701 87: onsuccess: #509: 2: Success after binutils/gcc: 58 commits new b3e2370aee 88: onsuccess: #510: 2: Success after binutils/gcc: 55 commits new 19520a9af6 89: onsuccess: #511: 2: Success after binutils/gcc: 20 commits new 11e14ad4bb 90: onsuccess: #512: 2: Success after binutils/gcc: 50 commits new 1daf7f70aa 91: onsuccess: #513: 2: Success after binutils/gcc: 71 commits new 6ff8ee2e11 92: onsuccess: #514: 2: Success after binutils/gcc: 58 commits new 4d3b0122d6 93: onsuccess: #515: 2: Success after binutils/gcc: 47 commits new 1c149d95b0 94: onsuccess: #516: 2: Success after binutils/gcc: 58 commits new 15c9b2f6a1 95: onsuccess: #518: 2: Success after binutils: 10 commits new 2fa259996e 96: force: #520: 2: Success after gcc: 24 commits new 490fe6342e 97: force: #521: 1: Failure after basepoints/gcc-13-3918-gba [...] new 983380eb33 98: onsuccess: #522: 1: Success after gcc: 11 commits new db341f2c3c 99: onsuccess: #523: 2: Success after binutils/gcc: 84 commits new 3fb8940252 100: onsuccess: #525: 2: Success after binutils/gcc: 128 commits new 4838b7c33a 101: onsuccess: #526: 2: Success after binutils/gcc: 52 commits new 2d0fa52a19 102: onsuccess: #527: 2: Success after binutils/gcc: 32 commits new 776c439a54 103: onsuccess: #528: 2: Success after binutils/gcc: 40 commits new 7f4978e242 104: onsuccess: #529: 2: Success after binutils/gcc: 11 commits new 150aa421cb 105: onsuccess: #530: 2: Success after binutils/gcc: 32 commits new 6cfe106ae0 106: onsuccess: #532: 2: Success after binutils: 12 commits new f492da94ce 107: force: #534: 2: Success after gcc: 26 commits new e904833bbf 108: force: #535: 1: Failure after basepoints/gcc-13-4227-g0 [...] new dd6ec7ca26 109: onsuccess: #536: 1: Success after gcc: 2 commits new ef5f56f202 110: onsuccess: #537: 1: Success after binutils/gcc: 51 commits new 16e9bef952 111: onsuccess: #538: 1: Success after binutils/gcc: 39 commits new 23820de835 112: onsuccess: #539: 1: Success after binutils/gcc: 31 commits new 7b58082012 113: onsuccess: #540: 1: Success after binutils/gcc: 11 commits new a2d25de697 114: onsuccess: #541: 1: Success after binutils/gcc: 8 commits new a9f72b9f28 115: onsuccess: #542: 1: Success after binutils/gcc: 58 commits new 39c2d2bfe0 116: onsuccess: #543: 2: Success after binutils/gcc: 73 commits new 1e420117bf 117: onsuccess: #544: 2: Success after binutils/gcc: 31 commits new f4dea4e546 118: onsuccess: #545: 2: Success after binutils/gcc: 48 commits new da13beaf7a 119: onsuccess: #546: 2: Success after binutils/gcc: 47 commits new d5547ef8e4 120: onsuccess: #547: 2: Success after binutils/gcc: 17 commits new 721ce184f7 121: onsuccess: #548: 2: Success after binutils/gcc: 9 commits new bb3d84a30a 122: onsuccess: #549: 2: Success after binutils/gcc: 20 commits new 7f9586d58d 123: onsuccess: #550: 2: Success after binutils/gcc: 40 commits new 4bfe23c36e 124: onsuccess: #551: 2: Success after binutils/gcc: 41 commits new a834ab37b4 125: onsuccess: #552: 2: Success after binutils/gcc: 25 commits new ff98dc0f9f 126: onsuccess: #553: 2: Success after binutils/gcc: 36 commits new 8ce3f83d4b 127: onsuccess: #554: 2: Success after binutils/gcc: 20 commits new 2399d4154e 128: onsuccess: #555: 2: Success after binutils/gcc: 4 commits new daa498382d 129: onsuccess: #556: 2: Success after binutils/gcc: 23 commits new 615106b2c8 130: force: #560: 2: Success after binutils: 21 commits new 7fe17f237d 131: force: #561: 1: Failure after gdb-12-branchpoint-3046-g [...] new 82eb7e4700 132: onsuccess: #562: 1: Success after baseline build: no ne [...] new b1a9c00693 133: onsuccess: #563: 1: Success after binutils/gcc: 108 commits new c22e6eae52 134: onsuccess: #564: 1: Success after binutils/gcc: 30 commits new 9b3ab58d99 135: onsuccess: #565: 2: Success after binutils/gcc: 40 commits new 3dc7224b8a 136: onsuccess: #566: 2: Success after binutils/gcc: 37 commits new 053116b11a 137: onsuccess: #567: 2: Success after binutils/gcc: 10 commits new ba36c6e120 138: onsuccess: #568: 2: Success after binutils/gcc: 22 commits new 04d57b40d0 139: onsuccess: #569: 2: Success after binutils/gcc: 42 commits new 9a086431dd 140: onsuccess: #570: 2: Success after binutils/gcc: 56 commits new d473c13096 141: onsuccess: #571: 2: Success after binutils/gcc: 43 commits new ee55167eeb 142: onsuccess: #572: 2: Success after binutils/gcc: 74 commits new 6f8a72d859 143: onsuccess: #573: 2: Success after binutils/gcc: 35 commits new f43ae4e953 144: onsuccess: #574: 2: Success after binutils/gcc: 26 commits new d266388524 145: onsuccess: #575: 2: Success after binutils/gcc: 6 commits new 62de87ba33 146: onsuccess: #576: 2: Success after binutils/gcc: 16 commits new 694b43344a 147: onsuccess: #577: 2: Success after binutils/gcc: 22 commits new 784f95f334 148: onsuccess: #578: 2: Success after binutils/gcc: 7 commits new afc635d5a6 149: onsuccess: #579: 2: Success after binutils/gcc: 20 commits new 2643ef7cea 150: onsuccess: #580: 2: Success after binutils/gcc: 19 commits new 7b87a57fce 151: onsuccess: #581: 2: Success after binutils/gcc: 12 commits new 1dbb96ea22 152: onsuccess: #582: 2: Success after binutils/gcc: 25 commits new b9d199035a 153: onsuccess: #583: 2: Success after binutils/gcc: 45 commits new 6b11e7e61c 154: onsuccess: #584: 2: Success after binutils/gcc: 36 commits new 3d04569cf1 155: onsuccess: #585: 2: Success after binutils/gcc: 36 commits new afd497024d 156: onsuccess: #586: 2: Success after binutils/gcc: 55 commits new c47006f445 157: onsuccess: #587: 2: Success after binutils/gcc: 16 commits new 31280c0716 158: onsuccess: #588: 2: Success after binutils/gcc: 6 commits new 1c8b7987fe 159: onsuccess: #592: 2: Success after binutils/gcc: 131 commits new f773e57499 160: onsuccess: #593: 2: Success after binutils/gcc: 40 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 (80d6fd062b) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] 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 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2756 bytes 04-build_abe-binutils/console.log.xz | Bin 53384 -> 52208 bytes 05-build_abe-bootstrap_O3/console.log.xz | Bin 470332 -> 468296 bytes 06-check_regression/console.log.xz | Bin 3084 -> 3012 bytes 07-update_baseline/console.log | 38 +++++++++++++++---------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++-------- 13 files changed, 34 insertions(+), 34 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-next-allyesconfig updated (73d153a809 -> 1e81889fb9)

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/gnu-release-aarch64-next-allyesconfig in repository toolchain/ci/base-artifacts. from 73d153a809 46: force: #723: 21887: Failure after linux: 401 commits new 1e81889fb9 47: onsuccess: #725: 21887: Success after binutils/gcc/qemu: [...] 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 1784 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 30956 -> 30388 bytes 04-build_abe-stage1/console.log.xz | Bin 68796 -> 68500 bytes 05-build_abe-qemu/console.log.xz | Bin 31576 -> 30896 bytes 06-build_linux/console.log.xz | Bin 3140 -> 3340 bytes 08-check_regression/console.log.xz | Bin 3412 -> 3640 bytes 08-check_regression/jira-body.txt | 2 +- 08-check_regression/mail-body.txt | 10 +++++----- 08-check_regression/mail-subject.txt | 2 +- 08-check_regression/results.regressions | 3 --- 08-check_regression/trigger-bisect | 2 -- 09-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 10 +++++----- mail/mail-subject.txt | 2 +- manifest.sh | 30 ++++++++++++++++-------------- results | 3 --- 22 files changed, 35 insertions(+), 41 deletions(-) delete mode 100644 08-check_regression/results.regressions delete mode 100644 08-check_regression/trigger-bisect -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-next-allmodconfig updated (d37a6eeb13 -> 097ed7fa1c)

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/gnu-release-aarch64-next-allmodconfig in repository toolchain/ci/base-artifacts. from d37a6eeb13 40: onsuccess: #734: all: Success after gcc/linux/qemu: 2765 [...] new 097ed7fa1c 41: onsuccess: #735: all: Success after binutils/gcc/linux/q [...] 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 1772 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 30708 -> 30836 bytes 04-build_abe-stage1/console.log.xz | Bin 69136 -> 69092 bytes 05-build_abe-qemu/console.log.xz | Bin 31380 -> 32484 bytes 06-build_linux/console.log.xz | Bin 3292 -> 3300 bytes 07-boot_linux/console.log.xz | Bin 504 -> 508 bytes 08-check_regression/console.log.xz | Bin 3944 -> 4272 bytes 08-check_regression/mail-body.txt | 4 ++-- 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 6 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 20 files changed, 33 insertions(+), 33 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[binutils-gdb] branch master updated (6baf06097b7 -> 4981a31d523)

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 6baf06097b7 sim: build: drop subdir Makefile.in files new 2070fc67bad Remove myself as hppa32 maintainer new 4981a31d523 Use __func__ rather than __FUNCTION__ The 2 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/bfd-in.h | 4 ++-- bfd/bfd-in2.h | 4 ++-- bfd/elf32-bfin.c | 3 +-- bfd/elfnn-aarch64.c | 2 +- bfd/elfxx-sparc.c | 2 +- binutils/MAINTAINERS | 1 - gas/config/tc-cris.c | 12 ++++++------ gas/config/tc-m68hc11.c | 6 +++--- gas/config/tc-msp430.c | 10 +++++----- gold/dwp.h | 2 +- gold/gold.h | 2 +- ld/emultempl/pe.em | 4 ++-- ld/emultempl/pep.em | 4 ++-- ld/pe-dll.c | 12 ++++++------ 14 files changed, 33 insertions(+), 35 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check_bootstrap/release-arm-check_bootstrap_lto updated (d89aad6229 -> 957be2fcc0)

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_bootstrap/release-arm-check_bootstrap_lto in repository toolchain/ci/base-artifacts. from d89aad6229 43: onsuccess: #159: 1: Success after gcc: 4 commits new 957be2fcc0 44: onsuccess: #160: 1: Success after binutils/gcc: 10 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 1740 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 51540 -> 51880 bytes 04-build_abe-bootstrap_lto/console.log.xz | Bin 468640 -> 469836 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3812 bytes 06-build_abe-check_bootstrap_lto/console.log.xz | Bin 2464 -> 2388 bytes 07-check_regression/console.log.xz | Bin 4392 -> 5256 bytes 07-check_regression/extra-bisect-params | 1 + 07-check_regression/fails.sum | 6 + 07-check_regression/mail-body.txt | 26 + 07-check_regression/results.compare | 25 +- 07-check_regression/results.compare2 | 60 +- 07-check_regression/results.regressions | 26 + dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 26 + sumfiles/g++.log.xz | Bin 2861820 -> 2849524 bytes sumfiles/g++.sum | 140 +- sumfiles/gcc.log.xz | Bin 2451600 -> 2459140 bytes sumfiles/gcc.sum | 4781 ++++++++++++----------- sumfiles/gfortran.log.xz | Bin 950732 -> 947040 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2316 -> 2308 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 206440 -> 207312 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2724 -> 2736 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 471740 -> 472756 bytes sumfiles/libstdc++.sum | 10 +- 35 files changed, 2708 insertions(+), 2519 deletions(-) create mode 100644 07-check_regression/extra-bisect-params create mode 100644 07-check_regression/fails.sum create mode 100644 07-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/gnu-arm-master-O3 created (now ee9d4a9557)

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_bmk-code_speed-spec2k6/gnu-arm-master-O3 in repository toolchain/ci/base-artifacts. at ee9d4a9557 46: onsuccess: #2: 1: [TCWG CI] 481.wrf built and run OK aft [...] This branch includes the following new commits: new ee9d4a9557 46: onsuccess: #2: 1: [TCWG CI] 481.wrf built and run OK aft [...] 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. -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

Jump to page: