Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[gcc] branch master updated (33b93ac3f2f -> 0af8d957d59)

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 33b93ac3f2f aarch64: Remove redundant zero-extends with LDAR new 0af8d957d59 middle-end/107115 - avoid bogus redundant store removal dur [...] 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/expr.cc | 4 +++- gcc/testsuite/gcc.dg/torture/pr107115.c | 37 +++++++++++++++++++++++++++++++++ 2 files changed, 40 insertions(+), 1 deletion(-) create mode 100644 gcc/testsuite/gcc.dg/torture/pr107115.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_bootstrap/master-arm-bootstrap_O3 updated (7645129d0e -> 64139e50b3)

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_O3 in repository toolchain/ci/base-artifacts. from 7645129d0e 56: onsuccess: #474: 2: Success after binutils/gcc: 39 commits new 64139e50b3 57: onsuccess: #475: 2: Success after binutils/gcc: 59 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 1744 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2740 bytes 04-build_abe-binutils/console.log.xz | Bin 53136 -> 52148 bytes 05-build_abe-bootstrap_O3/console.log.xz | Bin 464932 -> 463772 bytes 06-check_regression/console.log.xz | Bin 3088 -> 3096 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 | 18 +++++++++--------- 12 files changed, 15 insertions(+), 15 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-stable-allnoconfig updated (b40e0f1388 -> d89966f6bb)

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-stable-allnoconfig in repository toolchain/ci/base-artifacts. from b40e0f1388 13: onsuccess: #259: boot: Success after binutils/llvm/linux [...] new d89966f6bb 14: onsuccess: #260: 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 1700 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30180 -> 30204 bytes 04-build_kernel_llvm/console.log.xz | Bin 63540 -> 65344 bytes 05-build_abe-qemu/console.log.xz | Bin 31936 -> 31396 bytes 06-build_linux/console.log.xz | Bin 3336 -> 3336 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4316 -> 4160 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_bmk_gnu_sq/gnu-master-aarch64-spec2k6-Os updated (43f468b8e1 -> 351a28121a)

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_sq/gnu-master-aarch64-spec2k6-Os in repository toolchain/ci/base-artifacts. from 43f468b8e1 21: onsuccess: #46: 1: [TCWG CI] No change after binutils/gc [...] new 351a28121a 22: onsuccess: #49: 1: [TCWG CI] No change after binutils: 1 [...] 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 1788 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30648 -> 31116 bytes 04-build_abe-stage1/console.log.xz | Bin 72332 -> 73684 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8624 -> 7968 bytes 07-build_abe-glibc/console.log.xz | Bin 239128 -> 241412 bytes 08-build_abe-stage2/console.log.xz | Bin 176280 -> 179252 bytes 09-benchmark/benchmark-build.log | 96 +- 09-benchmark/benchmark.log | 94 +- 09-benchmark/console.log.xz | Bin 3656 -> 3632 bytes 10-check_regression/console.log.xz | Bin 13528 -> 12732 bytes 10-check_regression/csv-results-0/md5sum.csv | 3245 +- 10-check_regression/csv-results-0/perf.csv | 3800 +- 10-check_regression/csv-results-0/results.csv | 76730 +- 10-check_regression/csv-results-0/size.csv | 685435 +++++++++--------- 10-check_regression/csv-results-0/vect.csv | 44 +- 10-check_regression/csv-results-1/md5sum.csv | 3569 +- 10-check_regression/csv-results-1/perf.csv | 3823 +- 10-check_regression/csv-results-1/results.csv | 61602 +- 10-check_regression/csv-results-1/size.csv | 677610 ++++++++--------- 10-check_regression/csv-results-1/vect.csv | 44 +- 10-check_regression/results-brief.csv | 64 +- 10-check_regression/results-compare.csv | 7 +- 10-check_regression/results-full.csv | 3998 +- 10-check_regression/results-internal.csv | 249 +- 10-check_regression/results.csv | 249 +- 10-check_regression/results.log | 1072 +- 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-functional.json | 2 +- dashboard/squad/403.gcc/results-metadata.json | 10 +- dashboard/squad/403.gcc/results-metrics.json | 1 - 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/Mean/results-functional.json | 4 - dashboard/squad/Mean/results-metadata.json | 12 - dashboard/squad/Mean/results-metrics.json | 5 - dashboard/squad/dashboard-push-squad.sh | 125 +- git/binutils_rev | 2 +- mail/jira-body.txt | 21 +- mail/mail-body.txt | 21 +- mail/mail-subject.txt | 2 +- manifest.sh | 27 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 1263128 -> 1263996 bytes save-temps/401.bzip2.tar.xz | Bin 94504 -> 94600 bytes save-temps/403.gcc.tar.xz | Bin 3500412 -> 3502916 bytes save-temps/410.bwaves.tar.xz | Bin 15196 -> 15216 bytes save-temps/416.gamess.tar.xz | Bin 4196536 -> 4191836 bytes save-temps/429.mcf.tar.xz | Bin 36864 -> 36844 bytes save-temps/433.milc.tar.xz | Bin 168816 -> 168676 bytes save-temps/434.zeusmp.tar.xz | Bin 125040 -> 124392 bytes save-temps/435.gromacs.tar.xz | Bin 976836 -> 978208 bytes save-temps/436.cactusADM.tar.xz | Bin 726928 -> 728316 bytes save-temps/437.leslie3d.tar.xz | Bin 46260 -> 46272 bytes save-temps/444.namd.tar.xz | Bin 173076 -> 172784 bytes save-temps/445.gobmk.tar.xz | Bin 1825420 -> 1820052 bytes save-temps/447.dealII.tar.xz | Bin 6056992 -> 6011992 bytes save-temps/450.soplex.tar.xz | Bin 742900 -> 739720 bytes save-temps/453.povray.tar.xz | Bin 1396848 -> 1385420 bytes save-temps/454.calculix.tar.xz | Bin 1226064 -> 1227028 bytes save-temps/456.hmmer.tar.xz | Bin 380896 -> 381824 bytes save-temps/458.sjeng.tar.xz | Bin 147072 -> 146996 bytes save-temps/459.GemsFDTD.tar.xz | Bin 146292 -> 146576 bytes save-temps/462.libquantum.tar.xz | Bin 62544 -> 62272 bytes save-temps/464.h264ref.tar.xz | Bin 563076 -> 562796 bytes save-temps/465.tonto.tar.xz | Bin 2246308 -> 2247856 bytes save-temps/470.lbm.tar.xz | Bin 26400 -> 26516 bytes save-temps/471.omnetpp.tar.xz | Bin 1071400 -> 1097672 bytes save-temps/473.astar.tar.xz | Bin 91972 -> 92084 bytes save-temps/481.wrf.tar.xz | Bin 1581720 -> 1581352 bytes save-temps/482.sphinx3.tar.xz | Bin 256580 -> 256392 bytes save-temps/483.xalancbmk.tar.xz | Bin 11125268 -> 11258852 bytes 127 files changed, 753559 insertions(+), 768744 deletions(-) delete mode 100644 dashboard/squad/Mean/results-functional.json delete mode 100644 dashboard/squad/Mean/results-metadata.json delete mode 100644 dashboard/squad/Mean/results-metrics.json -- 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 (9f158895b8 -> 17ceeaeb30)

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 9f158895b8 168: onsuccess: #1788: 1: Success after binutils/gcc: 9 commits discards b806ca6fe2 167: onsuccess: #1787: 1: Success after gcc: 8 commits discards 186ecd66da 166: onsuccess: #1786: 1: Success after gcc: 10 commits discards f8717f5efa 165: onsuccess: #1785: 1: Success after binutils/gcc: 6 commits discards 713a982df3 164: onsuccess: #1784: 1: Success after binutils/gcc: 11 commits discards 2a0f7a9911 163: onsuccess: #1783: 1: Success after binutils/gcc: 8 commits discards 7a7824b7d3 162: onsuccess: #1782: 1: Success after binutils/gcc: 14 commits discards 86008eddcc 161: onsuccess: #1781: 1: Success after binutils/gcc: 16 commits discards aa2679f891 160: onsuccess: #1780: 1: Success after binutils/gcc: 4 commits discards f52ad5daa2 159: onsuccess: #1779: 1: Success after gcc: 2 commits discards ac66a6e7cb 158: onsuccess: #1778: 1: Success after binutils/gcc: 30 commits discards d9e2a14ff8 157: onsuccess: #1777: 1: Success after binutils/gcc: 3 commits discards 203888c288 156: onsuccess: #1776: 1: Success after binutils/gcc: 4 commits discards 6cc3c780f6 155: onsuccess: #1775: 1: Success after binutils: 2 commits discards edeba39e1e 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 commits discards e835892a98 153: onsuccess: #1773: 1: Success after gcc: 4 commits discards a0a59e6a08 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits discards db0d5fb0b2 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] discards 2644f651f0 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] discards 4138c5b125 149: onsuccess: #1769: 1: Success after gcc: 3 commits discards cbb1700038 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits discards 51dff6780f 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits discards df49be1487 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits discards 5dd8569cf4 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits discards d365b0f18a 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits discards a27532c462 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits discards 4043b53682 142: onsuccess: #1761: 1: Success after gcc: 83 commits discards dad2c1bba1 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] discards a223b05ebe 140: onsuccess: #1756: 1: Success after binutils: 3 commits discards bc3cd31779 139: onsuccess: #1753: 1: Success after binutils: 5 commits discards 8e477fca0e 138: onsuccess: #1749: 1: Success after binutils: 5 commits discards 4e8a7c004d 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] discards 8aad108522 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] discards e568966874 135: onsuccess: #1739: 1: Success after binutils: 4 commits discards d857c319d2 134: onsuccess: #1736: 1: Success after binutils: 3 commits discards 684d6bbad3 133: onsuccess: #1733: 1: Success after binutils: 3 commits discards 8b85b6cb04 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits discards 6e57695e5c 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits discards 68fab5beba 130: onsuccess: #1729: 1: Success after gcc: 9 commits discards fa8136f045 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] discards 231439fbd6 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits discards dca3726ad4 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] discards 04e650b38e 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits discards b5ece0be15 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits discards d1b0c3eea7 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits discards 38433078e9 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits discards df3668be18 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits discards d9fb335be4 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits discards 25ad5ddd05 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits discards 4190d348e0 119: onsuccess: #1715: 1: Success after binutils: 4 commits discards 82a534d699 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits discards 8cda1f2836 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits discards 48ed620886 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits discards 899ce65906 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits discards 00838c7057 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits discards e41aa03c23 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits discards ad20706e0c 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits discards e549ce4241 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits discards cdb1cbb11b 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits discards 0c0d53e043 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] discards 7c86518d29 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits discards 41b814daef 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] discards 0c478abd70 106: onsuccess: #1702: 1: Success after gcc: 4 commits discards 32da515523 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits discards a02225949a 104: onsuccess: #1700: 1: Success after gcc: 2 commits discards cb9064b20f 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits discards b6ea442c24 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits discards 730084cf07 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits discards 28ec380fdd 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] discards 0501624de2 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits discards b13831e14c 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits discards 8cfec6c2e4 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits discards e1741a63a3 96: onsuccess: #1654: 1: Success after gcc: 5 commits discards 2c4bfac900 95: onsuccess: #1653: 1: Success after gcc: 13 commits discards 9b2e813330 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits discards 0ea199ee00 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] discards daa50233ef 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits discards dcd608c158 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] discards 009630ba18 90: onsuccess: #1645: 1: Success after gcc: 2 commits discards 1723f3c6b6 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] discards cc907c9707 88: onsuccess: 1: Success after binutils/gcc: 2 commits discards 8873b53c7a 87: onsuccess: 1: Success after gcc: 6 commits discards 7231b03159 86: onsuccess: 1: Success after binutils/gcc: 8 commits discards 2235dda643 85: onsuccess: 1: Success after binutils/gcc: 19 commits discards 7e5c020731 84: onsuccess: 1: Success after binutils/gcc: 2 commits discards 3fd4021729 83: onsuccess: 1: Success after gcc: 14 commits discards f4cb92ef70 82: onsuccess: 1: Success after binutils/gcc: 9 commits discards b29166b9ff 81: onsuccess: 1: Success after binutils/gcc: 8 commits discards ad8c9b9017 80: onsuccess: 1: Success after binutils/gcc: 8 commits discards a7f9c5ad78 79: onsuccess: 1: Success after binutils/gcc: 23 commits discards 34e370ec64 78: onsuccess: 1: Success after binutils/gcc: 17 commits discards f468b2d1a1 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards c22dc5c6e4 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards a5420546ec 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards cdaa153866 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits discards f4c308b56b 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards ba2052d163 72: onsuccess: 1: Successful build after baseline build: no [...] discards 295af0df38 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards e9ab9d5025 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards ede1e1bf3e 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] discards 2fc92f428b 68: onsuccess: 1: Successful build after gcc: 2 commits new d505cf4964 68: onsuccess: 1: Successful build after gcc: 2 commits new a09aa9905f 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] new 12e4939c95 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 491d6180e9 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] new ba3e1e67e4 72: onsuccess: 1: Successful build after baseline build: no [...] new b8ce3d388b 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits new 01cda64b38 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits new 2a2713262e 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 5906e45917 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 2b5c5230c9 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 0a89a8ded5 78: onsuccess: 1: Success after binutils/gcc: 17 commits new 045666c2ab 79: onsuccess: 1: Success after binutils/gcc: 23 commits new 64353974f6 80: onsuccess: 1: Success after binutils/gcc: 8 commits new 42a343806d 81: onsuccess: 1: Success after binutils/gcc: 8 commits new d6dbae9e66 82: onsuccess: 1: Success after binutils/gcc: 9 commits new 850d386277 83: onsuccess: 1: Success after gcc: 14 commits new 7104d80b2e 84: onsuccess: 1: Success after binutils/gcc: 2 commits new 48fdc1fdca 85: onsuccess: 1: Success after binutils/gcc: 19 commits new 7abf0dc6d5 86: onsuccess: 1: Success after binutils/gcc: 8 commits new ac40fbd078 87: onsuccess: 1: Success after gcc: 6 commits new 2e5a1ce0fd 88: onsuccess: 1: Success after binutils/gcc: 2 commits new b92e684789 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] new 3eccbf38a7 90: onsuccess: #1645: 1: Success after gcc: 2 commits new e6c765428e 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] new 3944488913 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits new de8a970019 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] new 3a7f6e7410 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits new 0d8adae414 95: onsuccess: #1653: 1: Success after gcc: 13 commits new 6d514bf069 96: onsuccess: #1654: 1: Success after gcc: 5 commits new eaf29add3a 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits new fe1380cce5 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits new 7234bb06e8 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits new 6e6c84197c 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] new 4752f0d321 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits new 4c96e5e25e 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits new f44885026b 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits new 776b9a3769 104: onsuccess: #1700: 1: Success after gcc: 2 commits new 7f0e5abcb8 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits new 072183c831 106: onsuccess: #1702: 1: Success after gcc: 4 commits new 73f93e8716 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] new 26bf7c0fd0 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits new 6c25771cab 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] new a5f3103075 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits new 30e3106b4d 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits new c9e6dc43fa 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits new d5632cda6a 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits new 922b7e88bd 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits new 73c72fab31 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits new 386c6eaa4b 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits new 980e409839 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits new 0173dddb27 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits new 40f32daa51 119: onsuccess: #1715: 1: Success after binutils: 4 commits new 36d2361906 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits new f8abe4e52b 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits new e6614fc5d8 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits new 2db1a89cdf 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits new f08d180e33 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits new 2bd35d00f4 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits new 821ed3c953 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits new 862bb61357 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] new 80629bfeac 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits new b61a1b145c 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] new 72ed7a08d5 130: onsuccess: #1729: 1: Success after gcc: 9 commits new 222278ba71 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits new 53d76a7abc 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits new 8169264c85 133: onsuccess: #1733: 1: Success after binutils: 3 commits new 1387137e90 134: onsuccess: #1736: 1: Success after binutils: 3 commits new 16770e6d4f 135: onsuccess: #1739: 1: Success after binutils: 4 commits new b5662c85fe 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] new 5e865fdf46 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] new 02774ab1b6 138: onsuccess: #1749: 1: Success after binutils: 5 commits new 8d98ddd92a 139: onsuccess: #1753: 1: Success after binutils: 5 commits new c93b510d69 140: onsuccess: #1756: 1: Success after binutils: 3 commits new 4918f1d5c0 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] new d6ee3a127c 142: onsuccess: #1761: 1: Success after gcc: 83 commits new 65c46c1cb2 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits new 68eabbbc08 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits new 13a595a2b4 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits new b55abb95e2 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits new c96e965ff3 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits new 0c8788f2c0 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits new f1a9404e76 149: onsuccess: #1769: 1: Success after gcc: 3 commits new fa9ca8423d 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] new 11ce04291b 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] new 0192a2386c 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits new 08a55479fd 153: onsuccess: #1773: 1: Success after gcc: 4 commits new cd3dc299e9 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 commits new 38e0233f61 155: onsuccess: #1775: 1: Success after binutils: 2 commits new 076371d126 156: onsuccess: #1776: 1: Success after binutils/gcc: 4 commits new 2ceea8b68f 157: onsuccess: #1777: 1: Success after binutils/gcc: 3 commits new 8ee6fc98b3 158: onsuccess: #1778: 1: Success after binutils/gcc: 30 commits new 5af67c5fea 159: onsuccess: #1779: 1: Success after gcc: 2 commits new ea1c32667f 160: onsuccess: #1780: 1: Success after binutils/gcc: 4 commits new ad1fb3e4a0 161: onsuccess: #1781: 1: Success after binutils/gcc: 16 commits new e693d94714 162: onsuccess: #1782: 1: Success after binutils/gcc: 14 commits new 717d238729 163: onsuccess: #1783: 1: Success after binutils/gcc: 8 commits new 85f93e00c1 164: onsuccess: #1784: 1: Success after binutils/gcc: 11 commits new ef26785288 165: onsuccess: #1785: 1: Success after binutils/gcc: 6 commits new c376d69f46 166: onsuccess: #1786: 1: Success after gcc: 10 commits new 30be91cec6 167: onsuccess: #1787: 1: Success after gcc: 8 commits new d52f1ffb34 168: onsuccess: #1788: 1: Success after binutils/gcc: 9 commits new 17ceeaeb30 169: onsuccess: #1789: 1: Success after binutils/gcc: 30 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 (9f158895b8) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (17 [...] 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 1664 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2716 bytes 03-build_abe-binutils/console.log.xz | Bin 50816 -> 51064 bytes 04-build_abe-gcc/console.log.xz | Bin 234080 -> 234656 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3860 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2388 -> 2648 bytes 07-check_regression/console.log.xz | Bin 4608 -> 5900 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 313 ++- 08-update_baseline/console.log | 58 +- 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 2785020 -> 2800672 bytes sumfiles/g++.sum | 337 ++- sumfiles/gcc.log.xz | Bin 2407348 -> 2398092 bytes sumfiles/gcc.sum | 4724 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 908220 -> 906916 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2172 -> 2164 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 204624 -> 204700 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2532 -> 2548 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 468848 -> 470712 bytes sumfiles/libstdc++.sum | 10 +- 31 files changed, 3062 insertions(+), 2496 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 (e18d6daa24 -> ac4b585383)

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 e18d6daa24 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards 853e7c7717 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards 7ac3f867b8 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards 69a39416ea 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 5006cb03e1 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards 777eaffdd2 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards 1e993eed7b 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards c2765a2fb5 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards b6153acd4f 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 99bef2312a 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards 83c7b85621 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 4b6ea9ac2a 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards db3c83745b 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 4d9f7af32d 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards b7f7f4a43d 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards ac91615e37 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 1edf1366c0 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 3f332cd4c5 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards d9070cfc69 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 77b8765cee 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 6bd3f33ae2 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards e6448de526 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards ea4f9d04d6 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 163fffdc8e 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 5f8b71c40a 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 5088c378cb 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 3605df8610 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards b7ed1a9a2f 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 851981a1fc 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 2a7f3babad 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 5e45b6d5f9 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards c95358486e 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 3419c2bbf7 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards a9c378a4aa 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards e79832f07f 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 5680f760e8 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 8514d48403 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 875c9ef0d2 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 2ea701dd33 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 809b3241c6 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 7fb40cc54c 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 0dd86766a7 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards fc2699cfa2 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 6877f7a418 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 6769d555f0 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 0435bca341 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards df2b71fac2 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 50925b503f 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 728be28c77 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 329cb6c5f3 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards b3ffa4d7df 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 34a0f2a046 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 3e5bf61a7b 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards c0fa9f1f50 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 3d15d1822f 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 5c85382a78 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 3925fed944 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 21a3ba8ceb 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 2a1e600fa3 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 7478b50a97 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards dbb042f0fe 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 0ae0b09ded 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards f0873b63c0 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 51f3228056 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards b2497a9718 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards fad593599b 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 5430c691f6 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 790dffe978 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 20dd0aeaea 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards ecba86c5c8 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 3379109346 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 17930ed0b7 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards a455d7d603 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards d91b4de0cc 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 7a296ca038 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 0dd27c0cf8 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 88e6a82edd 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 798df13a5a 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 4198919a83 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 06b0404741 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 8cc7353f56 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 60e760c285 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 4fc3690a9b 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards e1385db204 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 1027e8d691 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards dc7e0d8a98 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 848c3a470c 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards ed3f60a930 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards ac0152c59d 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 484ba5ae18 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 503febccbd 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 01873480a6 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 91ea91fd94 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 39a7e3bee3 75: onsuccess: 1: Successful build after linux: 44 commits discards 458b65aa96 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 830496133e 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8d4ebcfcbf 72: onsuccess: 1: Successful build after linux: 12 commits discards 242af325d3 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards c69d6497e3 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 5c11a675b2 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 8fefcf48b0 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4ad3077db3 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bf6428eff5 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 78e3b09cd7 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new e47725fe06 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 92c7a35100 72: onsuccess: 1: Successful build after linux: 12 commits new 82a9b615ac 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d85ab6e05a 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 76b8ecdf6b 75: onsuccess: 1: Successful build after linux: 44 commits new 162ac62811 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 110e4e4988 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 78c7fa04c7 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 1e2535173e 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0b36046607 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 6de47d02e4 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new f60f857584 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 12d8245521 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 31e531637a 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 650d755ccc 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 2add9a7170 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 3dc5ada593 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new ca43f887b5 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 12939b4017 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 6bba865f7d 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 942fe15a7d 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 5350572a74 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 0b7a09e171 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 4602abe110 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 145b527a2e 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new b31e8341fd 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 7dc6eece9a 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new c31ac63f72 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 472ab4581b 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 855f01adf2 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 313f240578 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 1c23142ba6 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new e1d84ec7d5 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new f3a389fef4 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new fee4097cca 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 53ccd48622 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 7ff5ac3616 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new d1fbe57af4 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 5e8ec89d49 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 398c4bf10d 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new f2a9872c0e 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 7ef997f5c3 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 88a7e320c1 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 7b76344c79 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 30517d7931 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 89120d82ba 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new f7fb1df333 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new a70251f01e 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 0dd62a1d2b 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 389500abe4 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 2877cc1461 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 107abfe735 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new ee149f6f97 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 8d9c029fea 124: onsuccess: #2159: 1: Success after linux: 23 commits new e9bfa109f9 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new a6468dc900 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new ddcf2409ec 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 6d2e97c045 128: onsuccess: #2163: 1: Success after linux: 23 commits new 7b73dd2199 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 147bff82fb 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new d05b6864d2 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 43a59370c5 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 72924c8784 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 2ac2e4fbf6 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new e95cb6d7f6 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 68f747eaa7 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 6abfd39626 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 3adec6a604 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 837e8171c0 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 7933641e8d 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 67939d7c4d 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new c54e997681 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new ffd17911d0 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new d545157c6a 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 4f84ab730e 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new ca7702cb12 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new b922dc1a20 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 945a9ad034 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 7273546e78 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new ee4d018647 150: onsuccess: #2185: 1: Success after gcc: 3 commits new c618163db8 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 765357880d 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new d4ecf5e6f3 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new e4416ef864 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new f5e5c26486 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 67289af8da 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 1ff40d8d51 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new eba5773860 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 03f94bd424 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 1bc86276ec 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 848b8eb4ba 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new 1eef9370f9 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new e7a6515952 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new fca5e90383 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new eacb44af22 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 23c73fe47d 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new 3ee4e9c169 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new abafad1d63 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new ac4b585383 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/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 (e18d6daa24) \ 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 1708 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30136 -> 30612 bytes 04-build_abe-stage1/console.log.xz | Bin 72176 -> 72668 bytes 06-build_abe-linux/console.log.xz | Bin 9468 -> 9456 bytes 07-build_abe-glibc/console.log.xz | Bin 240004 -> 240312 bytes 08-build_abe-stage2/console.log.xz | Bin 202628 -> 203316 bytes 09-build_abe-gdb/console.log.xz | Bin 37372 -> 37676 bytes 10-build_abe-qemu/console.log.xz | Bin 31792 -> 31376 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3924 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2464 -> 2656 bytes 13-check_regression/console.log.xz | Bin 6384 -> 12400 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 98 +- 13-check_regression/mail-body.txt | 129 +- 13-check_regression/results.compare | 123 +- 13-check_regression/results.compare2 | 1132 ++++++- 13-check_regression/results.regressions | 98 +- 14-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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 131 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 98 +- sumfiles/g++.log.xz | Bin 3443748 -> 3438112 bytes sumfiles/g++.sum | 363 ++- sumfiles/gcc.log.xz | Bin 3017360 -> 3007960 bytes sumfiles/gcc.sum | 5021 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1032696 -> 1028612 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202740 -> 202472 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 424924 -> 424388 bytes sumfiles/libstdc++.sum | 6 +- 43 files changed, 4514 insertions(+), 2815 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[glibc] branch master updated (e76369ed63 -> 90d58fe844)

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 glibc. from e76369ed63 elf: Simplify output of hwcap subdirectories in ld.so help new 90d58fe844 NEWS: Fix grammar 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: NEWS | 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 (db2f5d66123 -> 33b93ac3f2f)

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 db2f5d66123 aarch64: update Ampere-1 core definition new badd1ac23d2 aarch64: Add test for LDAR generation from __atomic_load_n new 33b93ac3f2f aarch64: Remove redundant zero-extends with LDAR The 2 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/aarch64/atomics.md | 17 ++++++++ gcc/testsuite/gcc.target/aarch64/ldar_1.c | 66 +++++++++++++++++++++++++++++++ gcc/testsuite/gcc.target/aarch64/ldar_2.c | 27 +++++++++++++ 3 files changed, 110 insertions(+) create mode 100644 gcc/testsuite/gcc.target/aarch64/ldar_1.c create mode 100644 gcc/testsuite/gcc.target/aarch64/ldar_2.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[glibc] branch master updated (7fe6734d28 -> e76369ed63)

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 glibc. from 7fe6734d28 Update to Unicode 15.0.0 [BZ #29604] new d178c67535 x86_64: Remove platform directory library loading test new 6099908fb8 elf: Remove legacy hwcaps support from the dynamic loader new b78ff5a25d elf: Remove legacy hwcaps support from ldconfig new 4a7094119c elf: Remove hwcap parameter from add_to_cache signature new cfbf883db3 elf: Remove hwcap and bits_hwcap fields from struct cache_entry new 78d9a1620b Add NEWS entry for legacy hwcaps removal new ab40f20364 elf: Remove _dl_string_hwcap new e76369ed63 elf: Simplify output of hwcap subdirectories in ld.so help The 8 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: NEWS | 5 +- elf/Makefile | 6 - elf/cache.c | 42 ++---- elf/dl-hwcaps.c | 184 ++------------------------ elf/dl-usage.c | 75 +---------- elf/ldconfig.c | 156 ++-------------------- sysdeps/alpha/dl-procinfo.h | 2 - sysdeps/csky/dl-procinfo.h | 2 - sysdeps/generic/dl-procinfo.h | 2 - sysdeps/generic/ldconfig.h | 2 +- sysdeps/mips/dl-procinfo.h | 2 - sysdeps/powerpc/dl-procinfo.h | 10 -- sysdeps/s390/dl-procinfo.h | 14 -- sysdeps/sparc/dl-procinfo.h | 13 -- sysdeps/unix/sysv/linux/aarch64/dl-procinfo.h | 12 -- sysdeps/unix/sysv/linux/arm/dl-procinfo.h | 12 -- sysdeps/x86/dl-hwcap.h | 14 -- sysdeps/x86_64/Makefile | 16 --- sysdeps/x86_64/tst-x86_64-1.c | 26 ---- sysdeps/x86_64/tst-x86_64mod-1.c | 22 --- 20 files changed, 40 insertions(+), 577 deletions(-) delete mode 100644 sysdeps/x86_64/tst-x86_64-1.c delete mode 100644 sysdeps/x86_64/tst-x86_64mod-1.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_kernel/gnu-release-arm-next-allnoconfig updated (1bb6804a87 -> 9a0ae7d80f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-arm-next-allnoconfig in repository toolchain/ci/base-artifacts. from 1bb6804a87 13: onsuccess: #372: all: Success after binutils/gcc/linux/q [...] new 9a0ae7d80f 14: onsuccess: #373: all: Success after binutils/gcc/linux/q [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1692 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 29796 -> 29916 bytes 04-build_abe-stage1/console.log.xz | Bin 86936 -> 86800 bytes 05-build_abe-qemu/console.log.xz | Bin 31292 -> 30748 bytes 06-build_linux/console.log.xz | Bin 3040 -> 3020 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4164 -> 4096 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits October 2022