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-cpu2017fast/gnu-aarch64-master-Os updated (56013cfb03 -> bc60501e52)

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-cpu2017fast/gnu-aarch64-master-Os in repository toolchain/ci/base-artifacts. from 56013cfb03 0: init: #1: 1: [TCWG CI] No change after baseline build: no [...] new bc60501e52 1: onsuccess: #2: 1: [TCWG CI] No change after binutils/gcc/ [...] 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 2508 -> 1792 bytes 01-reset_artifacts/patch-env.sh | 2 - 02-prepare_abe/console.log.xz | Bin 2760 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 30752 -> 31392 bytes 04-build_abe-stage1/console.log.xz | Bin 71540 -> 71952 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8604 -> 8612 bytes 07-build_abe-glibc/console.log.xz | Bin 244932 -> 246176 bytes 08-build_abe-stage2/console.log.xz | Bin 177972 -> 176596 bytes 09-benchmark/benchmark-build.log | 123 +- 09-benchmark/benchmark.log | 121 +- 09-benchmark/console.log.xz | Bin 3956 -> 3864 bytes .../compare-results-vs-first-internal.csv | 170 +- .../compare-results-vs-prev-internal.csv | 170 +- 10-check_regression/console.log.xz | Bin 10088 -> 12164 bytes .../csv-results-vs-first-0/md5sum.csv | 2064 +- .../csv-results-vs-first-0/results.csv | 1006226 ++++++++-------- .../csv-results-vs-first-0/size.csv | 1006460 ++++++++-------- 10-check_regression/csv-results-vs-first-0/sve.csv | 26 +- .../csv-results-vs-first-0/vect.csv | 32 +- .../csv-results-vs-first-1/md5sum.csv | 2551 +- .../csv-results-vs-first-1/perf.csv | 2900 +- .../csv-results-vs-first-1/results.csv | 1006882 ++++++++-------- .../csv-results-vs-first-1/size.csv | 1007020 +++++++++-------- 10-check_regression/csv-results-vs-first-1/sve.csv | 26 +- .../csv-results-vs-first-1/vect.csv | 32 +- .../csv-results-vs-prev-0/md5sum.csv | 2064 +- .../csv-results-vs-prev-0/results.csv | 1006226 ++++++++-------- 10-check_regression/csv-results-vs-prev-0/size.csv | 1006460 ++++++++-------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 26 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 32 +- .../csv-results-vs-prev-1/md5sum.csv | 2551 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 2900 +- .../csv-results-vs-prev-1/results.csv | 1006882 ++++++++-------- 10-check_regression/csv-results-vs-prev-1/size.csv | 1007020 +++++++++-------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 26 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 32 +- 10-check_regression/results-vs-first-brief.csv | 50 +- 10-check_regression/results-vs-first-full.csv | 2934 +- 10-check_regression/results-vs-first-internal.csv | 170 +- 10-check_regression/results-vs-first.csv | 170 +- 10-check_regression/results-vs-first.log | 1090 +- 10-check_regression/results-vs-prev-brief.csv | 50 +- 10-check_regression/results-vs-prev-compare.csv | 8 +- 10-check_regression/results-vs-prev-full.csv | 2934 +- 10-check_regression/results-vs-prev-internal.csv | 170 +- 10-check_regression/results-vs-prev.csv | 170 +- 10-check_regression/results-vs-prev.log | 1052 +- 11-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- .../508.namd_r/results-metadata.json | 14 +- .../squad-vs-first/508.namd_r/results-metrics.json | 2 +- .../510.parest_r/results-metadata.json | 14 +- .../510.parest_r/results-metrics.json | 2 +- .../511.povray_r/results-metadata.json | 14 +- .../511.povray_r/results-metrics.json | 2 +- .../526.blender_r/results-metadata.json | 14 +- .../526.blender_r/results-metrics.json | 2 +- .../600.perlbench_s/results-metadata.json | 14 +- .../600.perlbench_s/results-metrics.json | 2 +- .../squad-vs-first/602.gcc_s/results-metadata.json | 14 +- .../squad-vs-first/602.gcc_s/results-metrics.json | 2 +- .../603.bwaves_s/results-metadata.json | 14 +- .../603.bwaves_s/results-metrics.json | 2 +- .../squad-vs-first/605.mcf_s/results-metadata.json | 14 +- .../squad-vs-first/605.mcf_s/results-metrics.json | 2 +- .../607.cactuBSSN_s/results-metadata.json | 14 +- .../607.cactuBSSN_s/results-metrics.json | 2 +- .../squad-vs-first/619.lbm_s/results-metadata.json | 14 +- .../squad-vs-first/619.lbm_s/results-metrics.json | 2 +- .../620.omnetpp_s/results-metadata.json | 14 +- .../620.omnetpp_s/results-metrics.json | 2 +- .../squad-vs-first/621.wrf_s/results-metadata.json | 14 +- .../squad-vs-first/621.wrf_s/results-metrics.json | 2 +- .../623.xalancbmk_s/results-metadata.json | 14 +- .../623.xalancbmk_s/results-metrics.json | 2 +- .../625.x264_s/results-metadata.json | 14 +- .../squad-vs-first/625.x264_s/results-metrics.json | 2 +- .../627.cam4_s/results-metadata.json | 14 +- .../628.pop2_s/results-metadata.json | 14 +- .../squad-vs-first/628.pop2_s/results-metrics.json | 2 +- .../631.deepsjeng_s/results-metadata.json | 14 +- .../631.deepsjeng_s/results-metrics.json | 2 +- .../638.imagick_s/results-metadata.json | 14 +- .../638.imagick_s/results-metrics.json | 2 +- .../641.leela_s/results-metadata.json | 14 +- .../641.leela_s/results-metrics.json | 2 +- .../squad-vs-first/644.nab_s/results-metadata.json | 14 +- .../squad-vs-first/644.nab_s/results-metrics.json | 2 +- .../648.exchange2_s/results-metadata.json | 14 +- .../649.fotonik3d_s/results-metadata.json | 14 +- .../649.fotonik3d_s/results-metrics.json | 2 +- .../654.roms_s/results-metadata.json | 14 +- .../squad-vs-first/654.roms_s/results-metrics.json | 2 +- .../squad-vs-first/657.xz_s/results-metadata.json | 14 +- .../squad-vs-first/657.xz_s/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 14 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 102 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 20 +- mail/mail-body.txt | 20 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results_id | 2 +- 106 files changed, 4040107 insertions(+), 4038297 deletions(-) delete mode 100644 01-reset_artifacts/patch-env.sh -- 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-fujitsu_speed-cpu2017rate/gnu-aarch64-master-O3 deleted (was 98def9e7f4)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. laurent.alfonsi pushed a change to branch linaro-local/ci/tcwg_bmk-fujitsu_speed-cpu2017rate/gnu-aarch64-master-O3 in repository toolchain/ci/base-artifacts. was 98def9e7f4 53: onsuccess: #46: 1: [TCWG CI] 549.fotonik3d_r built and r [...] This change permanently discards the following revisions: discards 98def9e7f4 53: onsuccess: #46: 1: [TCWG CI] 549.fotonik3d_r built and r [...] discards 3d67d17ec0 52: force: #43: 1: [TCWG CI] 549.fotonik3d_r failed to build [...] discards 39e00b7076 51: force: #42: 1: [TCWG CI] 525.x264_r:[.] mc_chroma slowed [...] discards 602ddfd703 50: force: #41: 1: [TCWG CI] 538.imagick_r slowed down by 4% [...] discards 7d4975b2b4 49: onsuccess: #29: 1: [TCWG CI] No change after baseline bu [...] discards d652501080 48: force: #28: 1: [TCWG CI] 531.deepsjeng_r speeds up by -4 [...] discards 0dd9f52259 47: force: #27: 1: [TCWG CI] 531.deepsjeng_r slowed down by [...] discards 320806c9af 46: onsuccess: #25: 1: [TCWG CI] No change after glibc: 45 commits discards b96200d60d 45: onsuccess: #24: 1: [TCWG CI] No change after gcc: 245 commits discards d494e783db 44: onsuccess: #20: 1: [TCWG CI] 500.perlbench_r speeds up b [...] discards be0311b332 43: force: #19: 1: [TCWG CI] No change after baseline build: [...] discards 7392adbd3b 42: onsuccess: #17: 1: [TCWG CI] No change after v6.1.8-4559 [...] discards f55d7667d0 41: onsuccess: #16: 1: [TCWG CI] No change after glibc: 7 commits discards 2640499cfb 40: force: #12: 1: [TCWG CI] No change after baseline build: [...] discards d4c4494e3d 39: onsuccess: #9: 1: [TCWG CI] No change after binutils: 60 [...] discards 80d73799e4 38: onsuccess: #7: 1: [TCWG CI] No change after v6.1.7-45589 [...] discards cf8cdce0a3 37: onsuccess: #6: 1: [TCWG CI] No change after glibc: 14 commits discards b5c1beb669 36: onsuccess: #5: 1: [TCWG CI] No change after gcc: 71 commits discards 46cbd60ed0 35: onsuccess: #4: 1: [TCWG CI] No change after binutils: 38 [...] discards 18d0b2162f 34: onsuccess: #2: 1: [TCWG CI] No change after binutils/gcc [...] discards 6219f0ffd9 33: onsuccess: #1: 1: [TCWG CI] No change after binutils/gcc [...] discards 7f8420f89d 32: onsuccess: #10: 1: [TCWG CI] No change after baseline bu [...] discards df05d52baf 31: force: #9: 1: [TCWG CI] No change after basepoints/gcc-1 [...] discards 4696d18d34 30: force: #8: 1: [TCWG CI] 549.fotonik3d_r built and run OK [...] discards 42e6ddcfd8 29: force: #7: 1: [TCWG CI] 549.fotonik3d_r failed to build [...] discards 2e0c9ab3ba 28: onsuccess: #6: 1: [TCWG CI] No change after v6.0.17-4168 [...] discards d9b84fadd7 27: onsuccess: #5: 1: [TCWG CI] No change after glibc: 2 commits discards 619cd53700 26: onsuccess: #1: 1: [TCWG CI] No change after binutils/gcc [...] discards fc7eabf012 25: onsuccess: #82: 1: [TCWG CI] 503.bwaves_r built and run [...] discards 7673b9401d 24: onsuccess: #81: 1: [TCWG CI] No change after binutils/gc [...] discards 50b0f27388 23: force: #80: 1: [TCWG CI] 503.bwaves_r failed to build af [...] discards 178a0b6b6c 22: onsuccess: #79: 1: [TCWG CI] No change after glibc-2.36. [...] discards 2d02d4d807 21: onsuccess: #77: 1: [TCWG CI] No change after gcc: 142 commits discards 6741fcf4a7 20: onsuccess: #74: 1: [TCWG CI] No change after baseline bu [...] discards b8808a7393 19: force: #73: 1: [TCWG CI] No change after v6.0.15-41683-g [...] discards ea4b6a0653 18: force: #72: 1: [TCWG CI] No change after v6.0.14-41682-g [...] discards 9ba791088c 17: onsuccess: #70: 1: [TCWG CI] No change after glibc: 25 commits discards fbe4f5b297 16: onsuccess: #65: 1: [TCWG CI] No change after binutils/gc [...] discards a4239c0afe 15: onsuccess: #56: 1: [TCWG CI] No change after gcc: 55 commits discards be81a8aee4 14: onsuccess: #55: 1: [TCWG CI] No change after binutils: 5 [...] discards 9a31ad328b 13: onsuccess: #53: 1: [TCWG CI] No change after binutils/gc [...] discards c51618bcb3 12: force: #52: 1: [TCWG CI] 531.deepsjeng_r:[.] _Z5fevalP7s [...] discards 4e835e7ca5 11: onsuccess: #51: 1: [TCWG CI] No change after v6.0.10-416 [...] discards 53e84f6c43 10: onsuccess: #50: 1: [TCWG CI] 554.roms_r built and run OK [...] discards 806ee935cf 9: force: #41: 1: [TCWG CI] 527.cam4_r failed to build after [...] discards db45499ea1 8: onsuccess: #37: 1: [TCWG CI] No change after binutils/gcc [...] discards 452743fca3 7: onsuccess: #36: 1: [TCWG CI] No change after baseline bui [...] discards 858c62753e 6: force: #35: 1: Failure after gcc: 3349 commits discards e78b8d1a1e 5: force: #32: -6: Failure after basepoints/gcc-13-754-ga1c9 [...] discards 9cbc63bbb9 4: force: #31: -6: Failure after gcc: 1121 commits discards 0379bf23e5 3: force: #30: 1: [TCWG CI] No change after baseline build: [...] discards 8eaa66cf50 2: onsuccess: #29: 1: [TCWG CI] No change after linux: 94897 [...] discards 597fa78137 1: onsuccess: #28: 1: [TCWG CI] No change after glibc: 728 commits discards 118e0b7310 0: init: #24: 1: [TCWG CI] No change after baseline build: n [...] -- 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_aosp-code_size-surfaceflinger--oriole-master deleted (was 624381316d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. laurent.alfonsi pushed a change to branch linaro-local/ci/tcwg_aosp-code_size-surfaceflinger--oriole-master in repository toolchain/ci/base-artifacts. was 624381316d 2: force: #15: 0: Failure after llvmorg-17-init-3240-g02828a [...] This change permanently discards the following revisions: discards 624381316d 2: force: #15: 0: Failure after llvmorg-17-init-3240-g02828a [...] discards fcd3804ef3 1: force: #12: 0: Failure after llvmorg-17-init-3239-g025952 [...] discards 79e8197676 0: init: #10: 0: Success after baseline build: no new commits -- 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-vect_speed-cpu2017/llvm-aarch64-master-O3_VECT deleted (was 7202ae822c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. laurent.alfonsi pushed a change to branch linaro-local/ci/tcwg_bmk-vect_speed-cpu2017/llvm-aarch64-master-O3_VECT in repository toolchain/ci/base-artifacts. was 7202ae822c 20: onsuccess: #13: 1: [TCWG CI] No change after binutils/gc [...] This change permanently discards the following revisions: discards 7202ae822c 20: onsuccess: #13: 1: [TCWG CI] No change after binutils/gc [...] discards 6e94e6df92 19: onsuccess: #12: 1: [TCWG CI] No change after binutils/gc [...] discards e6f65af51b 18: onsuccess: #10: 1: [TCWG CI] No change after binutils/gc [...] discards 153fdd4357 17: onsuccess: #9: 1: [TCWG CI] No change after binutils/gcc [...] discards 1195bc9fdd 16: onsuccess: #8: 1: [TCWG CI] No change after binutils/gcc [...] discards 47072b11c5 15: onsuccess: #7: 1: [TCWG CI] No change after binutils/gcc [...] discards 38f3d7afbd 14: onsuccess: #6: 1: [TCWG CI] No change after binutils/gcc [...] discards b4351a0a8f 13: onsuccess: #5: 1: [TCWG CI] No change after binutils/gcc [...] discards 95987ea37f 12: onsuccess: #4: 1: [TCWG CI] No change after binutils/gcc [...] discards c1e7bebb55 11: onsuccess: #3: 1: [TCWG CI] No change after binutils/gcc [...] discards e94dda43a6 10: onsuccess: #3: 1: [TCWG CI] No change after binutils/gcc [...] discards b5f6356a2a 9: onsuccess: #2: 1: [TCWG CI] No change after binutils/gcc/ [...] discards 85d642d7e7 8: onsuccess: #55: 1: [TCWG CI] No change after binutils/gcc [...] discards d2e07daf62 7: onsuccess: #54: 1: [TCWG CI] No change after binutils/gcc [...] discards d405e1a4a4 6: onsuccess: #36: 1: [TCWG CI] No change after binutils/gcc [...] discards a21abd0bab 5: onsuccess: #34: 1: [TCWG CI] No change after glibc: 7 commits discards 022db01f03 4: onsuccess: #32: 1: [TCWG CI] No change after binutils: 37 [...] discards c181ae0f91 3: onsuccess: #30: 1: [TCWG CI] No change after binutils/gcc [...] discards 6fbbae1344 2: onsuccess: #29: 1: [TCWG CI] No change after binutils/gcc [...] discards 3c2f096fcf 1: onsuccess: #28: 1: [TCWG CI] No change after binutils/gcc [...] discards 5095035e5f 0: init: #27: 1: [TCWG CI] No change after baseline build: n [...] -- 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-vect_speed-cpu2017/gnu-aarch64-master-O3_VECT deleted (was d76f196938)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. laurent.alfonsi pushed a change to branch linaro-local/ci/tcwg_bmk-vect_speed-cpu2017/gnu-aarch64-master-O3_VECT in repository toolchain/ci/base-artifacts. was d76f196938 8: onsuccess: #13: 1: [TCWG CI] No change after binutils/gcc [...] This change permanently discards the following revisions: discards d76f196938 8: onsuccess: #13: 1: [TCWG CI] No change after binutils/gcc [...] discards e62bc99a66 7: onsuccess: #12: 1: [TCWG CI] No change after binutils/gcc [...] discards 38b35829be 6: onsuccess: #8: 1: [TCWG CI] No change after binutils/gcc/ [...] discards e704a1d088 5: onsuccess: #7: 1: [TCWG CI] No change after binutils/gcc/ [...] discards fa973b49d5 4: onsuccess: #6: 1: [TCWG CI] No change after binutils/gcc/ [...] discards 5e6714a5f3 3: onsuccess: #5: 1: [TCWG CI] No change after binutils/gcc/ [...] discards 06f337deaa 2: onsuccess: #4: 1: [TCWG CI] No change after binutils/gcc: [...] discards 4a8aaf2ca1 1: onsuccess: #3: 1: [TCWG CI] 638.imagick_s increased up by [...] discards e948e4a3d0 0: init: #41: 1: [TCWG CI] No change after baseline build: n [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[binutils-gdb] branch master updated (945efa5c538 -> 67748abf53b)

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 945efa5c538 Tidy type handling in binutils/rdcoff.c new 81588de012f x86: avoid .byte in testcases where possible new e9339bee560 gas: default .debug section compression method adjustments new 43da3d648ed x86: drop redundant calculation of EVEX broadcast size new 67748abf53b x86: use swap_2_operands() in build_vex_prefix() 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: gas/as.c | 9 +- gas/config/tc-i386.c | 23 +-- gas/testsuite/gas/i386/notrack.s | 11 +- gas/testsuite/gas/i386/opcode.s | 2 +- gas/testsuite/gas/i386/prefix.s | 339 +++++++++++++------------------- gas/testsuite/gas/i386/x86-64-notrack.s | 20 +- 6 files changed, 162 insertions(+), 242 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_gnu_native_check_binutils/master-aarch64 updated (38a091a8b8 -> 48f7a8e897)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 in repository toolchain/ci/base-artifacts. discards 38a091a8b8 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 8b3057ebc2 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards db74599c8c 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 69a2342099 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 0ad05d4008 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards af4c74e04a 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards bfdc7329db 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards b897b280ba 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] discards 8f33676d95 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] discards d665c2a80e 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] discards 35ceaa9c8c 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] discards bc023098f9 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] discards ad0544abc3 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] discards 812da004c1 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] discards f6905371bd 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits discards 1100be67f2 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] discards e4c6b90bf2 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] discards 06785d059f 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] discards ca07bfdd22 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] discards f92c43a56b 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] discards 206e42c06b 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] discards 2e1b54511e 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] discards a1b4c101f4 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] discards 9077ef5d60 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] discards 724a1a8f86 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] discards 5af0ac7ca7 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] discards 9656bece12 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] discards d2be15e243 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] discards 0ce37a6e93 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] discards 58cdf8bc8e 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] discards a32eee8ca2 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] discards 2318f435e3 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] discards 1d830f40b2 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] discards 5bcf0eca04 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] discards 2902ff20ef 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] discards fcaa440a3a 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] discards 1f76a41f9f 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] discards 1ab2d58eb1 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards 2400377c69 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] discards 78cfb0404d 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards 0135cc2e16 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] discards 66df9500ea 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] discards 85b47471fc 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] discards 3b359fcc6f 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] discards 4d4cadd279 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] discards a51a16872b 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] discards bd45e35e99 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] discards 5155d9af13 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] discards fe68aaff05 149: onsuccess: #684: 1: Success after linux: 10 commits discards 9740bf6dd6 148: onsuccess: #683: 1: Success after glibc: 9 commits discards af18608ad4 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 0ce0b823ba 146: onsuccess: #680: 1: Success after binutils: 20 commits discards f41dda0b95 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] discards 4cdc7ffa03 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] discards ed56ed23bd 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] discards a4b6b1f06f 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards 80bb062538 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits discards 242181e640 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits discards 789d5ad43a 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits discards b3a1de1915 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards bb02de8689 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits discards 6e8606ab30 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards 94a9e3a962 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards 84a850d9a6 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] discards 56659eec07 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] discards bdfd3dc1f6 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards de378a024e 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] discards 269482a8ed 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards fbcb273ac5 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards 55b391ec43 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] discards a8a3fc3de3 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards cd61f2fa70 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 844a0b4123 125: onsuccess: #658: 1: Success after linux: 3224 commits discards e2d3cb823a 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 65d6161508 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 134a8ef392 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards a62a5d75dc 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards c47c104159 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 03d02b5d5b 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards d14dc4b301 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 0f60399dd4 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] discards 03767ef454 116: onsuccess: #647: 1: Success after linux: 3 commits discards d0cdbf5654 115: onsuccess: #645: 1: Success after binutils: 27 commits discards a264b3c0ab 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards c12d6fe52a 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards 8a9af7975b 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 2756d5af1a 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] discards 2a7df73ef6 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] discards e666f36f71 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] discards b8f1e975a8 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] discards 9ff3d347b4 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] discards 70832c0aec 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards 8e5917fd20 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards 6d8b7c9675 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards 00e7eaa811 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits discards 56c1153b74 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] discards 6c423b0a0b 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] discards edd481a170 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] discards 306b25c7a5 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] discards 747a678e25 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] discards d937406bac 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new dd7d75d138 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 6232f58f82 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] new ef701719bf 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] new 17950fc4e0 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] new 81d44a521d 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] new eb068c66f8 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] new 4a5250c1da 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits new 74d569b014 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new d4f26f2b02 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new c08df83b05 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 4faf580b81 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] new f3f5e448b6 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] new 2a52fd8c89 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] new 243737ab79 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] new 2d0f605ea4 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] new 5cc86006b3 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 974880aaac 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new b19d3f874c 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 08f592b23d 115: onsuccess: #645: 1: Success after binutils: 27 commits new 8ac7f3565c 116: onsuccess: #647: 1: Success after linux: 3 commits new 133258c58b 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] new 1f76a03788 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new 3d878a27a3 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new caa72893fe 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 6f0658e858 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new 64250c01de 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 04bae5b279 123: onsuccess: #655: 1: Success after binutils: 22 commits new 198522d9d1 124: onsuccess: #657: 1: Success after glibc: 2 commits new 02f927d7b2 125: onsuccess: #658: 1: Success after linux: 3224 commits new 4f42ae3179 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new e91bd7b5aa 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new 4c7cb1d757 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] new 2498ba62e7 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new fdd6ad34e6 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new 39c61f3076 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new cebcf93671 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new 8b27077a5c 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] new 301cb67137 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] new 14beb9bd31 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new 2f1a822628 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new e495b85f0c 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits new 963176e92d 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new 07316a961c 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits new 250f286174 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits new 34d876e58c 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits new 6a36c3354c 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new e099d376cc 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] new 704c1e8429 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] new 4ea4710603 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] new 6cbae09ca3 146: onsuccess: #680: 1: Success after binutils: 20 commits new b5a9b5d875 147: onsuccess: #681: 1: Success after gcc: 6 commits new 9f1d2d71e2 148: onsuccess: #683: 1: Success after glibc: 9 commits new 2044351dd2 149: onsuccess: #684: 1: Success after linux: 10 commits new 9a0469d297 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] new 8479bbd7ba 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] new 4128531be2 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] new 663aeada94 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] new 9d8e7e27a1 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] new cd4288e3aa 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] new b5b9508585 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] new e1ce0ddfb2 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] new f3ab670a01 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new 7f4d6a7b5d 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] new b8601b5964 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new b2a1b503ac 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] new b0238ef743 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] new 5005ffa9d2 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] new 0df5dcff1d 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] new d4ef22ba41 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] new 96731c0a53 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] new cb94f63c6f 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] new 819d92dcce 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] new 4c7c02d341 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] new 95239236fd 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] new 0b038ad45a 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] new a901a41c13 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] new d49f4f767f 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] new 4d27c815f5 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] new c77f257484 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] new b9abeddb81 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] new b6d4497494 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] new 93e6ddd9aa 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] new c570f954ac 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] new 0f829f0665 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] new dac9125ab2 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] new ceb6cd77bd 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] new a5d6890731 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits new dbc3cd9be5 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] new 7815ba4b87 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] new 16899de44c 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] new c3e1428a92 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] new ebf08d46e5 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] new 9762f113fb 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] new df06c21b9e 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] new 90a48daf35 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new f5b0ec06b7 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new b656467fc2 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 2da1a5e553 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 918e90126c 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 6edeb28f5d 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 27ab82ed93 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 48f7a8e897 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] 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 (38a091a8b8) \ 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 1752 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 38880 -> 38896 bytes 04-build_abe-gcc/console.log.xz | Bin 203728 -> 203336 bytes 06-build_abe-linux/console.log.xz | Bin 8420 -> 9224 bytes 07-build_abe-glibc/console.log.xz | Bin 243804 -> 244304 bytes 08-build_abe-gdb/console.log.xz | Bin 39108 -> 38588 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3776 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2284 -> 2288 bytes 11-check_regression/console.log.xz | Bin 6196 -> 6284 bytes 11-check_regression/results.compare2 | 4 +- 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 63012 -> 63000 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 83964 -> 83988 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 122256 -> 122284 bytes sumfiles/ld.sum | 4 +- 28 files changed, 67 insertions(+), 67 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_gnu_cross_check_gcc/master-arm updated (7ee4ab9c9f -> 542dee0e1c)

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 7ee4ab9c9f 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 11b3a395df 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 61962757ef 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] discards 08ae3b428a 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 83df5d6624 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 93b7444128 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits discards 3d2a179696 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 5839162127 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 4fe29146b7 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards 11f093c236 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] discards 1b5199fcc8 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] discards f472daaa13 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] discards 993f5ef85b 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] discards e86c276923 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] discards fb9c26ff14 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] discards ec0a1027f2 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards c6422598cd 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] discards ff4a981540 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] discards a91d32e36d 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] discards 32962093c3 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards c5cf19e283 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] discards 7f88e051ef 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] discards 8d90d63b2f 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] discards 65a4203f47 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards f948ca135a 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] discards cefb8c4b9d 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards c0d4dfb980 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards 3a302e53ed 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards d295d16d2a 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards 4415737978 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards 54d8281af8 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards 30ff1df65d 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards 6852352a4b 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards 41a2e9b98d 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards d9fe110e2d 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards 32ee80549a 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards 453d91b5ec 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards 2a5261012b 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards ea93daf1a3 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards ac3025e15f 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 748b0aa5a3 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards f2cda356e9 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards de93e8cd9f 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 9c467cd85f 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 3f4153f1f2 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 5d40124a05 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards a7e472475f 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards d29e46d931 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 1bfec553ae 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards a99eba52cf 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards b0ff2bf951 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 553135c235 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards b31bbcaace 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 2a95bb6e2f 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 94bd96e71f 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 0db326681f 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 40c1aff11f 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 74091b3390 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards aa4e309a2d 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 49bb4788e1 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 17758815e4 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 0c0d80815d 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 3be8511c6c 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards b8f1427fb2 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards a441b970fe 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 73763d3cbb 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards d32f3b46b7 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 17cc2fcc3e 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards e3b7af1d9b 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 15f3b66015 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 1dd2996353 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards c2dcbc5bda 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards d8e8b92e7d 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 55fb8b6674 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards fcc7912208 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards b1b9354d52 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards edd6ca059b 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards ff7a974137 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 33d6b563d9 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards f7eebea38e 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 9d3479b90b 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 6a52766161 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards d178af9d2d 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 3a3342fe58 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 04419d2a8d 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 2acc62777a 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 98b5dd330e 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards abeae7e1ab 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 97e7d970a8 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 8daec411f4 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards f8ac4a3e76 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards fb235f4f32 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards d7ae3e905a 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 053c508b75 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 2e8e7add97 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 5ddb593742 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 1c17bac708 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 2b359844a9 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards d78f989af1 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 8fae905ecd 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 5850946b7f 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 2fdc14d134 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 6696498fa6 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 3af861c1e6 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 1e093149ae 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new f9aa97ca39 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new d5b2e8c4ec 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 2a7abc1d38 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 18f3c9adb8 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new a2bf368a3d 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 75da8cbc6d 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 178e253972 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 2725bdecee 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 01766db818 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new f4cd96c8c5 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 9f99864084 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 4e2c8e99b6 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 00ffd13ecc 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 0daa82b830 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new dfb92ce265 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new e1a1d64db0 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 2e5d579851 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 16cd941a0e 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new e7aa0fe9b1 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 942842b6fb 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new c201d6ceb5 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 6b159aff3c 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new cfe1106225 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 8eccf7f6fc 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 8d9b58b974 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 9e11f4cd65 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 6ae811f21b 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 850e11755e 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new c6e0e4c0e2 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new eff54d2b7f 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 58f50048f7 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 16bfb46846 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 0f480bcf6f 387: onsuccess: #2208: 1: Success after gcc: 2 commits new e6b976fa1b 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 844bb6604b 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new c9f36a7fb5 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new ed3d08c33a 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 81c00b789c 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 82b52995a6 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new fb172a12ff 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 2e35d4ade5 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new ebee3a7192 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new f65f09abb8 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 4b9b91c633 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 7cba44d81e 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 66016de01d 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 8904237890 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new eef4b05637 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new f73f975a42 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new ba05a01f9f 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 6b178b7884 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 7a9ce16a97 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 1f6453af60 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 0b8a827419 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new d562797f2d 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new b86d6b1a96 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new cb83c4a7b9 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 2a0a4ddc74 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new b119a559a0 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new 8d447f66c3 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new db56d4f184 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new f16b33f92d 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new 5321f03093 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new e933d2cd49 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new 3914ead423 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new fdab7d4e83 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new c6038a6a12 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new aeee207552 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new 0485b8ce7b 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new cc107fc160 424: onsuccess: #2248: 1: Success after gcc: 6 commits new 9007378435 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new dfb6e474c0 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new cad39197d9 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] new 8ff8488a8f 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new d7bb0ee720 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] new 86db32c5bc 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] new 7480bf1e6d 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] new 7a4c3d9a10 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new b15b703e6b 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] new d45b50dda8 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] new 3c55c1f267 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] new 2f553222a4 436: onsuccess: #2260: 1: Success after gcc: 7 commits new d82d3edc7d 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] new eaa722f29e 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] new 07615365d0 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] new 32dd83c5a1 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] new 832eaea86e 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] new e3d2fe052f 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] new 47efc96143 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new 083a4f608c 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 9685a77434 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 1d49d408f2 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits new b835551a08 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 8f02c44db1 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 8dda3e3c20 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] new bc3b87c909 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 040afa3a65 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 542dee0e1c 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] 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 (7ee4ab9c9f) \ 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 1760 -> 1804 bytes 02-prepare_abe/console.log.xz | Bin 2836 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 30912 -> 30772 bytes 04-build_abe-stage1/console.log.xz | Bin 89600 -> 89624 bytes 06-build_abe-linux/console.log.xz | Bin 8524 -> 9300 bytes 07-build_abe-glibc/console.log.xz | Bin 235396 -> 236776 bytes 08-build_abe-stage2/console.log.xz | Bin 224696 -> 225732 bytes 09-build_abe-gdb/console.log.xz | Bin 38816 -> 38268 bytes 10-build_abe-qemu/console.log.xz | Bin 32280 -> 32012 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3792 -> 3792 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2740 -> 2924 bytes 13-check_regression/console.log.xz | Bin 8328 -> 8120 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 11 -- 13-check_regression/mail-body.txt | 42 ++--- 13-check_regression/results.compare | 30 +--- 13-check_regression/results.compare2 | 289 ++++++++++++-------------------- 13-check_regression/results.regressions | 31 ---- 14-update_baseline/console.log | 46 ++--- 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 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 ++--- mail/mail-subject.txt | 2 +- manifest.sh | 48 +++--- results | 31 ---- sumfiles/g++.log.xz | Bin 2668260 -> 2640384 bytes sumfiles/g++.sum | 76 ++++++++- sumfiles/gcc.log.xz | Bin 2208408 -> 2206876 bytes sumfiles/gcc.sum | 15 +- sumfiles/gfortran.log.xz | Bin 899604 -> 901424 bytes sumfiles/gfortran.sum | 5 +- sumfiles/libatomic.log.xz | Bin 2284 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216952 -> 217212 bytes sumfiles/libgomp.sum | 6 +- sumfiles/libitm.log.xz | Bin 2692 -> 2688 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 443116 -> 437396 bytes 44 files changed, 300 insertions(+), 397 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch master updated (33ca5c92dfa -> 60101899239)

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 33ca5c92dfa debug/108772 - ICE with late debug generated with -flto new 60101899239 target/108738 - limit STV chain discovery The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/config/i386/i386-features.cc | 77 ++++++++++++++++++++++++++++------------ gcc/config/i386/i386-features.h | 10 ++++-- gcc/config/i386/i386.opt | 4 +++ gcc/doc/invoke.texi | 4 +++ 4 files changed, 70 insertions(+), 25 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch master updated (1e4122f1159 -> 33ca5c92dfa)

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 1e4122f1159 [PR100127] Test for coroutine header in clang-compatible tests new 33ca5c92dfa debug/108772 - ICE with late debug generated with -flto 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/dwarf2out.cc | 5 +++- gcc/testsuite/g++.dg/lto/pr108772_0.C | 46 +++++++++++++++++++++++++++++++++++ 2 files changed, 50 insertions(+), 1 deletion(-) create mode 100644 gcc/testsuite/g++.dg/lto/pr108772_0.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