Tcwg-commits November 2022

tcwg-commits@lists.linaro.org

5 participants
4683 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-allyesconfig updated (f7054407d1 -> 38b2eb4210)

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-master-aarch64-stable-allyesconfig in repository toolchain/ci/base-artifacts. from f7054407d1 29: onsuccess: #501: 33: Success after binutils/gcc/qemu: 12 [...] new 38b2eb4210 30: onsuccess: #502: 33: Success after binutils/gcc/qemu: 21 [...] 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 1712 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31840 -> 32672 bytes 04-build_abe-stage1/console.log.xz | Bin 73160 -> 74956 bytes 05-build_abe-qemu/console.log.xz | Bin 31524 -> 32676 bytes 06-build_linux/console.log.xz | Bin 3688 -> 3760 bytes 08-check_regression/console.log.xz | Bin 4016 -> 4076 bytes 09-update_baseline/console.log | 8 ++++---- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 16 files changed, 25 insertions(+), 25 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check_bootstrap/release-arm-check_bootstrap updated (cfbc708564 -> 8ca47b6994)

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 in repository toolchain/ci/base-artifacts. from cfbc708564 34: onsuccess: #157: 1: Success after binutils/gcc: 10 commits new 8ca47b6994 35: onsuccess: #158: 1: Success after binutils/gcc: 18 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 1688 -> 1668 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 50832 -> 51172 bytes 04-build_abe-bootstrap/console.log.xz | Bin 463896 -> 464220 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3908 -> 3944 bytes 06-build_abe-check_bootstrap/console.log.xz | Bin 2840 -> 2444 bytes 07-check_regression/console.log.xz | Bin 4828 -> 4996 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 39 +- 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 | 20 +- sumfiles/g++.log.xz | Bin 2826372 -> 2813304 bytes sumfiles/g++.sum | 112 +- sumfiles/gcc.log.xz | Bin 2506168 -> 2470904 bytes sumfiles/gcc.sum | 3968 +++++++++++++-------------- sumfiles/gfortran.log.xz | Bin 948736 -> 942428 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2304 -> 2304 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 207372 -> 207324 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2720 -> 2728 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 471568 -> 466136 bytes sumfiles/libstdc++.sum | 22 +- 30 files changed, 2137 insertions(+), 2120 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_debug updated (dad2be9925 -> 963da29641)

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/release-arm-bootstrap_debug in repository toolchain/ci/base-artifacts. from dad2be9925 34: onsuccess: #157: 2: Success after binutils/gcc: 10 commits new 963da29641 35: onsuccess: #158: 2: Success after binutils/gcc: 18 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 1668 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2708 bytes 04-build_abe-binutils/console.log.xz | Bin 52840 -> 51984 bytes 05-build_abe-bootstrap_debug/console.log.xz | Bin 462168 -> 465336 bytes 06-check_regression/console.log.xz | Bin 2816 -> 2920 bytes 07-update_baseline/console.log | 9 +++++++++ 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 | 20 ++++++++++---------- 13 files changed, 25 insertions(+), 16 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (17a35a5845 -> d0644afb78)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/master-aarch64 in repository toolchain/ci/base-artifacts. discards 17a35a5845 353: onsuccess: #2309: 1: Success after gcc: 7 commits discards 8e42e48628 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits discards f7a9fb0124 351: onsuccess: #2307: 1: Success after binutils: 2 commits discards c82504b2d9 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits discards bc3577b3c4 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits discards 072f08158d 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits discards d01c8a4a6e 347: onsuccess: #2303: 1: Success after binutils/gcc: 3 commits discards c1337742be 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits discards 27efdc8829 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits discards ba34210b8a 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits discards 45793911b2 343: onsuccess: #2299: 1: Success after binutils/gcc: 18 commits discards 25f2f5c223 342: onsuccess: #2298: 1: Success after binutils/gcc: 17 commits discards 8d6bbeff1a 341: onsuccess: #2297: 1: Success after binutils/gcc: 7 commits discards a0b7d3e091 340: onsuccess: #2296: 1: Success after gcc: 3 commits discards db986420f3 339: onsuccess: #2295: 1: Success after binutils/gcc: 18 commits discards 758071e34b 338: onsuccess: #2294: 1: Success after binutils/gcc: 13 commits discards e127a88c2f 337: onsuccess: #2293: 1: Success after gcc: 21 commits discards cdeb7f3db6 336: onsuccess: #2292: 1: Success after binutils/gcc: 3 commits discards ab9527dbe4 335: onsuccess: #2291: 1: Success after binutils/gcc: 3 commits discards 1b65d0b61b 334: onsuccess: #2290: 1: Success after binutils/gcc: 5 commits discards d8d46ca471 333: onsuccess: #2289: 1: Success after basepoints/gcc-13-41 [...] discards 6ed1956a3e 332: onsuccess: #2288: 1: Success after gcc: 2 commits discards 8c3964bb56 331: onsuccess: #2287: 1: Success after gdb-12-branchpoint-2 [...] discards 70b9397acd 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 commits discards ef6cc69a38 329: onsuccess: #2285: 1: Success after gcc: 8 commits discards 1c01f313e8 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint-2 [...] discards db787543f6 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits discards e98e219a96 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits discards 6557b5369b 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits discards 0e8c241d28 324: onsuccess: #2278: 1: Success after binutils/gcc: 4 commits discards 019c98780a 323: onsuccess: #2277: 1: Success after binutils/gcc: 5 commits discards 502ad64efe 322: onsuccess: #2276: 1: Success after binutils/gcc: 15 commits discards 5b6b43f23b 321: onsuccess: #2275: 1: Success after binutils/gcc: 12 commits discards 9880894466 320: onsuccess: #2274: 1: Success after gcc: 5 commits discards c59bde7be0 319: onsuccess: #2273: 1: Success after binutils/gcc: 15 commits discards c862f39952 318: onsuccess: #2272: 1: Success after binutils/gcc: 22 commits discards 0173385291 317: onsuccess: #2271: 1: Success after binutils/gcc: 8 commits discards cc48351867 316: onsuccess: #2270: 1: Success after gcc: 2 commits discards 7e1ce9ffb7 315: onsuccess: #2269: 1: Success after binutils/gcc: 17 commits discards ee8d51d3d3 314: onsuccess: #2268: 1: Success after binutils/gcc: 101 commits discards 3ab784db87 313: onsuccess: #2267: 1: Success after binutils/gcc: 90 commits discards 3e0fd7ea17 312: onsuccess: #2265: 1: Success after binutils: 2 commits discards 0f05fc4d10 311: onsuccess: #2262: 1: Success after gdb-12-branchpoint-2 [...] discards c1e514f458 310: onsuccess: #2259: 1: Success after binutils: 2 commits discards 1544ab3ada 309: onsuccess: #2255: 1: Success after gdb-12-branchpoint-2 [...] discards 76f656d9b5 308: onsuccess: #2252: 1: Success after gdb-12-branchpoint-2 [...] discards bf37e5330d 307: onsuccess: #2249: 1: Success after gdb-12-branchpoint-2 [...] discards c5bddc44ef 306: onsuccess: #2246: 1: Success after gdb-12-branchpoint-2 [...] discards 27c9623256 305: onsuccess: #2244: 1: Success after binutils/gcc: 8 commits discards e1ecc20b1e 304: onsuccess: #2243: 1: Success after binutils/gcc: 23 commits discards ab01da32a4 303: onsuccess: #2242: 1: Success after binutils/gcc: 17 commits discards 8070e75d05 302: onsuccess: #2241: 1: Success after binutils/gcc: 10 commits discards 94cb0563eb 301: onsuccess: #2240: 1: Success after binutils/gcc: 10 commits discards 99049e93da 300: onsuccess: #2239: 1: Success after binutils/gcc: 20 commits discards a28f8e0728 299: onsuccess: #2238: 1: Success after binutils/gcc: 12 commits discards dea64930fc 298: onsuccess: #2237: 1: Success after binutils/gcc: 9 commits discards 1ff4fe5620 297: onsuccess: #2236: 1: Success after binutils/gcc: 9 commits discards d9b74106d9 296: onsuccess: #2235: 1: Success after binutils/gcc: 14 commits discards d4793a38ef 295: onsuccess: #2234: 1: Success after binutils/gcc: 33 commits discards 59727a3461 294: onsuccess: #2233: 1: Success after binutils/gcc: 4 commits discards 2b331f6189 293: onsuccess: #2232: 1: Success after binutils/gcc: 5 commits discards bbfefc12a0 292: onsuccess: #2231: 1: Success after binutils/gcc: 19 commits discards 8970f963e4 291: onsuccess: #2230: 1: Success after binutils/gcc: 31 commits discards e7bd43d306 290: onsuccess: #2229: 1: Success after binutils/gcc: 12 commits discards 0760ab36c8 289: onsuccess: #2228: 1: Success after binutils/gcc: 11 commits discards 912af5d9d4 288: onsuccess: #2227: 1: Success after binutils/gcc: 16 commits discards 7decd31b23 287: onsuccess: #2226: 1: Success after binutils/gcc: 38 commits discards 5176453605 286: onsuccess: #2225: 1: Success after binutils/gcc: 7 commits discards 4275acdf1f 285: onsuccess: #2224: 1: Success after binutils/gcc: 2 commits discards 64c0c57901 284: onsuccess: #2223: 1: Success after binutils/gcc: 5 commits discards 25a91cfc33 283: onsuccess: #2222: 1: Success after gcc: 4 commits discards ad4c797b09 282: onsuccess: #2221: 1: Success after gcc: 2 commits discards 52cb224610 281: onsuccess: #2220: 1: Success after binutils/gcc: 4 commits discards fdf130e367 280: onsuccess: #2219: 1: Success after binutils/gcc: 10 commits discards 7565c64e62 279: onsuccess: #2218: 1: Success after basepoints/gcc-13-36 [...] discards 04903bfa21 278: onsuccess: #2217: 1: Success after binutils: 7 commits discards 467aa60d34 277: onsuccess: #2216: 1: Success after binutils: 2 commits discards 229bf56d05 276: onsuccess: #2215: 1: Success after binutils/gcc: 44 commits discards 5460ab94ff 275: onsuccess: #2214: 1: Success after binutils/gcc: 14 commits discards 8b4007abf4 274: onsuccess: #2213: 1: Success after binutils/gcc: 12 commits discards 2b01422a43 273: onsuccess: #2212: 1: Success after binutils/gcc: 13 commits discards 30dfe5357b 272: onsuccess: #2211: 1: Success after binutils/gcc: 19 commits discards 504a809f84 271: onsuccess: #2210: 1: Success after binutils/gcc: 8 commits discards 7d3c40485b 270: onsuccess: #2209: 1: Success after gcc: 2 commits discards df40dff1cc 269: onsuccess: #2208: 1: Success after binutils/gcc: 8 commits discards 0676dbeb9c 268: onsuccess: #2207: 1: Success after binutils/gcc: 12 commits discards 4bf2fdcced 267: onsuccess: #2206: 1: Success after binutils/gcc: 5 commits discards 890874a4ff 266: onsuccess: #2205: 1: Success after binutils/gcc: 8 commits discards a65e811d35 265: onsuccess: #2204: 1: Success after binutils/gcc: 5 commits discards 2d1cadea72 264: onsuccess: #2203: 1: Success after gcc: 9 commits discards 8e362e7bcf 263: onsuccess: #2202: 1: Success after binutils/gcc: 5 commits discards ea7306a96e 262: onsuccess: #2201: 1: Success after gcc: 6 commits discards 23558ac8b1 261: onsuccess: #2200: 1: Success after binutils/gcc: 8 commits discards 15d32c0c2e 260: onsuccess: #2199: 1: Success after binutils/gcc: 18 commits discards b50d843935 259: onsuccess: #2198: 1: Success after binutils/gcc: 8 commits discards 27bd61cb0e 258: onsuccess: #2197: 1: Success after binutils/gcc: 5 commits discards 552450d5e3 257: onsuccess: #2196: 1: Success after binutils/gcc: 2 commits discards f1661624d6 256: onsuccess: #2195: 1: Success after gdb-12-branchpoint-2 [...] discards ee2cffae2b 255: onsuccess: #2194: 1: Success after basepoints/gcc-13-35 [...] discards 5ce915d1b2 254: onsuccess: #2193: 1: Success after gdb-12-branchpoint-2 [...] discards 3d397c5dab 253: onsuccess: #2192: 1: Success after gdb-12-branchpoint-2 [...] new 6bc24ada88 253: onsuccess: #2192: 1: Success after gdb-12-branchpoint-2 [...] new 08813ab469 254: onsuccess: #2193: 1: Success after gdb-12-branchpoint-2 [...] new b3fe2bcb2b 255: onsuccess: #2194: 1: Success after basepoints/gcc-13-35 [...] new b7d3f37149 256: onsuccess: #2195: 1: Success after gdb-12-branchpoint-2 [...] new 983ca36293 257: onsuccess: #2196: 1: Success after binutils/gcc: 2 commits new 270828c4d2 258: onsuccess: #2197: 1: Success after binutils/gcc: 5 commits new d6e16560f9 259: onsuccess: #2198: 1: Success after binutils/gcc: 8 commits new d885fd4211 260: onsuccess: #2199: 1: Success after binutils/gcc: 18 commits new c820197ac4 261: onsuccess: #2200: 1: Success after binutils/gcc: 8 commits new e14e965645 262: onsuccess: #2201: 1: Success after gcc: 6 commits new 3fb5ae137d 263: onsuccess: #2202: 1: Success after binutils/gcc: 5 commits new 669b2f8133 264: onsuccess: #2203: 1: Success after gcc: 9 commits new a3fca3b6e9 265: onsuccess: #2204: 1: Success after binutils/gcc: 5 commits new 795663651e 266: onsuccess: #2205: 1: Success after binutils/gcc: 8 commits new dcfe25ad2e 267: onsuccess: #2206: 1: Success after binutils/gcc: 5 commits new 568fc2f051 268: onsuccess: #2207: 1: Success after binutils/gcc: 12 commits new 96db1e50ad 269: onsuccess: #2208: 1: Success after binutils/gcc: 8 commits new 08e07b029d 270: onsuccess: #2209: 1: Success after gcc: 2 commits new 00b388aee9 271: onsuccess: #2210: 1: Success after binutils/gcc: 8 commits new b0c91cecd2 272: onsuccess: #2211: 1: Success after binutils/gcc: 19 commits new 9ae1f972fc 273: onsuccess: #2212: 1: Success after binutils/gcc: 13 commits new 357a17ad6a 274: onsuccess: #2213: 1: Success after binutils/gcc: 12 commits new 5dcfc7af58 275: onsuccess: #2214: 1: Success after binutils/gcc: 14 commits new 93813d151a 276: onsuccess: #2215: 1: Success after binutils/gcc: 44 commits new a9a1912357 277: onsuccess: #2216: 1: Success after binutils: 2 commits new e087af7028 278: onsuccess: #2217: 1: Success after binutils: 7 commits new 8e874f35a0 279: onsuccess: #2218: 1: Success after basepoints/gcc-13-36 [...] new 379b0f7732 280: onsuccess: #2219: 1: Success after binutils/gcc: 10 commits new 73d26d6850 281: onsuccess: #2220: 1: Success after binutils/gcc: 4 commits new 8bf48b5f78 282: onsuccess: #2221: 1: Success after gcc: 2 commits new 4f47f268cb 283: onsuccess: #2222: 1: Success after gcc: 4 commits new 4b436fd58e 284: onsuccess: #2223: 1: Success after binutils/gcc: 5 commits new e2ec783938 285: onsuccess: #2224: 1: Success after binutils/gcc: 2 commits new 45dd7e830c 286: onsuccess: #2225: 1: Success after binutils/gcc: 7 commits new aac5d00c26 287: onsuccess: #2226: 1: Success after binutils/gcc: 38 commits new 551cd63370 288: onsuccess: #2227: 1: Success after binutils/gcc: 16 commits new 7027677137 289: onsuccess: #2228: 1: Success after binutils/gcc: 11 commits new d489ff5481 290: onsuccess: #2229: 1: Success after binutils/gcc: 12 commits new 024434fb73 291: onsuccess: #2230: 1: Success after binutils/gcc: 31 commits new 26021642bc 292: onsuccess: #2231: 1: Success after binutils/gcc: 19 commits new d37b1c988d 293: onsuccess: #2232: 1: Success after binutils/gcc: 5 commits new b45d331090 294: onsuccess: #2233: 1: Success after binutils/gcc: 4 commits new 9e115d4b2a 295: onsuccess: #2234: 1: Success after binutils/gcc: 33 commits new 89de6fe6fb 296: onsuccess: #2235: 1: Success after binutils/gcc: 14 commits new c0821e852a 297: onsuccess: #2236: 1: Success after binutils/gcc: 9 commits new 209efa71ee 298: onsuccess: #2237: 1: Success after binutils/gcc: 9 commits new 48face2095 299: onsuccess: #2238: 1: Success after binutils/gcc: 12 commits new 3257591ea5 300: onsuccess: #2239: 1: Success after binutils/gcc: 20 commits new c34f24b190 301: onsuccess: #2240: 1: Success after binutils/gcc: 10 commits new c3ee4d6912 302: onsuccess: #2241: 1: Success after binutils/gcc: 10 commits new 934fabd243 303: onsuccess: #2242: 1: Success after binutils/gcc: 17 commits new 9c108274cb 304: onsuccess: #2243: 1: Success after binutils/gcc: 23 commits new 7d188b0b6d 305: onsuccess: #2244: 1: Success after binutils/gcc: 8 commits new 80394b94ac 306: onsuccess: #2246: 1: Success after gdb-12-branchpoint-2 [...] new 76593caff8 307: onsuccess: #2249: 1: Success after gdb-12-branchpoint-2 [...] new cabd2cfc4b 308: onsuccess: #2252: 1: Success after gdb-12-branchpoint-2 [...] new d201e4e6aa 309: onsuccess: #2255: 1: Success after gdb-12-branchpoint-2 [...] new ca8a6fb3db 310: onsuccess: #2259: 1: Success after binutils: 2 commits new ae2e9c9a20 311: onsuccess: #2262: 1: Success after gdb-12-branchpoint-2 [...] new da438924b5 312: onsuccess: #2265: 1: Success after binutils: 2 commits new 3b74b58122 313: onsuccess: #2267: 1: Success after binutils/gcc: 90 commits new ec9de9d808 314: onsuccess: #2268: 1: Success after binutils/gcc: 101 commits new 8ed437dfe4 315: onsuccess: #2269: 1: Success after binutils/gcc: 17 commits new c52a9c2346 316: onsuccess: #2270: 1: Success after gcc: 2 commits new 2a280861fc 317: onsuccess: #2271: 1: Success after binutils/gcc: 8 commits new 8a91e039b2 318: onsuccess: #2272: 1: Success after binutils/gcc: 22 commits new ce34d906b5 319: onsuccess: #2273: 1: Success after binutils/gcc: 15 commits new 017522a4ca 320: onsuccess: #2274: 1: Success after gcc: 5 commits new 8a6c182d5b 321: onsuccess: #2275: 1: Success after binutils/gcc: 12 commits new 974e98fdf1 322: onsuccess: #2276: 1: Success after binutils/gcc: 15 commits new 6b72f8bdda 323: onsuccess: #2277: 1: Success after binutils/gcc: 5 commits new 916d6f4259 324: onsuccess: #2278: 1: Success after binutils/gcc: 4 commits new 59e83a33d6 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits new 6199491664 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits new effd684a2c 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits new 2b38e6679a 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint-2 [...] new 647897da55 329: onsuccess: #2285: 1: Success after gcc: 8 commits new 0e6e11880b 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 commits new 848460d93b 331: onsuccess: #2287: 1: Success after gdb-12-branchpoint-2 [...] new 4f5642910c 332: onsuccess: #2288: 1: Success after gcc: 2 commits new dbdfdad1c2 333: onsuccess: #2289: 1: Success after basepoints/gcc-13-41 [...] new b400f9db3b 334: onsuccess: #2290: 1: Success after binutils/gcc: 5 commits new f956f731e5 335: onsuccess: #2291: 1: Success after binutils/gcc: 3 commits new 2c81428a27 336: onsuccess: #2292: 1: Success after binutils/gcc: 3 commits new 62ce392751 337: onsuccess: #2293: 1: Success after gcc: 21 commits new fc5ee4f5a0 338: onsuccess: #2294: 1: Success after binutils/gcc: 13 commits new 4276665d23 339: onsuccess: #2295: 1: Success after binutils/gcc: 18 commits new d40179a26d 340: onsuccess: #2296: 1: Success after gcc: 3 commits new 9b3ae72fc0 341: onsuccess: #2297: 1: Success after binutils/gcc: 7 commits new aa2cde3b3c 342: onsuccess: #2298: 1: Success after binutils/gcc: 17 commits new 894696f5c9 343: onsuccess: #2299: 1: Success after binutils/gcc: 18 commits new 50724fa941 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits new 694d942776 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits new e7a296e8e3 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits new ee56598882 347: onsuccess: #2303: 1: Success after binutils/gcc: 3 commits new a786b0daf1 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits new 1726a794bc 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits new 3b4b86ac07 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits new d1001b580a 351: onsuccess: #2307: 1: Success after binutils: 2 commits new 7c7771ef59 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits new 1036e1295a 353: onsuccess: #2309: 1: Success after gcc: 7 commits new d0644afb78 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 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 (17a35a5845) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-aarch64 [...] 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 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 39712 -> 39884 bytes 04-build_abe-gcc/console.log.xz | Bin 213528 -> 215436 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3872 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2516 -> 2528 bytes 07-check_regression/console.log.xz | Bin 4764 -> 4876 bytes 07-check_regression/mail-body.txt | 27 - 07-check_regression/results.compare | 31 +- 07-check_regression/results.compare2 | 32 +- 08-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- sumfiles/g++.log.xz | Bin 3602860 -> 3629580 bytes sumfiles/g++.sum | 126 +- sumfiles/gcc.log.xz | Bin 3126364 -> 3130376 bytes sumfiles/gcc.sum | 5052 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1047032 -> 1045872 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2188 -> 2180 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 218732 -> 219056 bytes sumfiles/libgomp.sum | 22 +- sumfiles/libitm.log.xz | Bin 2552 -> 2552 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 454484 -> 453456 bytes sumfiles/libstdc++.sum | 12 +- 32 files changed, 2697 insertions(+), 2756 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (8ff27634e5 -> b1861fc090)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards 8ff27634e5 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards c7a043e9f7 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards 5043dab7c8 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards c04bc4c5c2 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards 1f08cec5c2 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 416eacd448 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards fd10c9d537 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 9e115977d8 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards bf1846730d 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 720bf16da1 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 11baa7ffbe 103: onsuccess: #589: 1: Success after binutils: 3 commits discards e31cde74eb 102: onsuccess: #586: 1: Success after binutils: 5 commits discards c8968012f4 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards 7629f65d19 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards d008f6538a 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards e17de61114 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards b3bf3aac53 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards ba994ebfeb 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 8931a772f3 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 21c24872ac 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 8e8220d55d 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards 83d06ad6cb 92: onsuccess: #575: 1: Success after linux: 34 commits discards 8a66f8f75b 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 63c252ddd6 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 8d80aecce3 89: onsuccess: #570: 1: Success after linux: 11 commits discards eadf489dd4 88: onsuccess: #569: 1: Success after glibc: 10 commits discards f61579a8f6 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 03f7252cfd 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 196dec1bb9 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards 13118e7fe5 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 4cb808ebf3 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards e848d52b98 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards 8a971d0743 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards 3ebf4da571 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards 139a0275ec 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards 8f073a9baa 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards 8a6d52d2b0 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 77d39aa2c0 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards 3c2c6c27d3 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards c6d606d2ac 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards b08ff49f9b 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards e6bdcc0d5e 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 80f815dcba 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards e7e0b168d7 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards ed9173ca1b 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards 610709e496 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards 3b0d2472d7 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 6aaea03175 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 843d73a9a2 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards fab90fb8f8 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 56217eacf5 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 078a9c0b0d 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards a55638cc7e 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 2a27919237 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards d7ec2cd875 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards fefe85f5f3 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards 9e5e1702ed 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards 18843227cc 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards 8073d0897c 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 1fcf2b954c 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards 92280a2415 53: onsuccess: #531: 1: Success after binutils: 12 commits discards 6559e6bdc1 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 5a99df54bb 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 926698864e 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] discards c5f827d215 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] discards 7bbd764588 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] discards ec68993817 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] discards f45d1b4e48 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 5e86e29e10 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] discards 77209f524c 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 29e48d2682 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 2957a77c8f 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] discards 2b48ce5997 41: onsuccess: #514: 1: Success after linux: 64 commits discards 165d0d236f 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] discards 986a2224c7 39: onsuccess: #511: 1: Success after binutils: 8 commits discards 17bb21b3ad 38: onsuccess: #508: 1: Success after binutils: 3 commits discards 876a8cb3a6 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards 956525e549 36: onsuccess: #505: 1: Success after glibc: 3 commits discards ede1dd8526 35: onsuccess: #503: 1: Success after binutils: 11 commits discards 413ba11147 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 2f94156d64 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] discards da01324472 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards 96705b4954 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards c80a7004f4 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards d31a3ed36f 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 91290ef0ff 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] discards ecf3032d6c 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 068e7ff370 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] discards a12afc12b9 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards 5930c03987 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards 9ae4e2dc58 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards e41e4b4a32 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 5ce576918d 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b4ef6daa8e 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ce53188256 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3b2089211e 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fbb29c4cf8 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 887fc2a2ec 16: onsuccess: 1: Successful build after binutils: 4 commits discards 028ce2c26e 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9c91487718 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c435f1f287 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bc2df8a76c 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 957ad2b95a 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 698125396e 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4f5a1121a0 16: onsuccess: 1: Successful build after binutils: 4 commits new f34b51930d 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c3ff5c37df 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8b389c6e3c 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5982764234 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 207ca527ed 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d0bb34c1dd 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 45390dfe89 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 561d5045be 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 7a69bdf78b 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 62907c6b66 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] new 0fc0e0cb6c 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 369df10621 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] new 5c676de996 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 74535c4aa9 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new cd4a46dfb5 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new 0642abaaa6 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new 1bf24b1946 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] new 5907948485 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new f496aaa272 35: onsuccess: #503: 1: Success after binutils: 11 commits new 715daa7568 36: onsuccess: #505: 1: Success after glibc: 3 commits new 520e3a029f 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] new 2421b9f968 38: onsuccess: #508: 1: Success after binutils: 3 commits new 25812f4c73 39: onsuccess: #511: 1: Success after binutils: 8 commits new 865fec032d 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] new 6160c1abbb 41: onsuccess: #514: 1: Success after linux: 64 commits new 0eb09ffec2 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] new 6f8230a7d0 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new e13543a260 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new d055de2ecd 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] new a33ce666a7 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 588ea4a649 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] new 943bbe27be 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] new 11e29c45c6 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] new 62474d4697 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new 8b51e2c73f 51: onsuccess: #525: 1: Success after binutils: 8 commits new f7af3aa0fc 52: onsuccess: #528: 1: Success after binutils: 8 commits new e56b4398a9 53: onsuccess: #531: 1: Success after binutils: 12 commits new 40bdb10c0d 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new 3e2954af2b 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 8eca219a5f 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new c4d354de00 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new 68f8df0259 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new 60b538ef25 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 68278180a4 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new a79931e200 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 2dea08bcc3 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new 44b7825827 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 62b41388e8 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 88a05dc20c 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new 23219ab8a1 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new e07423f12a 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new ff5e347f92 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new 1ffa29a1b6 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new 07b3c67f86 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 48a851e9f3 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new 374cc8b51a 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new 5069c682f0 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 7a0e83d562 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new b92a0237ae 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new 8c500c4bdf 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new 6f83c9a469 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new d8401757a6 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new a961ce5263 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 042d463c12 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new 5af4fca387 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new 94e7868fb2 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 29b76b4d6f 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 06c0808525 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 95cf077696 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new 5dc532145a 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 1a713019f1 87: onsuccess: #567: 1: Success after binutils: 8 commits new 6acbb309df 88: onsuccess: #569: 1: Success after glibc: 10 commits new b48a8f5d3a 89: onsuccess: #570: 1: Success after linux: 11 commits new 562ed38490 90: onsuccess: #572: 1: Success after binutils: 15 commits new 36cee161f8 91: onsuccess: #574: 1: Success after glibc: 3 commits new c18d259f18 92: onsuccess: #575: 1: Success after linux: 34 commits new 1816adc89d 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 6e15001e88 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 6086146385 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new a3b1698c3b 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new a396ffa81e 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 4da5d7f22e 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new b0a5d22ea1 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new ad33d5fd2e 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 13caf389d6 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 560f3fe33f 102: onsuccess: #586: 1: Success after binutils: 5 commits new 32aec39e09 103: onsuccess: #589: 1: Success after binutils: 3 commits new aacbd8fb3c 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new ddc4fae52e 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new 3fcb03b091 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new d086e96055 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 3ac5ca222c 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new e5804fe921 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 27aa36a8ed 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new 99bc0112e0 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new c077794124 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new 53bbc64df5 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new b1861fc090 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] 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 (8ff27634e5) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] 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 1704 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 53192 -> 53152 bytes 04-build_abe-gcc/console.log.xz | Bin 236040 -> 234924 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8656 -> 9520 bytes 07-build_abe-glibc/console.log.xz | Bin 236392 -> 237144 bytes 08-build_abe-gdb/console.log.xz | Bin 51660 -> 51912 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3864 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2176 -> 2200 bytes 11-check_regression/console.log.xz | Bin 12508 -> 10360 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 55 +- 11-check_regression/mail-body.txt | 203 +- 11-check_regression/results.compare | 113 +- 11-check_regression/results.compare2 | 1698 ++------- 11-check_regression/results.regressions | 101 +- 12-update_baseline/console.log | 62 +- 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 | 205 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 101 +- sumfiles/gdb.log.xz | Bin 1711952 -> 1730220 bytes sumfiles/gdb.sum | 5989 ++++++++++++++----------------- 30 files changed, 3349 insertions(+), 5228 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 updated (46cb8b9b94 -> 3822c46070)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards 46cb8b9b94 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards bd074ed87f 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards ac5354e1b6 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards d15e8f0564 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards cbc1d6fb5a 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 789b6dfec8 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards 81c565b5a3 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards a0861c51f8 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 117f77c352 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 328769d724 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 4861e4d1ac 95: onsuccess: #835: 1: Success after binutils: 3 commits discards a22ecc3282 94: onsuccess: #832: 1: Success after binutils: 5 commits discards e9ffac24fb 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 3906bc5855 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards e973a5fca5 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 4ac72f0099 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards e985b627c9 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 36311a1615 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards b55ff47f14 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 7e50426e6f 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 4946d4dc5d 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 6f0d71d66a 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 35016909d2 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 5cde51b5a1 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards b692cc35c8 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards f4351516e4 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 6fa7d70306 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards a5dd83e144 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards d0da0484be 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards f3ecb8e4b1 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards d4c5c88382 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards d1e3a9ad05 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 8f5e685844 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 2c40b3b492 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 340c8b0a1c 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 1fc4e817b5 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 08b1f2050e 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards a803ef75fa 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 46a3f9888a 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 5cf243d24c 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 7289c94ab9 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards f8e99eeb6e 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 2efc6be314 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 640afca595 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 168e44ddcf 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards f1f1c90657 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards ba71bef5c4 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards fbc1b9fa58 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards 4928255d42 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards 5eb071839e 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards ae2ccff6a6 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 6d0ca6298a 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards 0d3ce97b4d 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards a1dad78169 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards f336f4143f 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards ed031165e0 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards 38bdcdde23 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 8ea08df888 48: onsuccess: #782: 1: Success after binutils: 8 commits discards b50d78121e 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards 8c1c4432bf 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards 436fb96d13 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards a77661accf 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] discards 7592e9bb3c 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] discards 525a976005 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] discards 7936c94d31 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] discards 221646095f 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] discards fb20d7a01a 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] discards 7654c41641 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] discards 3e29644a1d 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] discards 3e5ab1f8b9 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 9bb03ceb95 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] discards e3a6b4f9a9 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] discards 5cd2b744df 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] discards e7fd167d69 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] discards f8cbcc1706 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] discards af14e3c26d 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] discards 7d3fad6525 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] discards bbd7e4c47a 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] discards d98c8be98a 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] discards 10ba189b9b 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] discards decd5c14f5 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] discards ad12efa7cd 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards 042feadc95 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 964ea31705 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 3466717e6c 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 73b0b33d61 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e0c870a497 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5696d461cb 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9ec5af3d46 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8717e3e46a 16: onsuccess: 1: Successful build after binutils: 4 commits discards d738b80ea3 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 00e1fdd2df 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 78069d98af 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ffce259b31 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 277d001666 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 32a325528a 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 99d64956e5 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 8069af9b6b 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards ac370e4878 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards ad79c8713e 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards f1d9e40543 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 66041e9ccf 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 426f284298 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new bcefa11c9a 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 997b1769f3 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 88373bc4e0 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 80b837fe20 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 787b401272 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cbead31d5c 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b5f10c808b 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b7e6b102e4 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7bd325ffb3 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3f9dd591e9 16: onsuccess: 1: Successful build after binutils: 4 commits new c02f0af1ed 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 57e89c12c7 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c24332671a 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ab1b1169d7 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1b1f467c75 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a19142a764 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 5318691b6a 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 818dbbe132 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 1593976da6 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] new ea44ae79cb 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] new c0e00cb5b1 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] new 34570243a8 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] new da4fc7ec50 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] new 9f5a508e68 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] new 07788853b2 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] new 619a1952ac 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] new 0a17ac557a 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] new 4cf6df99f9 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] new a1ae4a91c2 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] new 3b68ee7c32 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 24566a6fbb 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] new 2942703694 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] new d1eddcbe29 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] new 0e5dc1850d 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] new a90fe51e6d 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] new 1f81b725b0 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] new 5965b5ef36 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new c95a710796 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new 0f7383c022 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new 1b4494350e 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new ac80051f72 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new f73b6b005c 48: onsuccess: #782: 1: Success after binutils: 8 commits new 597054fb9c 49: onsuccess: #785: 1: Success after binutils: 12 commits new a178a380ba 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new b1f649cdfd 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new d625be300b 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new 6c53f499e5 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new 0636f85f34 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new 10e6f9e25f 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 00b546c8ee 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 4462cd6acd 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new a9e9a25829 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new 08cc175a27 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new b689522dd4 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new eedda08df3 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new 7fb87c3933 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new e58019d609 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new ffa60f0c1e 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 5692507d1b 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new d942a3b516 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 2067b6b1bb 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new a6fa0e0169 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 6d0a0f8c89 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new 030ef561a0 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 62c58fb369 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 7252f0fda2 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 8eb4ceec8e 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 96e6d1059f 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 2bb2b8e446 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 91359aaabf 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 2874ea1d28 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 1fcf7aaf4b 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 62ff6520e5 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 59a99321ba 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 063dc393f7 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new f197ebb1ac 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 5e1032d748 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 3dee8464b3 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 02e17fed94 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 2fd0640ec0 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 250b5b5a50 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 956fa97044 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 02b87eb8cd 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 1191885369 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 4bfd152dd0 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 1665534e10 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 985c54272f 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new eb7f3e3017 94: onsuccess: #832: 1: Success after binutils: 5 commits new 58846d51db 95: onsuccess: #835: 1: Success after binutils: 3 commits new fbc21fed1c 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 71ba76e4a0 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 9185b8fd5d 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 034ed959d7 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 8da56d63ff 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 2bcab5b6ba 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new b18f13b6ee 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new cbaa0df499 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new 627e4e8e97 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new 0a542f16c8 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new 3822c46070 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] 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 (46cb8b9b94) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...] 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 1684 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 39236 -> 39272 bytes 04-build_abe-gcc/console.log.xz | Bin 214764 -> 213312 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8528 -> 9548 bytes 07-build_abe-glibc/console.log.xz | Bin 243512 -> 243792 bytes 08-build_abe-gdb/console.log.xz | Bin 38888 -> 38800 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3840 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2724 -> 2572 bytes 11-check_regression/console.log.xz | Bin 7208 -> 6456 bytes 11-check_regression/mail-body.txt | 40 - 11-check_regression/results.compare | 30 +- 11-check_regression/results.compare2 | 196 +- 12-update_baseline/console.log | 58 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 42 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.xz | Bin 3720096 -> 3724504 bytes sumfiles/g++.sum | 140 +- sumfiles/gcc.log.xz | Bin 3272888 -> 3310512 bytes sumfiles/gcc.sum | 5060 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1083272 -> 1078664 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2276 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 230664 -> 230840 bytes sumfiles/libgomp.sum | 22 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 452588 -> 450496 bytes sumfiles/libstdc++.sum | 14 +- 38 files changed, 2740 insertions(+), 2962 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_llvm_tk1/llvm-master-arm-spec2k6-O2 updated (8de3cb3898 -> ac52043709)

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_llvm_tk1/llvm-master-arm-spec2k6-O2 in repository toolchain/ci/base-artifacts. from 8de3cb3898 25: onsuccess: #404: 1: [TCWG CI] No change after binutils/g [...] new ac52043709 26: onsuccess: #406: 1: [TCWG CI] No change after binutils/g [...] 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 1780 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 32004 -> 32092 bytes 04-build_abe-stage1/console.log.xz | Bin 93156 -> 93532 bytes 06-build_abe-linux/console.log.xz | Bin 8700 -> 8740 bytes 07-build_abe-glibc/console.log.xz | Bin 237904 -> 236908 bytes 08-build_abe-stage2/console.log.xz | Bin 221536 -> 215176 bytes 09-build_llvm-true-false-/console.log.xz | Bin 62768 -> 64312 bytes 10-benchmark/benchmark-build.log | 126 +- 10-benchmark/benchmark.log | 124 +- 10-benchmark/console.log.xz | Bin 3992 -> 3988 bytes 11-check_regression/console.log.xz | Bin 13776 -> 12420 bytes .../csv-results-vs-first-0/md5sum.csv | 1796 +- .../csv-results-vs-first-0/results.csv | 221498 ++++++------- .../csv-results-vs-first-0/size.csv | 277424 ++++++++-------- .../csv-results-vs-first-0/vect.csv | 20108 +- .../csv-results-vs-first-1/md5sum.csv | 1712 +- .../csv-results-vs-first-1/perf.csv | 2037 +- .../csv-results-vs-first-1/results.csv | 231124 ++++++------- .../csv-results-vs-first-1/size.csv | 312938 +++++++++--------- .../csv-results-vs-first-1/vect.csv | 20644 +- .../csv-results-vs-prev-0/md5sum.csv | 1679 +- 11-check_regression/csv-results-vs-prev-0/perf.csv | 2010 +- .../csv-results-vs-prev-0/results.csv | 229765 +++++++------ 11-check_regression/csv-results-vs-prev-0/size.csv | 303088 ++++++++--------- 11-check_regression/csv-results-vs-prev-0/vect.csv | 20502 +- .../csv-results-vs-prev-1/md5sum.csv | 1712 +- 11-check_regression/csv-results-vs-prev-1/perf.csv | 2037 +- .../csv-results-vs-prev-1/results.csv | 231124 ++++++------- 11-check_regression/csv-results-vs-prev-1/size.csv | 312938 +++++++++--------- 11-check_regression/csv-results-vs-prev-1/vect.csv | 20644 +- 11-check_regression/results-vs-first-brief.csv | 40 +- 11-check_regression/results-vs-first-full.csv | 1942 +- 11-check_regression/results-vs-first-internal.csv | 154 +- 11-check_regression/results-vs-first.csv | 154 +- 11-check_regression/results-vs-first.log | 826 +- 11-check_regression/results-vs-prev-brief.csv | 40 +- 11-check_regression/results-vs-prev-compare.csv | 4 +- 11-check_regression/results-vs-prev-full.csv | 2116 +- 11-check_regression/results-vs-prev-internal.csv | 154 +- 11-check_regression/results-vs-prev.csv | 154 +- 11-check_regression/results-vs-prev.log | 962 +- 11-check_regression/skipped-symbols.txt | 2 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 12 +- .../squad-vs-first/401.bzip2/results-metadata.json | 12 +- .../squad-vs-first/403.gcc/results-metadata.json | 12 +- .../squad-vs-first/429.mcf/results-metadata.json | 12 +- .../squad-vs-first/433.milc/results-metadata.json | 12 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 12 +- .../squad-vs-first/445.gobmk/results-metadata.json | 12 +- .../squad-vs-first/445.gobmk/results-metrics.json | 2 +- .../447.dealII/results-metadata.json | 12 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 12 +- .../453.povray/results-metadata.json | 12 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../squad-vs-first/456.hmmer/results-metadata.json | 12 +- .../squad-vs-first/458.sjeng/results-metadata.json | 12 +- .../462.libquantum/results-metadata.json | 12 +- .../464.h264ref/results-metadata.json | 12 +- .../squad-vs-first/470.lbm/results-metadata.json | 12 +- .../471.omnetpp/results-metadata.json | 12 +- .../squad-vs-first/473.astar/results-metadata.json | 12 +- .../482.sphinx3/results-metadata.json | 12 +- .../482.sphinx3/results-metrics.json | 2 +- .../483.xalancbmk/results-metadata.json | 12 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 12 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 82 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 35 +- mail/mail-body.txt | 35 +- mail/mail-subject.txt | 2 +- manifest.sh | 35 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 1281720 -> 2549756 bytes save-temps/401.bzip2.tar.xz | Bin 94476 -> 234492 bytes save-temps/403.gcc.tar.xz | Bin 3567072 -> 6843768 bytes save-temps/410.bwaves.tar.xz | Bin 15100 -> 47844 bytes save-temps/416.gamess.tar.xz | Bin 4210492 -> 13817220 bytes save-temps/429.mcf.tar.xz | Bin 36580 -> 69628 bytes save-temps/433.milc.tar.xz | Bin 167760 -> 333244 bytes save-temps/434.zeusmp.tar.xz | Bin 126512 -> 428176 bytes save-temps/435.gromacs.tar.xz | Bin 979240 -> 2111148 bytes save-temps/436.cactusADM.tar.xz | Bin 725464 -> 1524620 bytes save-temps/437.leslie3d.tar.xz | Bin 46336 -> 151400 bytes save-temps/444.namd.tar.xz | Bin 168352 -> 486200 bytes save-temps/445.gobmk.tar.xz | Bin 1833032 -> 2490084 bytes save-temps/447.dealII.tar.xz | Bin 6165516 -> 10714172 bytes save-temps/450.soplex.tar.xz | Bin 709924 -> 1215988 bytes save-temps/453.povray.tar.xz | Bin 1335448 -> 2277212 bytes save-temps/454.calculix.tar.xz | Bin 1232436 -> 3174532 bytes save-temps/456.hmmer.tar.xz | Bin 379444 -> 808860 bytes save-temps/458.sjeng.tar.xz | Bin 148100 -> 301852 bytes save-temps/459.GemsFDTD.tar.xz | Bin 145032 -> 521928 bytes save-temps/462.libquantum.tar.xz | Bin 61684 -> 120504 bytes save-temps/464.h264ref.tar.xz | Bin 563352 -> 1827476 bytes save-temps/465.tonto.tar.xz | Bin 2068872 -> 6061996 bytes save-temps/470.lbm.tar.xz | Bin 26328 -> 43972 bytes save-temps/471.omnetpp.tar.xz | Bin 1066824 -> 1408972 bytes save-temps/473.astar.tar.xz | Bin 88336 -> 141708 bytes save-temps/481.wrf.tar.xz | Bin 1583616 -> 6952448 bytes save-temps/482.sphinx3.tar.xz | Bin 254240 -> 519772 bytes save-temps/483.xalancbmk.tar.xz | Bin 11851876 -> 15541408 bytes 107 files changed, 1113663 insertions(+), 1108364 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 updated (86bbbf3345 -> 30457de104)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. from 86bbbf3345 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb: [...] new 30457de104 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb: [...] 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 1688 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 39416 -> 39524 bytes 04-build_abe-gcc/console.log.xz | Bin 213756 -> 213516 bytes 06-build_abe-linux/console.log.xz | Bin 8604 -> 9628 bytes 07-build_abe-glibc/console.log.xz | Bin 245556 -> 245844 bytes 08-build_abe-gdb/console.log.xz | Bin 39408 -> 40168 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3920 -> 3964 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2536 -> 2564 bytes 11-check_regression/console.log.xz | Bin 7552 -> 5768 bytes 11-check_regression/results.compare2 | 256 +--------------------------------- 12-update_baseline/console.log | 9 ++ 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 ++--- sumfiles/gdb.log.xz | Bin 14676 -> 14652 bytes sumfiles/gdb.sum | 4 +- 23 files changed, 41 insertions(+), 278 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[linux] branch master updated (08ad43d554ba -> 0b1dcc2cf55a)

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 linux. from 08ad43d554ba Merge tag 'net-6.1-rc7' of git://git.kernel.org/pub/scm/li [...] new b09d6acba1d9 drm/amdgpu: handle gang submit before VMID new c19083c72ea7 dma-buf: Use dma_fence_unwrap_for_each when importing fences new 432e25902b96 dma-buf: fix racing conflict of dma_heap_add() new a6a00d7e8ffd fbcon: Use kzalloc() in fbcon_prepare_logo() new 9e2c5c651a63 Merge tag 'drm-misc-fixes-2022-11-24' of git://anongit.fre [...] new 00a6c36cca76 drm/i915/ttm: never purge busy objects new ebbaa4392e36 drm/i915: Fix warn in intel_display_power_*_domain() functions new 9ed1fdee9ee3 drm/i915/gvt: Get reference to KVM iff attachment to VM is [...] new 3c9fd44b9330 drm/i915/gvt: Unconditionally put reference to KVM when de [...] new 14af5d385878 Merge tag 'gvt-fixes-2022-11-11' of https://github.com/int [...] new b65a648865c4 Merge tag 'drm-intel-fixes-2022-11-24' of git://anongit.fr [...] new 3ca682389435 drm/amd/display: Align dcn314_smu logging with other DCNs new ba891436c2d2 drm/amdgpu/mst: Stop ignoring error codes and deadlocking new 2f3a1273862c drm/display/dp_mst: Fix drm_dp_mst_add_affected_dsc_crtcs( [...] new dfbc00410c48 drm/amdgpu/dm/mst: Use the correct topology mgr pointer in [...] new d60b82aa4d67 drm/amdgpu/dm/dp_mst: Don't grab mst_mgr->lock when comput [...] new 85ef1679a190 drm/amdgpu/dm/mst: Fix uninitialized var in pre_compute_ms [...] new b39df63b16b6 drm/amdgpu: always register an MMU notifier for userptr new 4458da0bb09d drm/amdgpu: fix userptr HMM range handling v2 new b9ab82da8804 drm/amdgpu: Enable Aldebaran devices to report CU Occupancy new 91abf28a6362 drm/amd/amdgpu: reserve vm invalidation engine for firmware new 4f2bea62cf38 drm/amdgpu/psp: don't free PSP buffers on suspend new 44035ec2fde1 drm/amd/dc/dce120: Fix audio register mapping, stop trigge [...] new 5d82c82f1dbe drm/amd/display: Update soc bounding box for dcn32/dcn321 new dd2c028c1395 drm/amd/display: Use viewport height for subvp mall alloca [...] new 2a5dd86a69ea drm/amd/display: Avoid setting pixel rate divider to N/A new e667ee3b0c04 drm/amd/display: Use new num clk levels struct for max mclk index new a26a54fbe32b drm/amd/display: Fix rotated cursor offset calculation new f2e1aa267f12 drm/amd/pm: update driver if header for smu_13_0_7 new 3cb93f390453 drm/amdgpu: fix use-after-free during gpu recovery new a6e1775da04a drm/amd/display: No display after resume from WB/CB new 602ad43c3cd8 drm/amdgpu: Partially revert "drm/amdgpu: update drm_displ [...] new ecb41b71ef90 drm/amdgpu/vcn: re-use original vcn0 doorbell value new e57702069b26 Merge tag 'amd-drm-fixes-6.1-2022-11-23' of https://gitlab [...] new 6fe0e074e769 Merge tag 'drm-fixes-2022-11-25' of git://anongit.freedesk [...] new 05530ef7cf7c ALSA: seq: Fix function prototype mismatch in snd_seq_expa [...] new 3ca507bf9961 ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register new 7c0f8f1462c9 ASoC: stm32: i2s: remove irqf_oneshot flag new 37882100cd06 ASoC: hdac_hda: fix hda pcm buffer overflow issue new 0bb8e9b36b5b ASoC: sgtl5000: Reset the CHIP_CLK_CTRL reg on remove new 39bd801d6908 ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open() new c7d7d4e7bb12 ASoC: rt711-sdca: fix the latency time of clock stop prepa [...] new 60591bbf6d5e ASoC: max98373: Add checks for devm_kcalloc new f5f8ad3fcdc4 ASoC: SOF: dai: move AMD_HS to end of list to restore back [...] new db8f91d424fe ASoC: soc-pcm: Add NULL check in BE reparenting new ecae4c8954a1 Merge tag 'asoc-fix-v6.1-rc6' of https://git.kernel.org/pu [...] new ca66e58001ad Merge tag 'sound-6.1-rc7' of git://git.kernel.org/pub/scm/ [...] new 7ee47dcfff18 fs: use acquire ordering in __fget_light() new 406c706c7b7f vfs: vfs_tmpfile: ensure O_EXCL flag is enforced new b30857095733 Merge tag 'pull-fixes' of git://git.kernel.org/pub/scm/lin [...] new f53af4285d77 mm: vmscan: fix extreme overreclaim and swap floods new e031ff96b334 mm: khugepaged: allow page allocation fallback to eligible nodes new ed86b74874f8 mm/page_exit: fix kernel doc warning in page_ext_put() new 045634ff1e86 mm/khugepaged: refactor mm_khugepaged_scan_file tracepoint [...] new a6f810efabfd gcov: clang: fix the buffer overflow issue new b6305049f306 ipc/shm: call underlying open/close vm_ops new cd08d80ecdac mm: correctly charge compressed memory to its memcg new 4a955bed882e mm/memory: return vm_fault_t result from migrate_to_ram() [...] new 8468b486612c mm/damon/sysfs-schemes: skip stats update if the scheme di [...] new 4a42344081ff mm: mmap: fix documentation for vma_mas_szero new d39e2ad63def mailmap: update Alex Hung's email address new db8e0998c35a MAINTAINERS: update Alex Hung's email address new 50c697215a8c kbuild: fix -Wimplicit-function-declaration in license_is_ [...] new 44af0b45d58d mm/migrate_device: return number of migrating pages in arg [...] new 47123d7fdfff mailmap: update email address for Satya Priya new 359a5e1416ca mm: multi-gen LRU: retry folios written back while isolated new f850c84948ef proc/meminfo: fix spacing in SecPageTables new 747c0f35f2d5 kfence: fix stack trace pruning new 7fb0728a9b00 hugetlb: fix __prep_compound_gigantic_page page flag setting new de1ccfb64824 swapfile: fix soft lockup in scan_swap_map_slots new ea4452de2ae9 mm: fix unexpected changes to {failslab|fail_page_alloc}.attr new 81a70c21d917 mm/cgroup/reclaim: fix dirty pages throttling on cgroup v1 new 512c5ca01a36 nilfs2: fix nilfs_sufile_mark_dirty() not set segment usag [...] new de3db3f883a8 test_kprobes: fix implicit declaration error of test_kprobes new 0b1dcc2cf55a Merge tag 'mm-hotfixes-stable-2022-11-24' of git://git.ker [...] The 75 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: .mailmap | 2 + MAINTAINERS | 2 +- drivers/dma-buf/dma-buf.c | 23 +- drivers/dma-buf/dma-heap.c | 28 +-- .../gpu/drm/amd/amdgpu/amdgpu_amdkfd_aldebaran.c | 1 + drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c | 12 +- drivers/gpu/drm/amd/amdgpu/amdgpu_bo_list.c | 1 + drivers/gpu/drm/amd/amdgpu/amdgpu_bo_list.h | 3 + drivers/gpu/drm/amd/amdgpu/amdgpu_connectors.c | 1 - drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 8 +- drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c | 14 +- drivers/gpu/drm/amd/amdgpu/amdgpu_gmc.c | 6 + drivers/gpu/drm/amd/amdgpu/amdgpu_job.c | 12 +- drivers/gpu/drm/amd/amdgpu/amdgpu_psp.c | 16 +- drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 53 ++--- drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.h | 14 +- drivers/gpu/drm/amd/amdgpu/mmsch_v4_0.h | 1 - drivers/gpu/drm/amd/amdgpu/vcn_v4_0.c | 9 +- drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 55 ++++- .../amd/display/amdgpu_dm/amdgpu_dm_mst_types.c | 254 +++++++++++---------- .../amd/display/amdgpu_dm/amdgpu_dm_mst_types.h | 12 +- .../drm/amd/display/dc/clk_mgr/dcn314/dcn314_smu.c | 11 +- .../drm/amd/display/dc/dce120/dce120_resource.c | 3 +- drivers/gpu/drm/amd/display/dc/dcn10/dcn10_dpp.c | 34 ++- drivers/gpu/drm/amd/display/dc/dcn10/dcn10_hubp.c | 28 ++- drivers/gpu/drm/amd/display/dc/dcn20/dcn20_hubp.c | 32 ++- .../gpu/drm/amd/display/dc/dcn314/dcn314_dccg.c | 7 + .../gpu/drm/amd/display/dc/dcn314/dcn314_hwseq.c | 6 +- drivers/gpu/drm/amd/display/dc/dcn32/dcn32_dccg.c | 4 +- drivers/gpu/drm/amd/display/dc/dcn32/dcn32_hwseq.c | 4 +- .../amd/display/dc/dcn32/dcn32_resource_helpers.c | 2 +- .../gpu/drm/amd/display/dc/dml/dcn32/dcn32_fpu.c | 8 +- .../gpu/drm/amd/display/dc/dml/dcn321/dcn321_fpu.c | 8 +- .../pm/swsmu/inc/pmfw_if/smu13_driver_if_v13_0_7.h | 117 +++++++--- drivers/gpu/drm/amd/pm/swsmu/inc/smu_v13_0.h | 2 +- drivers/gpu/drm/display/drm_dp_mst_topology.c | 2 +- drivers/gpu/drm/i915/display/intel_display_power.c | 8 +- drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 4 + drivers/gpu/drm/i915/gvt/kvmgt.c | 8 +- drivers/video/fbdev/core/fbcon.c | 2 +- fs/file.c | 11 +- fs/namei.c | 3 +- fs/nilfs2/sufile.c | 8 + fs/proc/meminfo.c | 2 +- include/linux/fault-inject.h | 7 +- include/linux/license.h | 2 + include/sound/sof/dai.h | 2 +- include/trace/events/huge_memory.h | 8 +- ipc/shm.c | 34 ++- kernel/gcov/clang.c | 2 + lib/Kconfig.debug | 1 + lib/fault-inject.c | 13 +- mm/damon/sysfs.c | 4 + mm/failslab.c | 12 +- mm/hugetlb.c | 4 +- mm/kfence/report.c | 13 +- mm/khugepaged.c | 35 ++- mm/memcontrol.c | 2 +- mm/memory.c | 2 +- mm/migrate_device.c | 8 +- mm/mmap.c | 2 +- mm/page_alloc.c | 7 +- mm/page_ext.c | 2 +- mm/swapfile.c | 8 +- mm/vmscan.c | 72 ++++-- sound/core/seq/seq_memory.c | 11 +- sound/soc/codecs/hdac_hda.h | 4 +- sound/soc/codecs/max98373-i2c.c | 4 + sound/soc/codecs/rt711-sdca-sdw.c | 2 +- sound/soc/codecs/sgtl5000.c | 1 + sound/soc/codecs/wm8962.c | 8 + sound/soc/soc-pcm.c | 7 +- sound/soc/stm/stm32_i2s.c | 2 +- 73 files changed, 699 insertions(+), 421 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[gcc] branch master updated (3de627ffe4b -> 309e2d95e3b)

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 3de627ffe4b sync libsframe toplevel from binutils-gdb new 309e2d95e3b OpenMP: Generate SIMD clones for functions with "declare target" 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/common.opt | 22 ++ gcc/config/aarch64/aarch64.cc | 24 +- gcc/config/gcn/gcn.cc | 10 +- gcc/config/i386/i386.cc | 27 +- gcc/doc/invoke.texi | 23 +- gcc/doc/tm.texi | 2 +- gcc/flag-types.h | 9 + gcc/omp-simd-clone.cc | 309 +++++++++++++++++++-- gcc/opts.cc | 2 + gcc/target.def | 2 +- gcc/testsuite/g++.dg/gomp/target-simd-clone-1.C | 25 ++ gcc/testsuite/g++.dg/gomp/target-simd-clone-2.C | 23 ++ gcc/testsuite/gcc.dg/gomp/target-simd-clone-1.c | 25 ++ gcc/testsuite/gcc.dg/gomp/target-simd-clone-2.c | 22 ++ gcc/testsuite/gcc.dg/gomp/target-simd-clone-3.c | 22 ++ gcc/testsuite/gcc.dg/gomp/target-simd-clone-4.c | 26 ++ gcc/testsuite/gcc.dg/gomp/target-simd-clone-5.c | 28 ++ gcc/testsuite/gcc.dg/gomp/target-simd-clone-6.c | 27 ++ gcc/testsuite/gcc.dg/gomp/target-simd-clone-7.c | 15 + gcc/testsuite/gcc.dg/gomp/target-simd-clone-8.c | 25 ++ .../lib/{scanipa.exp => scanoffloadipa.exp} | 86 +++--- libgomp/testsuite/lib/libgomp.exp | 1 + libgomp/testsuite/libgomp.c/target-simd-clone-1.c | 43 +++ libgomp/testsuite/libgomp.c/target-simd-clone-2.c | 39 +++ libgomp/testsuite/libgomp.c/target-simd-clone-3.c | 40 +++ 25 files changed, 783 insertions(+), 94 deletions(-) create mode 100644 gcc/testsuite/g++.dg/gomp/target-simd-clone-1.C create mode 100644 gcc/testsuite/g++.dg/gomp/target-simd-clone-2.C create mode 100644 gcc/testsuite/gcc.dg/gomp/target-simd-clone-1.c create mode 100644 gcc/testsuite/gcc.dg/gomp/target-simd-clone-2.c create mode 100644 gcc/testsuite/gcc.dg/gomp/target-simd-clone-3.c create mode 100644 gcc/testsuite/gcc.dg/gomp/target-simd-clone-4.c create mode 100644 gcc/testsuite/gcc.dg/gomp/target-simd-clone-5.c create mode 100644 gcc/testsuite/gcc.dg/gomp/target-simd-clone-6.c create mode 100644 gcc/testsuite/gcc.dg/gomp/target-simd-clone-7.c create mode 100644 gcc/testsuite/gcc.dg/gomp/target-simd-clone-8.c copy gcc/testsuite/lib/{scanipa.exp => scanoffloadipa.exp} (54%) create mode 100644 libgomp/testsuite/libgomp.c/target-simd-clone-1.c create mode 100644 libgomp/testsuite/libgomp.c/target-simd-clone-2.c create mode 100644 libgomp/testsuite/libgomp.c/target-simd-clone-3.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits November 2022