Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[toolchain/jenkins-scripts] branch master updated (624d2c04 -> ef69d8c9)

by Maxim Kuvyrkov

This is an automated email from the git hooks/post-receive script. "Maxim Kuvyrkov pushed a change to branch master in repository toolchain/jenkins-scripts. from 624d2c04 tcwg-update-llvmbot-containers: Move clang-native-arm-lnt-per [...] new ef69d8c9 round-robin.sh: Workaround containers running out of RAM on 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: round-robin.sh | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/release-arm updated (6bb05783165 -> 06bf7415a28)

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/release-arm in repository toolchain/ci/base-artifacts. from 6bb05783165 32: onsuccess: #186: 1: Success after binutils/gcc/gdb: 10 commits new 06bf7415a28 33: onsuccess: #187: 1: Success after binutils/gcc/linux/gd [...] 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 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 51796 -> 51636 bytes 04-build_abe-gcc/console.log.xz | Bin 229240 -> 229384 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8716 -> 8684 bytes 07-build_abe-glibc/console.log.xz | Bin 232020 -> 232256 bytes 08-build_abe-gdb/console.log.xz | Bin 46532 -> 46580 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3832 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2144 -> 2140 bytes 11-check_regression/console.log.xz | Bin 22680 -> 17480 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 35 +- 11-check_regression/mail-body.txt | 146 +- 11-check_regression/results.compare | 73 +- 11-check_regression/results.compare2 | 3975 ++------------ 11-check_regression/results.regressions | 73 +- 12-update_baseline/console.log | 9 + dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 148 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 73 +- sumfiles/gdb.log.xz | Bin 1708160 -> 1740132 bytes sumfiles/gdb.sum | 9106 ++++++++++++++++++++++--------- 30 files changed, 7579 insertions(+), 6109 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch master updated (716c2d08893 -> 892e8c520be)

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 716c2d08893 range-op-float: frange_arithmetic tweaks for MODE_COMPOSITE_P new c690779637e [testsuite] [arm/aarch64] -fno-short-enums for auto-init-[12].c new a82c119b1e9 [arm] xfail fp-uint64-convert-double tests new 4505270128e [PR102706] [testsuite] -Wno-stringop-overflow vs Warray-bounds new 892e8c520be tree-optimization/107699 - missed &data._M_elems + _1 != &d [...] The 4 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/match.pd | 21 +++++++++++++-------- gcc/testsuite/c-c++-common/auto-init-1.c | 2 +- gcc/testsuite/c-c++-common/auto-init-2.c | 2 +- gcc/testsuite/gcc.dg/Warray-bounds-48.c | 11 +++++++++-- gcc/testsuite/gcc.dg/Wzero-length-array-bounds-2.c | 11 +++++++++-- gcc/testsuite/gcc.dg/debug/btf/btf-enum-1.c | 2 +- .../gcc.dg/torture/fp-uint64-convert-double-1.c | 2 +- .../gcc.dg/torture/fp-uint64-convert-double-2.c | 2 +- gcc/testsuite/gcc.dg/tree-ssa/pr107699.c | 15 +++++++++++++++ 9 files changed, 51 insertions(+), 17 deletions(-) create mode 100644 gcc/testsuite/gcc.dg/tree-ssa/pr107699.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/bmk-scripts] branch master updated (50c53ac -> fc00dc2)

by Prathamesh Kulkarni

This is an automated email from the git hooks/post-receive script. "Prathamesh Kulkarni pushed a change to branch master in repository toolchain/bmk-scripts. from 50c53ac vect-data-to-csv.py: Punt if no vect dump files are found. new fc00dc2 Add extract_dump_files_to_dir method and re-enable SVE metric [...] 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: metric_utils.py | 6 ++++++ sve-data-to-csv.py | 30 +++++++++++++++++++----------- 2 files changed, 25 insertions(+), 11 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/bmk-scripts] branch master updated (772beed -> 50c53ac)

by Prathamesh Kulkarni

