Tcwg-commits January 2023

tcwg-commits@lists.linaro.org

5 participants
4127 discussions

[gcc] branch master updated (fec9fc1a17e -> aa966d54ee4)

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 fec9fc1a17e Fortran: frontend passes do_subscript leaks gmp memory [PR97345] new aa966d54ee4 MAINTAINERS: Add myself as Rust front-end maintainer 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 | 1 + 1 file changed, 1 insertion(+) -- 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_native_fast_check_gdb/release-aarch64 updated (04a8ca9c97 -> b75fcb8c65)

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/release-aarch64 in repository toolchain/ci/base-artifacts. from 04a8ca9c97 14: onsuccess: #22: 1: Success after gcc/linux: 187 commits new b75fcb8c65 15: onsuccess: #23: 1: Success after gcc/glibc: 8 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 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 37976 -> 38448 bytes 04-build_abe-gcc/console.log.xz | Bin 206352 -> 207648 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8760 -> 8672 bytes 07-build_abe-glibc/console.log.xz | Bin 239884 -> 238784 bytes 08-build_abe-gdb/console.log.xz | Bin 36960 -> 37184 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3836 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2492 -> 2484 bytes 11-check_regression/console.log.xz | Bin 5348 -> 5220 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 +++--- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 22 +++++++++++----------- sumfiles/gdb.log.xz | Bin 11980 -> 11984 bytes sumfiles/gdb.sum | 34 +++++++++++++++++----------------- 22 files changed, 39 insertions(+), 39 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[gcc] branch master updated (e9a39ad7936 -> fec9fc1a17e)

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 e9a39ad7936 Adding missing dependencies to gcc/m2/Make-lang.in new fec9fc1a17e Fortran: frontend passes do_subscript leaks gmp memory [PR97345] 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/fortran/frontend-passes.cc | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) -- 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-release-aarch64-stable-allyesconfig updated (9b2c786260 -> 24b7ba5070)

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-stable-allyesconfig in repository toolchain/ci/base-artifacts. from 9b2c786260 35: onsuccess: #262: all: Success after binutils/llvm/linux/ [...] new 24b7ba5070 36: onsuccess: #263: all: Success after binutils/llvm/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 1760 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 30516 -> 30708 bytes 04-build_kernel_llvm/console.log.xz | Bin 63924 -> 64936 bytes 05-build_abe-qemu/console.log.xz | Bin 31772 -> 31804 bytes 06-build_linux/console.log.xz | Bin 3376 -> 3376 bytes 07-boot_linux/console.log.xz | Bin 576 -> 576 bytes 08-check_regression/console.log.xz | Bin 3788 -> 3776 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_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.

1 year, 10 months

