Tcwg-commits January 2023

tcwg-commits@lists.linaro.org

5 participants
4127 discussions

[gcc] branch master updated (607f278a354 -> 049a5290907)

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 607f278a354 Daily bump. new 049a5290907 c++: TARGET_EXPR collapsing [PR107303] 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/cp-gimplify.cc | 31 +++++++++++++++++++--- gcc/testsuite/g++.dg/ext/builtin-shufflevector-5.C | 14 ++++++++++ gcc/testsuite/g++.dg/init/new51.C | 10 +++++++ 3 files changed, 52 insertions(+), 3 deletions(-) create mode 100644 gcc/testsuite/g++.dg/ext/builtin-shufflevector-5.C create mode 100644 gcc/testsuite/g++.dg/init/new51.C -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-mainline-defconfig updated (4a55322a57 -> adbaf0bad2)

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-arm-mainline-defconfig in repository toolchain/ci/base-artifacts. from 4a55322a57 42: onsuccess: #483: boot: Success after binutils/gcc/linux/ [...] new adbaf0bad2 43: onsuccess: #484: boot: Success after binutils/gcc/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1804 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 31472 -> 31448 bytes 04-build_abe-stage1/console.log.xz | Bin 92212 -> 91732 bytes 05-build_abe-qemu/console.log.xz | Bin 32492 -> 32448 bytes 06-build_linux/console.log.xz | Bin 6008 -> 6960 bytes 07-boot_linux/console.log.xz | Bin 5660 -> 5648 bytes 08-check_regression/console.log.xz | Bin 4348 -> 4340 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/gnu-arm-master-O3 updated (42150a82dd -> 0d83996efb)

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-spec2k6/gnu-arm-master-O3 in repository toolchain/ci/base-artifacts. from 42150a82dd 52: force: #16: 1: [TCWG CI] 465.tonto failed to build after [...] new 0d83996efb 53: onsuccess: #17: 1: [TCWG CI] 465.tonto built and run OK [...] 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 1832 -> 1892 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 32896 -> 33056 bytes 04-build_abe-stage1/console.log.xz | Bin 93628 -> 93764 bytes 06-build_abe-linux/console.log.xz | Bin 8236 -> 7988 bytes 07-build_abe-glibc/console.log.xz | Bin 238552 -> 237724 bytes 08-build_abe-stage2/console.log.xz | Bin 214968 -> 216440 bytes 09-benchmark/benchmark-build.log | 112 +- 09-benchmark/benchmark.log | 110 +- 09-benchmark/console.log.xz | Bin 3868 -> 3852 bytes 10-check_regression/console.log.xz | Bin 16068 -> 15804 bytes .../csv-results-vs-first-1/md5sum.csv | 2054 +- .../csv-results-vs-first-1/perf.csv | 2977 +- .../csv-results-vs-first-1/results.csv | 34917 +- .../csv-results-vs-first-1/size.csv | 257189 ++++++------ 10-check_regression/csv-results-vs-first-1/sve.csv | 14931 +- .../csv-results-vs-first-1/vect.csv | 217 +- .../csv-results-vs-prev-0/md5sum.csv | 2548 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 2909 +- .../csv-results-vs-prev-0/results.csv | 54429 +-- 10-check_regression/csv-results-vs-prev-0/size.csv | 382508 +++++++++--------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 15820 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 386 +- .../csv-results-vs-prev-1/md5sum.csv | 2054 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 2977 +- .../csv-results-vs-prev-1/results.csv | 34917 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 257189 ++++++------ 10-check_regression/csv-results-vs-prev-1/sve.csv | 14931 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 217 +- 10-check_regression/exe.improvement | 2 +- 10-check_regression/exe.regression | 2 - 10-check_regression/extra-bisect-params | 2 +- 10-check_regression/jira-body.txt | 3 +- 10-check_regression/mail-body.txt | 3 +- 10-check_regression/mail-subject.txt | 2 +- 10-check_regression/results-vs-first-brief.csv | 58 +- 10-check_regression/results-vs-first-full.csv | 2888 +- 10-check_regression/results-vs-first-internal.csv | 225 +- 10-check_regression/results-vs-first.csv | 225 +- 10-check_regression/results-vs-first.log | 1185 +- 10-check_regression/results-vs-prev-brief.csv | 58 +- 10-check_regression/results-vs-prev-compare.csv | 11 +- 10-check_regression/results-vs-prev-full.csv | 3130 +- 10-check_regression/results-vs-prev-internal.csv | 227 +- 10-check_regression/results-vs-prev.csv | 227 +- 10-check_regression/results-vs-prev.log | 1441 +- 10-check_regression/results.regressions | 6 - 10-check_regression/skipped-symbols.txt | 4 +- 10-check_regression/trigger-bisect | 3 - 10-check_regression/trigger-notify | 0 11-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 10 +- .../squad-vs-first/401.bzip2/results-metadata.json | 10 +- .../squad-vs-first/401.bzip2/results-metrics.json | 2 +- .../squad-vs-first/403.gcc/results-metadata.json | 10 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../410.bwaves/results-metadata.json | 10 +- .../416.gamess/results-metadata.json | 10 +- .../squad-vs-first/429.mcf/results-metadata.json | 10 +- .../squad-vs-first/433.milc/results-metadata.json | 10 +- .../434.zeusmp/results-metadata.json | 10 +- .../435.gromacs/results-metadata.json | 10 +- .../436.cactusADM/results-metadata.json | 10 +- .../437.leslie3d/results-metadata.json | 10 +- .../squad-vs-first/444.namd/results-metadata.json | 10 +- .../squad-vs-first/444.namd/results-metrics.json | 2 +- .../squad-vs-first/445.gobmk/results-metadata.json | 10 +- .../447.dealII/results-metadata.json | 10 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 10 +- .../squad-vs-first/450.soplex/results-metrics.json | 2 +- .../453.povray/results-metadata.json | 10 +- .../454.calculix/results-metadata.json | 10 +- .../squad-vs-first/456.hmmer/results-metadata.json | 10 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 10 +- .../459.GemsFDTD/results-metadata.json | 10 +- .../462.libquantum/results-metadata.json | 10 +- .../464.h264ref/results-metadata.json | 10 +- .../464.h264ref/results-metrics.json | 2 +- .../465.tonto/results-functional.json | 4 +- .../squad-vs-first/465.tonto/results-metadata.json | 10 +- .../squad-vs-first/465.tonto/results-metrics.json | 3 + .../squad-vs-first/470.lbm/results-metadata.json | 10 +- .../471.omnetpp/results-metadata.json | 10 +- .../squad-vs-first/473.astar/results-metadata.json | 10 +- .../squad-vs-first/481.wrf/results-metadata.json | 10 +- .../482.sphinx3/results-metadata.json | 10 +- .../482.sphinx3/results-metrics.json | 2 +- .../483.xalancbmk/results-metadata.json | 10 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 128 +- dashboard/squad-vs-first/summary-annotation.txt | 1 - git/linux_rev | 2 +- jenkins/jira-status.draft | 4 - jenkins/mail-body.draft | 443 - jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/jira-body.txt | 14 +- mail/mail-body.txt | 14 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 6 - results_id | 2 +- 107 files changed, 579270 insertions(+), 514788 deletions(-) delete mode 100644 10-check_regression/exe.regression delete mode 100644 10-check_regression/results.regressions delete mode 100644 10-check_regression/trigger-bisect delete mode 100644 10-check_regression/trigger-notify delete mode 100644 jenkins/jira-status.draft delete mode 100644 jenkins/mail-body.draft delete mode 100644 jenkins/mail-recipients.draft delete mode 100644 jenkins/mail-subject.draft delete mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-next-allmodconfig updated (f31dbf65c1 -> f3797926f5)

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-next-allmodconfig in repository toolchain/ci/base-artifacts. from f31dbf65c1 40: onsuccess: #570: 23869: Success after binutils/gcc/linux [...] new f3797926f5 41: onsuccess: #571: 23874: Success after binutils/gcc/linux [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1800 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 31980 -> 31524 bytes 04-build_abe-stage1/console.log.xz | Bin 73788 -> 73832 bytes 05-build_abe-qemu/console.log.xz | Bin 32492 -> 32908 bytes 06-build_linux/console.log.xz | Bin 13272 -> 13404 bytes 08-check_regression/console.log.xz | Bin 4484 -> 4648 bytes 08-check_regression/mail-body.txt | 4 ++-- 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 | 6 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 18 files changed, 29 insertions(+), 29 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-defconfig updated (ba10a3e59c -> f7034919af)

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-defconfig in repository toolchain/ci/base-artifacts. from ba10a3e59c 47: onsuccess: #523: boot: Success after binutils/llvm/linux [...] new f7034919af 48: onsuccess: #524: boot: Success after binutils/llvm/linux [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1780 -> 1992 bytes 02-prepare_abe/console.log.xz | Bin 2804 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31664 -> 31316 bytes 04-build_kernel_llvm/console.log.xz | Bin 66300 -> 65948 bytes 05-build_abe-qemu/console.log.xz | Bin 32696 -> 32380 bytes 06-build_linux/console.log.xz | Bin 3516 -> 3392 bytes 07-boot_linux/console.log.xz | Bin 6164 -> 6140 bytes 08-check_regression/console.log.xz | Bin 4528 -> 4332 bytes 08-check_regression/mail-body.txt | 4 ++-- 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 | 6 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 19 files changed, 29 insertions(+), 29 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 updated (e5a738040e -> ecefc26ff6)

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 e5a738040e 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 7ade8b8d19 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards 6729bc5284 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] discards 0dbd7bbc3b 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards 656311711c 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards 0543496d7b 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards bf5591f211 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards 8bb6f7479c 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards 1a83babf41 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] discards e808dbfcef 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] discards 73bb489306 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] discards c3e9382e8a 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] discards 8131132490 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] discards 1268e732de 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] discards 962d443f42 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] discards ccc193cdf8 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] discards d8b9c1fdbd 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] discards f0186f3dc0 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] discards 4802636de0 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] discards 275975d74d 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] discards de7c23641b 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits discards c89548fb27 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits discards 21b28df8b0 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits discards 55bb4d2aac 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] discards 156c8ae707 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits discards 5aa27fd5fc 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards 30bca34497 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards 09e8d6ca5f 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards bafe104b3a 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards 10825cfe6a 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards e11ce3c124 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards 0f36d14990 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards 14302cb333 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards ee3facc789 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards 2c15f7eb6d 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards ac2f8586b9 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards dc67ae4cb6 122: onsuccess: #909: 1: Success after linux: 2753 commits discards d9e6d46304 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 294ec3c5d4 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 803e5ad626 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards 93ea03187a 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards fc50eb94ef 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards 5dc773df5f 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards e7c12b9a44 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards 2d02824afe 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards bed138e454 113: onsuccess: #898: 1: Success after linux: 3 commits discards 923fc2c06d 112: onsuccess: #896: 1: Success after binutils: 24 commits discards b3cccef7f8 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards edff01cb70 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards d364a5babd 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards 9eaad1d707 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 810f6f89e0 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards ea8604dfdf 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 5b4cc6a0eb 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 0415bc96da 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards 52c35bc40c 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards 5aa78bbdca 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards 9b6f9abcc7 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards b4ed8e8293 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards eef76d9717 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 21016a2af7 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards 10a7587f60 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards b632d2309c 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards 9f8211ce2a 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards b46bfbbdf2 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards 57e1bcf4e7 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards d567a21446 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards d028cf7c0e 91: onsuccess: #870: 1: Success after binutils: 5 commits discards ddefc6c964 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 4e2cb4479e 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 04ab187d30 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards 7adbe6bcb0 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards e4704e99ae 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards 289a1240d5 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards 668a2350d5 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards 14235e25c1 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards bba32c0924 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards 6eaf86e9fe 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards f179687943 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards 5befe675b3 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards aaba4d86be 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards d8b25f686a 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards d2626fdb79 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards a94d4ed0a0 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards ebc64b5ee2 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards 44c0a1afa9 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards 3e4d7fc5a9 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards 53711a04db 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards 71193e71e9 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards 31140b15e0 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards 954dc4c4d8 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards 597741c244 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards 154ab92952 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards 38fbd2f9f5 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards e55591b180 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards f23da1fc4e 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards 567a415c92 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards b9b72a8806 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards 4591f7254f 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards c699ba563c 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards 5aa3fa4b8e 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new 32bb6837ce 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new d876cb7cca 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new e30a12260e 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new f1ad04fd31 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new 8f2c755144 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new 9d8729494b 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new c3ada3ffb5 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new 459f831532 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new d7843ddfe5 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new 93d7aef22a 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new dcaa6fef39 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new 999b3b0325 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new c35fac56fa 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new 406aae64ae 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new 11aa29036d 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new 86e9a0e949 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new f5c8a70838 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new 8ef0109c2a 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new 364fbde786 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new 734f1c22fe 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new 45cc809cc1 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new 9c452e7691 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new 52db9c97f3 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 2fd9a29b90 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new 2ef114d425 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new 44ecef0bb1 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new 91f64186d3 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new 4e7471e275 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new 2be43920a2 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new ce1ebf0674 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new 8efa82687c 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new 35eb762eac 89: onsuccess: #864: 1: Success after binutils: 25 commits new 8d5edd3651 90: onsuccess: #867: 1: Success after binutils: 4 commits new 61e3a4540e 91: onsuccess: #870: 1: Success after binutils: 5 commits new aefa98721c 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new 2ed1e36f95 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 7568ba0d88 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new bfc72c00c8 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new 28b1fe45cc 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new 44d2acd31e 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new a75760dc3c 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new 1e09f6df88 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 563d877cdf 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new 8ecd5a68b3 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new da983e6b2e 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new fb22ddcdbe 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new 660c2cf7b7 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new 645557a5cd 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new c01a0b9751 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 36862f5375 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new 9a2cdab5e6 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 24378c86c8 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new 7f76303003 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 208e8783be 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new bd0b5a2b66 112: onsuccess: #896: 1: Success after binutils: 24 commits new 379736f075 113: onsuccess: #898: 1: Success after linux: 3 commits new 2c3c9c6a65 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new 42770bbabd 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new db37ad14d4 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new 62bf662b0c 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new a46881734f 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new 4588245016 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new 0206861f1e 120: onsuccess: #906: 1: Success after binutils: 29 commits new c31b0d0715 121: onsuccess: #908: 1: Success after glibc: 2 commits new 5a7e6614d1 122: onsuccess: #909: 1: Success after linux: 2753 commits new 6c0c891df7 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new 24bbc3cb77 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new a4d01baa0a 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new 63496ddad5 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new 5a5507a8ad 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new 0c1f9cc58c 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new 50ed68c3ec 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new 9bc94b8cfa 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new 7dbf2816c5 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new ffdaab1688 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new 53b839a35e 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new 60379a52b6 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits new 2ab8bbcb6d 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] new 795b08621e 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits new 956e261915 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits new aa9bf4f0f7 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits new bda6dfacd7 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new b5c69e9d69 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] new ebabc93f0e 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] new 518fe1e6a3 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] new b6585accbd 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new 34fcf15234 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] new d9df688288 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new 560a06f4bd 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new d4441313ae 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] new 51f892ad33 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] new f832300814 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] new e8ad906615 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new cf39400dda 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new 16caef502e 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new 3c956e1fda 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new 449bee130b 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new 63938d981a 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new 2fc3d1d878 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new be820572ef 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new d366c70ed4 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new ecefc26ff6 159: onsuccess: #952: 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 (e5a738040e) \ 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 1748 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 38700 -> 38676 bytes 04-build_abe-gcc/console.log.xz | Bin 213984 -> 213980 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8680 -> 8712 bytes 07-build_abe-glibc/console.log.xz | Bin 244232 -> 244308 bytes 08-build_abe-gdb/console.log.xz | Bin 38236 -> 38316 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3840 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2020 -> 2016 bytes 11-check_regression/console.log.xz | Bin 12484 -> 13780 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 78 +- 11-check_regression/mail-body.txt | 219 +- 11-check_regression/results.compare | 100 +- 11-check_regression/results.compare2 | 4978 +++++++++++---------- 11-check_regression/results.regressions | 106 +- 12-update_baseline/console.log | 38 +- 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 | 221 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 106 +- sumfiles/gdb.log.xz | Bin 1964516 -> 1962544 bytes sumfiles/gdb.sum | 7125 ++++++++++++++++++------------- 31 files changed, 7460 insertions(+), 5567 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-mainline-defconfig updated (9065c469a5 -> 45a615791e)

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-mainline-defconfig in repository toolchain/ci/base-artifacts. from 9065c469a5 39: onsuccess: #508: boot: Success after binutils/llvm/linux [...] new 45a615791e 40: onsuccess: #509: boot: Success after binutils/llvm/linux [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1796 -> 1992 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 32792 -> 31748 bytes 04-build_kernel_llvm/console.log.xz | Bin 66116 -> 66216 bytes 05-build_abe-qemu/console.log.xz | Bin 31816 -> 32752 bytes 06-build_linux/console.log.xz | Bin 4088 -> 3964 bytes 07-boot_linux/console.log.xz | Bin 6196 -> 6232 bytes 08-check_regression/console.log.xz | Bin 4644 -> 4452 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 18 files changed, 28 insertions(+), 28 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[binutils-gdb] branch master updated (844be75db5f -> 7ebf464bbd5)

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 844be75db5f Automatic date update in version.in new 7ebf464bbd5 ld: Avoid magic numbers for subsystems in pe.em and pep.em 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: ld/emultempl/pe.em | 8 ++++---- ld/emultempl/pep.em | 4 ++-- 2 files changed, 6 insertions(+), 6 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[gcc] branch releases/gcc-11 updated (7566551ea41 -> 429699a4a80)

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-11 in repository gcc. from 7566551ea41 Daily bump. new 429699a4a80 Daily bump. 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/DATESTAMP | 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, 10 months

[gcc] branch releases/gcc-12 updated (ea99f8d0f66 -> 7ec291e86b2)

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 ea99f8d0f66 Fortran: error recovery for invalid CLASS component [PR108434] new 7ec291e86b2 Daily bump. 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/ChangeLog | 18 ++++++++++++++++++ gcc/DATESTAMP | 2 +- gcc/fortran/ChangeLog | 10 ++++++++++ gcc/testsuite/ChangeLog | 16 ++++++++++++++++ 4 files changed, 45 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits January 2023