This is an automated email from the git hooks/post-receive script. "Prathamesh Kulkarni pushed a change to branch master in repository toolchain/bmk-scripts. from 772beed run.sh: limit nb of parallel build/run jobs (fix) new 50c53ac vect-data-to-csv.py: Punt if no vect dump files are found. 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: vect-data-to-csv.py | 4 ++++ 1 file changed, 4 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-mainline-allmodconfig updated (7471dcee55b -> d977d841b44)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-mainline-allmodconfig in repository toolchain/ci/base-artifacts. from 7471dcee55b 31: onsuccess: #570: 33: Success after binutils/gcc/linux/q [...] new d977d841b44 32: onsuccess: #571: 33: Success after binutils/gcc/linux/q [...] 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 2036 -> 1804 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 32120 -> 32608 bytes 04-build_abe-stage1/console.log.xz | Bin 73428 -> 73748 bytes 05-build_abe-qemu/console.log.xz | Bin 31104 -> 31396 bytes 06-build_linux/console.log.xz | Bin 3428 -> 3500 bytes 08-check_regression/console.log.xz | Bin 4340 -> 4448 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 28 insertions(+), 28 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_llvm_fx/llvm-master-aarch64-cpu2017rate-O2 updated (113d3bd03c4 -> 7fee39106fa)

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_llvm_fx/llvm-master-aarch64-cpu2017rate-O2 in repository toolchain/ci/base-artifacts. from 113d3bd03c4 21: force: #137: 1: [TCWG CI] 520.omnetpp_r slowed down by [...] new 7fee39106fa 22: force: #138: 1: [TCWG CI] 531.deepsjeng_r speeds up by [...] 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 1920 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 32064 -> 32156 bytes 04-build_abe-stage1/console.log.xz | Bin 72856 -> 72928 bytes 06-build_abe-linux/console.log.xz | Bin 8840 -> 8800 bytes 07-build_abe-glibc/console.log.xz | Bin 243664 -> 243600 bytes 08-build_abe-stage2/console.log.xz | Bin 178328 -> 178304 bytes 09-build_llvm-true-false-cflags-/console.log.xz | Bin 62772 -> 63388 bytes 10-benchmark/benchmark-build.log | 90 +- 10-benchmark/benchmark.log | 89 +- 10-benchmark/console.log.xz | Bin 5020 -> 3848 bytes .../541.leela_r.symbols-improvement | 1 - 11-check_regression/console.log.xz | Bin 12868 -> 11192 bytes .../csv-results-vs-first-1/md5sum.csv | 1082 +- .../csv-results-vs-first-1/perf.csv | 1980 +- .../csv-results-vs-first-1/results.csv | 2165 +- .../csv-results-vs-prev-0/md5sum.csv | 1604 +- 11-check_regression/csv-results-vs-prev-0/perf.csv | 2040 +- .../csv-results-vs-prev-0/results.csv | 55221 +++-- 11-check_regression/csv-results-vs-prev-0/size.csv | 190200 +++++++++--------- 11-check_regression/csv-results-vs-prev-0/vect.csv | 25585 +-- .../csv-results-vs-prev-1/md5sum.csv | 1082 +- 11-check_regression/csv-results-vs-prev-1/perf.csv | 1980 +- .../csv-results-vs-prev-1/results.csv | 2165 +- 11-check_regression/exe.improvement | 2 + 11-check_regression/exe.regression | 7 - 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/jira-body.txt | 30 +- 11-check_regression/mail-body.txt | 30 +- 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results-vs-first-brief.csv | 42 +- 11-check_regression/results-vs-first-full.csv | 1989 +- 11-check_regression/results-vs-first-internal.csv | 135 +- 11-check_regression/results-vs-first.csv | 135 +- 11-check_regression/results-vs-first.log | 460 +- 11-check_regression/results-vs-prev-brief.csv | 42 +- 11-check_regression/results-vs-prev-compare.csv | 37 +- 11-check_regression/results-vs-prev-full.csv | 2133 +- 11-check_regression/results-vs-prev-internal.csv | 137 +- 11-check_regression/results-vs-prev.csv | 137 +- 11-check_regression/results-vs-prev.log | 592 +- 11-check_regression/results.regressions | 29 - 11-check_regression/skipped-symbols.txt | 15 +- 11-check_regression/symbol.regression | 8 - 11-check_regression/trigger-bisect | 3 - dashboard/dashboard-generate.sh | 2 +- .../500.perlbench_r/results-metadata.json | 10 +- .../500.perlbench_r/results-metrics.json | 2 +- .../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 +- .../510.parest_r/results-metadata.json | 10 +- .../510.parest_r/results-metrics.json | 2 +- .../511.povray_r/results-metadata.json | 10 +- .../squad-vs-first/519.lbm_r/results-metadata.json | 10 +- .../520.omnetpp_r/results-metadata.json | 10 +- .../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 +- .../538.imagick_r/results-metrics.json | 2 +- .../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 | 74 +- dashboard/squad-vs-first/summary-annotation.txt | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 39 +- mail/mail-body.txt | 39 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- results | 29 - results_id | 2 +- 81 files changed, 128810 insertions(+), 162836 deletions(-) delete mode 100644 11-check_regression/541.leela_r.symbols-improvement create mode 100644 11-check_regression/exe.improvement delete mode 100644 11-check_regression/exe.regression delete mode 100644 11-check_regression/results.regressions delete mode 100644 11-check_regression/symbol.regression delete mode 100644 11-check_regression/trigger-bisect -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

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

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 b734523e81f 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards a4c2110c75d 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards 573c848f7e2 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards 65a6c09c165 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards a910d9580b0 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards e78d5e8b4c9 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards 2811056adcf 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards 840aebae58a 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] discards 11ba4ba296c 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards fb6ba572c2a 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards e6a4d8b2a7a 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] discards 20b87c82769 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] discards 786d1dc400a 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] discards 2231572ae43 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] discards 601b0d714c3 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] discards dadb31a87da 109: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] discards fe7f37e2047 108: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] discards 0bf9d6515b0 107: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] discards 77e186574be 106: onsuccess: #532: 1: Success after binutils/gcc/linux/g [...] discards c885c3a2112 105: onsuccess: #531: 1: Success after binutils/gcc/linux/g [...] discards 398b7893cc3 104: onsuccess: #530: 1: Success after gcc: 7 commits discards 83c4ece0738 103: onsuccess: #529: 1: Success after binutils/gcc/linux/g [...] discards fac0de27d0c 102: onsuccess: #527: 1: Success after binutils: 5 commits discards c4ce8d0cf52 101: onsuccess: #524: 1: Success after binutils: 2 commits discards 3c78cf4fd49 100: onsuccess: #521: 1: Success after binutils: 10 commits discards 1a32782c359 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] discards 0a8b43d2346 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gl [...] discards 11450717494 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] discards 46f2ae1377e 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] discards 7be6f42aed2 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gd [...] discards 180c5a1e5c3 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gd [...] discards e13548a699d 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] discards 485c191fa58 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gl [...] discards 2fd24d7151e 91: onsuccess: #511: 1: Success after linux: 27 commits discards 5133c58dbd3 90: onsuccess: #510: 1: Success after glibc: 5 commits discards c74a2a3f518 89: onsuccess: #508: 1: Success after binutils: 12 commits discards 70753a6fed9 88: onsuccess: #506: 1: Success after linux: 34 commits discards 0378bb910a9 87: onsuccess: #505: 1: Success after glibc: 7 commits discards 0f995f04ca3 86: onsuccess: #503: 1: Success after binutils: 12 commits discards 24e76c47465 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] discards dacd2b18143 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] discards 69eae3df2f6 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gd [...] discards 1979cbc5224 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gl [...] discards 5373a9c722f 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] discards 2bf6f792503 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] discards 9d3fd6270d8 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] discards f42388beacb 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] discards 141706d6154 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gd [...] discards 5f4fb58e109 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gd [...] discards 26da26b84ce 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gd [...] discards 579b6902e82 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gl [...] discards de4118b02f4 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gd [...] discards 16c508f14a1 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gl [...] discards d55291cebe8 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gd [...] discards f4ef6f8d7b8 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gl [...] discards 7a8d21f2b7a 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] discards 1a6049dfe2c 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gl [...] discards 3133fa6a4ac 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] discards af444382719 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gl [...] discards e87a11b3804 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gd [...] discards 8292a8fbb40 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] discards 5691e6229f3 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gl [...] discards 07183a6bd8d 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gl [...] discards dabf2f35750 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gl [...] discards b47c3b1cf1b 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gl [...] discards 7a7652e5b83 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gl [...] discards 76899fb4815 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gl [...] discards dd0e627cb26 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gl [...] discards 2884b1525d5 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gd [...] discards 8b4c49fe9e5 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gl [...] discards d368f63a34f 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gl [...] discards 2bf33ccaae4 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gl [...] discards 0aaa035b97f 52: onsuccess: #467: 1: Success after binutils: 9 commits discards e90f793412f 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 23a7a2434f7 50: onsuccess: #461: 1: Success after binutils: 12 commits discards 5a098f09f8e 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gd [...] discards 112750a988e 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gd [...] discards 6e1d72e62a1 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gl [...] discards 5c1f77fb191 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gl [...] discards 4dea4c2a6ea 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gl [...] discards 13e5ee3abf8 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gd [...] discards 86d5d380988 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gd [...] discards ef278895b53 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gd [...] discards b377db0c2cb 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gl [...] discards 2350ea9b34c 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g [...] discards db8f883d4ac 39: onsuccess: #447: 1: Success after binutils: 5 commits discards 06391858ef8 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g [...] discards 0dd0477fdba 37: onsuccess: #443: 1: Success after binutils: 2 commits discards d13c05d39a8 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gl [...] discards 1a221876fe4 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gl [...] discards 48698338c14 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gl [...] discards a4953e7ab5b 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gd [...] discards 41fc3daa8ee 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gl [...] discards ebda297fbe7 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gl [...] discards f0f6f3f70d6 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gd [...] discards 8a149edf0fd 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gl [...] discards 3a6cf1d0de1 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gl [...] discards bf3317d1b21 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gd [...] discards 031ff81edfe 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gd [...] discards bb091119867 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gd [...] discards 325dae79924 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 [...] new b2025dba3c6 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 [...] new 675765c889e 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gd [...] new a1c0438060c 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gd [...] new 46a2fe3aae6 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gd [...] new 06e6e5d0383 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gl [...] new 3f9c979a4a7 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gl [...] new ad20caac387 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gd [...] new 45c54ddc5e0 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gl [...] new f661c8319dc 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gl [...] new 4c90d8e19e4 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gd [...] new 1ca13142073 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gl [...] new 99cad7d5d0b 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gl [...] new 7b662fe6fd3 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gl [...] new 091fdd218f6 37: onsuccess: #443: 1: Success after binutils: 2 commits new c1f33def5e8 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g [...] new 6eb5dfa95a4 39: onsuccess: #447: 1: Success after binutils: 5 commits new d8f5372037d 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g [...] new 17b564b870a 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gl [...] new bda198be4fa 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gd [...] new a45880ae21c 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gd [...] new 48150a8046d 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gd [...] new b6a93c6d220 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gl [...] new e7758e8a353 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gl [...] new ab7b8222fb1 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gl [...] new 588cc9339b0 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gd [...] new 2cb7b5f0597 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gd [...] new 6e12d16f846 50: onsuccess: #461: 1: Success after binutils: 12 commits new 15497209ef0 51: onsuccess: #464: 1: Success after binutils: 6 commits new 23521a8777e 52: onsuccess: #467: 1: Success after binutils: 9 commits new 9042c2ac10c 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gl [...] new 992111855d4 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gl [...] new 4cefaa1675c 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gl [...] new 33870c33e15 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gd [...] new a17ded876ec 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gl [...] new ebb50a89759 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gl [...] new 0a25b0b2bb5 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gl [...] new e495e7e62b1 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gl [...] new dfaf0a9136f 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gl [...] new 449c1e3d3e9 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gl [...] new f5843a351f1 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gl [...] new ed624002378 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] new bec71ea2468 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gd [...] new 3d1dda2e027 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gl [...] new e9350c35635 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] new d3a60337a01 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gl [...] new 786cda7e394 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] new cde0a92849f 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gl [...] new eb56f19fac7 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gd [...] new 181d7590418 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gl [...] new 5eba714f7f3 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gd [...] new cd6d5ba1c34 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gl [...] new 2a6b2137ba6 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gd [...] new e7c7bec1ea5 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gd [...] new dd82f146170 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gd [...] new 725522a2685 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] new fb1db6ca1e6 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] new 266825d052a 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] new c41b2155bbf 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] new d03845a19ac 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gl [...] new 3fc02b42360 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gd [...] new af440b0745a 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] new f4a7728fc53 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new 7fa457c7c69 86: onsuccess: #503: 1: Success after binutils: 12 commits new fb1657c623c 87: onsuccess: #505: 1: Success after glibc: 7 commits new 2a4c403869f 88: onsuccess: #506: 1: Success after linux: 34 commits new 0ba876dcd33 89: onsuccess: #508: 1: Success after binutils: 12 commits new 67992ffd6c1 90: onsuccess: #510: 1: Success after glibc: 5 commits new f52a18c238d 91: onsuccess: #511: 1: Success after linux: 27 commits new 8be7b75c7d3 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gl [...] new 9eab462f4f8 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] new 8d3b4035453 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gd [...] new 37c381e676b 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gd [...] new 2149f8a4d5a 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] new 138de6edafb 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] new 33f1735fc80 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gl [...] new 232b901c6d7 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] new 3234e597225 100: onsuccess: #521: 1: Success after binutils: 10 commits new 85693c42cba 101: onsuccess: #524: 1: Success after binutils: 2 commits new 08be7a27561 102: onsuccess: #527: 1: Success after binutils: 5 commits new a092dada0c3 103: onsuccess: #529: 1: Success after binutils/gcc/linux/g [...] new c7148eacd61 104: onsuccess: #530: 1: Success after gcc: 7 commits new e78632fe8b0 105: onsuccess: #531: 1: Success after binutils/gcc/linux/g [...] new bf17762d8ea 106: onsuccess: #532: 1: Success after binutils/gcc/linux/g [...] new 8039438b97f 107: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] new 22a9e9c8724 108: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] new d291358b21e 109: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] new 9386db7c97f 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] new 4ea6e36ec9e 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] new de589f96945 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new 0fd8e9e7c2a 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new 88b624349a4 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new 05713fdf422 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new 9840d9c4a91 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new 1e4c61c1458 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new 627110567d6 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new fb38e77368b 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new 17c6ca66155 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new 57492550635 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new 95c1ffda1fc 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new a3fc9d480d7 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new f32e6265cf1 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 39cb73d897d 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (b734523e81f) \ 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 1724 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 52252 -> 52312 bytes 04-build_abe-gcc/console.log.xz | Bin 234148 -> 234684 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8592 -> 8576 bytes 07-build_abe-glibc/console.log.xz | Bin 235280 -> 235168 bytes 08-build_abe-gdb/console.log.xz | Bin 51988 -> 51792 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3816 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2212 -> 2116 bytes 11-check_regression/console.log.xz | Bin 6224 -> 6232 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 62520 -> 62832 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 98088 -> 98240 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 131580 -> 131644 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 30 files changed, 407 insertions(+), 407 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch master updated (8d4f007398b -> 716c2d08893)

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 8d4f007398b arm: fix mve intrinsics scan body tests for C++ new 716c2d08893 range-op-float: frange_arithmetic tweaks for MODE_COMPOSITE_P 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/range-op-float.cc | 62 ++++++++++++++++++++++++++++++++++++++------------- 1 file changed, 46 insertions(+), 16 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (0a2b6eafb59 -> 66f43fa158d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm in repository toolchain/ci/base-artifacts. discards 0a2b6eafb59 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/ [...] discards 953aa33427a 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/ [...] discards fb1f6ae6383 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards d0e35827f9c 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/ [...] discards 30f9d335128 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/ [...] discards 57cdfc5e76f 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/ [...] discards a4d4897695b 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qe [...] discards 4258a1420b6 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 48967df27c5 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 530203adae0 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards ea424bad2e0 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards a559eae6cc1 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 9d3059b81f2 208: onsuccess: #2012: 1: Success after linux: 12 commits discards beddc81521d 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 7ca4cd08545 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards d157d94d309 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 00ee491825b 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] discards 395e898d114 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] discards 6b2e6b81d91 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] discards db8bc8df7a1 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 9bcedb01d95 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] discards 4e98d3ec3ac 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 454495fed4e 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] discards e4f541b52df 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] discards ebd54a7876e 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] discards 33ccfea5c3a 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] discards 17979e28b19 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 930b355e5e6 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards ea092a86e23 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] discards 0c3986d9711 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] discards 07f0171a7f5 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] discards fb79b28f5af 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] discards 104a2a93a5c 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] discards 6693f4a8c8f 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] discards 411455a874c 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] discards cb43cf6a050 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] discards a1802759052 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] discards caee53c7c1a 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] discards 9880d4ff578 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] discards 16b7fb454a2 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] discards 161a17a717a 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] discards b4369d22e99 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] discards 2fde0061bb0 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] discards a5be5b7dd49 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] discards 43840eeb6f7 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] discards c080dbe8311 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] discards 81c79e12d45 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] discards c70f565d1c2 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] discards ce994361496 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] discards 4043fb0aaed 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] discards eea8f985123 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] discards c11fa492770 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] discards 3ae8e3b8b22 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] discards 9db1dcc32e2 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] discards ef1275f088c 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] discards e57533ef443 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] discards 9545d88cace 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] discards c19f6ab7013 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 2668b0319c1 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] discards 06aaaa289fa 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] discards e18e751bae0 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] discards 5d3c269528c 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] discards 37a56359c95 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] discards 58eac5f4f5c 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] discards 1225f36a404 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards ff56fa2a299 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] discards f2e80dab0a0 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 88744078a8b 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards d7b58671bdf 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] discards dc4347afbb8 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] discards 124510e8131 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] discards 7f7b54ba8e4 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] discards 6bf2049ec91 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] discards 27b6aee0659 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] discards 01041203429 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] discards 7e8f362ca9e 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] discards 92a63725c1a 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards e9c2186f3b5 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] discards 6c513739b23 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] discards 9a9258f22c4 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] discards 3175e92cb4d 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] discards cc66e678389 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] discards e61fe561c68 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] discards 8bfa80f01e2 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards bc6299575ee 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] discards eccc223b95a 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 852203b66dd 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 4261df96d9c 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] discards b81b4c789c4 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] discards 2e2b2358f01 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] discards 60081ed32d8 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 3d4fb30adb2 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] discards f3afbb85601 128: onsuccess: #1723: 1: Success after linux: 12 commits discards fe12e878c86 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] discards 4e5aa76abd4 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 5abeed55a4a 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] discards ad5b1888005 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards dfc3016e4c7 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] discards 70e16ead027 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] discards 8077e8e821d 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] discards 3ce6c5608f8 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] new 28642298f1d 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] new 2058ff872d1 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] new 177177b9297 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] new 9d9ab9854a3 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] new eb4009a0999 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 5a6ac7ade3e 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] new 638a307e5f8 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 0f0c3b99cea 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] new f0b08f540ba 128: onsuccess: #1723: 1: Success after linux: 12 commits new 6af317bb228 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] new 5d0d1c422ba 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new d8f2fefbe42 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] new e91463c09eb 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] new 57f96e7f624 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] new 490143ecc09 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 4a6a8c22772 135: onsuccess: #1733: 1: Success after binutils: 5 commits new ab2768be6a7 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] new 9c8261032a9 137: onsuccess: #1736: 1: Success after gcc: 5 commits new f6808121a58 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] new 4caf1ead5b4 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] new 1bf5cbbf694 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] new 425aaced8ff 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new c20da35aafc 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] new a51e14bd786 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] new 9720eaedcc7 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 3b5072a8b9e 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] new 68fd21b4bf3 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] new 9b171f40181 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] new 9922db3568b 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] new 0e71cb8c405 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] new bdfe9720f51 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] new d35ac213a4e 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] new bfbe7fa3a0a 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] new 3173a988cfb 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 09131241f9e 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new be0c44113db 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] new f036ec4b38c 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 6dd66f38ccb 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] new cd97aaaeefd 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] new c5ad2719987 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] new dd6dd8c41e5 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] new 6a4e5c8bfee 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] new 84457e73aad 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] new bf68a43eaa0 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new d3d8c51c139 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] new aa4bf0af128 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] new f2c94e3961e 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] new 33cc0a0689a 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] new 0014e412889 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] new 51d6de581a6 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] new b7445846215 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] new 724ceccb1db 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] new d61ce87f1ec 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] new 2fed66e29c8 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] new 3a6737f902c 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] new 31c9d8ccff1 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] new 05886958c6e 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] new cd35ff74238 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] new 1e6ead6cf17 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] new cb3786f5b24 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] new 13bdc551e32 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] new 4c862bbe9ff 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] new 9e738c90dca 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] new fb5f3582c49 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] new bec6c263248 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] new e65741a74c6 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] new 45b7e0a4c14 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] new 98c33a85416 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] new 96496b23a6d 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] new d65ad29646b 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] new b54da965f19 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] new f570dc7a8ef 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] new 44d1db7d9d2 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] new 5cb1d36a532 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 039af5cc1cb 194: onsuccess: #1995: 1: Success after linux: 517 commits new 78c99227ff0 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] new 3d9d42913cd 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] new 7aeb4c9b5fb 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] new 4ab8ed9b2d0 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] new 190c6aa82d0 199: onsuccess: #2000: 1: Success after gcc: 5 commits new ced77805ff5 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] new 86e46a1b070 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 97bfacdca08 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] new 5281b610601 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] new 5c446648f0e 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] new 54ad7cca8da 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 70797672cc6 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 2e80da8584e 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 4ce8c8c8e01 208: onsuccess: #2012: 1: Success after linux: 12 commits new 9da5e231221 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 7f1a9739180 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 1852659c7f8 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 7621233594d 212: onsuccess: #2022: 1: Success after linux: 3 commits new 9a07842c693 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 81eaa3da6c1 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qe [...] new 2386cf02552 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/ [...] new 302aa43ca5c 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/ [...] new 41afe17a2ad 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/ [...] new 51b5744046f 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 4a337149501 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/ [...] new cd8d19285ee 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/ [...] new 66f43fa158d 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 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 (0a2b6eafb59) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1800 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31952 -> 31508 bytes 04-build_abe-stage1/console.log.xz | Bin 92432 -> 92276 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8620 -> 8656 bytes 07-build_abe-glibc/console.log.xz | Bin 237552 -> 235848 bytes 08-build_abe-stage2/console.log.xz | Bin 225044 -> 224768 bytes 09-build_abe-gdb/console.log.xz | Bin 38716 -> 38736 bytes 10-build_abe-qemu/console.log.xz | Bin 30588 -> 30488 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3120 -> 3128 bytes 13-check_regression/console.log.xz | Bin 6904 -> 5720 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 40 + 13-check_regression/results.compare | 47 +- 13-check_regression/results.compare2 | 56 +- 13-check_regression/results.regressions | 40 + 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 42 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- results | 40 + sumfiles/g++.log.xz | Bin 2749848 -> 2708732 bytes sumfiles/g++.sum | 120 +- sumfiles/gcc.log.xz | Bin 2282668 -> 2275848 bytes sumfiles/gcc.sum | 2348 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 894668 -> 887844 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 213168 -> 213232 bytes sumfiles/libgomp.sum | 21 +- sumfiles/libitm.log.xz | Bin 2668 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 432108 -> 436720 bytes sumfiles/libstdc++.sum | 16 +- 42 files changed, 1553 insertions(+), 1380 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022