[binutils-gdb] branch master updated (7987c4636ab -> 38190b2f010)

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 7987c4636ab Convert say_where to method on code_breakpoint new 38190b2f010 gdb/dwarf2: Fix 'rw_pieced_value' for values casted to diff [...] 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: gdb/dwarf2/expr.c | 3 -- gdb/testsuite/gdb.dwarf2/shortpiece.exp | 52 ++++++++++++++++++++++++++++++++- 2 files changed, 51 insertions(+), 4 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_gnu_native_check_binutils/master-arm updated (8f07389b9c -> 28d8449f31)

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 8f07389b9c 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] discards 9596cad0de 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards ddc90b2e43 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] discards 80c8fe4c31 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] discards b1f055724a 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards c6ebc008c6 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards e7f2d99242 154: onsuccess: #583: 1: Success after linux: 10 commits discards d782fb61bc 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 1e660b1f15 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 31c7a2d33f 151: onsuccess: #579: 1: Success after binutils: 21 commits discards ff87e75227 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] discards 2576542708 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards 57b93ed84d 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] discards 8375e939eb 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards 8d67386c58 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits discards 2c2e450905 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits discards be9cf9be5c 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits discards 45f3f5e0a0 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] discards 3543c061eb 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits discards 2ff8b7c765 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] discards 93de6c19c7 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards d2cded5c2f 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards d734755778 138: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 7d1bd9d5ad 137: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards 1d2d586fcc 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/gd [...] discards a4bf193f85 135: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards 17384c1c97 134: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards f15fbdc0dc 133: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards 608039e917 132: onsuccess: #559: 1: Success after binutils/gcc/linux/gd [...] discards b4ae3a6342 131: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] discards 8e000345f7 130: onsuccess: #557: 1: Success after binutils/gcc/linux/gl [...] discards f6de4e6074 129: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] discards f954ead5fd 128: onsuccess: #555: 1: Success after binutils/gcc/linux/gd [...] discards ad47e70ae2 127: onsuccess: #554: 1: Success after binutils/gcc/linux/gl [...] discards dbddc9784f 126: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] discards 531f41e063 125: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 80f4b34e6c 124: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 4a1516c66e 123: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] discards de8fe5b79e 122: onsuccess: #549: 1: Success after binutils/gcc/linux/gd [...] discards af8ba22646 121: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] discards f83bbcff0f 120: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] discards a783ea4add 119: onsuccess: #546: 1: Success after binutils/gcc/linux/gd [...] discards d65702ab52 118: onsuccess: #545: 1: Success after binutils/gcc/linux/gd [...] discards 20eaa8094b 117: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] discards d4bf81ce8b 116: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards 5367f180d1 115: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards ab85fe81bb 114: onsuccess: #541: 1: Success after binutils/gcc/linux/gd [...] discards cdfb32ce01 113: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards f1b3e56399 112: onsuccess: #538: 1: Success after binutils/gcc/linux/gd [...] discards f0d9316da3 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 commits discards d461f2e44e 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards 3dcde627d6 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] discards 5b0905cf00 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] discards 3ea1a7c807 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards eb58445a80 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] discards 6b767f5bf1 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] discards 0af99f4d63 104: onsuccess: #530: 1: Success after gcc: 7 commits discards a0da2a7a7b 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards 82ea750197 102: onsuccess: #527: 1: Success after binutils: 5 commits discards 825bd5c796 101: onsuccess: #524: 1: Success after binutils: 2 commits discards 89e1c48bc1 100: onsuccess: #521: 1: Success after binutils: 10 commits discards 58735665b4 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 88ce09e535 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] discards 6df9536002 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 5dd0a3653a 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 1aaa7d6e5c 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] discards 9c8d16acaa 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] discards 7b29719cf2 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards cc973999a6 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] discards 2479d70391 91: onsuccess: #511: 1: Success after linux: 27 commits discards c2e3674665 90: onsuccess: #510: 1: Success after glibc: 5 commits discards fd2f8b2d30 89: onsuccess: #508: 1: Success after binutils: 12 commits discards 408f4cae8d 88: onsuccess: #506: 1: Success after linux: 34 commits discards 13a37f61bc 87: onsuccess: #505: 1: Success after glibc: 7 commits discards 9a14336a59 86: onsuccess: #503: 1: Success after binutils: 12 commits discards 3efed5a6dd 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 8787a6efdd 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards 0c50e731b8 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] discards d6004a0d38 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] discards cc9898ccae 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 097e79d4f9 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards afa4cffa18 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 148f8a2107 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards b302b8d50a 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] discards cd59a84e60 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] discards 80957e8ab8 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards 6f62e50ff9 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] discards 236d3a0879 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] discards 9f90f864da 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] discards e6117dab5c 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] discards ba7c915856 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] discards 19a414bca5 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards c930690ddb 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] discards 393b2af15d 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards 6b625feea2 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] discards c813513ea9 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] discards 69925bb667 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 20c4eaecb9 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] discards 50677353b9 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] discards 7c62371c8f 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] discards 29f676c9a8 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] new 102e05ad30 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] new 4ddde908da 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] new d85b1e9192 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] new 2807ff25fe 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] new 653ea5c918 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new e8ff31d162 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] new 88c4fed63f 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] new c06e3b6657 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 6a21496f28 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] new bd49376965 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 1371ec41e5 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] new c0e15ca510 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] new 9a86e9526f 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] new a8e4f9805c 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] new 8c94e83e13 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] new 1f2b9bedee 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 4352160abe 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] new bdf7e791d4 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] new 96c5a6668f 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 783ec0f04b 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new bbc60ab3e6 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 4d6b86c98c 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new e919c5ecda 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] new 6f0d9adf88 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] new ee44f45632 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new d97c189f7a 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new ea8c994c94 86: onsuccess: #503: 1: Success after binutils: 12 commits new 88565ece13 87: onsuccess: #505: 1: Success after glibc: 7 commits new 242633b4f3 88: onsuccess: #506: 1: Success after linux: 34 commits new 3e6888b95e 89: onsuccess: #508: 1: Success after binutils: 12 commits new 6de1ac01d4 90: onsuccess: #510: 1: Success after glibc: 5 commits new ca5d3e2c41 91: onsuccess: #511: 1: Success after linux: 27 commits new 951f28add1 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] new 68562b1f12 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new 6c7d6b5631 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] new 2a74d566a8 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] new d05a9282f2 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new dea919fa3a 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new 22a4ba4a5c 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] new dbac02205f 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 5510f7c64b 100: onsuccess: #521: 1: Success after binutils: 10 commits new 030e574722 101: onsuccess: #524: 1: Success after binutils: 2 commits new 9a2cebc969 102: onsuccess: #527: 1: Success after binutils: 5 commits new bbea75c5f1 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new 1eb2ce172c 104: onsuccess: #530: 1: Success after gcc: 7 commits new a4c9bc7350 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] new 3533104372 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] new a78ec7f7ef 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new b28dbcf251 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] new d9179ee2d8 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] new 7729a71c1c 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new 197342e3a6 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 commits new a70f4e08aa 112: onsuccess: #538: 1: Success after binutils/gcc/linux/gd [...] new ffeab5e0a4 113: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new 95f04b919a 114: onsuccess: #541: 1: Success after binutils/gcc/linux/gd [...] new 834e782d99 115: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new 0a69e7eaf5 116: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new bc791285e8 117: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] new 79517eb9df 118: onsuccess: #545: 1: Success after binutils/gcc/linux/gd [...] new 12d5471b8a 119: onsuccess: #546: 1: Success after binutils/gcc/linux/gd [...] new ff2bb68619 120: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] new 3a1c576c33 121: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] new 3ae348d5f6 122: onsuccess: #549: 1: Success after binutils/gcc/linux/gd [...] new fa25a4f7db 123: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] new 1a350ff7ac 124: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 58d44b911b 125: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new bc79879a5f 126: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] new bcffeb7496 127: onsuccess: #554: 1: Success after binutils/gcc/linux/gl [...] new dbc2452b5a 128: onsuccess: #555: 1: Success after binutils/gcc/linux/gd [...] new 57fcbb3fe5 129: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] new d6feacae43 130: onsuccess: #557: 1: Success after binutils/gcc/linux/gl [...] new 4f5b710bf0 131: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] new 6bf2df3c28 132: onsuccess: #559: 1: Success after binutils/gcc/linux/gd [...] new 76a1b88533 133: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new daa0153bf6 134: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new ed8ec059b7 135: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new 162c48eb92 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/gd [...] new 6651bd37bf 137: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new df8eb0f9f4 138: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new bb592f9576 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new c9f9f22326 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new d240d9cb84 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] new 74962fad6c 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits new 8b0580720b 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new dc57fdc7dc 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits new 6682d117f3 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits new 71aff91540 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits new 8888f141b6 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new 0fe74e9460 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] new da56a2d9a3 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new 2c0764e8d0 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] new 987288c662 151: onsuccess: #579: 1: Success after binutils: 21 commits new dfd7994d86 152: onsuccess: #580: 1: Success after gcc: 6 commits new a57e7e0312 153: onsuccess: #582: 1: Success after glibc: 9 commits new 0d8e41538d 154: onsuccess: #583: 1: Success after linux: 10 commits new e4110b54a6 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new 74891d11cc 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new 8e2be270e1 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] new 70a799abb9 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] new 27bb13003a 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new e0c6ae0418 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] new 28d8449f31 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] 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 (8f07389b9c) \ 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 1716 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 53104 -> 54028 bytes 04-build_abe-gcc/console.log.xz | Bin 239540 -> 240380 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8848 -> 8652 bytes 07-build_abe-glibc/console.log.xz | Bin 238020 -> 237472 bytes 08-build_abe-gdb/console.log.xz | Bin 51292 -> 52512 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3828 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2092 -> 2324 bytes 11-check_regression/console.log.xz | Bin 5668 -> 6300 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 42 +++- 12-update_baseline/console.log | 64 ++--- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/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 62644 -> 62352 bytes sumfiles/binutils.sum | 62 ++--- sumfiles/gas.log.xz | Bin 100424 -> 100412 bytes sumfiles/gas.sum | 272 +++++++++++----------- sumfiles/ld.log.xz | Bin 132236 -> 132000 bytes sumfiles/ld.sum | 360 ++++++++++++++--------------- 30 files changed, 443 insertions(+), 421 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_gcc_check/release-aarch64 updated (fcf4a72f9c -> 6222efd68c)

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/release-aarch64 in repository toolchain/ci/base-artifacts. from fcf4a72f9c 48: onsuccess: #251: 1: Success after gcc: 8 commits new 6222efd68c 49: onsuccess: #252: 1: 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 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 38168 -> 38388 bytes 04-build_abe-gcc/console.log.xz | Bin 207436 -> 206052 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3864 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2336 -> 2932 bytes 07-check_regression/console.log.xz | Bin 5360 -> 5268 bytes 07-check_regression/extra-bisect-params | 2 +- 07-check_regression/fails.sum | 5 +- 07-check_regression/mail-body.txt | 71 +- 07-check_regression/results.compare | 32 +- 07-check_regression/results.compare2 | 62 +- 07-check_regression/results.regressions | 32 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 73 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 32 +- sumfiles/g++.log.xz | Bin 3513596 -> 3526708 bytes sumfiles/g++.sum | 150 +- sumfiles/gcc.log.xz | Bin 3017672 -> 3055248 bytes sumfiles/gcc.sum | 4679 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1038220 -> 1030324 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2180 -> 2184 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202704 -> 202444 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2540 -> 2540 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 433232 -> 426368 bytes sumfiles/libstdc++.sum | 12 +- 35 files changed, 2596 insertions(+), 2650 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[binutils-gdb] branch master updated (8ec0b0b5df0 -> 7987c4636ab)

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 8ec0b0b5df0 gdb/doc: use @value{GDBP} in some spots new 7987c4636ab Convert say_where to method on code_breakpoint 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: gdb/breakpoint.c | 49 ++++++++++++++++++++++++------------------------- gdb/breakpoint.h | 4 ++++ 2 files changed, 28 insertions(+), 25 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[linux] branch master updated (40c18f363a08 -> 7dd4b804e080)

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 40c18f363a08 Merge tag '6.2-rc3-ksmbd-server-fixes' of git://git.samba. [...] new 5b24ac2dfd3e kcsan: test: don't put the expect array on the stack new 4414c1f5c7a3 xtensa: drop unused members of struct thread_struct new 092f6239108d Merge tag 'xtensa-20230110' of https://github.com/jcmvbkbc [...] new 0b3a551fa58b nfsd: fix handling of cached open files in nfsd4_open codepath new 7827c81f0248 Revert "SUNRPC: Use RMW bitops in single-threaded hot paths" new 5304930dbae8 NFSD: Use set_bit(RQ_DROPME) new 7dd4b804e080 Merge tag 'nfsd-6.2-3' of git://git.kernel.org/pub/scm/lin [...] The 7 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: arch/xtensa/include/asm/processor.h | 9 ------ arch/xtensa/kernel/traps.c | 2 -- arch/xtensa/mm/fault.c | 4 --- fs/nfsd/filecache.c | 40 +++++++++++++----------- fs/nfsd/filecache.h | 5 +-- fs/nfsd/nfs4proc.c | 7 ++--- fs/nfsd/nfs4state.c | 16 +++------- fs/nfsd/nfs4xdr.c | 2 +- fs/nfsd/nfsproc.c | 4 +-- fs/nfsd/trace.h | 52 ++++++++------------------------ kernel/kcsan/kcsan_test.c | 7 ++++- net/sunrpc/auth_gss/svcauth_gss.c | 4 +-- net/sunrpc/svc.c | 6 ++-- net/sunrpc/svc_xprt.c | 2 +- net/sunrpc/svcsock.c | 8 ++--- net/sunrpc/xprtrdma/svc_rdma_transport.c | 2 +- 16 files changed, 65 insertions(+), 105 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_gnu_native_check_binutils/master-aarch64 updated (c39f5dc634 -> d74b5e6e63)

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-aarch64 in repository toolchain/ci/base-artifacts. discards c39f5dc634 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] discards 17c588721e 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] discards 2e21a24b6d 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] discards e0b7c48ce8 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] discards 4a409281ad 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] discards c9558c83cd 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] discards 4c4291db27 149: onsuccess: #684: 1: Success after linux: 10 commits discards 4e12585665 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 6a8387a36b 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 281caed9a2 146: onsuccess: #680: 1: Success after binutils: 20 commits discards f2c19f75d5 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] discards 575c90d266 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] discards 7269af9f19 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] discards 96683d4412 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards 7504385671 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits discards 5d1c3d5f79 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits discards cf8d819627 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits discards cd9c7f8c4e 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards 4207c85784 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits discards cbcc6285d3 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards 37e2913060 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards 769b22e35e 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] discards d2f4d7aa36 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] discards c42191036b 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards 556d4572eb 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] discards e5986fbd49 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards ecd51a67aa 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards f63994f3bb 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] discards 9b0781850b 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards 6b82b87205 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 658eefe97a 125: onsuccess: #658: 1: Success after linux: 3224 commits discards c8397db8c9 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 23f4d2641b 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 22dda679b3 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards fac2e28381 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards e6ed90de39 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards d2a60ee71f 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards cad07dff03 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards a82c903ea4 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] discards 7a8b6f1b75 116: onsuccess: #647: 1: Success after linux: 3 commits discards 736caa68ff 115: onsuccess: #645: 1: Success after binutils: 27 commits discards 61bd80cbd0 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards 4118956f8b 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards ece06203eb 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards e5b8734007 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] discards bfad21b033 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] discards 4fa6348e25 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] discards 7f55c6e384 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] discards 15b1697bd4 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] discards 7f613911bd 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards ec598825c6 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards 19eb95d9e7 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards 144b39a3ea 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits discards 490da97d0e 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] discards 9cc685e50a 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] discards 6d190024b5 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] discards d3c7a6324e 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] discards 6d270d8b17 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] discards d32eeb9734 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards 88e725cf47 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] discards 5a16da07fb 95: onsuccess: #619: 1: Success after binutils: 5 commits discards cbc5764478 94: onsuccess: #616: 1: Success after binutils: 2 commits discards 2a7abdcf57 93: onsuccess: #613: 1: Success after binutils: 19 commits discards 60ae59577c 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] discards 83c53f8327 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] discards cdb09c08f7 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] discards 005f24cfe3 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] discards d1221ebc9f 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] discards 6437d24036 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] discards 0f64e29a33 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] discards d203705bac 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] discards 56627645d9 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] discards 3fb897fcf3 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] discards f687312d42 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] discards cad1e4fe4b 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] discards 919837a3f3 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] discards 9e6f959134 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] discards 26f9ef4c4c 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] discards a2274eafa1 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] discards 9f634d64dd 76: onsuccess: #592: 1: Success after linux: 63 commits discards 167af32b8d 75: onsuccess: #591: 1: Success after gcc: 25 commits discards e05d47e707 74: onsuccess: #590: 1: Success after binutils: 16 commits discards b4108414c0 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] discards 581d2c7885 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] discards e32ae63a2b 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] discards aaa7efcd73 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] discards 44a856a773 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] discards 2c8bdb1798 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] discards bf5703eeef 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] discards 18d999560a 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 4ff2412ac8 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] discards 35716db2be 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] discards 13ef610629 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 1bf3a4c4f1 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] discards 7c8b0d4e19 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] discards ee273c6bd5 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] discards f946f3e678 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] discards 53cfec7c64 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] discards 4205618296 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] discards b0cb6ea8c1 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] discards b476de9e90 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] new d91ee621cb 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] new aec378d70e 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] new 66f4f55e3f 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] new e424017c41 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] new 277dfe69a7 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] new 292db74bf4 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] new 4300486774 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] new 5a6c707b19 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] new aa5cd3072b 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 008cb9fe62 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] new 235ec99cfc 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] new 82e757ead0 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 2f55a82af0 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] new 2a81ba162d 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] new 205bc48a16 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] new 3ad48d7c4a 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] new c188feda9e 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] new e9063acdd5 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] new fc468a78bb 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] new 1c2cb179da 74: onsuccess: #590: 1: Success after binutils: 16 commits new 008f711f35 75: onsuccess: #591: 1: Success after gcc: 25 commits new 18859fa3c0 76: onsuccess: #592: 1: Success after linux: 63 commits new 57a468390d 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] new af25d2083f 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] new b16dc64aca 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] new d3bc159937 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] new 5195b3fbe0 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] new dcf1ac1929 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] new f9f118ae52 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] new ab44b42281 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] new 3f4121870f 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] new fd2260febd 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] new df364f228f 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] new 2aebf64887 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] new d7a28b3c72 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] new 17009f1c1e 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] new df1a49caa0 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] new 1c615131fc 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] new 1e1900328a 93: onsuccess: #613: 1: Success after binutils: 19 commits new 2fc97c6c5a 94: onsuccess: #616: 1: Success after binutils: 2 commits new 40ea8eefd2 95: onsuccess: #619: 1: Success after binutils: 5 commits new 778798abb1 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] new a608d31b1d 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 57c6d934b5 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] new 900fe26978 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] new 6926aeb4d8 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] new 8491b208bf 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] new 7bff315e4e 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] new f14eeec682 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits new 7446e89d2d 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new 6c64e788ee 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new fcec321a7b 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new ee7ecb3e5c 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] new ca3a25ffc9 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] new ca97816dcb 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] new fd993c781f 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] new 49138c14b9 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] new a25a52c8c3 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 543d111bc9 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new f50fbccd89 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new a493a26a3a 115: onsuccess: #645: 1: Success after binutils: 27 commits new 53597a7bc6 116: onsuccess: #647: 1: Success after linux: 3 commits new ac340d2c7a 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] new 3f87c527b0 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new 1eea1bc3f3 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new d4da0dd035 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 8b923e4e14 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new 8db2bc74c4 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new f65c4a523d 123: onsuccess: #655: 1: Success after binutils: 22 commits new 1f81efae70 124: onsuccess: #657: 1: Success after glibc: 2 commits new a744b10586 125: onsuccess: #658: 1: Success after linux: 3224 commits new 52981ca459 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 032c05fcb0 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new cc7d3cc1bc 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] new 9bc33f137b 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new 7fd5ade253 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new bc4c4e6338 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new b1c22e2431 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new 39d5e124de 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] new 0d5f32bca1 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] new 9bbb261e90 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new 39d0b809cf 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new b007df404a 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits new c1a027d2ef 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new 58f8fae6b5 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits new 7c2b47b484 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits new 2360b1e741 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits new 1034c3ef42 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 0873f90c47 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] new 050d7e70f7 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] new 08011ada00 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] new 9ff6f2a156 146: onsuccess: #680: 1: Success after binutils: 20 commits new 54dd91a6fd 147: onsuccess: #681: 1: Success after gcc: 6 commits new e847ca6bae 148: onsuccess: #683: 1: Success after glibc: 9 commits new 314b649875 149: onsuccess: #684: 1: Success after linux: 10 commits new e9a9a12987 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] new b8c1634088 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] new 2d7f1ab7b0 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] new 4df9ac62b5 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] new 8868e4168c 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] new 0b702ab7f4 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] new d74b5e6e63 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] 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 (c39f5dc634) \ 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 1792 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 39688 -> 39708 bytes 04-build_abe-gcc/console.log.xz | Bin 215540 -> 214628 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8752 -> 8644 bytes 07-build_abe-glibc/console.log.xz | Bin 244692 -> 245100 bytes 08-build_abe-gdb/console.log.xz | Bin 39784 -> 39740 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3848 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2068 -> 2256 bytes 11-check_regression/console.log.xz | Bin 5584 -> 6268 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 64 +++--- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/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 63136 -> 63060 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 83872 -> 83884 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 122196 -> 122212 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 30 files changed, 406 insertions(+), 406 deletions(-) -- 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