Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_tk1/gnu-release-arm-spec2k6-O3 updated (65962820e8 -> 388af43eda)

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_gnu_tk1/gnu-release-arm-spec2k6-O3 in repository toolchain/ci/base-artifacts. from 65962820e8 9: onsuccess: #285: 1: [TCWG CI] No change after binutils: 6 [...] new 388af43eda 10: onsuccess: #288: 1: [TCWG CI] No change after v5.19.12-3 [...] 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 1684 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30120 -> 30684 bytes 04-build_abe-stage1/console.log.xz | Bin 87604 -> 89256 bytes 06-build_abe-linux/console.log.xz | Bin 7984 -> 8644 bytes 07-build_abe-glibc/console.log.xz | Bin 231380 -> 231868 bytes 08-build_abe-stage2/console.log.xz | Bin 208104 -> 211828 bytes 09-benchmark/benchmark-build.log | 118 +- 09-benchmark/benchmark.log | 116 +- 09-benchmark/console.log.xz | Bin 3800 -> 3808 bytes 10-check_regression/console.log.xz | Bin 15448 -> 15568 bytes 10-check_regression/csv-results-0/md5sum.csv | 3015 +- 10-check_regression/csv-results-0/perf.csv | 3313 +- 10-check_regression/csv-results-0/results.csv | 601056 ++++++++--------- 10-check_regression/csv-results-0/size.csv | 607575 +++++++++--------- 10-check_regression/csv-results-0/vect.csv | 858 +- 10-check_regression/csv-results-1/md5sum.csv | 2877 +- 10-check_regression/csv-results-1/perf.csv | 3341 +- 10-check_regression/csv-results-1/results.csv | 603765 +++++++++-------- 10-check_regression/csv-results-1/size.csv | 604648 +++++++++-------- 10-check_regression/csv-results-1/vect.csv | 844 +- 10-check_regression/results-brief.csv | 68 +- 10-check_regression/results-compare.csv | 6 +- 10-check_regression/results-full.csv | 3411 +- 10-check_regression/results-internal.csv | 250 +- 10-check_regression/results.csv | 250 +- 10-check_regression/results.log | 1482 +- 10-check_regression/skipped-symbols.txt | 5 +- 11-update_baseline/console.log | 8 +- dashboard/dashboard-generate.sh | 2 +- .../squad/400.perlbench/results-metadata.json | 10 +- dashboard/squad/400.perlbench/results-metrics.json | 2 +- dashboard/squad/401.bzip2/results-metadata.json | 10 +- dashboard/squad/401.bzip2/results-metrics.json | 2 +- dashboard/squad/403.gcc/results-metadata.json | 10 +- dashboard/squad/403.gcc/results-metrics.json | 2 +- dashboard/squad/410.bwaves/results-metadata.json | 10 +- dashboard/squad/410.bwaves/results-metrics.json | 2 +- dashboard/squad/416.gamess/results-metadata.json | 10 +- dashboard/squad/416.gamess/results-metrics.json | 2 +- dashboard/squad/429.mcf/results-metadata.json | 10 +- dashboard/squad/429.mcf/results-metrics.json | 2 +- dashboard/squad/433.milc/results-metadata.json | 10 +- dashboard/squad/433.milc/results-metrics.json | 2 +- dashboard/squad/434.zeusmp/results-metadata.json | 10 +- dashboard/squad/434.zeusmp/results-metrics.json | 2 +- dashboard/squad/435.gromacs/results-metadata.json | 10 +- dashboard/squad/435.gromacs/results-metrics.json | 2 +- .../squad/436.cactusADM/results-metadata.json | 10 +- dashboard/squad/436.cactusADM/results-metrics.json | 2 +- dashboard/squad/437.leslie3d/results-metadata.json | 10 +- dashboard/squad/437.leslie3d/results-metrics.json | 2 +- dashboard/squad/444.namd/results-metadata.json | 10 +- dashboard/squad/444.namd/results-metrics.json | 2 +- dashboard/squad/445.gobmk/results-metadata.json | 10 +- dashboard/squad/445.gobmk/results-metrics.json | 2 +- dashboard/squad/447.dealII/results-metadata.json | 10 +- dashboard/squad/447.dealII/results-metrics.json | 2 +- dashboard/squad/450.soplex/results-metadata.json | 10 +- dashboard/squad/450.soplex/results-metrics.json | 2 +- dashboard/squad/453.povray/results-metadata.json | 10 +- dashboard/squad/453.povray/results-metrics.json | 2 +- dashboard/squad/454.calculix/results-metadata.json | 10 +- dashboard/squad/454.calculix/results-metrics.json | 2 +- dashboard/squad/456.hmmer/results-metadata.json | 10 +- dashboard/squad/456.hmmer/results-metrics.json | 2 +- dashboard/squad/458.sjeng/results-metadata.json | 10 +- dashboard/squad/458.sjeng/results-metrics.json | 2 +- dashboard/squad/459.GemsFDTD/results-metadata.json | 10 +- dashboard/squad/459.GemsFDTD/results-metrics.json | 2 +- .../squad/462.libquantum/results-metadata.json | 10 +- .../squad/462.libquantum/results-metrics.json | 2 +- dashboard/squad/464.h264ref/results-metadata.json | 10 +- dashboard/squad/464.h264ref/results-metrics.json | 2 +- dashboard/squad/465.tonto/results-metadata.json | 10 +- dashboard/squad/465.tonto/results-metrics.json | 2 +- dashboard/squad/470.lbm/results-metadata.json | 10 +- dashboard/squad/470.lbm/results-metrics.json | 2 +- dashboard/squad/471.omnetpp/results-metadata.json | 10 +- dashboard/squad/471.omnetpp/results-metrics.json | 2 +- dashboard/squad/473.astar/results-metadata.json | 10 +- dashboard/squad/473.astar/results-metrics.json | 2 +- dashboard/squad/481.wrf/results-metadata.json | 10 +- dashboard/squad/481.wrf/results-metrics.json | 2 +- dashboard/squad/482.sphinx3/results-metadata.json | 10 +- dashboard/squad/482.sphinx3/results-metrics.json | 2 +- .../squad/483.xalancbmk/results-metadata.json | 10 +- dashboard/squad/483.xalancbmk/results-metrics.json | 2 +- dashboard/squad/dashboard-push-squad.sh | 118 +- git/linux_rev | 2 +- mail/jira-body.txt | 12 +- mail/mail-body.txt | 12 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 2902048 -> 2898576 bytes save-temps/401.bzip2.tar.xz | Bin 298196 -> 299080 bytes save-temps/403.gcc.tar.xz | Bin 7538108 -> 7560264 bytes save-temps/410.bwaves.tar.xz | Bin 53128 -> 53376 bytes save-temps/416.gamess.tar.xz | Bin 16700968 -> 16701856 bytes save-temps/429.mcf.tar.xz | Bin 71032 -> 71372 bytes save-temps/433.milc.tar.xz | Bin 366264 -> 366768 bytes save-temps/434.zeusmp.tar.xz | Bin 543680 -> 543984 bytes save-temps/435.gromacs.tar.xz | Bin 2326484 -> 2321912 bytes save-temps/436.cactusADM.tar.xz | Bin 1753012 -> 1744816 bytes save-temps/437.leslie3d.tar.xz | Bin 175540 -> 175380 bytes save-temps/444.namd.tar.xz | Bin 492928 -> 493480 bytes save-temps/445.gobmk.tar.xz | Bin 2694780 -> 2679892 bytes save-temps/447.dealII.tar.xz | Bin 11585288 -> 11638688 bytes save-temps/450.soplex.tar.xz | Bin 1391184 -> 1389136 bytes save-temps/453.povray.tar.xz | Bin 2559884 -> 2592488 bytes save-temps/454.calculix.tar.xz | Bin 3488776 -> 3505440 bytes save-temps/456.hmmer.tar.xz | Bin 984744 -> 985120 bytes save-temps/458.sjeng.tar.xz | Bin 319752 -> 320348 bytes save-temps/459.GemsFDTD.tar.xz | Bin 635184 -> 634160 bytes save-temps/462.libquantum.tar.xz | Bin 116448 -> 116436 bytes save-temps/464.h264ref.tar.xz | Bin 3083148 -> 3108232 bytes save-temps/465.tonto.tar.xz | Bin 8097572 -> 8092536 bytes save-temps/470.lbm.tar.xz | Bin 53440 -> 53348 bytes save-temps/471.omnetpp.tar.xz | Bin 1491796 -> 1497072 bytes save-temps/473.astar.tar.xz | Bin 157236 -> 156520 bytes save-temps/481.wrf.tar.xz | Bin 9096480 -> 9078004 bytes save-temps/482.sphinx3.tar.xz | Bin 586048 -> 585492 bytes save-temps/483.xalancbmk.tar.xz | Bin 17129396 -> 17183868 bytes 124 files changed, 1218401 insertions(+), 1219123 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_debug updated (3a93fc0a43 -> 4bcd03c936)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_debug in repository toolchain/ci/base-artifacts. from 3a93fc0a43 60: onsuccess: #476: 1: Success after baseline build: no new [...] new 4bcd03c936 61: onsuccess: #477: 2: Success after binutils/gcc: 121 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1668 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 51272 -> 51060 bytes 05-build_abe-bootstrap_debug/console.log.xz | Bin 52740 -> 467600 bytes 06-check_regression/console.log.xz | Bin 2056 -> 3096 bytes 06-check_regression/mail-body.txt | 9 +-------- 07-update_baseline/console.log | 9 --------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 11 ++--------- mail/mail-subject.txt | 2 +- manifest.sh | 21 +++++++++++---------- results | 2 +- 15 files changed, 20 insertions(+), 42 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-norov-defconfig updated (3f6cf05665 -> 209bfabc57)

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-release-aarch64-norov-defconfig in repository toolchain/ci/base-artifacts. from 3f6cf05665 11: onsuccess: #50: boot: Success after binutils/llvm/linux/ [...] new 209bfabc57 12: onsuccess: #51: 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 1728 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30460 -> 30216 bytes 04-build_kernel_llvm/console.log.xz | Bin 65512 -> 63836 bytes 05-build_abe-qemu/console.log.xz | Bin 32072 -> 31888 bytes 06-build_linux/console.log.xz | Bin 3468 -> 3472 bytes 07-boot_linux/console.log.xz | Bin 6256 -> 6256 bytes 08-check_regression/console.log.xz | Bin 4284 -> 4208 bytes 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 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (a6c9296282 -> df24a7fcb0)

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-aarch64 in repository toolchain/ci/base-artifacts. discards a6c9296282 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards 621a2452eb 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards 7c5aca15f0 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 71b860bdf2 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards d50bcfacee 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 8963064629 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards a0f5868d83 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards d016f47839 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards fcf10b984c 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 77d3a8c9ae 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 191cea079d 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 0048261030 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards a78b18ba76 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 3ed285fd18 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 34b0cb1abd 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 5a59f0914f 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards afdd380d0e 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 452ece8007 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 0273822d48 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 2dc81b6626 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards f81b2d68aa 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards ed7f3ff16c 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 77a0952fd7 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 9a784d11cc 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards faa8d994e1 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 897008f1e6 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 265d1c05e2 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 787012bc19 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards f42268936e 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 0514bab253 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 4801292882 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 1c4850af1f 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards d762e9595d 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards ea1b7f5432 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 1f01297726 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 05461d31f3 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 29ae108f36 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 12d05888ac 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards b5b938b0cc 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 4c798f71f0 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 9ec7d537f4 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards f8ea90f269 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards dfc64be600 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 8f0c10d96e 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 02bd408d81 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 7eb8a3f99c 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards b4e129f0f6 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 4bd8d63331 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards ad96eb2366 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 418518d092 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards aea3ed83f3 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 9c0a521241 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards d55267530a 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 5ad31d859b 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards e43322fc9e 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 1101692d58 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards c848972de4 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards b3e981321c 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 8e28af31b8 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards f63431ce89 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards ad89073ba2 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 5b0c70bcd8 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards d81bcac289 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards a0e6970b29 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 8f4a7f8269 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 4ced6a8bab 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 3638d91da1 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 4dccfb0f4b 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards be809e6c30 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 04b98cde14 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 844d57fb1f 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 5a1cc01b10 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 5843253e29 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 4ca6bef5e5 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards ccdf9a4209 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards efe9bf5859 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards dcf486d920 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 46175e8dc7 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 62a9966761 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 91d9cd5c07 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 9bc184e674 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards e9a102ecd5 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards d2be4dd2d8 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards afa5c5f0bf 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 26e1b456d1 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 3e8f4d62d6 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 7073310843 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b2a1ed533d 75: onsuccess: 1: Successful build after linux: 44 commits discards e4981204d7 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 048481ad69 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fe35cf32ea 72: onsuccess: 1: Successful build after linux: 12 commits discards 073664df36 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 18e5b63c96 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 0b09980422 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 3634dd1762 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dbfa27cb66 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 95e61a4363 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards b2f384cabd 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 08fbe77942 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6a7486e6f9 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards cc9207c2d8 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 9ea9275824 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new c4e45c3363 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 680ef0f8e0 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 43a997eaff 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1b78243f6c 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new cc92477e5f 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 3f5553b331 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a9af5d13fa 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 71bd7cc23a 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new f7c4fb4513 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 862dd7b854 72: onsuccess: 1: Successful build after linux: 12 commits new 5ce669517a 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1423b610d2 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 3686f85362 75: onsuccess: 1: Successful build after linux: 44 commits new 8e6df726c2 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0ecd661ed0 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 59e3ebf603 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new f9ae68073c 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new f4de20e4a1 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new fd76ee9754 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 023f3d651a 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 3fe5a125f3 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 10d7f17a7e 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new d4a0502061 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 5d52399e4a 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 45b9d5ec21 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 6ba49b0dc9 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 2e8f05ac70 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new ddf04ddd36 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new bd4d99a118 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 133c7ed7a3 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 1e85082482 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 8d901f9ad9 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 7fcae6ef64 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 285f8dafd7 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 343715294a 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new a74cf65df9 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 49d31e37ce 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 939f639a30 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 6a3cacabd5 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 9655c014f8 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 32b1cece37 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 6b955cede0 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 540ec2dd7b 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 4dbc3e9432 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 74315f9f2f 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new eb6906a700 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new b5b3b26de4 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 496210e9c9 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new f265362656 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 595fd93a1e 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new ff1870ade9 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 3bc571a524 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 6ad938029d 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 9ce230b00b 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new a2b1b3f533 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new cb4e7f55c8 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new c36f2f1ef5 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new cbdd4eb228 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 473a98bd03 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new bc228b1791 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 915eb868c4 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 69bcb103b5 124: onsuccess: #2159: 1: Success after linux: 23 commits new 3a2b8eda98 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new ab8363f96f 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new fb9baddfe3 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 19815f9deb 128: onsuccess: #2163: 1: Success after linux: 23 commits new d20ce12d7b 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new ff16f030d5 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 39d2b62bf1 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 736dc4731d 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new af4e564c6f 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 6db38ddd71 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 47515ca50d 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 81df9e8886 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new da1408a126 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 85e261d078 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new a7c13e99d5 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 5b68ebba44 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new a042e6407f 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new ca74f8a334 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 103b9d674f 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new b80c09847a 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new eb929bf144 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new a527e113e2 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new ddc2f14692 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 4b061431bb 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 41f269b4d0 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 7a7a860794 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 200232ce66 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 9919d34fe3 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new ff45a23679 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new 465d50759d 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new e824c4fda7 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 562b609382 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 9263ed146f 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new cfb52d97eb 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 27cb513f63 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 9cdbdcbb7c 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 8121b54132 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new b2e1c21d04 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new df24a7fcb0 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (a6c9296282) \ 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 1704 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30680 -> 30708 bytes 04-build_abe-stage1/console.log.xz | Bin 72208 -> 72784 bytes 06-build_abe-linux/console.log.xz | Bin 9188 -> 8512 bytes 07-build_abe-glibc/console.log.xz | Bin 239956 -> 239908 bytes 08-build_abe-stage2/console.log.xz | Bin 203236 -> 202916 bytes 09-build_abe-gdb/console.log.xz | Bin 37760 -> 37424 bytes 10-build_abe-qemu/console.log.xz | Bin 31908 -> 32048 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3924 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2608 -> 2656 bytes 13-check_regression/console.log.xz | Bin 6140 -> 6204 bytes 13-check_regression/results.compare | 16 +- 13-check_regression/results.compare2 | 31 +- 14-update_baseline/console.log | 36 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- sumfiles/g++.log.xz | Bin 3411544 -> 3403752 bytes sumfiles/g++.sum | 44 +- sumfiles/gcc.log.xz | Bin 3031412 -> 3029292 bytes sumfiles/gcc.sum | 4483 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1031376 -> 1035288 bytes sumfiles/gfortran.sum | 12 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202248 -> 202344 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2660 -> 2660 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 430132 -> 426720 bytes sumfiles/libstdc++.sum | 2 +- 38 files changed, 2349 insertions(+), 2335 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-aarch64-bootstrap_O3 updated (da6e3b169c -> 2b5102f39f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/release-aarch64-bootstrap_O3 in repository toolchain/ci/base-artifacts. from da6e3b169c 16: onsuccess: #139: 2: Success after binutils/gcc: 15 commits new 2b5102f39f 17: onsuccess: #140: 2: Success after binutils/gcc: 8 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1680 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 37892 -> 37644 bytes 05-build_abe-bootstrap_O3/console.log.xz | Bin 264168 -> 265864 bytes 06-check_regression/console.log.xz | Bin 2872 -> 2808 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++++++---------- 12 files changed, 16 insertions(+), 16 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (85872a69ee1 -> bfca9505f6f)

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 85872a69ee1 Daily bump. new e6fe02d8322 analyzer: widening_svalues take a function_point rather tha [...] new 7f42f7adfa6 analyzer: fold -(-(VAL)) to VAL new 0167154cdd0 analyzer: move region_model_manager decl to its own header new bfca9505f6f analyzer: revamp side-effects of call summaries [PR107072] The 4 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/Makefile.in | 1 + gcc/analyzer/analyzer-logging.h | 2 + gcc/analyzer/analyzer.h | 11 + gcc/analyzer/call-info.cc | 12 +- gcc/analyzer/call-summary.cc | 875 +++++++++++++++++++++ gcc/analyzer/call-summary.h | 118 +++ gcc/analyzer/constraint-manager.cc | 55 ++ gcc/analyzer/constraint-manager.h | 3 + gcc/analyzer/engine.cc | 201 ++++- gcc/analyzer/exploded-graph.h | 36 +- gcc/analyzer/known-function-manager.h | 2 + gcc/analyzer/program-point.h | 3 + gcc/analyzer/program-state.cc | 48 ++ gcc/analyzer/program-state.h | 6 + gcc/analyzer/region-model-manager.cc | 47 +- gcc/analyzer/region-model-manager.h | 318 ++++++++ gcc/analyzer/region-model.cc | 51 +- gcc/analyzer/region-model.h | 298 +------ gcc/analyzer/store.cc | 161 ++++ gcc/analyzer/store.h | 16 + gcc/analyzer/supergraph.cc | 9 +- gcc/analyzer/supergraph.h | 10 +- gcc/analyzer/svalue.cc | 12 +- gcc/analyzer/svalue.h | 12 +- gcc/testsuite/gcc.dg/analyzer/call-summaries-2.c | 646 +++++++++++++++ gcc/testsuite/gcc.dg/analyzer/call-summaries-3.c | 29 + .../gcc.dg/analyzer/call-summaries-asm-x86.c | 20 + .../gcc.dg/analyzer/call-summaries-malloc.c | 80 ++ .../gcc.dg/analyzer/call-summaries-pr107072.c | 90 +++ 29 files changed, 2819 insertions(+), 353 deletions(-) create mode 100644 gcc/analyzer/call-summary.cc create mode 100644 gcc/analyzer/call-summary.h create mode 100644 gcc/analyzer/region-model-manager.h create mode 100644 gcc/testsuite/gcc.dg/analyzer/call-summaries-2.c create mode 100644 gcc/testsuite/gcc.dg/analyzer/call-summaries-3.c create mode 100644 gcc/testsuite/gcc.dg/analyzer/call-summaries-asm-x86.c create mode 100644 gcc/testsuite/gcc.dg/analyzer/call-summaries-malloc.c create mode 100644 gcc/testsuite/gcc.dg/analyzer/call-summaries-pr107072.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-arm updated (c3d0875fb6 -> f313d9f2c4)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/master-arm in repository toolchain/ci/base-artifacts. discards c3d0875fb6 162: onsuccess: #1782: 1: Success after binutils/gcc: 14 commits discards 9a37902c29 161: onsuccess: #1781: 1: Success after binutils/gcc: 16 commits discards 2055d514ed 160: onsuccess: #1780: 1: Success after binutils/gcc: 4 commits discards d0bf89db53 159: onsuccess: #1779: 1: Success after gcc: 2 commits discards e70264000e 158: onsuccess: #1778: 1: Success after binutils/gcc: 30 commits discards bc469e3da1 157: onsuccess: #1777: 1: Success after binutils/gcc: 3 commits discards 9a77604617 156: onsuccess: #1776: 1: Success after binutils/gcc: 4 commits discards 04aa594e22 155: onsuccess: #1775: 1: Success after binutils: 2 commits discards 9d449cf757 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 commits discards 865fac16ff 153: onsuccess: #1773: 1: Success after gcc: 4 commits discards 9333b6749a 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits discards c38cee100b 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] discards e51e72e7b7 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] discards 6720b00e17 149: onsuccess: #1769: 1: Success after gcc: 3 commits discards ced56902ba 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits discards 2044e81763 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits discards f8bed4fce3 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits discards d8d2ba8794 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits discards daa0d4e76e 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits discards a5c5a6db37 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits discards 1d328b78e0 142: onsuccess: #1761: 1: Success after gcc: 83 commits discards be2e6accb0 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] discards 0fce028247 140: onsuccess: #1756: 1: Success after binutils: 3 commits discards 0f7fdb3368 139: onsuccess: #1753: 1: Success after binutils: 5 commits discards a9682ba3ed 138: onsuccess: #1749: 1: Success after binutils: 5 commits discards 2adff0758f 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] discards fa0e67c39f 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] discards 0b03261dac 135: onsuccess: #1739: 1: Success after binutils: 4 commits discards c83f8a9866 134: onsuccess: #1736: 1: Success after binutils: 3 commits discards 259b81ce3c 133: onsuccess: #1733: 1: Success after binutils: 3 commits discards 5fb4991792 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits discards 3e680f6ad1 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits discards 6d9c59deb0 130: onsuccess: #1729: 1: Success after gcc: 9 commits discards d9784eb6b1 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] discards df6c01350b 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits discards 6870499dca 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] discards 6ac1907474 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits discards c78bd4f8a9 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits discards 9d12dc08ce 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits discards 0f89b21d95 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits discards bd924b377a 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits discards cf436a0cf5 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits discards 67079fff3c 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits discards 80ff7f7d2c 119: onsuccess: #1715: 1: Success after binutils: 4 commits discards 8bd65da0e8 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits discards f6d4039470 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits discards 69fd7dd39f 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits discards 6df1d99f19 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits discards 04304ae1a0 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits discards 9d19588294 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits discards def9cbc07d 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits discards 4744ed7e6a 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits discards 21c63d562a 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits discards 2056683744 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] discards a40d882945 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits discards 836d8ce1e9 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] discards 710454b72a 106: onsuccess: #1702: 1: Success after gcc: 4 commits discards cb685c85c5 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits discards f1f671d209 104: onsuccess: #1700: 1: Success after gcc: 2 commits discards 8185277a42 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits discards 812e28fbb5 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits discards 5bd4e33778 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits discards 1eea713c64 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] discards 969f76cd91 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits discards 5c695dae58 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits discards bc54ee8732 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits discards 3be2f2cb84 96: onsuccess: #1654: 1: Success after gcc: 5 commits discards 5dcecdc1da 95: onsuccess: #1653: 1: Success after gcc: 13 commits discards 3f8e987f6f 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits discards 39a105bd40 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] discards fb16379a0b 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits discards e3f74602c2 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] discards 74641c72bf 90: onsuccess: #1645: 1: Success after gcc: 2 commits discards 0bdac86649 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] discards 4db29ef41d 88: onsuccess: 1: Success after binutils/gcc: 2 commits discards 1f53933579 87: onsuccess: 1: Success after gcc: 6 commits discards 172c7f8c3b 86: onsuccess: 1: Success after binutils/gcc: 8 commits discards aa105d6c11 85: onsuccess: 1: Success after binutils/gcc: 19 commits discards 6de864cfb5 84: onsuccess: 1: Success after binutils/gcc: 2 commits discards 9809ba0f38 83: onsuccess: 1: Success after gcc: 14 commits discards 80df80bfb6 82: onsuccess: 1: Success after binutils/gcc: 9 commits discards 850ff3b5dd 81: onsuccess: 1: Success after binutils/gcc: 8 commits discards 871f95d325 80: onsuccess: 1: Success after binutils/gcc: 8 commits discards 5b0cc45033 79: onsuccess: 1: Success after binutils/gcc: 23 commits discards 0da9ed1214 78: onsuccess: 1: Success after binutils/gcc: 17 commits discards 385bebf55f 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards cf8a1fc163 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards f9ede66270 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards b2f3083bcd 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits discards b7f8f9e6d5 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 21b7ffb91b 72: onsuccess: 1: Successful build after baseline build: no [...] discards f67e1a8fa4 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards 4c250cb881 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards ea879abed7 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] discards f443a87d51 68: onsuccess: 1: Successful build after gcc: 2 commits discards 2bb355a3e0 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards a0f2da2626 66: onsuccess: 1: Successful build after gcc: 4 commits discards bf10abfa96 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards 8f396403ac 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards 89ca77ebc1 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 89b98aad71 62: onsuccess: 1: Successful build after gcc: 4 commits new 70fd4d6812 62: onsuccess: 1: Successful build after gcc: 4 commits new 52121d96e9 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits new c06768d1e7 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits new 8c617c9fd4 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits new 2676b4ebc8 66: onsuccess: 1: Successful build after gcc: 4 commits new 30ce8f2135 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 3713a9a5b7 68: onsuccess: 1: Successful build after gcc: 2 commits new a0d2f4f551 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] new f064b75a8d 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits new bfc26d36aa 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] new 73e3b85e14 72: onsuccess: 1: Successful build after baseline build: no [...] new 526b64f788 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits new 961bbea1c6 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits new 21d5d46114 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 473fade264 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 89af9124df 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits new f0698708c8 78: onsuccess: 1: Success after binutils/gcc: 17 commits new 7debda209a 79: onsuccess: 1: Success after binutils/gcc: 23 commits new 13a1079715 80: onsuccess: 1: Success after binutils/gcc: 8 commits new 123b2542e7 81: onsuccess: 1: Success after binutils/gcc: 8 commits new 7935149d7c 82: onsuccess: 1: Success after binutils/gcc: 9 commits new a7f60da513 83: onsuccess: 1: Success after gcc: 14 commits new a2c4dbfc6a 84: onsuccess: 1: Success after binutils/gcc: 2 commits new bbc7d250fc 85: onsuccess: 1: Success after binutils/gcc: 19 commits new b55cf8c208 86: onsuccess: 1: Success after binutils/gcc: 8 commits new e6f3aa66dd 87: onsuccess: 1: Success after gcc: 6 commits new 91bc2e2a82 88: onsuccess: 1: Success after binutils/gcc: 2 commits new 5f3acb5676 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] new 143faab3a3 90: onsuccess: #1645: 1: Success after gcc: 2 commits new e3ed80e4fe 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] new fc7ab66090 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits new 4d3bb1b81a 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] new 50513d0de1 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits new 4019649746 95: onsuccess: #1653: 1: Success after gcc: 13 commits new d89524af2c 96: onsuccess: #1654: 1: Success after gcc: 5 commits new 0e85ca1582 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits new f3aa5cb246 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits new ac7d358c30 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits new 8e78497065 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] new 7b2b3e206b 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits new 1b08cb1e02 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits new 3063553cb7 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits new 13dbf5ea6e 104: onsuccess: #1700: 1: Success after gcc: 2 commits new ac56211827 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits new fd61cc8adb 106: onsuccess: #1702: 1: Success after gcc: 4 commits new 8f032f404c 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] new c0a00bbd2e 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits new fd8ecb38dc 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] new 83b1f2b212 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits new f119e5e9f9 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits new 2bddbe12eb 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits new 3b9e67a0d6 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits new 3314183924 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits new e4b42615f2 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits new 4da1a66b74 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits new e5d0c7d72b 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits new 83c3f490a9 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits new fd2ecd04cd 119: onsuccess: #1715: 1: Success after binutils: 4 commits new 79c12a9250 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits new 32e51c6503 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits new b91bf7bc21 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits new 9786c98f2e 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits new db8897dccc 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits new 9c80ff9a85 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits new bc4f0d07c3 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits new 6a1041dba0 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] new ed57fa43fe 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits new 3196f1106f 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] new ee5214c071 130: onsuccess: #1729: 1: Success after gcc: 9 commits new e0d5d37fd3 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits new 3da4648c9e 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits new 6c6d5e74a3 133: onsuccess: #1733: 1: Success after binutils: 3 commits new 5d53696d93 134: onsuccess: #1736: 1: Success after binutils: 3 commits new 976471f9fa 135: onsuccess: #1739: 1: Success after binutils: 4 commits new 59d2441030 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] new 9be2923e4f 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] new 0d6b2d2752 138: onsuccess: #1749: 1: Success after binutils: 5 commits new 2c98a0ab54 139: onsuccess: #1753: 1: Success after binutils: 5 commits new 0af8bfd5b0 140: onsuccess: #1756: 1: Success after binutils: 3 commits new 75f80e1939 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] new ea0c3e71c9 142: onsuccess: #1761: 1: Success after gcc: 83 commits new dbf8d7b325 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits new f82cf4c891 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits new 49adb15902 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits new 6b5e12b4ac 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits new 4029b1a3d5 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits new 60b2f6b969 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits new da9f0ad490 149: onsuccess: #1769: 1: Success after gcc: 3 commits new cc25af0df7 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] new 1061a6c26d 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] new 58942ceb1f 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits new a395620246 153: onsuccess: #1773: 1: Success after gcc: 4 commits new 303c3d7ae9 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 commits new 5121ed2e9a 155: onsuccess: #1775: 1: Success after binutils: 2 commits new 0050dc4a61 156: onsuccess: #1776: 1: Success after binutils/gcc: 4 commits new 65ce54bfab 157: onsuccess: #1777: 1: Success after binutils/gcc: 3 commits new 24f922152c 158: onsuccess: #1778: 1: Success after binutils/gcc: 30 commits new 9909f8e486 159: onsuccess: #1779: 1: Success after gcc: 2 commits new bb5d12f0d5 160: onsuccess: #1780: 1: Success after binutils/gcc: 4 commits new 04b4a2ee6d 161: onsuccess: #1781: 1: Success after binutils/gcc: 16 commits new 78710a2921 162: onsuccess: #1782: 1: Success after binutils/gcc: 14 commits new f313d9f2c4 163: onsuccess: #1783: 1: Success after binutils/gcc: 8 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (c3d0875fb6) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (f3 [...] 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 1684 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 51644 -> 50508 bytes 04-build_abe-gcc/console.log.xz | Bin 232392 -> 231488 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3872 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2572 -> 2664 bytes 07-check_regression/console.log.xz | Bin 5204 -> 4856 bytes 07-check_regression/results.compare2 | 36 +- 08-update_baseline/console.log | 52 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/g++.log.xz | Bin 2796952 -> 2781552 bytes sumfiles/g++.sum | 35 +- sumfiles/gcc.log.xz | Bin 2349548 -> 2389196 bytes sumfiles/gcc.sum | 4214 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 913824 -> 910040 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2172 -> 2176 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 204680 -> 204580 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2536 -> 2536 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 466124 -> 465668 bytes sumfiles/libstdc++.sum | 2 +- 30 files changed, 2196 insertions(+), 2183 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch releases/gcc-10 updated (5a304edf8f9 -> bfc4cec904e)

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-10 in repository gcc. from 5a304edf8f9 Daily bump. new bfc4cec904e 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.

2 years, 1 month

[gcc] branch master updated (ce3a1b59760 -> 85872a69ee1)

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 ce3a1b59760 c++: fix debug info for array temporary [PR107154] new 85872a69ee1 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 | 84 +++++++++++++++++++++++++++++++++++++++++++++++++ gcc/DATESTAMP | 2 +- gcc/c-family/ChangeLog | 5 +++ gcc/c/ChangeLog | 27 ++++++++++++++++ gcc/cp/ChangeLog | 40 +++++++++++++++++++++++ gcc/fortran/ChangeLog | 5 +++ gcc/testsuite/ChangeLog | 36 +++++++++++++++++++++ libgomp/ChangeLog | 5 +++ libstdc++-v3/ChangeLog | 74 +++++++++++++++++++++++++++++++++++++++++++ 9 files changed, 277 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[binutils-gdb] branch master updated (8f5bc64185a -> 63418f080f7)

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 8f5bc64185a Remove decode_location_spec_default new 63418f080f7 Automatic date update in version.in 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: bfd/version.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits October 2022