Tcwg-commits January 2023

tcwg-commits@lists.linaro.org

5 participants
4127 discussions

[gcc] branch master updated (7c4d1b7a440 -> 1472ba52f3f)

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 7c4d1b7a440 testsuite: Restore TORTURE_OPTIONS in gm2/warnings/returnty [...] new 1472ba52f3f aarch64: Update Ampere-1A (-mcpu=ampere1a) to include SM4 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/config/aarch64/aarch64-cores.def | 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, 10 months

[binutils-gdb] branch master updated (594a01c2171 -> 34f0de5a4ac)

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 594a01c2171 Automatic date update in version.in new ff52c0736a6 gdb: Make global feature array a per-remote target array new fe4c3ca0036 gdb: Add per-remote target variables for memory read and wr [...] new 34f0de5a4ac gdb: Remove workaround for the vCont packet The 3 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gdb/NEWS | 21 + gdb/doc/gdb.texinfo | 25 +- gdb/remote.c | 1840 +++++++++++--------- gdb/testsuite/gdb.base/cond-eval-mode.exp | 9 +- gdb/testsuite/gdb.base/dprintf.exp | 5 +- gdb/testsuite/gdb.base/find-unmapped.exp | 5 +- .../gdb.base/hbreak-in-shr-unsupported.exp | 4 +- gdb/testsuite/gdb.base/remote.exp | 47 +- .../gdb.multi/multi-target-info-inferiors.exp | 6 +- gdb/testsuite/gdb.multi/multi-target.exp.tcl | 8 +- .../gdb.server/connect-without-multi-process.exp | 4 +- gdb/testsuite/gdb.server/exit-multiple-threads.exp | 9 +- gdb/testsuite/gdb.server/ext-restart.exp | 5 +- gdb/testsuite/gdb.server/ext-wrapper.exp | 5 +- gdb/testsuite/gdb.server/server-exec-info.exp | 5 +- gdb/testsuite/gdb.server/server-kill.exp | 4 +- .../gdb.server/stop-reply-no-thread-multi.exp | 8 +- gdb/testsuite/gdb.server/stop-reply-no-thread.exp | 9 +- .../gdb.threads/process-dies-while-handling-bp.exp | 9 +- gdb/testsuite/gdb.trace/change-loc.exp | 4 +- gdb/testsuite/gdb.trace/qtro.exp | 6 +- 21 files changed, 1135 insertions(+), 903 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-mainline-allyesconfig updated (459879455d -> 06952a38de)

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-mainline-allyesconfig in repository toolchain/ci/base-artifacts. from 459879455d 52: force: #550: 21631: Failure after llvmorg-16-init-18491- [...] new 06952a38de 53: onsuccess: #551: 21631: Success after llvm: 39 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 1712 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 31008 -> 31136 bytes 04-build_kernel_llvm/console.log.xz | Bin 64108 -> 64068 bytes 05-build_abe-qemu/console.log.xz | Bin 31396 -> 31280 bytes 06-build_linux/console.log.xz | Bin 8808 -> 8824 bytes 08-check_regression/console.log.xz | Bin 3620 -> 2928 bytes 08-check_regression/jira-body.txt | 2 +- 08-check_regression/mail-body.txt | 26 +- 08-check_regression/mail-subject.txt | 2 +- 08-check_regression/results.regressions | 11 - 08-check_regression/trigger-bisect | 2 - 08-check_regression/trigger-notify | 0 09-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/llvm_rev | 2 +- jenkins/jira-status.draft | 4 - jenkins/mail-body.draft | 615 -------------------------------- jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/jira-body.txt | 2 +- mail/mail-body.txt | 26 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 11 - 26 files changed, 38 insertions(+), 690 deletions(-) delete mode 100644 08-check_regression/results.regressions delete mode 100644 08-check_regression/trigger-bisect delete mode 100644 08-check_regression/trigger-notify delete mode 100644 jenkins/jira-status.draft delete mode 100644 jenkins/mail-body.draft delete mode 100644 jenkins/mail-recipients.draft delete mode 100644 jenkins/mail-subject.draft delete mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (99391e40ea -> 9e128dfb1d)

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 99391e40ea 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 0c83bd26f1 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 3ce733d783 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 63ae1bdd7f 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 0b2de3bf25 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 346954cc17 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards be729ddddb 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 6680abd622 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 3869c35a74 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 7edcc41251 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards d54e17247f 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 1218bc59c3 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards bfd95179d8 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 564e7b7adf 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 8b74429786 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards a45e646da3 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards da3ce9f013 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 0497732a60 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 2b710256cc 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards fde7124617 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 04808b8275 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 875ca9be5d 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards efaab978af 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 803edfdb2b 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 3464250209 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 8a106b660d 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 3caca8429c 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 969e661d02 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 84e13ee546 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 8ffed55e4c 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards c93273078f 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards ff35b85226 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards af61295cd8 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 819e649e66 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 2e79a4fea3 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 2f976293d9 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 9fc93aedf5 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 3c47b62444 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards ac6a1fd878 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 4d10ad59b7 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 5ed9cd1e5b 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 7a28c39248 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 3e3a7ed79a 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 09c964feaf 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards e98a1040db 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 364e4aaaf2 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards e247315b9b 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 6afa517d7a 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 37ae58f41c 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 014993aef0 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 843e9001d0 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards b3f18d56b2 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards bb90da9362 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 89754085b3 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards e7b88a0ded 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards b0e022683f 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 3ca4dbb2ff 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards e183744093 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 6c3e1c9b10 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards af033fbec9 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 029e1f7ee7 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 91e7fcd1f5 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 33f6d7a77c 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 719b3b830b 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards e36db6dbcd 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 9973fecf84 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 8e1b559864 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards ccdf49ec9a 301: onsuccess: #2118: 1: Success after linux: 16 commits discards f3080d9f7f 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards c761b3202f 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 40e9d6c4aa 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 243bc75efa 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 164c30dbd8 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards a23cfa48bb 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 5fd8e757d4 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards b3704241f7 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards e527ca011c 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards fc3d81c492 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 2b9db276b9 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards d656dd4775 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 0321247923 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 68aebc541a 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 777557ec30 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 4fa9b1c1d3 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 6ff6741bf4 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 8b220bfee5 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 2c83a378ad 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 6483135d9e 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards dfe6cc4e35 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 0d9539bc57 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 817c4721e7 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 58b13f4142 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 8847052285 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 41e7c09263 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards e6c7c7f314 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards cbc8d06352 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards d8fccf89eb 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 01bbfa4891 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 5495e8df23 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 55f847a243 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 675845bd69 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new d6332aa4e0 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 22fad42fe7 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new af83d5e449 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 3e6757abe5 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 281a66e60b 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new c09850e63b 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new d1f600669e 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 33a0871357 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 0f529b6415 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 7a0bf9444c 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new f642c1e916 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new c095f47b1d 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 7409a1a147 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 5cf86ee597 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new d28ee74348 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 9fa7be692d 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 4e8fb8dfbd 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new a8cc5ee671 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new fe383c5621 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 3eb356dfa3 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 6808b794a3 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 418b026a95 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new de7cc53c1e 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 589ade4967 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 603a9612a8 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new bbc2536fa2 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 72e7d77e74 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 48352f0df0 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 1202f93cd5 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 2ebe0daae5 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new dde910b63a 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new cf76b2d6f4 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new b1ea81db4f 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new c1ee2a1da4 301: onsuccess: #2118: 1: Success after linux: 16 commits new 11061d205d 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 995f11b961 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 84b59f4842 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new d40549424a 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new a43c440b40 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 0b3ed9b1cd 307: onsuccess: #2124: 1: Success after gcc: 2 commits new a6780cf512 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new ed6cd045e5 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 88914767d3 310: onsuccess: #2129: 1: Success after binutils: 4 commits new a6dead0b67 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 43af303bc2 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 7d1f78eac0 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 9efb7fe2a3 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 3b8008e29c 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new ee15fdaf19 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 7bc421affe 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 5e1a66d796 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 78ad2426ce 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 7b137bd039 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new a56f5138e7 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 012023bed3 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 2f6c5fd82b 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 0019016d02 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 79bb6f81bd 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 3680acd75b 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 46ec374db8 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new c30bbca6f7 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 2b30956a82 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new fd51fe565a 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new f27be58431 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new ff11d5969b 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 2f132ca0a9 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 9fb38914e7 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 089ce1f8fb 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new b39a2592ef 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 399d09f325 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 534df12109 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new edd9c2d743 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new aafabfbe63 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new c379783704 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 962bb9dcc3 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new dc5a84e171 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new b49337e359 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 98b8367ac2 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new b6b174e821 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 5e08b11f6c 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 0a6c77d086 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 7c3a38d2d5 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new bcb69ecb31 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 0e0f81d27c 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 40b0426105 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new a7f2dc7fce 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 4273b684ef 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new d1efbe57b9 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 171618c649 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 53629bd16a 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 7f37eeb583 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 6e68d68638 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new b695e5b309 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 9531e861b0 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new fb6cb3687a 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 6e680e5ea2 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new eaba73e4a9 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new dd7b09d863 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new ac04ce9b67 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new cc52cae589 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 3e203eadec 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 9e128dfb1d 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (99391e40ea) \ 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 1800 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 31360 -> 31524 bytes 04-build_abe-stage1/console.log.xz | Bin 92688 -> 92288 bytes 06-build_abe-linux/console.log.xz | Bin 8588 -> 8560 bytes 07-build_abe-glibc/console.log.xz | Bin 237668 -> 238652 bytes 08-build_abe-stage2/console.log.xz | Bin 231180 -> 229664 bytes 09-build_abe-gdb/console.log.xz | Bin 38340 -> 38340 bytes 10-build_abe-qemu/console.log.xz | Bin 31580 -> 31092 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3908 -> 3928 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2780 -> 2784 bytes 13-check_regression/console.log.xz | Bin 7804 -> 6888 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 8 +- 13-check_regression/mail-body.txt | 69 +- 13-check_regression/results.compare | 41 +- 13-check_regression/results.compare2 | 110 +- 13-check_regression/results.regressions | 41 +- 14-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 | 71 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 41 +- sumfiles/g++.log.xz | Bin 2643904 -> 2642944 bytes sumfiles/g++.sum | 24 +- sumfiles/gcc.log.xz | Bin 2194372 -> 2229072 bytes sumfiles/gcc.sum | 2242 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 890556 -> 891436 bytes sumfiles/gfortran.sum | 74 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214252 -> 214232 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2672 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 436536 -> 445396 bytes sumfiles/libstdc++.sum | 44 +- 43 files changed, 1447 insertions(+), 1440 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-mainline-allyesconfig updated (7a9906a7af -> 459879455d)

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-mainline-allyesconfig in repository toolchain/ci/base-artifacts. from 7a9906a7af 51: force: #549: all: Success after llvm: 470 commits new 459879455d 52: force: #550: 21631: Failure after llvmorg-16-init-18491- [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1784 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 31140 -> 31008 bytes 04-build_kernel_llvm/console.log.xz | Bin 65256 -> 64108 bytes 05-build_abe-qemu/console.log.xz | Bin 31436 -> 31396 bytes 06-build_linux/console.log.xz | Bin 3092 -> 8808 bytes 07-boot_linux/console.log.xz | Bin 504 -> 0 bytes 08-check_regression/console.log.xz | Bin 2848 -> 3620 bytes 08-check_regression/jira-body.txt | 2 +- 08-check_regression/mail-body.txt | 17 +- 08-check_regression/mail-subject.txt | 2 +- 08-check_regression/results.regressions | 11 + 08-check_regression/trigger-bisect | 2 + 08-check_regression/trigger-notify | 0 dashboard/dashboard-generate.sh | 2 +- git/llvm_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 615 ++++++++++++++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 17 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 15 +- 26 files changed, 688 insertions(+), 24 deletions(-) delete mode 100644 07-boot_linux/console.log.xz create mode 100644 08-check_regression/results.regressions create mode 100644 08-check_regression/trigger-bisect create mode 100644 08-check_regression/trigger-notify create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/interesting-commits] branch master updated (3414578e -> 9906b94a)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from 3414578e Add entry 1500e55910eee2e65a6fd153f6db70889265229e from https [...] new 9906b94a Add entry de122cb920080fd9e24b2777114271fbef932d5e from https [...] 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: llvm/llvmorg-16-init-18491-gde122cb92008 | 1 + .../build_url | 2 +- .../last_good | 1 + .../summary.txt | 1 + .../tcwg_kernel/status.txt | 21 +++++++++++++++++++++ 5 files changed, 25 insertions(+), 1 deletion(-) create mode 120000 llvm/llvmorg-16-init-18491-gde122cb92008 copy {linux/sha1/0d2b746b1bef73de62d2d311e594a7ffed4ca434/tcwg_kernel/llvm-master- [...] create mode 100644 llvm/sha1/de122cb920080fd9e24b2777114271fbef932d5e/tcwg_kernel/ [...] create mode 100644 llvm/sha1/de122cb920080fd9e24b2777114271fbef932d5e/tcwg_kernel/ [...] create mode 100644 llvm/sha1/de122cb920080fd9e24b2777114271fbef932d5e/tcwg_kernel/ [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[gcc] branch master updated (876b3e0514b -> 7c4d1b7a440)

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 876b3e0514b Fix PR 108582: ICE due to PHI-OPT removing a still in use s [...] new 7c4d1b7a440 testsuite: Restore TORTURE_OPTIONS in gm2/warnings/returnty [...] 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: .../gm2/warnings/returntype/fail/warnings-returntype-fail.exp | 4 ++++ 1 file changed, 4 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[gcc] branch devel/rust/master updated (a91b12e2c4c -> 0ae13efb5a6)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch devel/rust/master in repository gcc. from a91b12e2c4c Merge #1769 new 248316afc36 Add get_item method for HIR::GroupedPattern new 01a07f7d395 Add type resolution for grouped patterns new fe828b4f931 Merge #1771 new 2ba4506b672 Added missing GroupedPattern visitors for code generation new d4f6a97c628 Merge #1772 new 53c0231c782 Revert 10-second timeout for each test new 21ec24265b2 Merge #1759 new 2ad7c1ca0e9 Rename file rust-ast-full-test.cc to rust-ast.cc new d12a38da686 Merge #1777 new e66cb001dc7 moved operator.h to util/rust-operators.h new 0ae13efb5a6 Merge #1778 The 11 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/rust/Make-lang.in | 2 +- gcc/rust/ast/{rust-ast-full-test.cc => rust-ast.cc} | 2 +- gcc/rust/ast/rust-expr.h | 2 +- gcc/rust/backend/rust-compile-pattern.cc | 12 ++++++++++++ gcc/rust/backend/rust-compile-pattern.h | 4 ++-- gcc/rust/hir/tree/rust-hir-expr.h | 2 +- gcc/rust/hir/tree/rust-hir-pattern.h | 6 ++++++ gcc/rust/rust-backend.h | 2 +- gcc/rust/typecheck/rust-hir-type-check-pattern.cc | 8 +++++--- gcc/rust/util/rust-lang-item.h | 2 +- gcc/rust/{operator.h => util/rust-operators.h} | 0 gcc/testsuite/lib/rust.exp | 5 +---- 12 files changed, 32 insertions(+), 15 deletions(-) rename gcc/rust/ast/{rust-ast-full-test.cc => rust-ast.cc} (99%) rename gcc/rust/{operator.h => util/rust-operators.h} (100%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-mainline-allyesconfig updated (e055c575a1 -> 7a9906a7af)

by git＠git.linaro.org

1 year, 10 months

[gcc] branch master updated (7ac3e69e311 -> 876b3e0514b)

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 7ac3e69e311 tree-optimization/108574 - wrong-code with PRE PHI node processing new 876b3e0514b Fix PR 108582: ICE due to PHI-OPT removing a still in use s [...] 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/testsuite/gcc.dg/pr108582-1.c | 58 +++++++++++++++++++++++++++++++++++++++ gcc/tree-ssa-phiopt.cc | 5 ++++ 2 files changed, 63 insertions(+) create mode 100644 gcc/testsuite/gcc.dg/pr108582-1.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits January 2023