Tcwg-commits March 2023

tcwg-commits@lists.linaro.org

5 participants
3834 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-allyesconfig updated (2318d3072a3 -> b2ef380f03c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-allyesconfig in repository toolchain/ci/base-artifacts. from 2318d3072a3 72: onsuccess: #10: 21715: Success after linux: 2653 commits new b2ef380f03c 73: onsuccess: #11: 21727: Success after binutils/llvm/linu [...] 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 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 3524 bytes 03-build_abe-binutils/console.log.xz | Bin 30836 -> 31036 bytes 04-build_kernel_llvm/console.log.xz | Bin 65240 -> 68064 bytes 05-build_abe-qemu/console.log.xz | Bin 31916 -> 31628 bytes 06-build_linux/console.log.xz | Bin 3416 -> 3644 bytes 08-check_regression/console.log.xz | Bin 3140 -> 4424 bytes 08-check_regression/mail-body.txt | 22 +++++++++++----------- 08-check_regression/results.regressions | 10 ---------- 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 | 24 ++++++++++++------------ mail/mail-subject.txt | 2 +- manifest.sh | 31 +++++++++++++++++-------------- results | 12 +----------- 19 files changed, 48 insertions(+), 65 deletions(-) delete mode 100644 08-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-coremark/gnu_eabi-arm_eabi-master-O3_LTO updated (bb5cc777f24 -> 183a40adc48)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_speed-coremark/gnu_eabi-arm_eabi-master-O3_LTO in repository toolchain/ci/base-artifacts. from bb5cc777f24 62: onsuccess: #6: 1: [TCWG CI] No change after binutils/gc [...] new 183a40adc48 63: onsuccess: #7: 1: [TCWG CI] No change after binutils/gc [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1784 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 3492 bytes 03-build_abe-binutils/console.log.xz | Bin 30932 -> 30680 bytes 04-build_abe-stage1/console.log.xz | Bin 88852 -> 88040 bytes 06-build_abe-newlib/console.log.xz | Bin 14408 -> 14564 bytes 07-build_abe-stage2/console.log.xz | Bin 163608 -> 163168 bytes 08-benchmark/benchmark-build.log | 106 +++--- 08-benchmark/benchmark.log | 104 +++--- 08-benchmark/console.log.xz | Bin 4032 -> 4028 bytes 09-check_regression/console.log.xz | Bin 5964 -> 7100 bytes .../output-bmk-results/error_code-1 | 0 09-check_regression/results-vs-first.log | 2 +- 09-check_regression/results-vs-prev.log | 4 +- 10-update_baseline/console.log | 9 - dashboard/dashboard-generate.sh | 2 +- .../squad-vs-first/Coremark/results-metadata.json | 12 +- .../squad-vs-first/Mean/results-metadata.json | 12 +- .../squad-vs-first/coremark/results-metadata.json | 12 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 406 ++++++++++----------- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/newlib_rev | 2 +- mail/jira-body.txt | 28 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +- results_id | 2 +- 27 files changed, 380 insertions(+), 385 deletions(-) delete mode 100644 09-check_regression/output-bmk-results/error_code-1 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[linux] branch master updated (6015b1aca1a2 -> 9c1bec9c0b08)

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 6015b1aca1a2 sched_getaffinity: don't assume 'cpumask_size()' is fully [...] new 2da789cda462 selftests: amd-pstate: fix TEST_FILES new 624c60f326c6 selftests: fix LLVM build for i386 and x86_64 new 9c1bec9c0b08 Merge tag 'linux-kselftest-fixes-6.3-rc3' of git://git.ker [...] The 3 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: tools/testing/selftests/amd-pstate/Makefile | 13 +++++++++---- tools/testing/selftests/lib.mk | 2 ++ 2 files changed, 11 insertions(+), 4 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch master updated (901edd99b44 -> 57052c6ed59)

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 901edd99b44 Fortran: rank checking with explicit-/assumed-size arrays a [...] new 57052c6ed59 i386: Fix blend vector permutation for 8-byte modes 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/i386/i386-expand.cc | 19 +++++++++++-------- gcc/config/i386/mmx.md | 19 +++++++++++++++++++ gcc/testsuite/gcc.target/i386/merge-1.c | 2 +- gcc/testsuite/gcc.target/i386/sse-movss-4.c | 6 +++--- gcc/testsuite/gcc.target/i386/sse2-mmx-21.c | 2 +- gcc/testsuite/gcc.target/i386/sse2-mmx-movss-1.c | 13 +++++++++++++ gcc/testsuite/gcc.target/i386/sse2-movsd-3.c | 10 +++++----- 7 files changed, 53 insertions(+), 18 deletions(-) create mode 100644 gcc/testsuite/gcc.target/i386/sse2-mmx-movss-1.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch master updated (be20dcc359b -> 901edd99b44)

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 be20dcc359b c++: ICE with constexpr lambda [PR107280] new 901edd99b44 Fortran: rank checking with explicit-/assumed-size arrays a [...] 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/interface.cc | 27 ++++++++++---- gcc/testsuite/gfortran.dg/class_dummy_10.f90 | 56 ++++++++++++++++++++++++++++ 2 files changed, 76 insertions(+), 7 deletions(-) create mode 100644 gcc/testsuite/gfortran.dg/class_dummy_10.f90 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled_lto updated (2f5e3fae7e7 -> 059e892fd16)

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/master-aarch64-bootstrap_profiled_lto in repository toolchain/ci/base-artifacts. discards 2f5e3fae7e7 205: onsuccess: #20: 2: Success after binutils/gcc: 59 commits discards 10bef23f305 204: onsuccess: #19: 2: Success after binutils/gcc: 39 commits discards baaee57dbfa 203: onsuccess: #18: 2: Success after binutils/gcc: 9 commits discards e6a02bd1753 202: onsuccess: #17: 2: Success after binutils/gcc: 25 commits discards 8a14a70eaa7 201: onsuccess: #16: 2: Success after binutils/gcc: 55 commits discards ea4922ab8bd 200: onsuccess: #15: 2: Success after binutils/gcc: 26 commits discards ba991f2fd9c 199: onsuccess: #14: 2: Success after binutils/gcc: 31 commits discards 79b517b974d 198: onsuccess: #13: 2: Success after binutils/gcc: 58 commits discards f61ba1a2218 197: onsuccess: #12: 2: Success after binutils/gcc: 29 commits discards f43c8082684 196: onsuccess: #11: 2: Success after binutils/gcc: 16 commits discards 8327d171eef 195: onsuccess: #10: 2: Success after binutils/gcc: 28 commits discards 6b5f28117e6 194: onsuccess: #9: 2: Success after binutils/gcc: 48 commits discards 818e0fbd526 193: onsuccess: #8: 2: Success after binutils/gcc: 37 commits discards 9d685c21e11 192: onsuccess: #7: 2: Success after binutils/gcc: 22 commits discards 9b5f6e0c349 191: onsuccess: #6: 2: Success after binutils/gcc: 65 commits discards fa90c8ec5b7 190: onsuccess: #5: 2: Success after binutils/gcc: 23 commits discards 49247d22fdb 189: onsuccess: #4: 2: Success after binutils/gcc: 8 commits discards 2bd18264bc1 188: onsuccess: #3: 2: Success after binutils/gcc: 5 commits discards 56e8f38915d 187: onsuccess: #2: 2: Success after binutils/gcc: 22 commits discards 942dc34f325 186: onsuccess: #1: 2: Success after binutils/gcc: 54 commits discards f59eaf90749 185: onsuccess: #605: 2: Success after binutils/gcc: 38 commits discards f9d5c8b4651 184: onsuccess: #604: 2: Success after binutils/gcc: 138 commits discards 5492a038fe0 183: onsuccess: #603: 2: Success after binutils/gcc: 33 commits discards 257ba00049a 182: onsuccess: #602: 2: Success after binutils/gcc: 32 commits discards fa6ef33dcd6 181: onsuccess: #601: 2: Success after binutils/gcc: 13 commits discards 117866f61eb 180: onsuccess: #600: 2: Success after binutils/gcc: 32 commits discards 9dd6d6eb114 179: onsuccess: #599: 2: Success after binutils/gcc: 27 commits discards 08d90553db8 178: onsuccess: #598: 2: Success after binutils/gcc: 54 commits discards bb047f20a7e 177: onsuccess: #597: 2: Success after binutils/gcc: 86 commits discards 8cd4a68fffc 176: onsuccess: #596: 2: Success after binutils/gcc: 84 commits discards b516ed0780d 175: onsuccess: #595: 2: Success after binutils/gcc: 30 commits discards 18b2b325ccf 174: onsuccess: #594: 2: Success after binutils/gcc: 147 commits discards 018bc4e8e37 173: onsuccess: #593: 2: Success after binutils/gcc: 74 commits discards 9b7e112f7f6 172: onsuccess: #592: 2: Success after binutils/gcc: 57 commits discards a1b5f06457b 171: onsuccess: #590: 2: Success after binutils/gcc: 21 commits discards d45a78976d6 170: onsuccess: #589: 2: Success after binutils/gcc: 28 commits discards d340de95018 169: onsuccess: #588: 2: Success after binutils/gcc: 7 commits discards 11957d8db56 168: onsuccess: #587: 2: Success after binutils/gcc: 2 commits discards 1e5d0d30a79 167: onsuccess: #586: 2: Success after binutils/gcc: 16 commits discards 5343544c819 166: onsuccess: #585: 2: Success after binutils/gcc: 59 commits discards 6c519ed0945 165: onsuccess: #584: 2: Success after binutils/gcc: 45 commits discards 4573f1fc6a8 164: onsuccess: #583: 2: Success after binutils/gcc: 110 commits discards 84190878f04 163: onsuccess: #582: 2: Success after binutils/gcc: 55 commits discards 67ed414de18 162: onsuccess: #581: 2: Success after binutils/gcc: 6 commits discards 95e00a2190d 161: onsuccess: #580: 2: Success after binutils/gcc: 10 commits discards ec03cbc321a 160: onsuccess: #579: 2: Success after binutils/gcc: 17 commits discards a872b29f18f 159: onsuccess: #578: 2: Success after binutils/gcc: 130 commits discards b85bb0bee3a 158: onsuccess: #577: 2: Success after binutils/gcc: 27 commits discards 8b61c3de11c 157: onsuccess: #576: 2: Success after binutils/gcc: 80 commits discards ffb6120a209 156: onsuccess: #575: 2: Success after binutils/gcc: 27 commits discards f0daa0b08c0 155: onsuccess: #574: 2: Success after binutils/gcc: 36 commits discards ebe53b843fa 154: onsuccess: #573: 2: Success after binutils/gcc: 6 commits discards 20cc6a09bc0 153: onsuccess: #572: 2: Success after binutils/gcc: 28 commits discards d6f15b5ab46 152: onsuccess: #571: 2: Success after binutils/gcc: 43 commits discards 7a82a870917 151: onsuccess: #570: 2: Success after binutils/gcc: 36 commits discards 6bc3bcc7dc5 150: onsuccess: #569: 2: Success after binutils/gcc: 32 commits discards 7b83dd90006 149: onsuccess: #568: 2: Success after binutils/gcc: 69 commits discards e6a9b172879 148: onsuccess: #567: 2: Success after binutils/gcc: 128 commits discards 93d1b61ffc0 147: onsuccess: #566: 2: Success after binutils/gcc: 50 commits discards 7e44f6897c3 146: onsuccess: #565: 2: Success after binutils/gcc: 115 commits discards 5a4cdfa77f8 145: onsuccess: #564: 2: Success after binutils/gcc: 30 commits discards c628e966da6 144: onsuccess: #563: 2: Success after binutils/gcc: 4 commits discards 377666b5b2d 143: onsuccess: #562: 2: Success after binutils/gcc: 6 commits discards e63f47cc73f 142: onsuccess: #561: 2: Success after binutils/gcc: 176 commits discards fe375a653f1 141: onsuccess: #559: 1: Success after gcc: 4 commits discards 220ac506242 140: force: #558: 1: Failure after basepoints/gcc-13-4953-g [...] discards 3bebe6e2dab 139: force: #557: 2: Success after gcc: 6 commits discards 7adcb8df23c 138: onsuccess: #554: 2: Success after binutils: 10 commits discards 6f8e639ba10 137: onsuccess: #552: 2: Success after binutils/gcc: 18 commits discards 2e2034d9168 136: onsuccess: #551: 2: Success after binutils/gcc: 18 commits discards eb453c974fb 135: onsuccess: #550: 2: Success after binutils/gcc: 31 commits discards c5145c01522 134: onsuccess: #549: 2: Success after binutils/gcc: 9 commits discards d12519e6f3d 133: onsuccess: #548: 2: Success after binutils/gcc: 29 commits discards 9d95efc92a3 132: onsuccess: #547: 2: Success after binutils/gcc: 7 commits discards ff8b7382ed7 131: onsuccess: #546: 2: Success after binutils/gcc: 24 commits discards 07cde712867 130: onsuccess: #545: 2: Success after binutils/gcc: 9 commits discards b75347e673d 129: onsuccess: #544: 2: Success after binutils/gcc: 79 commits discards ecab8547169 128: onsuccess: #543: 2: Success after binutils/gcc: 52 commits discards fe68c62e8ab 127: onsuccess: #542: 2: Success after binutils/gcc: 66 commits discards c5fb9e42871 126: onsuccess: #541: 2: Success after binutils/gcc: 17 commits discards affaa074b38 125: onsuccess: #540: 2: Success after binutils/gcc: 53 commits discards c205b6e4de7 124: onsuccess: #539: 2: Success after binutils/gcc: 9 commits discards eaf24f9676c 123: onsuccess: #538: 2: Success after binutils/gcc: 14 commits discards a156eb3e818 122: onsuccess: #537: 2: Success after binutils/gcc: 36 commits discards deb3880d6ab 121: onsuccess: #536: 1: Success after binutils/gcc: 76 commits discards 209dd62a818 120: onsuccess: #535: 1: Success after binutils: 10 commits discards a5d7ed2f782 119: force: #534: 1: Failure after gdb-12-branchpoint-3046- [...] discards 86b481eb7fc 118: force: #533: 2: Success after binutils: 4 commits discards c0c448e71d4 117: onsuccess: #531: 2: Success after gcc: 65 commits discards e005ea4d33e 116: onsuccess: #528: 2: Success after binutils/gcc: 48 commits discards 38af1268926 115: onsuccess: #527: 2: Success after binutils/gcc: 11 commits discards 76ebf8449a0 114: onsuccess: #526: 2: Success after binutils/gcc: 3 commits discards f0a09f648b6 113: onsuccess: #525: 2: Success after binutils/gcc: 35 commits discards 7fca6b18ea8 112: onsuccess: #524: 2: Success after binutils/gcc: 32 commits discards d8ddc1af517 111: onsuccess: #523: 2: Success after binutils/gcc: 26 commits discards 7c38c66ef59 110: onsuccess: #522: 2: Success after binutils/gcc: 47 commits discards fcbce496c67 109: onsuccess: #521: 2: Success after binutils/gcc: 32 commits discards 765591c21f1 108: onsuccess: #520: 2: Success after binutils/gcc: 13 commits discards 41f70427e01 107: onsuccess: #519: 2: Success after binutils/gcc: 8 commits discards 44edb5f5100 106: onsuccess: #518: 2: Success after binutils/gcc: 31 commits discards 16c3986f33c 105: onsuccess: #517: 2: Success after binutils/gcc: 52 commits new c7182fb51b6 105: onsuccess: #517: 2: Success after binutils/gcc: 52 commits new 1f287f6afff 106: onsuccess: #518: 2: Success after binutils/gcc: 31 commits new cac11b2f9c7 107: onsuccess: #519: 2: Success after binutils/gcc: 8 commits new 7de8454aa49 108: onsuccess: #520: 2: Success after binutils/gcc: 13 commits new fc7b8f024e0 109: onsuccess: #521: 2: Success after binutils/gcc: 32 commits new 4afc469f287 110: onsuccess: #522: 2: Success after binutils/gcc: 47 commits new 0ae6566bbf3 111: onsuccess: #523: 2: Success after binutils/gcc: 26 commits new 0dd91b14420 112: onsuccess: #524: 2: Success after binutils/gcc: 32 commits new 1c18d70b455 113: onsuccess: #525: 2: Success after binutils/gcc: 35 commits new 89b042dc0db 114: onsuccess: #526: 2: Success after binutils/gcc: 3 commits new 14c3610a1ab 115: onsuccess: #527: 2: Success after binutils/gcc: 11 commits new 8f8301c034d 116: onsuccess: #528: 2: Success after binutils/gcc: 48 commits new 6b2d929bf7d 117: onsuccess: #531: 2: Success after gcc: 65 commits new c4efd23ace3 118: force: #533: 2: Success after binutils: 4 commits new bba5424b921 119: force: #534: 1: Failure after gdb-12-branchpoint-3046- [...] new b1f2560a417 120: onsuccess: #535: 1: Success after binutils: 10 commits new f915a14cacc 121: onsuccess: #536: 1: Success after binutils/gcc: 76 commits new 14cb52cb88f 122: onsuccess: #537: 2: Success after binutils/gcc: 36 commits new ee046910f37 123: onsuccess: #538: 2: Success after binutils/gcc: 14 commits new 47ff891f1ab 124: onsuccess: #539: 2: Success after binutils/gcc: 9 commits new 8f60b27e8d5 125: onsuccess: #540: 2: Success after binutils/gcc: 53 commits new 0a4b4843736 126: onsuccess: #541: 2: Success after binutils/gcc: 17 commits new 167437b319a 127: onsuccess: #542: 2: Success after binutils/gcc: 66 commits new ad25d083d79 128: onsuccess: #543: 2: Success after binutils/gcc: 52 commits new 96a79a69c38 129: onsuccess: #544: 2: Success after binutils/gcc: 79 commits new b3fc515524d 130: onsuccess: #545: 2: Success after binutils/gcc: 9 commits new 60470a5f478 131: onsuccess: #546: 2: Success after binutils/gcc: 24 commits new 0aa729d5733 132: onsuccess: #547: 2: Success after binutils/gcc: 7 commits new a0291a8f546 133: onsuccess: #548: 2: Success after binutils/gcc: 29 commits new d2d38f01e67 134: onsuccess: #549: 2: Success after binutils/gcc: 9 commits new 03c86868cca 135: onsuccess: #550: 2: Success after binutils/gcc: 31 commits new a62b5f6a4c5 136: onsuccess: #551: 2: Success after binutils/gcc: 18 commits new 57fe81e1a28 137: onsuccess: #552: 2: Success after binutils/gcc: 18 commits new 3a0ba5bb9e5 138: onsuccess: #554: 2: Success after binutils: 10 commits new afb000b9775 139: force: #557: 2: Success after gcc: 6 commits new 1c019c35e44 140: force: #558: 1: Failure after basepoints/gcc-13-4953-g [...] new 91274f00b96 141: onsuccess: #559: 1: Success after gcc: 4 commits new ca28dfd0060 142: onsuccess: #561: 2: Success after binutils/gcc: 176 commits new 3c131d7cfe9 143: onsuccess: #562: 2: Success after binutils/gcc: 6 commits new a347a988d66 144: onsuccess: #563: 2: Success after binutils/gcc: 4 commits new 918d547b167 145: onsuccess: #564: 2: Success after binutils/gcc: 30 commits new d6bba890747 146: onsuccess: #565: 2: Success after binutils/gcc: 115 commits new 16b8e8f393c 147: onsuccess: #566: 2: Success after binutils/gcc: 50 commits new acf9f92fd80 148: onsuccess: #567: 2: Success after binutils/gcc: 128 commits new f710ecc4920 149: onsuccess: #568: 2: Success after binutils/gcc: 69 commits new 020734fd894 150: onsuccess: #569: 2: Success after binutils/gcc: 32 commits new 8c65187e917 151: onsuccess: #570: 2: Success after binutils/gcc: 36 commits new d3ffdf58cf9 152: onsuccess: #571: 2: Success after binutils/gcc: 43 commits new 908f74094ae 153: onsuccess: #572: 2: Success after binutils/gcc: 28 commits new 17be4d0f95e 154: onsuccess: #573: 2: Success after binutils/gcc: 6 commits new d58539eda48 155: onsuccess: #574: 2: Success after binutils/gcc: 36 commits new 30301656326 156: onsuccess: #575: 2: Success after binutils/gcc: 27 commits new f976634b479 157: onsuccess: #576: 2: Success after binutils/gcc: 80 commits new dbca7aa4016 158: onsuccess: #577: 2: Success after binutils/gcc: 27 commits new 554c1c10ce9 159: onsuccess: #578: 2: Success after binutils/gcc: 130 commits new 91599c170d3 160: onsuccess: #579: 2: Success after binutils/gcc: 17 commits new 1a8bf6f8f8b 161: onsuccess: #580: 2: Success after binutils/gcc: 10 commits new 700b04682ac 162: onsuccess: #581: 2: Success after binutils/gcc: 6 commits new e3281c5cda9 163: onsuccess: #582: 2: Success after binutils/gcc: 55 commits new 4cc90e93f42 164: onsuccess: #583: 2: Success after binutils/gcc: 110 commits new 5800ce2045b 165: onsuccess: #584: 2: Success after binutils/gcc: 45 commits new 618cf679703 166: onsuccess: #585: 2: Success after binutils/gcc: 59 commits new 52d3396d1f6 167: onsuccess: #586: 2: Success after binutils/gcc: 16 commits new a2c499babe5 168: onsuccess: #587: 2: Success after binutils/gcc: 2 commits new 8cb55c0f046 169: onsuccess: #588: 2: Success after binutils/gcc: 7 commits new 948fbf032ab 170: onsuccess: #589: 2: Success after binutils/gcc: 28 commits new 93eb0848378 171: onsuccess: #590: 2: Success after binutils/gcc: 21 commits new f8f535d42ba 172: onsuccess: #592: 2: Success after binutils/gcc: 57 commits new 6b55ff17d49 173: onsuccess: #593: 2: Success after binutils/gcc: 74 commits new 19158af2a17 174: onsuccess: #594: 2: Success after binutils/gcc: 147 commits new e3aaea21465 175: onsuccess: #595: 2: Success after binutils/gcc: 30 commits new 17a7cc822f9 176: onsuccess: #596: 2: Success after binutils/gcc: 84 commits new 2b7c2a1681f 177: onsuccess: #597: 2: Success after binutils/gcc: 86 commits new 80f31df06d4 178: onsuccess: #598: 2: Success after binutils/gcc: 54 commits new e0a88d026a6 179: onsuccess: #599: 2: Success after binutils/gcc: 27 commits new 345489d92c7 180: onsuccess: #600: 2: Success after binutils/gcc: 32 commits new da1f48ef746 181: onsuccess: #601: 2: Success after binutils/gcc: 13 commits new 09b7f53127b 182: onsuccess: #602: 2: Success after binutils/gcc: 32 commits new 61378c646a1 183: onsuccess: #603: 2: Success after binutils/gcc: 33 commits new 07bf4993042 184: onsuccess: #604: 2: Success after binutils/gcc: 138 commits new 673539e0360 185: onsuccess: #605: 2: Success after binutils/gcc: 38 commits new 5b82e723848 186: onsuccess: #1: 2: Success after binutils/gcc: 54 commits new 20048c6f384 187: onsuccess: #2: 2: Success after binutils/gcc: 22 commits new 1d55c371574 188: onsuccess: #3: 2: Success after binutils/gcc: 5 commits new 7089cc77e68 189: onsuccess: #4: 2: Success after binutils/gcc: 8 commits new c500ef41475 190: onsuccess: #5: 2: Success after binutils/gcc: 23 commits new 5e0f91c32e3 191: onsuccess: #6: 2: Success after binutils/gcc: 65 commits new 930b60e5810 192: onsuccess: #7: 2: Success after binutils/gcc: 22 commits new c5d9e174096 193: onsuccess: #8: 2: Success after binutils/gcc: 37 commits new 65ddbe8cb5d 194: onsuccess: #9: 2: Success after binutils/gcc: 48 commits new 8abfb004a27 195: onsuccess: #10: 2: Success after binutils/gcc: 28 commits new 3620a9a65ad 196: onsuccess: #11: 2: Success after binutils/gcc: 16 commits new 62bea11f176 197: onsuccess: #12: 2: Success after binutils/gcc: 29 commits new 7ab77eb5f47 198: onsuccess: #13: 2: Success after binutils/gcc: 58 commits new aeca556ac5f 199: onsuccess: #14: 2: Success after binutils/gcc: 31 commits new 179700366d5 200: onsuccess: #15: 2: Success after binutils/gcc: 26 commits new 7ba495d717a 201: onsuccess: #16: 2: Success after binutils/gcc: 55 commits new 975a4593d15 202: onsuccess: #17: 2: Success after binutils/gcc: 25 commits new 479e05f0722 203: onsuccess: #18: 2: Success after binutils/gcc: 9 commits new 3f160d38d78 204: onsuccess: #19: 2: Success after binutils/gcc: 39 commits new a605cda200d 205: onsuccess: #20: 2: Success after binutils/gcc: 59 commits new 059e892fd16 206: onsuccess: #21: 2: Success after binutils/gcc: 38 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (2f5e3fae7e7) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] 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 1900 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 3456 bytes 04-build_abe-binutils/console.log.xz | Bin 39528 -> 39384 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 306276 -> 305612 bytes 06-check_regression/console.log.xz | Bin 3080 -> 3080 bytes 07-update_baseline/console.log | 44 ++++++++++----------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +++++----- 13 files changed, 38 insertions(+), 38 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[binutils-gdb] branch master updated (a8ea150efb9 -> 06e8a3a98ab)

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 a8ea150efb9 Enable vector register visibility in core for AIX. new 06e8a3a98ab Fix formatting in gdb/printing.py 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/python/lib/gdb/printing.py | 3 +++ 1 file changed, 3 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm updated (1dd450c2ce8 -> c0524872d36)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm in repository toolchain/ci/base-artifacts. discards 1dd450c2ce8 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards e94590712f6 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 3b4568fd7b0 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] discards 7a9a3688307 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards e75ece85b14 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 99275e3e0ef 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards c2eabd0481c 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 272c4eb97c9 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards fe05529bc1a 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 30277fa674f 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards bfba3c08960 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] discards 0948f813ce4 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards c92eb3b9ed1 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards c039be724a7 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards d308831038e 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards ae90ebc512b 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 43ff048c4b9 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] discards 9bcb7aba988 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 8c37adb2a1a 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards c8c7263767c 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards e02d23ec5d6 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 927e5f86ec9 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 667a68aa205 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 45b3e6bd8a7 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 82521605e6a 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 97ff58700ec 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 2ecfbc9d9d7 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 30562c0e053 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 5602d749c62 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 214141c63da 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards d261fefe830 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 1588343fb2a 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 142910dd5f3 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 5bd14a66e81 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 1ddecba8948 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards f353798c2da 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 248a05b9447 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards efba8e5f5e0 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 4aefe0c7d76 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 9c2fd1f5851 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] discards bae6c52233d 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] discards d3962f34350 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] discards 28e30f9ec1b 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 9f4a783d2d2 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards d5ac15c2fa0 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards a32d0f269fe 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 112174d4f30 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 191487bf84b 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 1426fb4af56 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards b0853fb2ad6 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards f85f858756e 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 7b5d09bc756 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards f1ec5cfaa27 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 9921f673c83 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] discards a7173375805 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 61088a58155 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards cd2b51f981a 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 0e0756ed483 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards a5a00bb5511 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 873e75be9a3 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards c8c9c90772b 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] discards ff0b2bb86e3 162: onsuccess: #624: 1: Success after linux: 10 commits discards c64ffc29cf9 161: onsuccess: #623: 1: Success after glibc: 9 commits discards 8f9fc832434 160: onsuccess: #621: 1: Success after gcc: 11 commits discards bffcf1b9633 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 4c9c050f425 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards d0c65817654 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 7c9d628bfbb 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards a39c66e3cf9 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 4a1bc64dddf 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] discards 1cd0321e212 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] discards d41153dbba3 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] discards f9cbb2c0170 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 4faf5536884 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 64b2b02b209 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 4777afde368 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 5e5230b685e 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards de40426b303 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards aaa5239b48d 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 7cd64ab1173 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] discards 3d27b53d3f6 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 56a41c2b492 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards ea98a1bec4f 141: onsuccess: #601: 1: Success after linux: 794 commits discards 041851a1a6e 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 4e2b110ea42 139: onsuccess: #599: 1: Success after binutils: 10 commits discards 2760b5f4abc 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 46ec225dc59 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards e113a165873 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 657ae8d88c4 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards accc204209b 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 4b16e0ca744 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 496bddbe3e8 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 55ec7dea78c 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 5b16d51db8f 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards e8fc4fc6b2f 129: onsuccess: #588: 1: Success after linux: 4 commits discards 540551faade 128: onsuccess: #586: 1: Success after binutils: 22 commits discards 1c8fa199d44 127: onsuccess: #584: 1: Success after linux: 21 commits discards e9d0e19e197 126: onsuccess: #582: 1: Success after gcc: 9 commits discards 4c9fd078263 125: onsuccess: #581: 1: Success after binutils: 4 commits discards a50ece7f311 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards 823fc82ff67 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] new 36cf95c91ce 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] new 416405df1f6 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new 839bd96310a 125: onsuccess: #581: 1: Success after binutils: 4 commits new 47ffcd92972 126: onsuccess: #582: 1: Success after gcc: 9 commits new 0fce03a6d29 127: onsuccess: #584: 1: Success after linux: 21 commits new fd499531662 128: onsuccess: #586: 1: Success after binutils: 22 commits new 327edbf3d7b 129: onsuccess: #588: 1: Success after linux: 4 commits new 879eb8297da 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 13a033dc258 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 55655a0a99d 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 2e7373f2aa5 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new b2fdafd7e74 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 83872d7cf5f 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 98c8346961b 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new d60936a1b21 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 14aa0ffc5a8 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 7938f9c60b0 139: onsuccess: #599: 1: Success after binutils: 10 commits new dd0844a7407 140: onsuccess: #600: 1: Success after gcc: 23 commits new 3771d2600fb 141: onsuccess: #601: 1: Success after linux: 794 commits new 0f7bf2e1b06 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 8bf5afae346 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 386d9efd347 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] new 55e2f5a0982 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new f07b18ca1b9 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new a84c0801081 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 0bcd1ba5d97 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new c363ca3fb83 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new ad8ad714176 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new dda41f372e9 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 0ade9b61d9b 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] new 9986fcc1c81 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] new 5f42f799659 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] new 353f117449b 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 9717cbedb50 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 38f32c4b220 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new bed21b29ed3 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 279a16dd072 159: onsuccess: #620: 1: Success after binutils: 12 commits new 2efe18ce2f6 160: onsuccess: #621: 1: Success after gcc: 11 commits new de0882c8973 161: onsuccess: #623: 1: Success after glibc: 9 commits new c24e61cac1e 162: onsuccess: #624: 1: Success after linux: 10 commits new 8f06035bc22 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] new be948348c18 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 1915295aa61 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 806a5e08602 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 0030b54f92e 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new d7679794bab 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new bcd5bb2c8c3 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new c1097a1735e 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] new 3a6fc9193a5 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new de653d9f6c8 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 36a63586a5a 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 1184e09a5f0 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 4726d48c68b 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 9c361e80c5a 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 9730829275e 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new c807a12e194 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 02e272388d0 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new a6dea916dce 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new c71028aba69 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new c35075da0ba 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] new 7ee23980e48 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] new 48cbc18d279 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] new 311fa4f09a6 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 1b40efaac74 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new d718d5ebd12 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 8f508d2f806 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new cb6275697aa 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 57e4c678335 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new ca13cf83326 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new ec76eb35ffb 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 81ac52d7efa 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new abc74fdcfb9 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 5b117a27f67 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new b30dbd3a6fd 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 6170a63d94c 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 1f063b8567f 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 3b47b4e2093 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 5784d49d295 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 8b63d7bca9b 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new ff98bf20959 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new bc13254ed70 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 77e9dab8637 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new cf75e581aef 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 44abc7bc99c 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 8c69fc72510 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] new e57f54f1611 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 27967a7ac91 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new bde9de2ec1e 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 66567442aa9 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 682a7d5bef6 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new b7c34cc5f03 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] new 0bd382ef63d 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 4e801db61f0 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 7ab497e3d91 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new ee3360b6e64 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 44a721d9b0a 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 371173b0332 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 5dd254efbf1 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new 6ec5f7264d7 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] new 6201b197191 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 72ee566fe0a 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new c0524872d36 224: onsuccess: #21: 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 (1dd450c2ce8) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1756 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 3444 bytes 03-build_abe-binutils/console.log.xz | Bin 52912 -> 52780 bytes 04-build_abe-gcc/console.log.xz | Bin 239128 -> 238020 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8640 -> 9048 bytes 07-build_abe-glibc/console.log.xz | Bin 237464 -> 235800 bytes 08-build_abe-gdb/console.log.xz | Bin 51628 -> 50296 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3792 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2956 -> 9508 bytes 11-check_regression/console.log.xz | Bin 7216 -> 6288 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 9 + 11-check_regression/mail-body.txt | 43 +- 11-check_regression/results.compare | 36 +- 11-check_regression/results.compare2 | 211 +- .../{mail-body.txt => results.regressions} | 44 +- 12-update_baseline/console.log | 50 +- 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 | 45 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 29 + sumfiles/g++.log.sep.xz | Bin 0 -> 82832 bytes sumfiles/g++.log.xz | Bin 2890876 -> 2913932 bytes sumfiles/g++.sum | 188 +- sumfiles/g++.sum.sep | 6610 ++++++++++++++++++++ sumfiles/gcc.log.sep.xz | Bin 0 -> 74636 bytes sumfiles/gcc.log.xz | Bin 2472616 -> 2459192 bytes sumfiles/gcc.sum | 352 +- sumfiles/gcc.sum.sep | 1197 ++++ sumfiles/gfortran.log.sep.xz | Bin 0 -> 25860 bytes sumfiles/gfortran.log.xz | Bin 957292 -> 953864 bytes sumfiles/gfortran.sum | 38 +- sumfiles/gfortran.sum.sep | 1391 ++++ sumfiles/libatomic.log.xz | Bin 2276 -> 2276 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 233976 -> 234004 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2692 -> 2696 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.sep.xz | Bin 0 -> 13828 bytes sumfiles/libstdc++.log.xz | Bin 470568 -> 465792 bytes sumfiles/libstdc++.sum | 13 +- sumfiles/libstdc++.sum.sep | 16 + 51 files changed, 9817 insertions(+), 536 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum copy 11-check_regression/{mail-body.txt => results.regressions} (70%) create mode 100644 sumfiles/g++.log.sep.xz create mode 100644 sumfiles/g++.sum.sep create mode 100644 sumfiles/gcc.log.sep.xz create mode 100644 sumfiles/gcc.sum.sep create mode 100644 sumfiles/gfortran.log.sep.xz create mode 100644 sumfiles/gfortran.sum.sep create mode 100644 sumfiles/libstdc++.log.sep.xz create mode 100644 sumfiles/libstdc++.sum.sep -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch releases/gcc-12 updated (a1ebe3f7f9c -> 94af33aa4da)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-12 in repository gcc. from a1ebe3f7f9c c++: ICE with constexpr lambda [PR107280] new 94af33aa4da ubsan: missed -fsanitize=bounds for compound ops [PR108060] 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/c-family/c-gimplify.cc | 12 ++++++++++++ gcc/testsuite/c-c++-common/ubsan/bounds-17.c | 17 +++++++++++++++++ gcc/testsuite/c-c++-common/ubsan/bounds-18.c | 17 +++++++++++++++++ gcc/testsuite/c-c++-common/ubsan/bounds-19.c | 20 ++++++++++++++++++++ gcc/testsuite/c-c++-common/ubsan/bounds-20.c | 16 ++++++++++++++++ gcc/testsuite/c-c++-common/ubsan/bounds-21.c | 18 ++++++++++++++++++ 6 files changed, 100 insertions(+) create mode 100644 gcc/testsuite/c-c++-common/ubsan/bounds-17.c create mode 100644 gcc/testsuite/c-c++-common/ubsan/bounds-18.c create mode 100644 gcc/testsuite/c-c++-common/ubsan/bounds-19.c create mode 100644 gcc/testsuite/c-c++-common/ubsan/bounds-20.c create mode 100644 gcc/testsuite/c-c++-common/ubsan/bounds-21.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[binutils-gdb] branch master updated (5d47e20b22a -> a8ea150efb9)

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 5d47e20b22a [gdb/testsuite] Fix re-used exec in gdb.arch/ftrace-insn-reloc.exp new a8ea150efb9 Enable vector register visibility in core for AIX. 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/rs6000-aix-tdep.c | 36 ++++++++++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits March 2023