Tcwg-commits November 2022

tcwg-commits@lists.linaro.org

5 participants
4683 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_tk1/gnu-master-arm-spec2k6-O3 updated (9538a3d8c8 -> b1b65f825d)

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-master-arm-spec2k6-O3 in repository toolchain/ci/base-artifacts. from 9538a3d8c8 27: onsuccess: #506: 1: [TCWG CI] No change after binutils/g [...] new b1b65f825d 28: onsuccess: #507: 1: [TCWG CI] No change after binutils/g [...] 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 1748 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 31152 -> 32588 bytes 04-build_abe-stage1/console.log.xz | Bin 93524 -> 95188 bytes 05-clean_sysroot/console.log.xz | Bin 336 -> 336 bytes 06-build_abe-linux/console.log.xz | Bin 8696 -> 8688 bytes 07-build_abe-glibc/console.log.xz | Bin 237816 -> 237628 bytes 08-build_abe-stage2/console.log.xz | Bin 218448 -> 217052 bytes 09-benchmark/benchmark-build.log | 132 +- 09-benchmark/benchmark.log | 130 +- 09-benchmark/console.log.xz | Bin 3904 -> 3872 bytes 10-check_regression/console.log.xz | Bin 17372 -> 17016 bytes .../csv-results-vs-first-1/md5sum.csv | 2718 +- .../csv-results-vs-first-1/perf.csv | 3310 +- .../csv-results-vs-first-1/results.csv | 21932 +- .../csv-results-vs-first-1/size.csv | 545224 +++++++++--------- .../csv-results-vs-first-1/vect.csv | 250 +- .../csv-results-vs-prev-0/md5sum.csv | 2895 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 3354 +- .../csv-results-vs-prev-0/results.csv | 25431 +- 10-check_regression/csv-results-vs-prev-0/size.csv | 447814 +++++++------- 10-check_regression/csv-results-vs-prev-0/vect.csv | 416 +- .../csv-results-vs-prev-1/md5sum.csv | 2718 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 3310 +- .../csv-results-vs-prev-1/results.csv | 21932 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 545224 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/vect.csv | 250 +- 10-check_regression/results-vs-first-brief.csv | 68 +- 10-check_regression/results-vs-first-full.csv | 3142 +- 10-check_regression/results-vs-first-internal.csv | 247 +- 10-check_regression/results-vs-first.csv | 247 +- 10-check_regression/results-vs-first.log | 1346 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-compare.csv | 9 +- 10-check_regression/results-vs-prev-full.csv | 3462 +- 10-check_regression/results-vs-prev-internal.csv | 249 +- 10-check_regression/results-vs-prev.csv | 249 +- 10-check_regression/results-vs-prev.log | 1566 +- 10-check_regression/skipped-symbols.txt | 34 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 14 +- .../400.perlbench/results-metrics.json | 2 +- .../squad-vs-first/401.bzip2/results-metadata.json | 14 +- .../squad-vs-first/401.bzip2/results-metrics.json | 2 +- .../squad-vs-first/403.gcc/results-metadata.json | 14 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../410.bwaves/results-metadata.json | 14 +- .../416.gamess/results-metadata.json | 14 +- .../squad-vs-first/416.gamess/results-metrics.json | 2 +- .../squad-vs-first/429.mcf/results-metadata.json | 14 +- .../squad-vs-first/433.milc/results-metadata.json | 14 +- .../434.zeusmp/results-metadata.json | 14 +- .../435.gromacs/results-metadata.json | 14 +- .../436.cactusADM/results-metadata.json | 14 +- .../437.leslie3d/results-metadata.json | 14 +- .../squad-vs-first/444.namd/results-metadata.json | 14 +- .../squad-vs-first/445.gobmk/results-metadata.json | 14 +- .../447.dealII/results-metadata.json | 14 +- .../450.soplex/results-metadata.json | 14 +- .../453.povray/results-metadata.json | 14 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../454.calculix/results-metadata.json | 14 +- .../squad-vs-first/456.hmmer/results-metadata.json | 14 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 14 +- .../squad-vs-first/458.sjeng/results-metrics.json | 2 +- .../459.GemsFDTD/results-metadata.json | 14 +- .../462.libquantum/results-metadata.json | 14 +- .../464.h264ref/results-metadata.json | 14 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/465.tonto/results-metadata.json | 14 +- .../squad-vs-first/470.lbm/results-metadata.json | 14 +- .../471.omnetpp/results-metadata.json | 14 +- .../squad-vs-first/473.astar/results-metadata.json | 14 +- .../squad-vs-first/481.wrf/results-metadata.json | 14 +- .../squad-vs-first/481.wrf/results-metrics.json | 2 +- .../482.sphinx3/results-metadata.json | 14 +- .../483.xalancbmk/results-metadata.json | 14 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 14 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 44 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results_id | 2 +- 89 files changed, 790012 insertions(+), 848409 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

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

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 ecb848f007 319: onsuccess: #1954: 1: Success after binutils/gcc: 9 commits discards c2c48936d8 318: onsuccess: #1953: 1: Success after gcc: 11 commits discards fc7653bc86 317: onsuccess: #1952: 1: Success after binutils/gcc: 22 commits discards d5be99b6ff 316: onsuccess: #1951: 1: Success after binutils/gcc: 8 commits discards 5e061377ba 315: onsuccess: #1950: 1: Success after basepoints/gcc-13-40 [...] discards e1ebc0123a 314: onsuccess: #1949: 1: Success after binutils/gcc: 17 commits discards 900f0fb76a 313: onsuccess: #1948: 1: Success after binutils/gcc: 105 commits discards beaa3f4f0a 312: onsuccess: #1947: 1: Success after gcc: 87 commits discards a33bcfcabc 311: onsuccess: #1945: 1: Success after binutils: 3 commits discards 772e8c5000 310: onsuccess: #1941: 1: Success after binutils: 2 commits discards 7204abdd46 309: onsuccess: #1938: 1: Success after gdb-12-branchpoint-2 [...] discards a1dbd34654 308: onsuccess: #1934: 1: Success after gdb-12-branchpoint-2 [...] discards 4c5394df8d 307: onsuccess: #1931: 1: Success after binutils: 2 commits discards 155b451828 306: onsuccess: #1928: 1: Success after gdb-12-branchpoint-2 [...] discards f4a4bce889 305: onsuccess: #1926: 1: Success after binutils/gcc: 8 commits discards 8d58669ea4 304: onsuccess: #1925: 1: Success after binutils/gcc: 21 commits discards dfd46e130c 303: onsuccess: #1924: 1: Success after binutils/gcc: 23 commits discards ba79efcd50 302: onsuccess: #1923: 1: Success after binutils/gcc: 6 commits discards 8347d1fa23 301: onsuccess: #1922: 1: Success after binutils/gcc: 13 commits discards e4dcd582b8 300: onsuccess: #1921: 1: Success after binutils/gcc: 18 commits discards 264e88cb93 299: onsuccess: #1920: 1: Success after binutils/gcc: 12 commits discards a0fac9651e 298: onsuccess: #1919: 1: Success after binutils/gcc: 7 commits discards 9ee8939a98 297: onsuccess: #1918: 1: Success after binutils/gcc: 12 commits discards 78d79a9be3 296: onsuccess: #1917: 1: Success after binutils/gcc: 14 commits discards 9a7b02cec0 295: onsuccess: #1916: 1: Success after binutils/gcc: 29 commits discards 100c5db419 294: onsuccess: #1915: 1: Success after binutils/gcc: 6 commits discards a24939c607 293: onsuccess: #1914: 1: Success after binutils/gcc: 12 commits discards 17b2e0121b 292: onsuccess: #1913: 1: Success after binutils/gcc: 11 commits discards d6157f82bf 291: onsuccess: #1912: 1: Success after binutils/gcc: 30 commits discards d86a054620 290: onsuccess: #1911: 1: Success after binutils/gcc: 15 commits discards 552737750f 289: onsuccess: #1910: 1: Success after binutils/gcc: 8 commits discards 9883039ce9 288: onsuccess: #1909: 1: Success after binutils/gcc: 18 commits discards b192dfdb5f 287: onsuccess: #1908: 1: Success after gcc: 36 commits discards 0201f6893a 286: onsuccess: #1907: 1: Success after binutils/gcc: 8 commits discards e3032546b7 285: onsuccess: #1906: 1: Success after basepoints/gcc-13-37 [...] discards 8a4641ab6b 284: onsuccess: #1905: 1: Success after binutils/gcc: 8 commits discards 20a312c048 283: onsuccess: #1904: 1: Success after basepoints/gcc-13-37 [...] discards ab063b6440 282: onsuccess: #1903: 1: Success after binutils/gcc: 4 commits discards 96d0239a0e 281: onsuccess: #1902: 1: Success after gcc: 2 commits discards 3c332d2084 280: onsuccess: #1901: 1: Success after binutils/gcc: 10 commits discards 1673368c57 279: onsuccess: #1900: 1: Success after basepoints/gcc-13-36 [...] discards 65f920b381 278: onsuccess: #1899: 1: Success after binutils: 9 commits discards 5f094c289e 277: onsuccess: #1898: 1: Success after gcc: 4 commits discards fc80eae70f 276: onsuccess: #1897: 1: Success after binutils/gcc: 42 commits discards c445ae3806 275: onsuccess: #1896: 1: Success after binutils/gcc: 12 commits discards 13d1475255 274: onsuccess: #1895: 1: Success after binutils/gcc: 13 commits discards 13a3db2958 273: onsuccess: #1894: 1: Success after binutils/gcc: 20 commits discards f882fb22cc 272: onsuccess: #1893: 1: Success after binutils/gcc: 12 commits discards b02d4d11bd 271: onsuccess: #1892: 1: Success after binutils/gcc: 7 commits discards 9c0339ca1a 270: onsuccess: #1891: 1: Success after binutils/gcc: 3 commits discards b0544bdc82 269: onsuccess: #1890: 1: Success after binutils/gcc: 8 commits discards 75694ecf64 268: onsuccess: #1889: 1: Success after binutils/gcc: 11 commits discards 3fd47185fb 267: onsuccess: #1888: 1: Success after binutils/gcc: 6 commits discards b58f58c57c 266: onsuccess: #1887: 1: Success after binutils/gcc: 8 commits discards fa42b646b7 265: onsuccess: #1886: 1: Success after gcc: 5 commits discards 6a6dcaf5c5 264: onsuccess: #1885: 1: Success after binutils/gcc: 9 commits discards 7a37aac19a 263: onsuccess: #1884: 1: Success after binutils/gcc: 5 commits discards b57fe27598 262: onsuccess: #1883: 1: Success after binutils/gcc: 7 commits discards b05f9e2ec1 261: onsuccess: #1882: 1: Success after binutils/gcc: 6 commits discards 7f779e8ec6 260: onsuccess: #1881: 1: Success after binutils/gcc: 19 commits discards 29fcf95b2d 259: onsuccess: #1880: 1: Success after binutils/gcc: 8 commits discards 77f097ea79 258: onsuccess: #1879: 1: Success after binutils/gcc: 6 commits discards 64eeeb5700 257: onsuccess: #1878: 1: Success after gdb-12-branchpoint-2 [...] discards 219219679a 256: onsuccess: #1877: 1: Success after binutils/gcc: 2 commits discards cb2daafb72 255: onsuccess: #1876: 1: Success after binutils/gcc: 4 commits discards 79fa1723b2 254: onsuccess: #1875: 1: Success after binutils/gcc: 13 commits discards a675e1ac79 253: onsuccess: #1874: 1: Success after binutils/gcc: 10 commits discards d9f34295b8 252: onsuccess: #1873: 1: Success after binutils/gcc: 4 commits discards 0696776734 251: onsuccess: #1872: 1: Success after binutils/gcc: 10 commits discards 04c2f3609e 250: onsuccess: #1871: 1: Success after binutils/gcc: 11 commits discards 1ddad54add 249: onsuccess: #1870: 1: Success after binutils/gcc: 9 commits discards 9a8413d1fa 248: onsuccess: #1869: 1: Success after gcc: 4 commits discards 509dd5befc 247: onsuccess: #1868: 1: Success after binutils/gcc: 7 commits discards f1b9cb92ab 246: onsuccess: #1867: 1: Success after binutils/gcc: 8 commits discards 9b69f1015a 245: onsuccess: #1866: 1: Success after binutils/gcc: 8 commits discards ef0a04a8a2 244: onsuccess: #1865: 1: Success after gcc: 6 commits discards ca8bc7681d 243: onsuccess: #1864: 1: Success after binutils/gcc: 6 commits discards 4a76e84a6b 242: onsuccess: #1863: 1: Success after binutils/gcc: 17 commits discards 8a7949481a 241: onsuccess: #1862: 1: Success after binutils/gcc: 5 commits discards e2dfc16413 240: onsuccess: #1861: 1: Success after gcc: 6 commits discards b06537a3e3 239: onsuccess: #1860: 1: Success after binutils/gcc: 9 commits discards 669e701095 238: onsuccess: #1859: 1: Success after binutils/gcc: 14 commits discards bf59d84ac8 237: onsuccess: #1858: 1: Success after binutils/gcc: 6 commits discards 07291eda7e 236: onsuccess: #1857: 1: Success after binutils/gcc: 10 commits discards 24e9f18b27 235: onsuccess: #1856: 1: Success after binutils/gcc: 18 commits discards fcb81a6fac 234: onsuccess: #1855: 1: Success after binutils/gcc: 7 commits discards d434c39a2a 233: onsuccess: #1854: 1: Success after binutils/gcc: 6 commits discards c4e8ec46b9 232: onsuccess: #1853: 1: Success after binutils: 3 commits discards 478270888e 231: onsuccess: #1852: 1: Success after binutils/gcc: 4 commits discards 06214a266b 230: onsuccess: #1851: 1: Success after basepoints/gcc-13-34 [...] discards 403ab33a1f 229: onsuccess: #1850: 1: Success after basepoints/gcc-13-34 [...] discards 0603064a73 228: onsuccess: #1849: 1: Success after binutils/gcc: 3 commits discards 36ddc2a4cc 227: onsuccess: #1848: 1: Success after binutils/gcc: 4 commits discards c330a4c28c 226: onsuccess: #1847: 1: Success after binutils/gcc: 8 commits discards b06a7c1ad0 225: onsuccess: #1846: 1: Success after binutils/gcc: 18 commits discards 7b717d265f 224: onsuccess: #1845: 1: Success after binutils/gcc: 9 commits discards eb1fcca81f 223: onsuccess: #1844: 1: Success after gcc: 7 commits discards 99dd14e3d7 222: onsuccess: #1843: 1: Success after binutils/gcc: 17 commits discards d223a8b783 221: onsuccess: #1842: 1: Success after binutils/gcc: 15 commits discards 9457af8d88 220: onsuccess: #1841: 1: Success after binutils/gcc: 10 commits discards b845e51a3d 219: onsuccess: #1840: 1: Success after gcc: 7 commits new b06b1bb47f 219: onsuccess: #1840: 1: Success after gcc: 7 commits new ae3374026c 220: onsuccess: #1841: 1: Success after binutils/gcc: 10 commits new b86f2427ca 221: onsuccess: #1842: 1: Success after binutils/gcc: 15 commits new 9a43246ea0 222: onsuccess: #1843: 1: Success after binutils/gcc: 17 commits new 162ad822e6 223: onsuccess: #1844: 1: Success after gcc: 7 commits new 98562d49ff 224: onsuccess: #1845: 1: Success after binutils/gcc: 9 commits new a6d09a7423 225: onsuccess: #1846: 1: Success after binutils/gcc: 18 commits new aac79c867f 226: onsuccess: #1847: 1: Success after binutils/gcc: 8 commits new df44cf7959 227: onsuccess: #1848: 1: Success after binutils/gcc: 4 commits new 8ad9f59c5a 228: onsuccess: #1849: 1: Success after binutils/gcc: 3 commits new ab7030494d 229: onsuccess: #1850: 1: Success after basepoints/gcc-13-34 [...] new 2242f71157 230: onsuccess: #1851: 1: Success after basepoints/gcc-13-34 [...] new 9ee7275a5d 231: onsuccess: #1852: 1: Success after binutils/gcc: 4 commits new 82b41e4504 232: onsuccess: #1853: 1: Success after binutils: 3 commits new 8643aa285f 233: onsuccess: #1854: 1: Success after binutils/gcc: 6 commits new 9935b5fd9e 234: onsuccess: #1855: 1: Success after binutils/gcc: 7 commits new 7394253f82 235: onsuccess: #1856: 1: Success after binutils/gcc: 18 commits new 0839a5c238 236: onsuccess: #1857: 1: Success after binutils/gcc: 10 commits new 93fe670e9a 237: onsuccess: #1858: 1: Success after binutils/gcc: 6 commits new 2850c12e44 238: onsuccess: #1859: 1: Success after binutils/gcc: 14 commits new bba91e23a9 239: onsuccess: #1860: 1: Success after binutils/gcc: 9 commits new dfce7f42f8 240: onsuccess: #1861: 1: Success after gcc: 6 commits new 2d720d4d84 241: onsuccess: #1862: 1: Success after binutils/gcc: 5 commits new 9f82ac12ce 242: onsuccess: #1863: 1: Success after binutils/gcc: 17 commits new 0d3a043532 243: onsuccess: #1864: 1: Success after binutils/gcc: 6 commits new eea98b0f6e 244: onsuccess: #1865: 1: Success after gcc: 6 commits new ae5807649c 245: onsuccess: #1866: 1: Success after binutils/gcc: 8 commits new 9508665c7c 246: onsuccess: #1867: 1: Success after binutils/gcc: 8 commits new 167e4b30b7 247: onsuccess: #1868: 1: Success after binutils/gcc: 7 commits new d88dbaa9ed 248: onsuccess: #1869: 1: Success after gcc: 4 commits new 8f5935f418 249: onsuccess: #1870: 1: Success after binutils/gcc: 9 commits new e7146533b4 250: onsuccess: #1871: 1: Success after binutils/gcc: 11 commits new 14d39dcf08 251: onsuccess: #1872: 1: Success after binutils/gcc: 10 commits new 591403ed0c 252: onsuccess: #1873: 1: Success after binutils/gcc: 4 commits new aa4e0db93e 253: onsuccess: #1874: 1: Success after binutils/gcc: 10 commits new c865eb0c0c 254: onsuccess: #1875: 1: Success after binutils/gcc: 13 commits new 96984c16b5 255: onsuccess: #1876: 1: Success after binutils/gcc: 4 commits new e3d31c1dce 256: onsuccess: #1877: 1: Success after binutils/gcc: 2 commits new d0549449a0 257: onsuccess: #1878: 1: Success after gdb-12-branchpoint-2 [...] new 44fe3827d8 258: onsuccess: #1879: 1: Success after binutils/gcc: 6 commits new 90d8fba506 259: onsuccess: #1880: 1: Success after binutils/gcc: 8 commits new 679e23b90c 260: onsuccess: #1881: 1: Success after binutils/gcc: 19 commits new 99efa428d5 261: onsuccess: #1882: 1: Success after binutils/gcc: 6 commits new 1b363f464b 262: onsuccess: #1883: 1: Success after binutils/gcc: 7 commits new 1f30bc3aff 263: onsuccess: #1884: 1: Success after binutils/gcc: 5 commits new d30bb384c7 264: onsuccess: #1885: 1: Success after binutils/gcc: 9 commits new 21d7f05065 265: onsuccess: #1886: 1: Success after gcc: 5 commits new 8e12b79ca4 266: onsuccess: #1887: 1: Success after binutils/gcc: 8 commits new ba79c52207 267: onsuccess: #1888: 1: Success after binutils/gcc: 6 commits new 9c581fbccf 268: onsuccess: #1889: 1: Success after binutils/gcc: 11 commits new aaca26ff66 269: onsuccess: #1890: 1: Success after binutils/gcc: 8 commits new d04184c6b7 270: onsuccess: #1891: 1: Success after binutils/gcc: 3 commits new 1d4465a8aa 271: onsuccess: #1892: 1: Success after binutils/gcc: 7 commits new d88cf13f7a 272: onsuccess: #1893: 1: Success after binutils/gcc: 12 commits new c5de670754 273: onsuccess: #1894: 1: Success after binutils/gcc: 20 commits new 3b2dbf2b57 274: onsuccess: #1895: 1: Success after binutils/gcc: 13 commits new c570d07925 275: onsuccess: #1896: 1: Success after binutils/gcc: 12 commits new 6b553a6e44 276: onsuccess: #1897: 1: Success after binutils/gcc: 42 commits new d71fea1ca0 277: onsuccess: #1898: 1: Success after gcc: 4 commits new 552deb88b9 278: onsuccess: #1899: 1: Success after binutils: 9 commits new a1b3509c11 279: onsuccess: #1900: 1: Success after basepoints/gcc-13-36 [...] new 3a2e2940d7 280: onsuccess: #1901: 1: Success after binutils/gcc: 10 commits new 2eb059165b 281: onsuccess: #1902: 1: Success after gcc: 2 commits new 51070e0d0c 282: onsuccess: #1903: 1: Success after binutils/gcc: 4 commits new c9e6dbe94a 283: onsuccess: #1904: 1: Success after basepoints/gcc-13-37 [...] new 20206cd139 284: onsuccess: #1905: 1: Success after binutils/gcc: 8 commits new b8b107b5dd 285: onsuccess: #1906: 1: Success after basepoints/gcc-13-37 [...] new e5a38ca8c0 286: onsuccess: #1907: 1: Success after binutils/gcc: 8 commits new 3a9e1faf89 287: onsuccess: #1908: 1: Success after gcc: 36 commits new ef2539c6d2 288: onsuccess: #1909: 1: Success after binutils/gcc: 18 commits new 4c21248019 289: onsuccess: #1910: 1: Success after binutils/gcc: 8 commits new ebfc141f06 290: onsuccess: #1911: 1: Success after binutils/gcc: 15 commits new 27aefb48a9 291: onsuccess: #1912: 1: Success after binutils/gcc: 30 commits new 969b75dd48 292: onsuccess: #1913: 1: Success after binutils/gcc: 11 commits new fd8f2e3c69 293: onsuccess: #1914: 1: Success after binutils/gcc: 12 commits new 806f34b99d 294: onsuccess: #1915: 1: Success after binutils/gcc: 6 commits new 3f1e1d977f 295: onsuccess: #1916: 1: Success after binutils/gcc: 29 commits new f35a0c699f 296: onsuccess: #1917: 1: Success after binutils/gcc: 14 commits new ec962b8355 297: onsuccess: #1918: 1: Success after binutils/gcc: 12 commits new c349bd5955 298: onsuccess: #1919: 1: Success after binutils/gcc: 7 commits new 35e7595843 299: onsuccess: #1920: 1: Success after binutils/gcc: 12 commits new 7345665679 300: onsuccess: #1921: 1: Success after binutils/gcc: 18 commits new a9754a2918 301: onsuccess: #1922: 1: Success after binutils/gcc: 13 commits new 6bb1a18815 302: onsuccess: #1923: 1: Success after binutils/gcc: 6 commits new 8c3d3f024d 303: onsuccess: #1924: 1: Success after binutils/gcc: 23 commits new 2cb709650e 304: onsuccess: #1925: 1: Success after binutils/gcc: 21 commits new 4f25634136 305: onsuccess: #1926: 1: Success after binutils/gcc: 8 commits new 9d2754a3f9 306: onsuccess: #1928: 1: Success after gdb-12-branchpoint-2 [...] new bcd1f0380d 307: onsuccess: #1931: 1: Success after binutils: 2 commits new 76dfc5de6d 308: onsuccess: #1934: 1: Success after gdb-12-branchpoint-2 [...] new bc155aa3b3 309: onsuccess: #1938: 1: Success after gdb-12-branchpoint-2 [...] new 68aefa8408 310: onsuccess: #1941: 1: Success after binutils: 2 commits new e7da85faea 311: onsuccess: #1945: 1: Success after binutils: 3 commits new 23cac7a7e3 312: onsuccess: #1947: 1: Success after gcc: 87 commits new ec95dd0890 313: onsuccess: #1948: 1: Success after binutils/gcc: 105 commits new 5cb2074993 314: onsuccess: #1949: 1: Success after binutils/gcc: 17 commits new 30c0e52568 315: onsuccess: #1950: 1: Success after basepoints/gcc-13-40 [...] new 1ec8f39c4d 316: onsuccess: #1951: 1: Success after binutils/gcc: 8 commits new 827073ffc7 317: onsuccess: #1952: 1: Success after binutils/gcc: 22 commits new b18f042d73 318: onsuccess: #1953: 1: Success after gcc: 11 commits new 76624783ef 319: onsuccess: #1954: 1: Success after binutils/gcc: 9 commits new a5c09544dc 320: onsuccess: #1955: 1: Success after binutils/gcc: 11 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 (ecb848f007) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (a5 [...] 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 1680 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 52108 -> 52824 bytes 04-build_abe-gcc/console.log.xz | Bin 236068 -> 233196 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3824 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2732 -> 2788 bytes 07-check_regression/console.log.xz | Bin 5068 -> 4876 bytes 07-check_regression/results.compare2 | 49 +- 08-update_baseline/console.log | 48 +- 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 +- sumfiles/g++.log.xz | Bin 2786672 -> 2793376 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 2399920 -> 2414984 bytes sumfiles/gcc.sum | 4456 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 928516 -> 915660 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2180 -> 2172 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216100 -> 216396 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2532 -> 2532 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 470356 -> 470220 bytes sumfiles/libstdc++.sum | 2 +- 30 files changed, 2281 insertions(+), 2320 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[gcc] branch master updated (06c8f2ebf06 -> 705bae2351a)

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 06c8f2ebf06 aarch64: Add mode size check on LDAPR-extend patterns new 705bae2351a Enable shrink wrapping for the RISC-V target. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/config/riscv/riscv.cc | 193 ++++++++++++++++++++++++- gcc/testsuite/gcc.target/riscv/shrink-wrap-1.c | 24 +++ 2 files changed, 215 insertions(+), 2 deletions(-) create mode 100644 gcc/testsuite/gcc.target/riscv/shrink-wrap-1.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[gcc] branch master updated (822a0823c01 -> 06c8f2ebf06)

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 822a0823c01 [PR68097] Try to avoid recursing for floats in gimple_stmt_ [...] new 06c8f2ebf06 aarch64: Add mode size check on LDAPR-extend patterns The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/config/aarch64/atomics.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-next-allyesconfig updated (c460cfb855 -> f9092be3ca)

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-next-allyesconfig in repository toolchain/ci/base-artifacts. from c460cfb855 36: onsuccess: #437: 21519: Success after linux: 7480 commits new f9092be3ca 37: onsuccess: #438: 21541: Success after binutils/llvm/linu [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1780 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 31024 -> 29996 bytes 04-build_kernel_llvm/console.log.xz | Bin 67088 -> 64864 bytes 05-build_abe-qemu/console.log.xz | Bin 32344 -> 30648 bytes 06-build_linux/console.log.xz | Bin 3824 -> 3636 bytes 08-check_regression/console.log.xz | Bin 2992 -> 4200 bytes 08-check_regression/mail-body.txt | 13 ++----------- 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 | 15 +++------------ mail/mail-subject.txt | 2 +- manifest.sh | 31 +++++++++++++++++-------------- results | 2 +- 18 files changed, 30 insertions(+), 45 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-norov-allmodconfig updated (8b2a5a0f79 -> 545514e202)

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-aarch64-norov-allmodconfig in repository toolchain/ci/base-artifacts. from 8b2a5a0f79 26: onsuccess: #74: all: Success after binutils/gcc/qemu: 28 [...] new 545514e202 27: onsuccess: #75: all: Success after binutils/gcc/qemu: 35 [...] 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 1732 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30340 -> 30192 bytes 04-build_abe-stage1/console.log.xz | Bin 68676 -> 68448 bytes 05-build_abe-qemu/console.log.xz | Bin 32072 -> 30388 bytes 06-build_linux/console.log.xz | Bin 3488 -> 3484 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 3568 -> 3620 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +++++++++++++------------- 16 files changed, 20 insertions(+), 20 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/release-arm updated (d7ed6b3360 -> 9e9ef3abee)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/release-arm in repository toolchain/ci/base-artifacts. from d7ed6b3360 27: onsuccess: #180: 1: Success after binutils/gcc/glibc/gdb [...] new 9e9ef3abee 28: onsuccess: #181: 1: Success after binutils/gcc/linux/gdb [...] 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 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 52328 -> 51728 bytes 04-build_abe-gcc/console.log.xz | Bin 228644 -> 228588 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8700 -> 8676 bytes 07-build_abe-glibc/console.log.xz | Bin 231836 -> 233004 bytes 08-build_abe-gdb/console.log.xz | Bin 46692 -> 46336 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3876 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2048 -> 2136 bytes 11-check_regression/console.log.xz | Bin 12836 -> 14040 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 59 +- 11-check_regression/mail-body.txt | 200 +- 11-check_regression/results.compare | 99 +- 11-check_regression/results.compare2 | 1640 ++++--- 11-check_regression/results.regressions | 105 +- 12-update_baseline/console.log | 9 - dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 202 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 105 +- sumfiles/gdb.log.xz | Bin 1698464 -> 1690908 bytes sumfiles/gdb.sum | 7899 ++++++++++--------------------- 30 files changed, 4113 insertions(+), 6255 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[binutils-gdb] branch master updated (f4ad82b3bcc -> 1c01b236037)

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 f4ad82b3bcc Fix various procfs.c compilation errors new 1c01b236037 gdb/fortran/testsuite: print values and types of string variables 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: gdb/testsuite/gdb.fortran/string-types.exp | 70 ++++++++++++++++++++++ .../{empty-string.f90 => string-types.f90} | 31 ++++++---- 2 files changed, 89 insertions(+), 12 deletions(-) create mode 100644 gdb/testsuite/gdb.fortran/string-types.exp copy gdb/testsuite/gdb.fortran/{empty-string.f90 => string-types.f90} (53%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-allmodconfig updated (8bc549df9b -> 79ae5cab5d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-allmodconfig in repository toolchain/ci/base-artifacts. from 8bc549df9b 33: onsuccess: #500: 23279: Success after binutils/llvm/linu [...] new 79ae5cab5d 34: onsuccess: #501: 23297: Success after binutils/llvm/linu [...] 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 1696 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30228 -> 31608 bytes 04-build_kernel_llvm/console.log.xz | Bin 63072 -> 63656 bytes 05-build_abe-qemu/console.log.xz | Bin 31716 -> 30712 bytes 06-build_linux/console.log.xz | Bin 5480 -> 5100 bytes 08-check_regression/console.log.xz | Bin 4400 -> 4440 bytes 08-check_regression/mail-body.txt | 4 ++-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 6 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 18 files changed, 29 insertions(+), 29 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm updated (c35199a524 -> 490c68b38f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm in repository toolchain/ci/base-artifacts. discards c35199a524 104: onsuccess: #530: 1: Success after gcc: 7 commits discards 619a4d7ddb 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards 0e675a0efc 102: onsuccess: #527: 1: Success after binutils: 5 commits discards 1a9861129a 101: onsuccess: #524: 1: Success after binutils: 2 commits discards 42245a364b 100: onsuccess: #521: 1: Success after binutils: 10 commits discards 44f550cf75 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 015cd8a847 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] discards c423d6654d 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 13194db21b 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 2ac9b3bb53 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] discards 7cf33a9944 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] discards 692900e66a 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 5097a25c6c 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] discards 1e46606bea 91: onsuccess: #511: 1: Success after linux: 27 commits discards 3562aa0025 90: onsuccess: #510: 1: Success after glibc: 5 commits discards 46480c8800 89: onsuccess: #508: 1: Success after binutils: 12 commits discards a68f199d2e 88: onsuccess: #506: 1: Success after linux: 34 commits discards db27699b1a 87: onsuccess: #505: 1: Success after glibc: 7 commits discards b19bb60b07 86: onsuccess: #503: 1: Success after binutils: 12 commits discards 7560854d27 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 6bfe4e23ea 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards 76cb34aee7 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] discards 015ae91692 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] discards 535e47028c 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards d152630107 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards f93870e2fe 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 53556b6010 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards dac9148492 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] discards 91a1abb711 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] discards 53422731ae 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards 667dd99233 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] discards 4949bf78b4 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] discards 6227de7deb 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] discards cf99d5afb7 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] discards a9e4878636 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] discards 4f359f576a 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards b344b6004a 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] discards 283c31ca41 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards dd3fd44320 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] discards a093ea2332 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] discards a55d79240f 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards c3844ed7f3 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] discards 01a931bdc1 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] discards b150f98a46 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] discards c3f3e65550 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] discards 542590c32a 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] discards d4e53223de 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] discards 7939d69774 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] discards ac59268c63 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] discards 217c728e3a 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] discards 4c5421d35c 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] discards 3af8bde19e 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] discards e0a825116a 52: onsuccess: #467: 1: Success after binutils: 9 commits discards 0b6fc26ccd 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 494a486295 50: onsuccess: #461: 1: Success after binutils: 12 commits discards 395fe9d643 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] discards d7e5eab694 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] discards 3452d85aaf 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards 4bbc779061 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards b4a46c1d17 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] discards b0c5ecef28 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] discards cc4c93df51 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] discards 7207fa84f2 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] discards 2a2b09d867 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] discards f0da4e9a41 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] discards f1e034ede8 39: onsuccess: #447: 1: Success after binutils: 5 commits discards c2f75ae1be 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] discards 09e6af5d51 37: onsuccess: #443: 1: Success after binutils: 2 commits discards a7cabc71a4 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] discards e771176691 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] discards 5531ec717e 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] discards 586eda8f4e 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] discards cc762ebd0d 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] discards 11ce999149 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] discards aba326cff4 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] discards 985c8980ba 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] discards fefc492f06 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] discards 535cacc57a 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] discards d4c1e084c3 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] discards 2a0c81fadd 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] discards 452845463d 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits discards 60083a54f3 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 79d9663f89 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ba851123ee 21: onsuccess: 1: Successful build after linux: 79 commits discards a4e1be7597 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ed91bee117 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ed2edbe6d0 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3bb8a39b30 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7e5e8bbbe2 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 79eca72610 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards de39579727 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 238d00be32 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3cbfa1e704 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d456b90bd2 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a20e5598fd 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 67d7863da2 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards d89b802ef2 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 273ef92bb3 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards e78670cfb8 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards c49d0f6e98 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 718558ddf8 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 8a7e1bc642 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 1af1998c19 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 6146a70db3 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 9156bbcea6 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new abb8752245 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 07689f27e3 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 405dd78f02 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a2474dd003 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f00b30a7fc 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cae31c2215 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0322db8cb0 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d250580bbc 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 264fdd48cc 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 883d1b6584 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0deac18ebc 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9113d9b94e 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 83e85866fd 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 891b4871ae 21: onsuccess: 1: Successful build after linux: 79 commits new fea6b27790 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new fefe922338 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 52bf428556 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits new 654105e1b8 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] new 835b7117ae 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] new 906f5fff90 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] new b05390804f 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] new 02c15576ae 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] new 1f8f69105c 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] new e38843cdf1 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] new 7b29b84971 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] new 3552210db4 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] new d9f2291d63 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] new 8299c53f58 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] new 4b863a22e6 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] new 244304fb36 37: onsuccess: #443: 1: Success after binutils: 2 commits new 2417a70ebf 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] new 9f9aaa7b2d 39: onsuccess: #447: 1: Success after binutils: 5 commits new cb57546ca3 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] new 1818827092 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] new 65c0c380fe 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] new 5121d1e248 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] new 9f9e5ad764 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] new e8b5775f76 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] new d7718a2c2f 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new c1a4c3397d 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new 11274dc71b 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] new 98ff917993 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] new 0a963e37f8 50: onsuccess: #461: 1: Success after binutils: 12 commits new 682f552dab 51: onsuccess: #464: 1: Success after binutils: 6 commits new e0c406f98e 52: onsuccess: #467: 1: Success after binutils: 9 commits new 3f6d96b950 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] new d2fb68c84b 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] new dbaa8c49e0 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] new 5d3decdd15 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] new 227d315465 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] new 04c0db6f60 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] new d577c293e8 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] new 1d1e89fdf5 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] new f3b9a40940 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] new 0c3036625e 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] new f8515db570 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] new dcf8e76442 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new 3580dca64e 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] new b40c57d06e 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] new 485c2aca6c 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 678e9444a0 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] new 6d851f4856 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new dd6197b240 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] new 3ddf995916 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] new b38dc95763 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] new 6c3e9b392d 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] new 9e3418ddee 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] new 1b128d8ade 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new fe1bfd8048 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] new a6cbe2ea4a 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] new c2513402fb 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new e42eff3981 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new eaca57005c 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 5f88d93a94 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 38cd7dbfe8 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] new 595b1b596f 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] new 65abf4b420 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new d551e3e6a5 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 387511018f 86: onsuccess: #503: 1: Success after binutils: 12 commits new d51f8f879e 87: onsuccess: #505: 1: Success after glibc: 7 commits new dfca820456 88: onsuccess: #506: 1: Success after linux: 34 commits new 579dae44ab 89: onsuccess: #508: 1: Success after binutils: 12 commits new a269c5c7f9 90: onsuccess: #510: 1: Success after glibc: 5 commits new e7d96bcaa0 91: onsuccess: #511: 1: Success after linux: 27 commits new 015ce21636 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] new 9f858fbc22 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new 96e00e90a0 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] new 96ab60ea14 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] new 40b894e684 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 63bde97ad5 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new 8d990b29d8 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] new 69cac45d3a 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 4e0fafa4fe 100: onsuccess: #521: 1: Success after binutils: 10 commits new 76a0604094 101: onsuccess: #524: 1: Success after binutils: 2 commits new 0e76e6de43 102: onsuccess: #527: 1: Success after binutils: 5 commits new c90d5b458d 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new 411efd2d0d 104: onsuccess: #530: 1: Success after gcc: 7 commits new 490c68b38f 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] 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 (c35199a524) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1744 -> 1668 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2708 bytes 03-build_abe-binutils/console.log.xz | Bin 52736 -> 52340 bytes 04-build_abe-gcc/console.log.xz | Bin 234948 -> 233308 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8832 -> 8592 bytes 07-build_abe-glibc/console.log.xz | Bin 236372 -> 235432 bytes 08-build_abe-gdb/console.log.xz | Bin 52408 -> 51736 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3820 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2068 -> 2264 bytes 11-check_regression/console.log.xz | Bin 4872 -> 6028 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 38 ++-- 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 | 34 +-- sumfiles/binutils.log.xz | Bin 62304 -> 62236 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 98092 -> 98008 bytes sumfiles/gas.sum | 270 +++++++++++----------- sumfiles/ld.log.xz | Bin 131580 -> 131532 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 29 files changed, 390 insertions(+), 390 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits November 2022