Tcwg-commits February 2023

tcwg-commits@lists.linaro.org

5 participants
3393 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (9a160ecf1a -> 8b31d8e950)

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 9a160ecf1a 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards f020a3bd77 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards a73fe56f2d 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards e571b6bbc2 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 709aea27d0 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 53feba3716 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 04187331ba 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards ce29ca9977 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 07051fef7d 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards cc8affcc78 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards d136e06fbc 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 85949951a2 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards cee1ad0451 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 11f9eb1953 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 949b5f8e14 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards a05342a463 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 4df5395413 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 8f9966a4b2 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards f811aa7fac 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 5003621f61 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 4b76ce3149 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 193ef8e8b3 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 2a4d914f1b 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 78c2f5595a 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 8ea7e2c3e4 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 637befe854 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards bf4d17a432 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards d0353521b9 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 7dd8ae3c5f 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 1c05901069 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards eaabd0e4e7 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 458aa10650 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards b923fcc188 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards d593c22a67 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards e61d36d2e8 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 635622b795 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards c35372c0cb 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 228ac3c777 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards dc3997a021 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards af4e78a50b 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 1f24341dfb 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 3ca526829a 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 116dffebc7 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 20bc1186fe 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 09ab7a85c4 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards c1ca1be5ce 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 59eefa6c49 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 8dd923b78b 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 48d7149ea6 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards f9e9241a10 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards d15dc63a7d 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards a80eafd2ad 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 7b5f89df44 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 445bbaab2b 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 53f0d66ebc 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 50bca415e2 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 144da59b22 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 064378c4b8 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards cb7c93ef0b 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 00f7ecbb38 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 7bd4fe5718 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 63469ec0e1 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 26e4123d49 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 2aef378fbd 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 262e44aa41 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards d9e992468a 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 32f65c65e1 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards dc0ab4bc4a 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards cb66b23814 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 2f3a2d6175 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards ca3f11775a 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 11ac2a8f41 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 8e56325308 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 608fa06d0c 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 600e3b4976 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 0180d54aba 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 1b378edfab 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 85e74243f0 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 69e7e9ed50 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards e8269cf158 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 2b484ba430 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards b8bcbdae48 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards ca14fd946c 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards b4ad41c25b 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 14cad5c4cb 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 2f605e0312 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 8ab831060f 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 87c7f5be2f 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 60fcc4c09c 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 1e304c58e5 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards b7a84fc61b 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards be0332442d 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards cb70063a39 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 6b96531694 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards cc01545b77 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 34eec244bf 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 50e4f9923c 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 4a3a3bb340 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 9d15d3524f 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards a10e0f2976 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 48b1427755 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 422b82fb50 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 197ae0cc2c 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 997fa9b412 310: onsuccess: #2129: 1: Success after binutils: 4 commits new e8cbbf256b 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 9d4b076846 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new e53f33404f 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 4ba92cd475 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new d7c9905c08 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 1155490124 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 6ba2209930 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new a730ed77b0 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new b5a5f5707b 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 240cd79583 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 7e5d1b87bb 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 987eac0aac 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 2ff8435168 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new f79850a650 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 086be1a1e5 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new a3ebf52714 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 0fe69fe987 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 796039bb72 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new fc55312a9c 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new f426095000 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 13d23124f8 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 9325ca3541 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 4e0251c83d 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new a2bb1c96b8 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 8d11617c08 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 343610d1f0 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new e3774cf0d3 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 75b745db30 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 669cd111b3 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 9c84d5b392 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 53e9539f48 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 159747c0d0 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new fc191097a7 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new bccfc34133 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new c398e256f7 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 855a4e1c22 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new e64c5fceee 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 6399cb2d5f 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 71b16c72d8 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 1fa2a359f6 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 0ae0094362 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 41ae4d6ad6 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 800a2771c3 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 724d171995 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 5fb9a3f13c 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 4d62556218 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 4eb7475902 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 44921df752 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 57119171a2 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new b0ea80ac9e 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 9c562d5285 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 9b31567e82 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 566a873e79 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 8d7940332c 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 23ff0c916a 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new d4ed83edc6 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new c96e59c9ac 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new d991a7737f 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 02ec5d8ed6 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 802a689500 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 95b2a9f76a 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new faa0b15851 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 2d3f3c5e54 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 29a9ad0bf9 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 03aea6e7c0 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 4fa923f070 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 56f49415f6 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 91b43a4f59 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new f1a11e2d78 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 1dfd1fdd7f 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 8c644a871e 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new b4ac9a8a68 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new e939c14d66 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 6895086174 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 2aaf68381f 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new a28b461365 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 59dc6d0292 387: onsuccess: #2208: 1: Success after gcc: 2 commits new d0da84e4aa 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new fecdc602f3 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 439907ea7d 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 44725bb8f7 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new ab6c398f1f 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new a1f85157ca 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 637e3baa44 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new db1d701bcf 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 1b9e2d1d16 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 5ca150d505 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 4904f1c2b3 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new c3700e348d 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 89c2c900fc 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new daead14c14 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new b9be8e87cc 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new c7257fe8d1 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new 6c8df03938 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 1b42d337b1 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 43d3be003b 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 149262f517 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 88d7c5ec34 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 8b31d8e950 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/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 (9a160ecf1a) \ 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 1756 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31016 -> 30792 bytes 04-build_abe-stage1/console.log.xz | Bin 91372 -> 91376 bytes 06-build_abe-linux/console.log.xz | Bin 8360 -> 8364 bytes 07-build_abe-glibc/console.log.xz | Bin 235948 -> 236212 bytes 08-build_abe-stage2/console.log.xz | Bin 227284 -> 227416 bytes 09-build_abe-gdb/console.log.xz | Bin 38148 -> 38164 bytes 10-build_abe-qemu/console.log.xz | Bin 31096 -> 32080 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2764 -> 2880 bytes 13-check_regression/console.log.xz | Bin 6228 -> 7284 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 10 + 13-check_regression/mail-body.txt | 56 +- 13-check_regression/results.compare | 13 +- 13-check_regression/results.compare2 | 100 +- .../results.regressions | 65 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 58 +- mail/mail-subject.txt | 2 +- manifest.sh | 44 +- results | 30 + sumfiles/g++.log.xz | Bin 2633360 -> 2649560 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 2180684 -> 2190764 bytes sumfiles/gcc.sum | 2155 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 889360 -> 889020 bytes sumfiles/gfortran.sum | 52 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216820 -> 217108 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 435788 -> 434352 bytes sumfiles/libstdc++.sum | 33 +- 44 files changed, 1399 insertions(+), 1326 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum copy mail/mail-body.txt => 13-check_regression/results.regressions (70%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[gcc] branch releases/gcc-12 updated (cb6861acc40 -> 35c6d02981b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-12 in repository gcc. from cb6861acc40 rs6000: Fix typo on vec_vsubcuq in rs6000-overload.def [PR108396] new 35c6d02981b Daily bump. 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/ChangeLog | 29 +++++++++++++++++++++++++++++ gcc/DATESTAMP | 2 +- gcc/testsuite/ChangeLog | 29 +++++++++++++++++++++++++++++ 3 files changed, 59 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[gcc] branch releases/gcc-11 updated (0e41d8a7788 -> 012a47ef16d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-11 in repository gcc. from 0e41d8a7788 rs6000: Teach rs6000_opaque_type_invalid_use_p about gcall [...] new 012a47ef16d Daily bump. 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/ChangeLog | 19 +++++++++++++++++++ gcc/DATESTAMP | 2 +- gcc/testsuite/ChangeLog | 20 ++++++++++++++++++++ 3 files changed, 40 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[gcc] branch releases/gcc-10 updated (7bbed35a05d -> 74148407575)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-10 in repository gcc. from 7bbed35a05d rs6000: Teach rs6000_opaque_type_invalid_use_p about gcall [...] new 74148407575 Daily bump. 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/ChangeLog | 19 +++++++++++++++++++ gcc/DATESTAMP | 2 +- gcc/testsuite/ChangeLog | 20 ++++++++++++++++++++ 3 files changed, 40 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[gcc] branch master updated (daeb6c94bbd -> ae7197818d6)

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 daeb6c94bbd d: Update __FreeBSD_version values [PR107469] new ae7197818d6 Daily bump. 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/ChangeLog | 92 +++++++++++++++++++++++++++++++++++++++++++++++++ gcc/DATESTAMP | 2 +- gcc/fortran/ChangeLog | 13 +++++++ gcc/testsuite/ChangeLog | 49 ++++++++++++++++++++++++++ libgcc/ChangeLog | 5 +++ libgm2/ChangeLog | 4 +++ libphobos/ChangeLog | 5 +++ libstdc++-v3/ChangeLog | 6 ++++ 8 files changed, 175 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[binutils-gdb] branch binutils-2_40-branch updated (5adb6769920 -> d4b31bc4db2)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch binutils-2_40-branch in repository binutils-gdb. from 5adb6769920 Automatic date update in version.in new d4b31bc4db2 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.

