Tcwg-commits March 2023

tcwg-commits@lists.linaro.org

5 participants
3834 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-cpu2017rate/llvm-arm-master-Os updated (ea84568dddb -> 5aa5aedba32)

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_size-cpu2017rate/llvm-arm-master-Os in repository toolchain/ci/base-artifacts. from ea84568dddb 4: onsuccess: #5: 1: [TCWG CI] No change after llvm: 186 commits new 5aa5aedba32 5: onsuccess: #6: 1: [TCWG CI] No change after llvm: 402 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 1924 -> 1888 bytes 02-build_bmk_llvm/console.log.xz | Bin 227720 -> 228992 bytes 03-benchmark/benchmark-build.log | 98 +- 03-benchmark/benchmark.log | 96 +- 03-benchmark/console.log.xz | Bin 3860 -> 3796 bytes .../compare-results-vs-first-internal.csv | 101 +- .../compare-results-vs-prev-internal.csv | 112 +- 04-check_regression/console.log.xz | Bin 9736 -> 9696 bytes .../csv-results-vs-first-1/md5sum.csv | 1052 +++++------ .../csv-results-vs-first-1/perf.csv | 1606 ++++++++-------- .../csv-results-vs-first-1/results.csv | 1873 ++++++++++--------- .../csv-results-vs-first-1/size.csv | 12 +- .../csv-results-vs-prev-0/md5sum.csv | 1146 ++++++------ 04-check_regression/csv-results-vs-prev-0/perf.csv | 1654 ++++++++-------- .../csv-results-vs-prev-0/results.csv | 1965 ++++++++++---------- 04-check_regression/csv-results-vs-prev-0/size.csv | 40 +- .../csv-results-vs-prev-1/md5sum.csv | 1052 +++++------ 04-check_regression/csv-results-vs-prev-1/perf.csv | 1606 ++++++++-------- .../csv-results-vs-prev-1/results.csv | 1873 ++++++++++--------- 04-check_regression/csv-results-vs-prev-1/size.csv | 12 +- .../output-bmk-results/symbol.regression | 3 +- .../output-bmk-results/symbol.regression.diff | 2 +- 04-check_regression/results-vs-first-brief.csv | 32 +- 04-check_regression/results-vs-first-full.csv | 1620 ++++++++-------- 04-check_regression/results-vs-first-internal.csv | 104 +- 04-check_regression/results-vs-first.csv | 104 +- 04-check_regression/results-vs-first.log | 700 ++++--- 04-check_regression/results-vs-prev-brief.csv | 40 +- 04-check_regression/results-vs-prev-compare.csv | 5 +- 04-check_regression/results-vs-prev-full.csv | 1788 +++++++++--------- 04-check_regression/results-vs-prev-internal.csv | 112 +- 04-check_regression/results-vs-prev.csv | 112 +- 04-check_regression/results-vs-prev.log | 736 +++++--- dashboard/dashboard-generate.sh | 2 +- .../500.perlbench_r/results-metadata.json | 10 +- .../squad-vs-first/502.gcc_r/results-metadata.json | 10 +- .../squad-vs-first/505.mcf_r/results-metadata.json | 10 +- .../squad-vs-first/505.mcf_r/results-metrics.json | 2 +- .../508.namd_r/results-metadata.json | 10 +- .../511.povray_r/results-metadata.json | 10 +- .../511.povray_r/results-metrics.json | 2 +- .../squad-vs-first/519.lbm_r/results-metadata.json | 10 +- .../squad-vs-first/519.lbm_r/results-metrics.json | 2 +- .../520.omnetpp_r/results-metadata.json | 10 +- .../520.omnetpp_r/results-metrics.json | 2 +- .../523.xalancbmk_r/results-metadata.json | 10 +- .../525.x264_r/results-metadata.json | 10 +- .../526.blender_r/results-metadata.json | 10 +- .../526.blender_r/results-metrics.json | 2 +- .../531.deepsjeng_r/results-metadata.json | 10 +- .../538.imagick_r/results-metadata.json | 10 +- .../541.leela_r/results-metadata.json | 10 +- .../541.leela_r/results-metrics.json | 2 +- .../squad-vs-first/544.nab_r/results-metadata.json | 10 +- .../squad-vs-first/557.xz_r/results-metadata.json | 10 +- .../squad-vs-first/557.xz_r/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 66 +- git/llvm_rev | 2 +- mail/jira-body.txt | 12 +- mail/mail-body.txt | 12 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results_id | 2 +- 64 files changed, 10157 insertions(+), 9785 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch master updated (097e2afdde0 -> c46b5b0a2c1)

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 097e2afdde0 Skip gnat.dg/div_zero.adb on Aarch64 new c46b5b0a2c1 ranger: Ranger meets aspell 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/gimple-range-cache.cc | 24 ++++++++++++------------ gcc/gimple-range-edge.cc | 8 ++++---- gcc/gimple-range-edge.h | 2 +- gcc/gimple-range-fold.cc | 10 +++++----- gcc/gimple-range-fold.h | 2 +- gcc/gimple-range-gori.cc | 24 ++++++++++++------------ gcc/gimple-range-gori.h | 6 +++--- gcc/gimple-range-infer.cc | 4 ++-- gcc/gimple-range-op.cc | 2 +- gcc/gimple-range-path.cc | 2 +- gcc/gimple-range-trace.cc | 2 +- gcc/gimple-range-trace.h | 2 +- gcc/gimple-range.cc | 10 +++++----- gcc/gimple-range.h | 4 ++-- gcc/range-op-float.cc | 12 ++++++------ gcc/range-op.cc | 26 +++++++++++++------------- gcc/range-op.h | 2 +- gcc/tree-vrp.cc | 6 +++--- gcc/value-query.cc | 8 ++++---- gcc/value-query.h | 2 +- gcc/value-range-storage.h | 2 +- gcc/value-range.cc | 4 ++-- gcc/value-range.h | 8 ++++---- gcc/value-relation.cc | 22 +++++++++++----------- gcc/value-relation.h | 18 +++++++++--------- 25 files changed, 106 insertions(+), 106 deletions(-) -- 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_vect-cpu2017rate/llvm-arm-master-O3 updated (4622067dd40 -> 81910f503c9)

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_vect-cpu2017rate/llvm-arm-master-O3 in repository toolchain/ci/base-artifacts. from 4622067dd40 4: onsuccess: #5: 1: [TCWG CI] No change after llvm: 187 commits new 81910f503c9 5: onsuccess: #6: 1: [TCWG CI] No change after llvm: 401 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 1936 -> 2032 bytes 02-build_bmk_llvm/console.log.xz | Bin 226364 -> 232888 bytes 03-benchmark/benchmark-build.log | 111 +- 03-benchmark/benchmark.log | 109 +- 03-benchmark/console.log.xz | Bin 3856 -> 3864 bytes .../compare-results-vs-first-internal.csv | 111 +- .../compare-results-vs-prev-internal.csv | 113 +- 04-check_regression/console.log.xz | Bin 8836 -> 8460 bytes .../csv-results-vs-first-1/md5sum.csv | 1074 +++++------ .../csv-results-vs-first-1/perf.csv | 1609 ++++++++-------- .../csv-results-vs-first-1/results.csv | 1906 ++++++++++--------- .../csv-results-vs-first-1/size.csv | 24 +- .../csv-results-vs-prev-0/md5sum.csv | 1098 +++++------ 04-check_regression/csv-results-vs-prev-0/perf.csv | 1585 ++++++++-------- .../csv-results-vs-prev-0/results.csv | 1930 ++++++++++---------- 04-check_regression/csv-results-vs-prev-0/size.csv | 38 +- .../csv-results-vs-prev-1/md5sum.csv | 1074 +++++------ 04-check_regression/csv-results-vs-prev-1/perf.csv | 1609 ++++++++-------- .../csv-results-vs-prev-1/results.csv | 1906 ++++++++++--------- 04-check_regression/csv-results-vs-prev-1/size.csv | 24 +- .../output-bmk-results/symbol.regression | 3 - .../output-bmk-results/symbol.regression.diff | 1 - 04-check_regression/results-vs-first-brief.csv | 40 +- 04-check_regression/results-vs-first-full.csv | 1635 ++++++++--------- 04-check_regression/results-vs-first-internal.csv | 113 +- 04-check_regression/results-vs-first.csv | 113 +- 04-check_regression/results-vs-first.log | 868 +++++---- 04-check_regression/results-vs-prev-brief.csv | 40 +- 04-check_regression/results-vs-prev-full.csv | 1753 +++++++++--------- 04-check_regression/results-vs-prev-internal.csv | 113 +- 04-check_regression/results-vs-prev.csv | 113 +- 04-check_regression/results-vs-prev.log | 866 +++++---- dashboard/dashboard-generate.sh | 2 +- .../500.perlbench_r/results-metadata.json | 10 +- .../squad-vs-first/502.gcc_r/results-metadata.json | 10 +- .../squad-vs-first/505.mcf_r/results-metadata.json | 10 +- .../squad-vs-first/505.mcf_r/results-metrics.json | 2 +- .../508.namd_r/results-metadata.json | 10 +- .../511.povray_r/results-metadata.json | 10 +- .../511.povray_r/results-metrics.json | 2 +- .../squad-vs-first/519.lbm_r/results-metadata.json | 10 +- .../520.omnetpp_r/results-metadata.json | 10 +- .../520.omnetpp_r/results-metrics.json | 2 +- .../523.xalancbmk_r/results-metadata.json | 10 +- .../523.xalancbmk_r/results-metrics.json | 2 +- .../525.x264_r/results-metadata.json | 10 +- .../526.blender_r/results-metadata.json | 10 +- .../526.blender_r/results-metrics.json | 2 +- .../531.deepsjeng_r/results-metadata.json | 10 +- .../531.deepsjeng_r/results-metrics.json | 2 +- .../538.imagick_r/results-metadata.json | 10 +- .../541.leela_r/results-metadata.json | 10 +- .../541.leela_r/results-metrics.json | 2 +- .../squad-vs-first/544.nab_r/results-metadata.json | 10 +- .../squad-vs-first/557.xz_r/results-metadata.json | 10 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 66 +- git/llvm_rev | 2 +- mail/jira-body.txt | 12 +- mail/mail-body.txt | 12 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results_id | 2 +- 63 files changed, 10308 insertions(+), 9957 deletions(-) delete mode 100644 04-check_regression/output-bmk-results/symbol.regression -- 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 (1b6b7f214ca -> bd63fdf8c59)

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 1b6b7f214ca Daily bump. new bd63fdf8c59 Skip gnat.dg/div_zero.adb on Aarch64 The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/testsuite/gnat.dg/div_zero.adb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch master updated (59bfdd5f467 -> 097e2afdde0)

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 59bfdd5f467 c++: further -Wdangling-reference refinement [PR107532] new 097e2afdde0 Skip gnat.dg/div_zero.adb on Aarch64 The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/testsuite/gnat.dg/div_zero.adb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 updated (b5c198a82ac -> 7cfd3530183)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. discards b5c198a82ac 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] discards a9e2ae467b5 209: force: #37: 1: Success after baseline build: no new commits discards 2b488db4877 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 37cc49b4f9f 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards ba435182915 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 05cd5418da9 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards b26e006b33e 204: force: #26: : Failure after baseline build: no new commits discards 4a0460459a9 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 2924a1fe867 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards a34ffbfca89 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 7a0f6af0e57 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 071f2a50316 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 35bc5e8284e 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards e0bb0483201 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 089056d0484 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 42a93a41033 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards ad0d7e97d7a 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 71e15249434 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 98a7a3d9465 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 4d11b247f9a 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 01419fba0fa 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 40ebed4a8b2 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 5f3fcbb62db 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards ecd8d4c35c5 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards cce1bb6995e 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 10f9bbf5346 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards f19f2d0915a 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards c21f11233ab 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards 0792b542e90 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards a75637cc463 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards f6f744ebf0f 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards 60bbe8b2874 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards f57fc347b60 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards 5659488c41c 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards cb8c0ba9506 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards 57ec164a36c 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards 8d2307242e1 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards d9f83394693 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards 1f4df512593 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards 0d88196c37e 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards c0468d9d0ea 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards d5830749349 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards 5f82296c7d5 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards 735bd9b8ed1 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards 48cda5bf198 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards 76f30c0871f 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards 70e353a2588 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards 9f3f793fbfa 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards 0695e4e5c08 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards 021aa6ef184 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards dc6c2f914d0 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards 8c021b46d86 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards aac354ec8f1 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards cc2dcd4fd64 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards 9b71949b128 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards 78ab5b5b09a 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards da9bc55615f 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 20b4686abbf 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards b2ecb57e34d 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards a37a2d1a12d 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards e96a397d2d5 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards ef2a7186b78 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards 6cade2ed4f3 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 6c3cd7ee006 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards 2334c4d32f1 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards ea9eba696d5 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards 92032964d10 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards b3eaee1f0c8 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 254f408c844 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 22f5fccd12d 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards 61d9fe17a69 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards 15e7a249fc4 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 853b25605b9 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards 6656cfb526b 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards 9d29e6d247c 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards f7ba91d61b2 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 2916b405c14 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards b8516a4eaff 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 7363a8fdde0 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards e355f320eee 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards c3f60a72e60 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards f8a3eccea81 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards 06e1bf4b385 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards aa2278e5767 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 595fa8d265f 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards 31743e07e45 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 2a3091cd051 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 7253598a383 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards fb848e675b1 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 5db03b718ea 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 731e2c7e3b9 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 656f2bb5c0d 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards cff94b3a2e0 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards 2c1e715b944 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards 38563c511a4 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards 2bf7f8e1eab 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards 425c99b359b 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards ec424f45c60 113: onsuccess: #898: 1: Success after linux: 3 commits discards 18580814606 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 80003363db3 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards d410fdc3b82 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 8c560f3be6b 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 0165f1d1b99 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new f96cc0e88aa 112: onsuccess: #896: 1: Success after binutils: 24 commits new 2797787edcb 113: onsuccess: #898: 1: Success after linux: 3 commits new e73106d6cce 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new 383fbeac6f0 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new 98ba0e9abd9 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new ae2efaa4cd4 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new b3bc2a33f98 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new a68863caff1 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 9a715726e00 120: onsuccess: #906: 1: Success after binutils: 29 commits new bf801c14cb8 121: onsuccess: #908: 1: Success after glibc: 2 commits new 7b07b2c0be1 122: onsuccess: #909: 1: Success after linux: 2753 commits new 6ff185a5411 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 7ba26ae4ebd 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 96008ec24f4 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 776cf24b60a 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 8e98f2bdcdb 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new b2b18b3642f 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new 8f173a68b68 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 6e7ad4ed09f 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new f749be2d729 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 32398fedf51 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new ed294bcf519 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new a9ce896f1ee 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new 2a37c6018c0 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new c002790c611 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new 4bff6a84405 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new 97364e9e6d5 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new 5a2e5a19871 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new 44aee06f691 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new f39c4144cdd 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 9680e5eae02 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 4782d200ef9 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 8693882cc94 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new 8f36e3b0c9a 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new d073d032473 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new db1038323d8 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new 86d7c8c2d86 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 27b2ad5218e 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new 66232d1b03f 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 044d96b74c1 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new bca6780fed4 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 24c7ebd9039 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new f5395f2a0d0 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 5bc86f1f31f 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 6759f56bbe3 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new 1d78c34607c 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new 06823285680 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new c3ad3c9b144 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new 369b769fd3b 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new 7f657c5458c 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new a67046587de 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new 1b1bbe75aea 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new a2d5f3e7cac 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new 023e6b1ed5e 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new b2b918eb245 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new 890bda69a91 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new 6c4dc4e63f0 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new 33347bfdf84 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new 6af5a1dc85e 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new 2b915e0b313 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new 63452f1e68e 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new 32f4837fbd3 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new 601e570adc3 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new 8f936c802fa 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new eadb8050a9d 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new 909912d79fe 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new 34101086ae0 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new b0296b4f492 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new 466bf787a45 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new b2e2f99499d 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new e8f3aeacbfd 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new f10fe4e71f1 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new 47278fa197c 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new 4bd303a9100 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 9b5aae16ab7 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 81864a10e31 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 5de87744b16 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 344b503ae06 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new f87e3f6e27d 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 21aa3629584 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 081f2692a9a 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 981bc6f28c0 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 8bdeadc876e 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 4a7a881e52a 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 3a21210ff0b 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new bbbb23788ba 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new f036d3ca9dc 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 2d1c0aefeb2 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 7167d49d80b 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new f75f48b3177 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 2a8af9ecf07 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 3b08c5da363 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 3262487ff22 204: force: #26: : Failure after baseline build: no new commits new cb454f6a114 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new ad206fd51dd 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new af95faeeaec 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 1aa659feb90 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new f06d8c11bcc 209: force: #37: 1: Success after baseline build: no new commits new 085a5483af6 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] new 7cfd3530183 211: onsuccess: #44: 1: Success after linux: 26 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 (b5c198a82ac) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2076 -> 2020 bytes 02-prepare_abe/console.log.xz | Bin 2488 -> 2532 bytes 03-build_abe-binutils/console.log.xz | Bin 35408 -> 35384 bytes 04-build_abe-gcc/console.log.xz | Bin 203412 -> 203480 bytes 06-build_abe-linux/console.log.xz | Bin 8368 -> 8384 bytes 07-build_abe-glibc/console.log.xz | Bin 242704 -> 241852 bytes 08-build_abe-gdb/console.log.xz | Bin 35108 -> 34880 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3792 -> 3808 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2952 -> 2956 bytes 11-check_regression/console.log.xz | Bin 3728 -> 4000 bytes 11-check_regression/results.compare2 | 54 +++++++++++++++++----------------- 12-update_baseline/console.log | 38 ++++++++++++------------ dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 ++++----- sumfiles/gdb.log.0.xz | Bin 1948520 -> 1935336 bytes sumfiles/gdb.log.1.xz | Bin 27172 -> 27008 bytes sumfiles/gdb.log.2.xz | Bin 5416 -> 5208 bytes sumfiles/gdb.log.3.xz | Bin 5412 -> 5420 bytes sumfiles/gdb.sum | 14 ++++----- sumfiles/gdb.sum.0 | 10 +++---- sumfiles/gdb.sum.1 | 15 ++++++---- sumfiles/gdb.sum.2 | 2 +- sumfiles/gdb.sum.3 | 2 +- 27 files changed, 81 insertions(+), 78 deletions(-) -- 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_size-spec2k6/llvm-aarch64-master-O3_LTO created (now b8227b381b1)

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_size-spec2k6/llvm-aarch64-master-O3_LTO in repository toolchain/ci/base-artifacts. at b8227b381b1 0: init: #1: 1: [TCWG CI] No change after baseline build: n [...] This branch includes the following new commits: new b8227b381b1 0: init: #1: 1: [TCWG CI] No change after baseline build: n [...] 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. -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[binutils-gdb] branch master updated (5834f36d93c -> 91ffa03af1c)

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 5834f36d93c bfd: aarch64: Optimize BTI stubs PR30076 new 91ffa03af1c [gdb/testsuite] Use gdb_remote_download in allow_opencl_tests 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/testsuite/lib/opencl.exp | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) -- 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_size-spec2k6/gnu-arm-master-O3_LTO created (now f505b5182f7)

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_size-spec2k6/gnu-arm-master-O3_LTO in repository toolchain/ci/base-artifacts. at f505b5182f7 0: init: #1: 1: [TCWG CI] No change after baseline build: n [...] This branch includes the following new commits: new f505b5182f7 0: init: #1: 1: [TCWG CI] No change after baseline build: n [...] 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. -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch master updated (3b97715af0e -> 59bfdd5f467)

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 3b97715af0e amdgcn: Fix register size bug new 59bfdd5f467 c++: further -Wdangling-reference refinement [PR107532] 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/cp/call.cc | 63 +++++++++++++---------- gcc/testsuite/g++.dg/warn/Wdangling-reference11.C | 23 +++++++++ gcc/testsuite/g++.dg/warn/Wdangling-reference12.C | 12 +++++ 3 files changed, 72 insertions(+), 26 deletions(-) create mode 100644 gcc/testsuite/g++.dg/warn/Wdangling-reference11.C create mode 100644 gcc/testsuite/g++.dg/warn/Wdangling-reference12.C -- 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