Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[newlib] branch cygwin-3_4-branch updated (f21d438a0 -> 55873f0d2)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch cygwin-3_4-branch in repository newlib. from f21d438a0 Cygwin: add __sFILE64 fix to 3.4.1 release notes new 55873f0d2 Cygwin: improve release text for FILE issue 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: winsup/cygwin/release/3.4.1 | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch devel/rust/master updated (d0cb3248ce6 -> 62d1620c910)

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 d0cb3248ce6 Merge #1683 new d77d5be0695 var_expression: document that the memory of the val argumen [...] new e91b6e5339c Merge #1681 new a3a755838fd Cleanup unused parameters to fix the bootstrap build new 88e509b1b14 const evaluator: Remove get_nth_callarg new ca0a935cdc3 Repair 'gcc/rust/lang.opt' comment new 62d1620c910 Merge #1678 #1682 #1687 The 6 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/rust/backend/rust-compile-type.cc | 8 +- gcc/rust/backend/rust-constexpr.cc | 33 +- gcc/rust/backend/rust-tree.cc | 38 +-- .../checks/errors/privacy/rust-privacy-reporter.cc | 58 ++-- .../checks/errors/privacy/rust-reachability.cc | 4 +- .../errors/privacy/rust-visibility-resolver.cc | 8 +- gcc/rust/checks/errors/rust-const-checker.cc | 132 ++++---- gcc/rust/checks/errors/rust-unsafe-checker.cc | 142 ++++----- gcc/rust/checks/lints/rust-lint-marklive.cc | 2 +- gcc/rust/checks/lints/rust-lint-unused-var.cc | 2 +- gcc/rust/expand/rust-macro-builtins.cc | 20 +- gcc/rust/hir/rust-ast-lower-base.cc | 352 ++++++++++----------- gcc/rust/hir/rust-hir-dump.cc | 4 +- gcc/rust/hir/tree/rust-hir-full-test.cc | 2 +- gcc/rust/lang.opt | 4 +- gcc/rust/lex/rust-lex.cc | 6 +- gcc/rust/lex/rust-lex.h | 2 +- gcc/rust/metadata/rust-export-metadata.cc | 24 +- gcc/rust/resolve/rust-ast-resolve-expr.cc | 6 +- gcc/rust/resolve/rust-ast-resolve-type.cc | 6 +- gcc/rust/resolve/rust-ast-verify-assignee.h | 8 +- gcc/rust/resolve/rust-early-name-resolver.cc | 120 +++---- gcc/rust/rust-gcc.cc | 1 + gcc/rust/typecheck/rust-hir-type-check-expr.h | 32 +- gcc/rust/typecheck/rust-hir-type-check-item.h | 4 +- gcc/rust/typecheck/rust-hir-type-check-pattern.cc | 10 +- gcc/rust/typecheck/rust-tyty-rules.h | 48 +-- gcc/rust/util/rust-attributes.cc | 312 +++++++++--------- 28 files changed, 666 insertions(+), 722 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-next-allyesconfig updated (c8e7c22a54a -> eecfc7d8705)

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-release-aarch64-next-allyesconfig in repository toolchain/ci/base-artifacts. from c8e7c22a54a 44: onsuccess: #447: 21601: Success after binutils/linux/qe [...] new eecfc7d8705 45: onsuccess: #448: 21612: Success after binutils/linux/qe [...] 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 1956 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 30260 -> 30352 bytes 04-build_kernel_llvm/console.log.xz | Bin 66648 -> 65024 bytes 05-build_abe-qemu/console.log.xz | Bin 31788 -> 30768 bytes 06-build_linux/console.log.xz | Bin 3980 -> 4332 bytes 08-check_regression/console.log.xz | Bin 3720 -> 3532 bytes 08-check_regression/mail-body.txt | 4 ++-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 6 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- results | 2 +- 17 files changed, 26 insertions(+), 26 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch master updated (96cb786b754 -> 71b31d13757)

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 96cb786b754 MAINTAINERS: fix spacing new 71b31d13757 rs6000: Remove useless copy_rtx in rs6000_emit_set_{,long}_const 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/rs6000/rs6000.cc | 61 ++++++++++++++++----------------------------- 1 file changed, 21 insertions(+), 40 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[binutils-gdb] branch master updated (8b272d7671f -> 73425813c1b)

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 8b272d7671f [gdb/testsuite] Fix gdb.guile/scm-symtab.exp for ppc64le new 73425813c1b PR28306, segfault in _bfd_mips_elf_reloc_unshuffle The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: bfd/elf32-mips.c | 11 +++++++- bfd/elf64-mips.c | 7 ++++- bfd/elfn32-mips.c | 7 ++++- bfd/elfxx-mips.c | 84 ++++++++++++++++++++++++++++++++++++++++++------------- bfd/elfxx-mips.h | 9 ++++++ 5 files changed, 96 insertions(+), 22 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (566df4736d4 -> eaea9d8dc85)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards 566df4736d4 204: onsuccess: #2435: 1: Success after linux: 3 commits discards 59ff715556a 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards a123055250a 202: onsuccess: #2431: 1: Success after linux: 944 commits discards ed4488400d8 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards 24732e5dbb8 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards bfde681c6eb 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/ [...] discards 3d85899d641 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/ [...] discards 86637352482 197: onsuccess: #2348: 1: Success after linux: 190 commits discards aea90c8abf2 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 4 [...] discards 3148d3658bb 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/ [...] discards 9c0a0bf2e28 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/ [...] discards 8ce1c39227d 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/ [...] discards a1bc21e7ac0 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/ [...] discards 12196dd4e65 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards ffcef0f78d4 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/ [...] discards 57badff52d9 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/ [...] discards 44e5eaacae1 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/ [...] discards 3250cdf97cf 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/ [...] discards b85c074263d 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/ [...] discards 9a2bd22a713 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/ [...] discards 2349183476c 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/ [...] discards 7dfd521236b 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/ [...] discards 1ff1a7ecb71 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/ [...] discards bdad810fb2d 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/ [...] discards aa3dc84c21b 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/ [...] discards 1950db90dac 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/ [...] discards 0f9b652fbe0 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] discards 3edcff888f4 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards 638b6995b23 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] discards 0c1a27a7ad8 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] discards 2df7e2cf192 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 2 [...] discards 0f1ed9a6141 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 2bdea3a95bf 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] discards 405c2a64df0 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/ [...] discards c3260ae7ec9 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/ [...] discards 8e4d6906938 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/ [...] discards 5f601c6dd64 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/ [...] discards b30aa8ed548 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qem [...] discards 8617e314fee 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards 2cdbc21d36f 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 13d0309a67c 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/ [...] discards 6b14d40ec2e 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/ [...] discards a2daf405875 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/ [...] discards 08d1b7e3a4a 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/ [...] discards 8eaf39039fc 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/ [...] discards ff1d6a94e7a 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 19 [...] discards b621cb7fdc4 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/ [...] discards 349bc35940b 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 [...] discards 6b9f25bd7d3 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/ [...] discards ef2ce4809c8 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/ [...] discards 01a418c495b 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 1 [...] discards 107e8a430fa 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 [...] discards 3fcac391c8a 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 [...] discards 0f976413000 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 36a08ab901e 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards f1fa2dafa32 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/ [...] discards c79ff39c41e 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 [...] discards 0dd3fc20f6e 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 1 [...] discards b3662d079b6 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 74cd52fa56d 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/ [...] discards 813bfe4b773 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/ [...] discards 8fa95d6b114 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qe [...] discards 0a863f024fb 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards ee98f8f027f 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 [...] discards 177a3f722ff 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/ [...] discards eee46af5bdf 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 1 [...] discards 4c0c6b055e5 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 [...] discards a1a93df2e2e 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/ [...] discards aa7cf6f7cd3 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qe [...] discards 45bdd10f190 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards f6363716df5 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 1 [...] discards 748b4579165 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/ [...] discards eb345a45b5a 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/ [...] discards 8a3d0627f8f 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 1 [...] discards 7409722f084 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 3 [...] discards 6fc779f133c 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/ [...] discards 11c554e54a5 128: onsuccess: #2163: 1: Success after linux: 23 commits discards f82f0629da2 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 132a3646f17 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-2 [...] discards 3c8b0b89025 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/ [...] discards 4b5dbfb543f 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 21bb5fe8eff 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-2 [...] discards d5503a3720d 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 [...] discards d168f3e264e 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/ [...] discards 1ca57ab60e2 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/ [...] discards a40e8f7eb41 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/ [...] discards 1e9373cd8b7 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/ [...] discards 53bb238384a 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/ [...] discards b4ee1f61c7a 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 [...] discards 6b99cd744fd 115: onsuccess: #2147: 1: Success after binutils/linux/glib [...] discards 564f9e19b04 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/ [...] discards 79c7785761f 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/ [...] discards d54e974fa96 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/ [...] discards aec93a1b929 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/ [...] discards 5b43e50aedd 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/ [...] discards acd7b7a7113 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards c3bc08f88e9 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 [...] discards 421b9d0bff2 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 [...] discards d4a60da9f1c 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/ [...] discards 3a532b49bc3 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-2 [...] discards cf5207785fd 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 [...] new 68a0f4c16a3 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 [...] new b3df08b672b 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-2 [...] new af56e6d03c8 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/ [...] new cbaa487e43e 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 [...] new 882efdfefcc 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 [...] new 4660259b4ff 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 210ec7ef6c6 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/ [...] new 0e1cba9b572 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/ [...] new f6fedfd1e24 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/ [...] new 8b992291bab 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/ [...] new 180cb114090 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/ [...] new fbf87d6e58d 115: onsuccess: #2147: 1: Success after binutils/linux/glib [...] new b5f6d282b9e 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 [...] new 0a083487f0d 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/ [...] new 415412cef50 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/ [...] new ef0222b0400 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/ [...] new cb44e021b95 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/ [...] new 6709324f99e 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/ [...] new 5e00769b37e 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 [...] new 89f8c237a12 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-2 [...] new 43abe47a7a0 124: onsuccess: #2159: 1: Success after linux: 23 commits new b26358bfa5a 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/ [...] new 55401f80870 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-2 [...] new bfcc51bae1e 127: onsuccess: #2162: 1: Success after gcc: 9 commits new fa4e3d2fa62 128: onsuccess: #2163: 1: Success after linux: 23 commits new 08fcd4eedd8 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/ [...] new b18f3845b02 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 3 [...] new 9dda70e82b4 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 1 [...] new 9f6e96bf472 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/ [...] new c4ab765d7e9 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/ [...] new a6e2fca1563 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 1 [...] new 813fc284883 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new f6e69abea56 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qe [...] new 077c4b36d88 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/ [...] new 10ac64cfbde 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 [...] new be28ad88ce4 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 1 [...] new 97f0fa53a4c 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/ [...] new ce340ff5174 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 [...] new 165312935ac 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new ab94f3dd498 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qe [...] new a9798a5b342 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/ [...] new 1b0bbb6651b 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/ [...] new 91c3d6622fe 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 70e46190eed 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 1 [...] new 5d8f8d831c6 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 [...] new 40caf1971f6 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/ [...] new 95e29710333 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 4cb0a6bb38e 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 7b570ea3f52 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 [...] new 5c8346f9011 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 [...] new 19b7a823ec1 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 1 [...] new d6e2d6b1c84 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/ [...] new 1bae9d44776 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/ [...] new 2e0701ad7a2 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 [...] new d6df413e78e 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/ [...] new e1f52b7d8eb 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 19 [...] new d25bbbb7b4c 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/ [...] new 4ee12ae2e5b 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/ [...] new 3ce2784c855 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/ [...] new 17341af2bb5 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/ [...] new 951982f031d 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/ [...] new c51bc82e3a4 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new e2a8c5c4d40 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new 2a7bbd9bf36 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qem [...] new af91b11bf52 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/ [...] new 14e8a0c0a24 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/ [...] new 6479678861d 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/ [...] new c5f77da51b7 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/ [...] new b7a1e8abaec 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] new 0d3df11e02c 173: onsuccess: #2208: 1: Success after gcc: 10 commits new d6a7f33544a 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 2 [...] new dc17541e05c 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] new 44d44117db1 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] new 9e081c5757f 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new f393c0630ef 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] new 980cf91736f 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/ [...] new c439dc21404 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/ [...] new d693ff4a565 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/ [...] new cecb94a0d08 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/ [...] new a0f853b97f2 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/ [...] new 9d156c09fc3 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/ [...] new 2a5dc136275 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/ [...] new 386b5fa970d 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/ [...] new c6fbc907c5f 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/ [...] new fabd1edd71f 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/ [...] new d3b0567d0e5 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/ [...] new 1a8695cdaa4 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/ [...] new 386e2e21b59 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new 0b21cb4a83e 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/ [...] new fdd8deb7dd7 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/ [...] new 8ad44362fe6 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/ [...] new a9b38d58493 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/ [...] new aa5650d9a0e 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 4 [...] new 53d442f39d7 197: onsuccess: #2348: 1: Success after linux: 190 commits new 749a631f270 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/ [...] new 116d098655a 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/ [...] new 9aae37828c2 200: onsuccess: #2427: 1: Success after binutils: 274 commits new 70133483d74 201: onsuccess: #2430: 1: Success after glibc: 26 commits new b3aad981ee6 202: onsuccess: #2431: 1: Success after linux: 944 commits new fc4680c0eec 203: onsuccess: #2433: 1: Success after binutils: 27 commits new 2e69a1ed6b8 204: onsuccess: #2435: 1: Success after linux: 3 commits new eaea9d8dc85 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/ [...] 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 (566df4736d4) \ 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 1796 -> 1804 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 32132 -> 31968 bytes 04-build_abe-stage1/console.log.xz | Bin 72616 -> 73160 bytes 06-build_abe-linux/console.log.xz | Bin 8704 -> 8912 bytes 07-build_abe-glibc/console.log.xz | Bin 245184 -> 244776 bytes 08-build_abe-stage2/console.log.xz | Bin 204152 -> 204604 bytes 09-build_abe-gdb/console.log.xz | Bin 37984 -> 39168 bytes 10-build_abe-qemu/console.log.xz | Bin 32188 -> 30984 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3948 -> 3896 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2692 -> 2864 bytes 13-check_regression/console.log.xz | Bin 5564 -> 41552 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 62 +- 13-check_regression/mail-body.txt | 135 +- 13-check_regression/results.compare | 664 ++- 13-check_regression/results.compare2 | 7493 ++++++++++++++++++++++++++- 13-check_regression/results.regressions | 94 +- 14-update_baseline/console.log | 68 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 137 +- mail/mail-subject.txt | 2 +- manifest.sh | 45 +- results | 94 +- sumfiles/g++.log.xz | Bin 3456844 -> 3409316 bytes sumfiles/g++.sum | 3536 ++++--------- sumfiles/gcc.log.xz | Bin 3042844 -> 3036664 bytes sumfiles/gcc.sum | 8640 +++++++++++++------------------ sumfiles/gfortran.log.xz | Bin 1030800 -> 1031528 bytes sumfiles/gfortran.sum | 310 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213660 -> 213924 bytes sumfiles/libgomp.sum | 27 +- sumfiles/libitm.log.xz | Bin 2700 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 429980 -> 429332 bytes sumfiles/libstdc++.sum | 35 +- 45 files changed, 13739 insertions(+), 7625 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_O1 updated (09fce8ed063 -> 22f4311ff76)

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_O1 in repository toolchain/ci/base-artifacts. from 09fce8ed063 36: onsuccess: #142: 2: Success after binutils/gcc: 7 commits new 22f4311ff76 37: onsuccess: #143: 2: Success after binutils/gcc: 7 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 1720 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2748 bytes 04-build_abe-binutils/console.log.xz | Bin 50760 -> 50960 bytes 05-build_abe-bootstrap_O1/console.log.xz | Bin 459176 -> 462208 bytes 06-check_regression/console.log.xz | Bin 2668 -> 2688 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- manifest.sh | 20 ++++++++++---------- 9 files changed, 13 insertions(+), 13 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch master updated (d71b20fc309 -> 96cb786b754)

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 d71b20fc309 i386: fix assert (__builtin_cpu_supports ("x86-64") >= 0) new 96cb786b754 MAINTAINERS: fix spacing 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: MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm updated (39cb73d897d -> 98f122b103a)

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_binutils/master-arm in repository toolchain/ci/base-artifacts. discards 39cb73d897d 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards f32e6265cf1 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards a3fc9d480d7 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards 95c1ffda1fc 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards 57492550635 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards 17c6ca66155 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards fb38e77368b 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards 627110567d6 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards 1e4c61c1458 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] discards 9840d9c4a91 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards 05713fdf422 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards 88b624349a4 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] discards 0fd8e9e7c2a 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] discards de589f96945 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] discards 4ea6e36ec9e 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] discards 9386db7c97f 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] discards d291358b21e 109: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] discards 22a9e9c8724 108: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] discards 8039438b97f 107: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] discards bf17762d8ea 106: onsuccess: #532: 1: Success after binutils/gcc/linux/g [...] discards e78632fe8b0 105: onsuccess: #531: 1: Success after binutils/gcc/linux/g [...] discards c7148eacd61 104: onsuccess: #530: 1: Success after gcc: 7 commits discards a092dada0c3 103: onsuccess: #529: 1: Success after binutils/gcc/linux/g [...] discards 08be7a27561 102: onsuccess: #527: 1: Success after binutils: 5 commits discards 85693c42cba 101: onsuccess: #524: 1: Success after binutils: 2 commits discards 3234e597225 100: onsuccess: #521: 1: Success after binutils: 10 commits discards 232b901c6d7 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] discards 33f1735fc80 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gl [...] discards 138de6edafb 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] discards 2149f8a4d5a 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] discards 37c381e676b 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gd [...] discards 8d3b4035453 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gd [...] discards 9eab462f4f8 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] discards 8be7b75c7d3 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gl [...] discards f52a18c238d 91: onsuccess: #511: 1: Success after linux: 27 commits discards 67992ffd6c1 90: onsuccess: #510: 1: Success after glibc: 5 commits discards 0ba876dcd33 89: onsuccess: #508: 1: Success after binutils: 12 commits discards 2a4c403869f 88: onsuccess: #506: 1: Success after linux: 34 commits discards fb1657c623c 87: onsuccess: #505: 1: Success after glibc: 7 commits discards 7fa457c7c69 86: onsuccess: #503: 1: Success after binutils: 12 commits discards f4a7728fc53 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] discards af440b0745a 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] discards 3fc02b42360 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gd [...] discards d03845a19ac 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gl [...] discards c41b2155bbf 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] discards 266825d052a 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] discards fb1db6ca1e6 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] discards 725522a2685 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] discards dd82f146170 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gd [...] discards e7c7bec1ea5 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gd [...] discards 2a6b2137ba6 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gd [...] discards cd6d5ba1c34 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gl [...] discards 5eba714f7f3 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gd [...] discards 181d7590418 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gl [...] discards eb56f19fac7 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gd [...] discards cde0a92849f 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gl [...] discards 786cda7e394 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] discards d3a60337a01 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gl [...] discards e9350c35635 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] discards 3d1dda2e027 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gl [...] discards bec71ea2468 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gd [...] discards ed624002378 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] discards f5843a351f1 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gl [...] discards 449c1e3d3e9 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gl [...] discards dfaf0a9136f 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gl [...] discards e495e7e62b1 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gl [...] discards 0a25b0b2bb5 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gl [...] discards ebb50a89759 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gl [...] discards a17ded876ec 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gl [...] discards 33870c33e15 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gd [...] discards 4cefaa1675c 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gl [...] discards 992111855d4 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gl [...] discards 9042c2ac10c 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gl [...] discards 23521a8777e 52: onsuccess: #467: 1: Success after binutils: 9 commits discards 15497209ef0 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 6e12d16f846 50: onsuccess: #461: 1: Success after binutils: 12 commits discards 2cb7b5f0597 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gd [...] discards 588cc9339b0 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gd [...] discards ab7b8222fb1 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gl [...] discards e7758e8a353 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gl [...] discards b6a93c6d220 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gl [...] discards 48150a8046d 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gd [...] discards a45880ae21c 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gd [...] discards bda198be4fa 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gd [...] discards 17b564b870a 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gl [...] discards d8f5372037d 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g [...] discards 6eb5dfa95a4 39: onsuccess: #447: 1: Success after binutils: 5 commits discards c1f33def5e8 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g [...] discards 091fdd218f6 37: onsuccess: #443: 1: Success after binutils: 2 commits discards 7b662fe6fd3 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gl [...] discards 99cad7d5d0b 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gl [...] discards 1ca13142073 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gl [...] discards 4c90d8e19e4 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gd [...] discards f661c8319dc 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gl [...] discards 45c54ddc5e0 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gl [...] discards ad20caac387 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gd [...] discards 3f9c979a4a7 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gl [...] discards 06e6e5d0383 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gl [...] discards 46a2fe3aae6 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gd [...] discards a1c0438060c 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gd [...] discards 675765c889e 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gd [...] new d67024436a1 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gd [...] new 0cacbd9ae26 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gd [...] new cdaccf82792 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gd [...] new d99d85ed15b 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gl [...] new 223fc9da410 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gl [...] new 06d838defba 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gd [...] new d566df7dd27 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gl [...] new 2e88a6536bf 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gl [...] new 457d1d411b5 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gd [...] new e152c6b29cc 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gl [...] new 92035ae5f3a 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gl [...] new 37b7c6c1963 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gl [...] new fc193dfb4d2 37: onsuccess: #443: 1: Success after binutils: 2 commits new b202b6c11f6 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g [...] new 48e4680b547 39: onsuccess: #447: 1: Success after binutils: 5 commits new d04363ae49f 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g [...] new f2bd64c32d8 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gl [...] new 97b597d4a21 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gd [...] new 29cf03d7f11 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gd [...] new 0cd6bdea314 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gd [...] new 7141e5a2e88 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gl [...] new d19639d1eb4 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gl [...] new 45a84c93e23 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gl [...] new a9b72761376 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gd [...] new fcf8c9dfe6f 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gd [...] new b2bc98ef2ce 50: onsuccess: #461: 1: Success after binutils: 12 commits new 435ab45eee0 51: onsuccess: #464: 1: Success after binutils: 6 commits new 439dc535024 52: onsuccess: #467: 1: Success after binutils: 9 commits new c7d301b78eb 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gl [...] new d0e7f1a3d65 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gl [...] new 064da0d0384 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gl [...] new aea784d573e 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gd [...] new 21572c5610a 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gl [...] new 4a018dfbb7d 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gl [...] new cd0aed23ef4 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gl [...] new b7933a1761b 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gl [...] new 6269c8d5e46 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gl [...] new 5af6f24917c 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gl [...] new 61f7fe1c6e5 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gl [...] new cebcea00075 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] new ec2a64f410e 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gd [...] new d9af3a19275 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gl [...] new f42c0b82af9 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] new 1c10a1ca129 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gl [...] new f8205346d0d 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] new 8e125b8b3c9 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gl [...] new 618f4868a82 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gd [...] new 21fc1652918 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gl [...] new 224520fe834 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gd [...] new 239706a5959 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gl [...] new 36702a1b0f2 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gd [...] new f0639ca6de0 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gd [...] new 601a51acd0d 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gd [...] new f25acac8853 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] new 6bb11b4644d 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] new 04bb234d41e 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] new 4a2721a23df 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] new 34e05060055 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gl [...] new a2d4ed5a7a6 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gd [...] new 4ba029e668c 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] new 3d2d7a6ea73 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new d01a68f116e 86: onsuccess: #503: 1: Success after binutils: 12 commits new 992a2340175 87: onsuccess: #505: 1: Success after glibc: 7 commits new df01b449cd3 88: onsuccess: #506: 1: Success after linux: 34 commits new 1e84dcb4180 89: onsuccess: #508: 1: Success after binutils: 12 commits new e79e5b8911c 90: onsuccess: #510: 1: Success after glibc: 5 commits new e07af51234e 91: onsuccess: #511: 1: Success after linux: 27 commits new 3dbda8eb8ce 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gl [...] new 6c745b197aa 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] new e23594a45de 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gd [...] new 3aed91ad4b2 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gd [...] new 93a9ae11769 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] new 0e7c4c1c834 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] new 8978148fc01 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gl [...] new ddfb14f908d 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] new 22b609fd5c4 100: onsuccess: #521: 1: Success after binutils: 10 commits new 1ba5e7668ce 101: onsuccess: #524: 1: Success after binutils: 2 commits new 821fc880d7e 102: onsuccess: #527: 1: Success after binutils: 5 commits new 78ad11e5479 103: onsuccess: #529: 1: Success after binutils/gcc/linux/g [...] new b6a3c555857 104: onsuccess: #530: 1: Success after gcc: 7 commits new b6e90605504 105: onsuccess: #531: 1: Success after binutils/gcc/linux/g [...] new 99157fcadd8 106: onsuccess: #532: 1: Success after binutils/gcc/linux/g [...] new 0c6531544b9 107: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] new b69cdc8edd7 108: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] new 9c6684bd9e6 109: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] new 9306abdba5a 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] new b2fa3b6ced5 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] new 8049db1c6f1 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new 64a33d99568 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new a6943348d51 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new 2d7f455f0b2 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new 01be9ad97f5 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new 2ed260084a8 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new 4e04589f6e6 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new f980134a5a3 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new 18e08a90afe 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new 54900a77e0c 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new 0d350625e0e 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new b27630eac77 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new 0a8cab2606b 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 8fb1ecaec80 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 98f122b103a 126: onsuccess: #553: 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 (39cb73d897d) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...] 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 1728 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 52312 -> 52352 bytes 04-build_abe-gcc/console.log.xz | Bin 234684 -> 233812 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8576 -> 8844 bytes 07-build_abe-glibc/console.log.xz | Bin 235168 -> 235208 bytes 08-build_abe-gdb/console.log.xz | Bin 51792 -> 52064 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3816 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2116 -> 2576 bytes 11-check_regression/console.log.xz | Bin 6232 -> 6112 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 34 +-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++-- sumfiles/binutils.log.xz | Bin 62832 -> 62736 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 98240 -> 98136 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 131644 -> 131548 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 30 files changed, 392 insertions(+), 392 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-allnoconfig updated (12e72ea6651 -> fd365074c6e)

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-allnoconfig in repository toolchain/ci/base-artifacts. from 12e72ea6651 26: onsuccess: #476: boot: Success after binutils/gcc/qemu: [...] new fd365074c6e 27: onsuccess: #477: boot: Success after binutils/gcc/linux [...] 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 1800 -> 2032 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 32340 -> 31760 bytes 04-build_abe-stage1/console.log.xz | Bin 73524 -> 73256 bytes 05-build_abe-qemu/console.log.xz | Bin 32780 -> 30860 bytes 06-build_linux/console.log.xz | Bin 5620 -> 5612 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 3996 -> 4096 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022