1 year, 9 months

[binutils-gdb] branch gdb-13-branch updated (c594b6f7d5d -> 3053fcf3d13)

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-13-branch in repository binutils-gdb. from c594b6f7d5d Fix doc build dependencies for --with-system-readline new 3053fcf3d13 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.

1 year, 9 months

[binutils-gdb] branch master updated (f28085dfb40 -> 978042640c7)

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 f28085dfb40 Rely on value_ref_ptr::operator-> new 978042640c7 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.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allmodconfig updated (c94cf166dd -> 28037f91ca)

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-allmodconfig in repository toolchain/ci/base-artifacts. from c94cf166dd 58: force: #547: 22037: Failure after linux: 0 commits new 28037f91ca 59: onsuccess: #548: 23519: Success after linux: 142737 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 1792 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 31536 -> 31320 bytes 04-build_kernel_llvm/console.log.xz | Bin 66368 -> 64348 bytes 05-build_abe-qemu/console.log.xz | Bin 31720 -> 31696 bytes 06-build_linux/console.log.xz | Bin 4680 -> 3652 bytes 08-check_regression/console.log.xz | Bin 3096 -> 2928 bytes 08-check_regression/jira-body.txt | 2 +- 08-check_regression/mail-body.txt | 28 ++++++++++++---------------- 08-check_regression/mail-subject.txt | 2 +- 08-check_regression/results.regressions | 11 ----------- 08-check_regression/trigger-bisect | 2 -- 09-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 ++++++++++++---------------- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++++--------- results | 13 +------------ 20 files changed, 41 insertions(+), 73 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.

1 year, 9 months

[gcc] branch master updated (a1292514f89 -> daeb6c94bbd)

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 a1292514f89 libstdc++: Adjust "The Component Object Model" reference new daeb6c94bbd d: Update __FreeBSD_version values [PR107469] 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: libphobos/libdruntime/core/sys/freebsd/config.d | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits February 2023