Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/release-aarch64 updated (936f277057 -> 9f5e33e9c9)

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/release-aarch64 in repository toolchain/ci/base-artifacts. from 936f277057 40: onsuccess: #139: 1: Success after binutils/gcc/linux/gdb [...] new 9f5e33e9c9 41: onsuccess: #140: 1: Success after gcc/linux: 38 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 1768 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 37684 -> 38024 bytes 04-build_abe-gcc/console.log.xz | Bin 205852 -> 207172 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8688 -> 8660 bytes 07-build_abe-glibc/console.log.xz | Bin 239992 -> 240916 bytes 08-build_abe-gdb/console.log.xz | Bin 37272 -> 37212 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3884 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2056 -> 2064 bytes 11-check_regression/console.log.xz | Bin 5648 -> 5236 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 +-- sumfiles/binutils.log.xz | Bin 55396 -> 55312 bytes sumfiles/binutils.sum | 58 ++--- sumfiles/gas.log.xz | Bin 80372 -> 80340 bytes sumfiles/gas.sum | 270 +++++++++++------------ sumfiles/ld.log.xz | Bin 118820 -> 118788 bytes sumfiles/ld.sum | 332 ++++++++++++++--------------- 26 files changed, 355 insertions(+), 355 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (7aadfd69a0 -> cd5cf62c32)

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_build/master-arm in repository toolchain/ci/base-artifacts. discards 7aadfd69a0 285: onsuccess: #2014: 7: Success after binutils/gcc/gdb: 74 [...] discards a6c43cda26 284: onsuccess: #2013: 7: Success after binutils/gcc/gdb: 33 [...] discards 8a4f5b6dbe 283: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards e40413dd62 282: onsuccess: #2011: 7: Success after binutils/gcc/glibc/g [...] discards 321db9684c 281: onsuccess: #2010: 7: Success after binutils/gcc/gdb: 30 [...] discards 5e55cb9b38 280: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards d9538b985d 279: onsuccess: #2008: 7: Success after binutils/gcc/glibc/g [...] discards ccfa336257 278: onsuccess: #2007: 7: Success after binutils/gcc/linux/g [...] discards 078a6775b1 277: onsuccess: #2006: 7: Success after binutils/gcc/gdb/qem [...] discards a6b4e60fdf 276: onsuccess: #2005: 7: Success after binutils/gcc/gdb: 69 [...] discards 7e95fdb893 275: onsuccess: #2004: 7: Success after binutils/gcc/gdb: 6 commits discards 56090135e3 274: onsuccess: #2003: 7: Success after binutils/gcc/linux/g [...] discards c0aee67e67 273: onsuccess: #2002: 7: Success after binutils/gcc/gdb/qem [...] discards 82956d5eef 272: onsuccess: #2001: 7: Success after basepoints/gcc-13-48 [...] discards 85598d139a 271: onsuccess: #2000: 7: Success after binutils/gcc/gdb: 10 [...] discards 4404efca1e 270: onsuccess: #1999: 7: Success after binutils/gcc/linux/g [...] discards 05c313c51d 269: onsuccess: #1998: 7: Success after binutils/gcc/glibc/g [...] discards 0b20b460a9 268: onsuccess: #1997: 7: Success after glibc: 2 commits discards e36703468f 267: onsuccess: #1996: 7: Success after binutils/gcc/glibc/g [...] discards 5be084abef 266: onsuccess: #1995: 7: Success after v7.2.0-211-g562d4af3 [...] discards 0faa686cac 265: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 5 commits discards 64f721ac59 264: onsuccess: #1993: 7: Success after binutils/gcc/gdb: 5 commits discards 36c01b38e4 263: onsuccess: #1992: 7: Success after binutils/gcc/gdb/qem [...] discards 8f52631442 262: onsuccess: #1991: 7: Success after gcc/linux: 109 commits discards f5f17deebe 261: onsuccess: #1990: 7: Success after binutils/gcc/gdb: 19 [...] discards 2cc960eb30 260: onsuccess: #1989: 7: Success after binutils/gcc/gdb/qem [...] discards 58b38ed033 259: onsuccess: #1988: 7: Success after binutils/gcc/linux/g [...] discards 0d812c48f0 258: onsuccess: #1987: 7: Success after binutils/gcc/gdb/qem [...] discards 692c524b9a 257: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] discards 0cf557400b 256: onsuccess: #1985: 7: Success after binutils/gcc/linux/g [...] discards ff7c668c1d 255: onsuccess: #1984: 7: Success after binutils/gcc/linux/g [...] discards 7b7fb4ea34 254: onsuccess: #1983: 7: Success after binutils/gcc/gdb/qem [...] discards 181b0977c2 253: onsuccess: #1982: 7: Success after basepoints/gcc-13-47 [...] discards 10a9b84422 252: onsuccess: #1981: 7: Success after binutils/gcc/linux/g [...] discards d27bc64aa2 251: onsuccess: #1980: 7: Success after binutils/gcc/linux/g [...] discards 0fc2410922 250: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 21 [...] discards a7ff67b047 249: onsuccess: #1978: 7: Success after binutils/gcc/linux/g [...] discards 9d27e9770c 248: onsuccess: #1977: 7: Success after binutils/gcc/linux/g [...] discards bad1358b38 247: onsuccess: #1976: 7: Success after binutils/gcc/linux/g [...] discards a5886c9169 246: onsuccess: #1975: 7: Success after binutils/gcc/gdb: 53 [...] discards 4474026b85 245: onsuccess: #1974: 7: Success after binutils/linux/gdb: [...] discards b0532415b1 244: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] discards bfeea94f11 243: onsuccess: #1972: 7: Success after binutils/gcc/linux/g [...] discards efe3297ed2 242: onsuccess: #1971: 7: Success after binutils/gcc/glibc/g [...] discards f1dcd2c14d 241: onsuccess: #1970: 7: Success after binutils/gcc/linux/g [...] discards c13ef43491 240: onsuccess: #1969: 7: Success after gcc/linux: 9 commits discards eea989f9c4 239: onsuccess: #1968: 7: Success after binutils/gcc/gdb: 3 commits discards 5f3e73ec2a 238: onsuccess: #1967: 7: Success after binutils/gcc/linux/g [...] discards 7746b92e0f 237: onsuccess: #1966: 7: Success after gcc/linux: 3 commits discards 30f62de7ea 236: onsuccess: #1965: 7: Success after binutils/gcc/gdb: 15 [...] discards 491ef3623e 235: onsuccess: #1964: 7: Success after binutils/linux/glibc [...] discards 6d734fde70 234: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 7 commits discards 2ee5241b09 233: onsuccess: #1962: 7: Success after gcc: 6 commits discards a87870b6b0 232: onsuccess: #1961: 7: Success after binutils/gcc/linux/g [...] discards d292a2349c 231: onsuccess: #1960: 7: Success after binutils/gcc/glibc/g [...] discards bc258518c6 230: onsuccess: #1958: 7: Success after binutils/gcc/linux/g [...] discards 1f40c5f0df 229: onsuccess: #1957: 7: Success after binutils/gcc/glibc/g [...] discards 8fb2b35630 228: onsuccess: #1956: 7: Success after gcc: 5 commits discards f98c8e8a3c 227: onsuccess: #1955: 7: Success after binutils/gdb: 10 commits discards b0bd71559b 226: onsuccess: #1954: 7: Success after binutils/gcc/glibc/g [...] discards a937197406 225: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] discards a8c4d2f470 224: onsuccess: #1952: 7: Success after binutils/gcc/gdb/qem [...] discards 3104c258b1 223: onsuccess: #1951: 3: Success after binutils/gcc/linux: [...] discards 342ba21e19 222: onsuccess: #1950: 3: Success after basepoints/gcc-13-44 [...] discards 99a24c5aaa 221: force: #1949: 3: Failure after basepoints/gcc-13-4492-g [...] discards 4b259e416e 220: force: #1948: 5: Success after gcc: 4 commits discards f64b307dc5 219: onsuccess: #1945: 5: Success after binutils: 8 commits discards 483cfe19a9 218: onsuccess: #1943: 5: Success after gdb: 3 commits discards b8d365bc1e 217: force: #1942: 5: Failure after gdb-12-branchpoint-2943- [...] discards f7f9c6cdc3 216: onsuccess: #1940: 7: Success after linux: 12 commits discards 527afef614 215: onsuccess: #1938: 7: Success after gcc: 4 commits discards ac44efc6d9 214: onsuccess: #1937: 7: Success after binutils: 4 commits discards 4f4ee47946 213: onsuccess: #1935: 7: Success after gcc: 2 commits discards 623acb2c1f 212: onsuccess: #1934: 7: Success after gcc: 3 commits discards f4bb94a427 211: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] discards 7c810b86ac 210: onsuccess: #1932: 7: Success after binutils/gcc/gdb: 7 commits discards b31ba9002a 209: onsuccess: #1931: 7: Success after binutils/gcc/linux/g [...] discards 9a5058567d 208: onsuccess: #1930: 7: Success after gcc/glibc: 5 commits discards 9559d859ef 207: onsuccess: #1929: 7: Success after binutils/gcc/gdb: 22 [...] discards 54d4be4839 206: onsuccess: #1927: 7: Success after binutils/gcc/linux/g [...] discards 82890bb7c6 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: 40 [...] discards b8f018a893 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: 13 [...] discards e6efab3690 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: 16 [...] discards 1b38eb269a 202: onsuccess: #1923: 7: Success after binutils/gcc/linux/g [...] discards e1ce9fa626 201: onsuccess: #1905: 7: Success after binutils/gcc/linux/g [...] discards 11e42b6842 200: onsuccess: #1899: 7: Success after binutils/gcc/linux/g [...] discards 11ab193638 199: onsuccess: #1881: 7: Success after binutils/gcc/linux/g [...] discards a53e018bc5 198: onsuccess: #1878: 7: Success after binutils/gcc/linux/g [...] discards 64b0892bd5 197: onsuccess: #1856: 4: Success after binutils/gcc/linux/g [...] discards 73335a45f8 196: onsuccess: #1855: 4: Success after gcc: 30 commits discards 07369ef54b 195: force: #1854: 4: Failure after basepoints/gcc-13-3918-g [...] discards 41797a459c 194: force: #1853: 7: Success after gcc: 26 commits discards 005701c9e5 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint-2 [...] discards 209d7a01be 192: onsuccess: #1848: 7: Success after linux: 213 commits discards 239a2fd94a 191: onsuccess: #1846: 7: Success after binutils: 4 commits discards ecb4ba33ef 190: onsuccess: #1834: 7: Success after binutils: 25 commits discards be14402317 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/g [...] discards 8f5b634560 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/g [...] discards 1417c9c86b 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/g [...] discards c0d11453b0 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/g [...] discards 08f1e9868a 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/g [...] new bd0c2c0290 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/g [...] new a08cb52e2b 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/g [...] new 7b1444b636 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/g [...] new c58c08b916 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/g [...] new 594bc19da1 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/g [...] new a9c66a7b6f 190: onsuccess: #1834: 7: Success after binutils: 25 commits new 79f7484019 191: onsuccess: #1846: 7: Success after binutils: 4 commits new 959f658f20 192: onsuccess: #1848: 7: Success after linux: 213 commits new 3487958ef0 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint-2 [...] new 0b25e91be2 194: force: #1853: 7: Success after gcc: 26 commits new 265a1793f4 195: force: #1854: 4: Failure after basepoints/gcc-13-3918-g [...] new e4cce29667 196: onsuccess: #1855: 4: Success after gcc: 30 commits new 3f6b927801 197: onsuccess: #1856: 4: Success after binutils/gcc/linux/g [...] new 9fc61466b3 198: onsuccess: #1878: 7: Success after binutils/gcc/linux/g [...] new 0617b4bfcd 199: onsuccess: #1881: 7: Success after binutils/gcc/linux/g [...] new 89aa97ec18 200: onsuccess: #1899: 7: Success after binutils/gcc/linux/g [...] new 0bca1eb7b9 201: onsuccess: #1905: 7: Success after binutils/gcc/linux/g [...] new c735e76812 202: onsuccess: #1923: 7: Success after binutils/gcc/linux/g [...] new 10ec317dff 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: 16 [...] new 754201ac77 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: 13 [...] new e08c9f5b6d 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: 40 [...] new 243188055b 206: onsuccess: #1927: 7: Success after binutils/gcc/linux/g [...] new 9a530263ed 207: onsuccess: #1929: 7: Success after binutils/gcc/gdb: 22 [...] new 4ede956d98 208: onsuccess: #1930: 7: Success after gcc/glibc: 5 commits new 87e3a9e98e 209: onsuccess: #1931: 7: Success after binutils/gcc/linux/g [...] new be607680a2 210: onsuccess: #1932: 7: Success after binutils/gcc/gdb: 7 commits new aac677bad4 211: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] new 0320ef4d6d 212: onsuccess: #1934: 7: Success after gcc: 3 commits new a5e89bceb1 213: onsuccess: #1935: 7: Success after gcc: 2 commits new 9e5315eae0 214: onsuccess: #1937: 7: Success after binutils: 4 commits new cb10105cb0 215: onsuccess: #1938: 7: Success after gcc: 4 commits new 987bc3e12f 216: onsuccess: #1940: 7: Success after linux: 12 commits new 7354d541bf 217: force: #1942: 5: Failure after gdb-12-branchpoint-2943- [...] new 72155e9a12 218: onsuccess: #1943: 5: Success after gdb: 3 commits new 38a2d05c68 219: onsuccess: #1945: 5: Success after binutils: 8 commits new de84305760 220: force: #1948: 5: Success after gcc: 4 commits new 190f44c177 221: force: #1949: 3: Failure after basepoints/gcc-13-4492-g [...] new 2dc751a3c4 222: onsuccess: #1950: 3: Success after basepoints/gcc-13-44 [...] new 5c9877145b 223: onsuccess: #1951: 3: Success after binutils/gcc/linux: [...] new f83a6a4350 224: onsuccess: #1952: 7: Success after binutils/gcc/gdb/qem [...] new 566e05423b 225: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] new 4d86b5f9ea 226: onsuccess: #1954: 7: Success after binutils/gcc/glibc/g [...] new 2705909d34 227: onsuccess: #1955: 7: Success after binutils/gdb: 10 commits new a45aa8d634 228: onsuccess: #1956: 7: Success after gcc: 5 commits new 6c1de33108 229: onsuccess: #1957: 7: Success after binutils/gcc/glibc/g [...] new 782481f875 230: onsuccess: #1958: 7: Success after binutils/gcc/linux/g [...] new b2ebe161ee 231: onsuccess: #1960: 7: Success after binutils/gcc/glibc/g [...] new de220438b3 232: onsuccess: #1961: 7: Success after binutils/gcc/linux/g [...] new 606e7ddd33 233: onsuccess: #1962: 7: Success after gcc: 6 commits new cd3cb57523 234: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 7 commits new b5689a7714 235: onsuccess: #1964: 7: Success after binutils/linux/glibc [...] new e8ad5da517 236: onsuccess: #1965: 7: Success after binutils/gcc/gdb: 15 [...] new f9b25ef8a7 237: onsuccess: #1966: 7: Success after gcc/linux: 3 commits new 79ff830492 238: onsuccess: #1967: 7: Success after binutils/gcc/linux/g [...] new 7c1f59aac3 239: onsuccess: #1968: 7: Success after binutils/gcc/gdb: 3 commits new 265770c610 240: onsuccess: #1969: 7: Success after gcc/linux: 9 commits new 0e28f77dee 241: onsuccess: #1970: 7: Success after binutils/gcc/linux/g [...] new bc900c4fa8 242: onsuccess: #1971: 7: Success after binutils/gcc/glibc/g [...] new f9a3bcdd82 243: onsuccess: #1972: 7: Success after binutils/gcc/linux/g [...] new 7756390367 244: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] new 101a2d0845 245: onsuccess: #1974: 7: Success after binutils/linux/gdb: [...] new 5b71240b19 246: onsuccess: #1975: 7: Success after binutils/gcc/gdb: 53 [...] new 5f22b3d2ca 247: onsuccess: #1976: 7: Success after binutils/gcc/linux/g [...] new 5c3bb0ac83 248: onsuccess: #1977: 7: Success after binutils/gcc/linux/g [...] new 61549cf418 249: onsuccess: #1978: 7: Success after binutils/gcc/linux/g [...] new e06cccc6a8 250: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 21 [...] new de72b5f796 251: onsuccess: #1980: 7: Success after binutils/gcc/linux/g [...] new f96d9e892e 252: onsuccess: #1981: 7: Success after binutils/gcc/linux/g [...] new 63e60eae76 253: onsuccess: #1982: 7: Success after basepoints/gcc-13-47 [...] new eedd8ef5fe 254: onsuccess: #1983: 7: Success after binutils/gcc/gdb/qem [...] new 18c93fe055 255: onsuccess: #1984: 7: Success after binutils/gcc/linux/g [...] new 602d6c2b34 256: onsuccess: #1985: 7: Success after binutils/gcc/linux/g [...] new 643fca7078 257: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] new b0400f809e 258: onsuccess: #1987: 7: Success after binutils/gcc/gdb/qem [...] new 3486de40d4 259: onsuccess: #1988: 7: Success after binutils/gcc/linux/g [...] new 8fcb8d2826 260: onsuccess: #1989: 7: Success after binutils/gcc/gdb/qem [...] new b7e3cec213 261: onsuccess: #1990: 7: Success after binutils/gcc/gdb: 19 [...] new 7d27736c5e 262: onsuccess: #1991: 7: Success after gcc/linux: 109 commits new 6e2fca1bc1 263: onsuccess: #1992: 7: Success after binutils/gcc/gdb/qem [...] new 617f929b88 264: onsuccess: #1993: 7: Success after binutils/gcc/gdb: 5 commits new e1422fed45 265: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 5 commits new b35a14275e 266: onsuccess: #1995: 7: Success after v7.2.0-211-g562d4af3 [...] new a8b369a35f 267: onsuccess: #1996: 7: Success after binutils/gcc/glibc/g [...] new bd269e4d18 268: onsuccess: #1997: 7: Success after glibc: 2 commits new bf274f59f7 269: onsuccess: #1998: 7: Success after binutils/gcc/glibc/g [...] new 32b1972c4f 270: onsuccess: #1999: 7: Success after binutils/gcc/linux/g [...] new 0e50bd2021 271: onsuccess: #2000: 7: Success after binutils/gcc/gdb: 10 [...] new ce0b340b6f 272: onsuccess: #2001: 7: Success after basepoints/gcc-13-48 [...] new 5e2936e7e5 273: onsuccess: #2002: 7: Success after binutils/gcc/gdb/qem [...] new 0f6ec6825e 274: onsuccess: #2003: 7: Success after binutils/gcc/linux/g [...] new 5a571aee27 275: onsuccess: #2004: 7: Success after binutils/gcc/gdb: 6 commits new 3748eef82e 276: onsuccess: #2005: 7: Success after binutils/gcc/gdb: 69 [...] new 2d6daa0eb9 277: onsuccess: #2006: 7: Success after binutils/gcc/gdb/qem [...] new 2646b5e925 278: onsuccess: #2007: 7: Success after binutils/gcc/linux/g [...] new 621a9fd604 279: onsuccess: #2008: 7: Success after binutils/gcc/glibc/g [...] new 8c1cd667b0 280: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new 25f3ea8608 281: onsuccess: #2010: 7: Success after binutils/gcc/gdb: 30 [...] new 1f0e341947 282: onsuccess: #2011: 7: Success after binutils/gcc/glibc/g [...] new 6702ded6f1 283: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new a8cb445dfb 284: onsuccess: #2013: 7: Success after binutils/gcc/gdb: 33 [...] new 82b5e36e41 285: onsuccess: #2014: 7: Success after binutils/gcc/gdb: 74 [...] new cd5cf62c32 286: onsuccess: #2015: 7: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (7aadfd69a0) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] 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 1756 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2764 bytes 04-build_abe-binutils/console.log.xz | Bin 32192 -> 31772 bytes 05-build_abe-stage1/console.log.xz | Bin 92112 -> 92140 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 8804 -> 8600 bytes 08-build_abe-glibc/console.log.xz | Bin 237324 -> 236204 bytes 09-build_abe-stage2/console.log.xz | Bin 229028 -> 228184 bytes 10-build_abe-gdb/console.log.xz | Bin 39780 -> 39444 bytes 11-build_abe-qemu/console.log.xz | Bin 31384 -> 31988 bytes 12-check_regression/console.log.xz | Bin 3928 -> 4164 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ 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 | 36 +++++++++---------- 21 files changed, 59 insertions(+), 59 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[binutils-gdb] branch master updated (32e62cbcc11 -> 095f84c7e3c)

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 32e62cbcc11 Use bool for dwarf2_has_info new 095f84c7e3c Automatic date update in version.in The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: bfd/version.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[binutils-gdb] branch gdb-13-branch updated (08081297f66 -> 661169d7b58)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch gdb-13-branch in repository binutils-gdb. from 08081297f66 Automatic date update in version.in new 661169d7b58 Automatic date update in version.in The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: bfd/version.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[binutils-gdb] branch binutils-2_39-branch updated (9d2043cca4c -> 74340608801)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch binutils-2_39-branch in repository binutils-gdb. from 9d2043cca4c Automatic date update in version.in new 74340608801 Automatic date update in version.in The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: bfd/version.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-next-defconfig updated (03e40fb456 -> ac53b1cc96)

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-arm-next-defconfig in repository toolchain/ci/base-artifacts. from 03e40fb456 30: onsuccess: #338: boot: Success after binutils/linux/qemu [...] new ac53b1cc96 31: onsuccess: #339: boot: Success after binutils/linux/qemu [...] 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 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 30212 -> 30092 bytes 04-build_kernel_llvm/console.log.xz | Bin 63452 -> 63368 bytes 05-build_abe-qemu/console.log.xz | Bin 30540 -> 31384 bytes 06-build_linux/console.log.xz | Bin 3132 -> 3132 bytes 07-boot_linux/console.log.xz | Bin 5708 -> 5664 bytes 08-check_regression/console.log.xz | Bin 3756 -> 3624 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_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 | 28 ++++++++++++++-------------- 16 files changed, 21 insertions(+), 21 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[gcc] branch master updated (6a95f0e0a06 -> 9149a5b7e0a)

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 6a95f0e0a06 Fortran: incorrect array bounds when bound intrinsic used i [...] new 9149a5b7e0a Reimplement GNU threads library on native Windows 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: libgcc/config.host | 16 +- libgcc/config/i386/gthr-win32-cond.c | 89 ++++ libgcc/config/i386/gthr-win32-thread.c | 162 +++++++ libgcc/config/i386/gthr-win32.c | 264 ++-------- libgcc/config/i386/gthr-win32.h | 536 ++++++++++++--------- .../i386/{libgcc-cygming.ver => libgcc-mingw.ver} | 9 +- libgcc/config/i386/t-gthr-win32 | 8 +- libgcc/config/i386/t-slibgcc-mingw | 1 + libstdc++-v3/acinclude.m4 | 42 +- libstdc++-v3/config.h.in | 6 +- libstdc++-v3/config/os/mingw32-w64/os_defines.h | 3 + libstdc++-v3/config/os/mingw32/os_defines.h | 3 + libstdc++-v3/configure | 60 ++- libstdc++-v3/src/c++11/thread.cc | 14 +- .../headers/system_error/errc_std_c++0x.cc | 19 + libstdc++-v3/testsuite/lib/libstdc++.exp | 14 +- 16 files changed, 725 insertions(+), 521 deletions(-) create mode 100644 libgcc/config/i386/gthr-win32-cond.c create mode 100644 libgcc/config/i386/gthr-win32-thread.c copy libgcc/config/i386/{libgcc-cygming.ver => libgcc-mingw.ver} (84%) create mode 100644 libgcc/config/i386/t-slibgcc-mingw -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_apm/gnu-master-arm-spec2k6-Os_LTO updated (4688dcb643 -> 95028da5d4)

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_apm/gnu-master-arm-spec2k6-Os_LTO in repository toolchain/ci/base-artifacts. from 4688dcb643 28: onsuccess: #189: 1: [TCWG CI] No change after linux: 947 [...] new 95028da5d4 29: onsuccess: #195: 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 1812 -> 2008 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31976 -> 32076 bytes 04-build_abe-stage1/console.log.xz | Bin 92524 -> 92304 bytes 06-build_abe-linux/console.log.xz | Bin 8684 -> 8692 bytes 07-build_abe-glibc/console.log.xz | Bin 238416 -> 236588 bytes 08-build_abe-stage2/console.log.xz | Bin 216404 -> 213520 bytes 09-benchmark/benchmark-build.log | 108 +- 09-benchmark/benchmark.log | 106 +- 09-benchmark/console.log.xz | Bin 3820 -> 3916 bytes 10-check_regression/console.log.xz | Bin 6072 -> 7668 bytes .../csv-results-vs-first-0/results.csv | 659164 ++++++++-------- .../csv-results-vs-first-0/size.csv | 671588 ++++++++-------- .../csv-results-vs-first-0/vect.csv | 29 - .../csv-results-vs-first-1/perf.csv | 257 +- .../csv-results-vs-first-1/results.csv | 722617 +++++++++--------- .../csv-results-vs-first-1/size.csv | 716816 ++++++++--------- .../csv-results-vs-first-1/vect.csv | 44 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 249 +- .../csv-results-vs-prev-0/results.csv | 689264 ++++++++--------- 10-check_regression/csv-results-vs-prev-0/size.csv | 707190 ++++++++--------- 10-check_regression/csv-results-vs-prev-0/vect.csv | 44 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 257 +- .../csv-results-vs-prev-1/results.csv | 722617 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/size.csv | 716816 ++++++++--------- 10-check_regression/csv-results-vs-prev-1/vect.csv | 44 +- 10-check_regression/mail-body.txt | 5 - 10-check_regression/results-vs-first-brief.csv | 68 +- 10-check_regression/results-vs-first-full.csv | 271 +- 10-check_regression/results-vs-first-internal.csv | 81 +- 10-check_regression/results-vs-first.csv | 81 +- 10-check_regression/results-vs-first.log | 1252 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-compare.csv | 1 + 10-check_regression/results-vs-prev-full.csv | 279 +- 10-check_regression/results-vs-prev-internal.csv | 81 +- 10-check_regression/results-vs-prev.csv | 81 +- 10-check_regression/results-vs-prev.log | 1384 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 16 +- .../400.perlbench/results-metrics.json | 2 +- .../squad-vs-first/401.bzip2/results-metadata.json | 16 +- .../squad-vs-first/401.bzip2/results-metrics.json | 2 +- .../squad-vs-first/403.gcc/results-metadata.json | 16 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../410.bwaves/results-metadata.json | 16 +- .../squad-vs-first/410.bwaves/results-metrics.json | 2 +- .../416.gamess/results-metadata.json | 16 +- .../squad-vs-first/429.mcf/results-metadata.json | 16 +- .../squad-vs-first/429.mcf/results-metrics.json | 2 +- .../squad-vs-first/433.milc/results-metadata.json | 16 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../434.zeusmp/results-metadata.json | 16 +- .../435.gromacs/results-metadata.json | 16 +- .../436.cactusADM/results-metadata.json | 16 +- .../436.cactusADM/results-metrics.json | 2 +- .../437.leslie3d/results-metadata.json | 16 +- .../squad-vs-first/444.namd/results-metadata.json | 16 +- .../squad-vs-first/445.gobmk/results-metadata.json | 16 +- .../squad-vs-first/445.gobmk/results-metrics.json | 2 +- .../447.dealII/results-metadata.json | 16 +- .../450.soplex/results-metadata.json | 16 +- .../453.povray/results-metadata.json | 16 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../454.calculix/results-metadata.json | 16 +- .../454.calculix/results-metrics.json | 2 +- .../squad-vs-first/456.hmmer/results-metadata.json | 16 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 16 +- .../squad-vs-first/458.sjeng/results-metrics.json | 2 +- .../459.GemsFDTD/results-metadata.json | 16 +- .../459.GemsFDTD/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 16 +- .../464.h264ref/results-metadata.json | 16 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/465.tonto/results-metadata.json | 16 +- .../squad-vs-first/465.tonto/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 16 +- .../squad-vs-first/470.lbm/results-metrics.json | 2 +- .../471.omnetpp/results-metadata.json | 16 +- .../squad-vs-first/473.astar/results-metadata.json | 16 +- .../squad-vs-first/481.wrf/results-metadata.json | 16 +- .../squad-vs-first/481.wrf/results-metrics.json | 2 +- .../482.sphinx3/results-metadata.json | 16 +- .../482.sphinx3/results-metrics.json | 2 +- .../483.xalancbmk/results-metadata.json | 16 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 16 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 32 +- mail/mail-body.txt | 37 +- mail/mail-subject.txt | 2 +- manifest.sh | 35 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 2549756 -> 0 bytes save-temps/401.bzip2.tar.xz | Bin 234492 -> 0 bytes save-temps/403.gcc.tar.xz | Bin 6843768 -> 0 bytes save-temps/410.bwaves.tar.xz | Bin 47844 -> 0 bytes save-temps/416.gamess.tar.xz | Bin 13817220 -> 0 bytes save-temps/429.mcf.tar.xz | Bin 69628 -> 0 bytes save-temps/433.milc.tar.xz | Bin 333244 -> 0 bytes save-temps/434.zeusmp.tar.xz | Bin 428176 -> 0 bytes save-temps/435.gromacs.tar.xz | Bin 2111148 -> 0 bytes save-temps/436.cactusADM.tar.xz | Bin 1524620 -> 0 bytes save-temps/437.leslie3d.tar.xz | Bin 151400 -> 0 bytes save-temps/444.namd.tar.xz | Bin 486200 -> 0 bytes save-temps/445.gobmk.tar.xz | Bin 2490084 -> 0 bytes save-temps/447.dealII.tar.xz | Bin 10714172 -> 0 bytes save-temps/450.soplex.tar.xz | Bin 1215988 -> 0 bytes save-temps/453.povray.tar.xz | Bin 2277212 -> 0 bytes save-temps/454.calculix.tar.xz | Bin 3174532 -> 0 bytes save-temps/456.hmmer.tar.xz | Bin 808860 -> 0 bytes save-temps/458.sjeng.tar.xz | Bin 301852 -> 0 bytes save-temps/459.GemsFDTD.tar.xz | Bin 521928 -> 0 bytes save-temps/462.libquantum.tar.xz | Bin 120504 -> 0 bytes save-temps/464.h264ref.tar.xz | Bin 1827476 -> 0 bytes save-temps/465.tonto.tar.xz | Bin 6061996 -> 0 bytes save-temps/470.lbm.tar.xz | Bin 43972 -> 0 bytes save-temps/471.omnetpp.tar.xz | Bin 1408972 -> 0 bytes save-temps/473.astar.tar.xz | Bin 141708 -> 0 bytes save-temps/481.wrf.tar.xz | Bin 6952448 -> 0 bytes save-temps/482.sphinx3.tar.xz | Bin 519772 -> 0 bytes save-temps/483.xalancbmk.tar.xz | Bin 15541408 -> 0 bytes 127 files changed, 2821424 insertions(+), 2790196 deletions(-) delete mode 100644 save-temps/400.perlbench.tar.xz delete mode 100644 save-temps/401.bzip2.tar.xz delete mode 100644 save-temps/403.gcc.tar.xz delete mode 100644 save-temps/410.bwaves.tar.xz delete mode 100644 save-temps/416.gamess.tar.xz delete mode 100644 save-temps/429.mcf.tar.xz delete mode 100644 save-temps/433.milc.tar.xz delete mode 100644 save-temps/434.zeusmp.tar.xz delete mode 100644 save-temps/435.gromacs.tar.xz delete mode 100644 save-temps/436.cactusADM.tar.xz delete mode 100644 save-temps/437.leslie3d.tar.xz delete mode 100644 save-temps/444.namd.tar.xz delete mode 100644 save-temps/445.gobmk.tar.xz delete mode 100644 save-temps/447.dealII.tar.xz delete mode 100644 save-temps/450.soplex.tar.xz delete mode 100644 save-temps/453.povray.tar.xz delete mode 100644 save-temps/454.calculix.tar.xz delete mode 100644 save-temps/456.hmmer.tar.xz delete mode 100644 save-temps/458.sjeng.tar.xz delete mode 100644 save-temps/459.GemsFDTD.tar.xz delete mode 100644 save-temps/462.libquantum.tar.xz delete mode 100644 save-temps/464.h264ref.tar.xz delete mode 100644 save-temps/465.tonto.tar.xz delete mode 100644 save-temps/470.lbm.tar.xz delete mode 100644 save-temps/471.omnetpp.tar.xz delete mode 100644 save-temps/473.astar.tar.xz delete mode 100644 save-temps/481.wrf.tar.xz delete mode 100644 save-temps/482.sphinx3.tar.xz delete mode 100644 save-temps/483.xalancbmk.tar.xz -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-mainline-defconfig updated (dc746659b3 -> 3ac47e7300)

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-arm-mainline-defconfig in repository toolchain/ci/base-artifacts. from dc746659b3 31: onsuccess: #421: boot: Success after binutils/linux/qemu [...] new 3ac47e7300 32: onsuccess: #422: boot: Success after binutils/linux/qemu [...] 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 1940 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 30676 -> 30060 bytes 04-build_kernel_llvm/console.log.xz | Bin 64948 -> 64632 bytes 05-build_abe-qemu/console.log.xz | Bin 31012 -> 31552 bytes 06-build_linux/console.log.xz | Bin 3176 -> 3132 bytes 07-boot_linux/console.log.xz | Bin 5636 -> 5664 bytes 08-check_regression/console.log.xz | Bin 3632 -> 3672 bytes 08-check_regression/mail-body.txt | 4 ++-- 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 6 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- results | 2 +- 19 files changed, 30 insertions(+), 30 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm updated (b123bdeff0 -> e8113a4497)

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_gcc/master-arm in repository toolchain/ci/base-artifacts. discards b123bdeff0 148: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 37a316b780 147: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] discards e09668d47e 146: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 6b080870ab 145: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards f12e2bf345 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 commits discards afdfe609a0 143: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards e33aff8470 142: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 443fcc79fc 141: onsuccess: #601: 1: Success after linux: 794 commits discards 95e22dafaa 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 24d11451e4 139: onsuccess: #599: 1: Success after binutils: 10 commits discards 2a776446d3 138: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards b3e6fa22dd 137: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] discards 1430cf3f2f 136: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards 767b11f667 135: onsuccess: #594: 1: Success after binutils/gcc/linux/gd [...] discards 96f8098373 134: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 0ffc7eac3b 133: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] discards cabf2f7ccc 132: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards b214120622 131: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] discards 1298fab671 130: onsuccess: #589: 1: Success after binutils/gcc/linux/gl [...] discards 6248c5cc90 129: onsuccess: #588: 1: Success after linux: 4 commits discards 3e9ef05d9c 128: onsuccess: #586: 1: Success after binutils: 22 commits discards 4c49c9081c 127: onsuccess: #584: 1: Success after linux: 21 commits discards 3cfc3ad196 126: onsuccess: #582: 1: Success after gcc: 9 commits discards 23cbbe9e91 125: onsuccess: #581: 1: Success after binutils: 4 commits discards 32ec4268a5 124: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] discards 48d4a8a744 123: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] discards 2c5352bd2f 122: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] discards 47bc983d2d 121: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] discards 673b9b2e65 120: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] discards 5aba127447 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/gd [...] discards f806eb82ad 118: onsuccess: #573: 1: Success after binutils/gcc/linux/gd [...] discards e6776a7c9e 117: onsuccess: #572: 1: Success after binutils/gcc/linux/gd [...] discards 71ff56df7c 116: onsuccess: #571: 1: Success after binutils/gcc/linux/gd [...] discards 366aa2acc9 115: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] discards 1ad16803a3 114: onsuccess: #569: 1: Success after binutils/gcc/linux/gd [...] discards 12f7344a5e 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits discards c0184f1840 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards b39838a049 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] discards d97752ad38 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] discards 7df79130eb 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards 93ba5d2b3c 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards d5a053737a 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards 1a86ef20ac 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards 9a1ab1d714 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards ee71dc8b11 104: onsuccess: #558: 1: Success after binutils: 3 commits discards da38bcae73 103: onsuccess: #555: 1: Success after binutils: 4 commits discards e784d2ce01 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards b445f3a696 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards be52427573 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 9806ddfada 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards d6aa2dd58b 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 5b1a1df55c 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] discards 0b37b4be26 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards ca87d99ff5 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 948d257512 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards b689449073 93: onsuccess: #544: 1: Success after linux: 34 commits discards 88a8f44f53 92: onsuccess: #543: 1: Success after glibc: 4 commits discards bdb9071a3b 91: onsuccess: #539: 1: Success after linux: 27 commits discards 5d4a387dcd 90: onsuccess: #538: 1: Success after glibc: 10 commits discards fb6c727af9 89: onsuccess: #536: 1: Success after binutils: 27 commits discards 901334d340 88: onsuccess: #534: 1: Success after linux: 12 commits discards b221e36671 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] discards 30b92a1b3d 86: onsuccess: #532: 1: Success after gcc: 16 commits discards 65a6a5251a 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] discards fe86a895c3 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] discards 54bdbc602e 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] discards 0938d9c256 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] discards 2673715295 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] discards 7bcb9c4a21 80: onsuccess: #524: 1: Success after linux: 9 commits discards e3ffa73607 79: onsuccess: #523: 1: Success after gcc: 25 commits discards 6a182b627d 78: onsuccess: #522: 1: Success after binutils: 10 commits discards a90fd08178 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] discards 37d0c80ba5 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] discards 7f5b7dccd3 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] discards 510e016e35 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] discards dcce87b209 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] discards 47799db4cf 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards cc0922bfbc 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] discards 708dcef7ab 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 4851f48cea 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] discards bd2e45032f 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] discards feba95bb1c 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] discards b560d96852 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] discards b5e7f6b6c1 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] discards 7cdde29ab1 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] discards e81f8344d7 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] discards f5009ff13f 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] discards 1efd11cc8a 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] discards f10f995b4f 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] discards 0cbf00f089 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] discards b137c2c0da 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards f230eafc05 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards ea131a518e 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards 3a47a435df 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards 7acb82ee7e 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 7bd6993f6c 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 0bba90d05d 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards bac6852466 51: onsuccess: #493: 1: Success after binutils: 13 commits discards ba37a7dea2 50: onsuccess: #490: 1: Success after binutils: 6 commits discards 995394dc90 49: onsuccess: #487: 1: Success after binutils: 11 commits discards 60d32c90bd 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 5e4e2e9377 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new ea2df8a0be 49: onsuccess: #487: 1: Success after binutils: 11 commits new c7906b863f 50: onsuccess: #490: 1: Success after binutils: 6 commits new 45b45589c7 51: onsuccess: #493: 1: Success after binutils: 13 commits new 1f5d5bc8c4 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new b241347b8c 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new dfcaac62ce 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 6c4e674066 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new c813054929 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new 8b1f3ec671 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 34690f4f81 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 3af928d0db 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] new e69643925c 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] new 0ab714f8e0 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] new 40d6bf7019 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] new d5fdde8ee2 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] new e6f58e9ca6 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] new 9cc5a43d07 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] new a07484a660 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] new f0eadb7f69 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] new cd764450e5 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] new 040bba5b17 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] new 709ead1797 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new 9721fc3638 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] new 5f2a3f08b4 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new 1c50541712 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] new ec3c2361e0 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] new 7be4f4f5ac 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] new 0ec5259c1b 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] new 17e4787f6b 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] new 9211cc83f5 78: onsuccess: #522: 1: Success after binutils: 10 commits new fb02c293ee 79: onsuccess: #523: 1: Success after gcc: 25 commits new 38110044f5 80: onsuccess: #524: 1: Success after linux: 9 commits new e4916e0db2 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] new 351ec8df02 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] new 690baa16cc 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] new 7e2b1c54f7 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] new f44a37dc76 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] new 8d71f1caa7 86: onsuccess: #532: 1: Success after gcc: 16 commits new 7bc77eca80 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] new 038f69173c 88: onsuccess: #534: 1: Success after linux: 12 commits new 80619cd2c0 89: onsuccess: #536: 1: Success after binutils: 27 commits new c6fff334bc 90: onsuccess: #538: 1: Success after glibc: 10 commits new ca10af5f28 91: onsuccess: #539: 1: Success after linux: 27 commits new 95bd54b98e 92: onsuccess: #543: 1: Success after glibc: 4 commits new 47a3202275 93: onsuccess: #544: 1: Success after linux: 34 commits new d767e243d1 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new b91247c187 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 911991768e 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new 0cc667e639 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] new 36bc8a15f7 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 0eb31c3ecf 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new 6a68cb8627 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 993c4abee8 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 7cfc689763 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new ce09695004 103: onsuccess: #555: 1: Success after binutils: 4 commits new 7f11e5ff7b 104: onsuccess: #558: 1: Success after binutils: 3 commits new e445c05896 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 1fcae7af3b 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new 1016513ed1 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new df7d77279b 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new 168f587b49 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new 323f32e1e8 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] new 8e2f778470 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] new 85cce96ebe 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new 98bcf2266a 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits new 0510d74ea4 114: onsuccess: #569: 1: Success after binutils/gcc/linux/gd [...] new 825fa89a90 115: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new 10e55a930b 116: onsuccess: #571: 1: Success after binutils/gcc/linux/gd [...] new db893a7ccb 117: onsuccess: #572: 1: Success after binutils/gcc/linux/gd [...] new 98a14b7a76 118: onsuccess: #573: 1: Success after binutils/gcc/linux/gd [...] new 407a55414e 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/gd [...] new eeb8c8a861 120: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] new 9fd425af60 121: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] new a84433ab23 122: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] new 4152f261b3 123: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] new 69730494f5 124: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] new f122034f61 125: onsuccess: #581: 1: Success after binutils: 4 commits new 3831fde8d6 126: onsuccess: #582: 1: Success after gcc: 9 commits new 6c8a82c592 127: onsuccess: #584: 1: Success after linux: 21 commits new 600cb628f9 128: onsuccess: #586: 1: Success after binutils: 22 commits new a9cd56e164 129: onsuccess: #588: 1: Success after linux: 4 commits new 8f3d465963 130: onsuccess: #589: 1: Success after binutils/gcc/linux/gl [...] new 8f85e0e6bb 131: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] new e45852d6c0 132: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 2489bcdc04 133: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] new 3d8cc134a7 134: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 372235cb59 135: onsuccess: #594: 1: Success after binutils/gcc/linux/gd [...] new 723bd8fd9e 136: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new 8049c4e518 137: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] new 6e2e1ae422 138: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 12712261db 139: onsuccess: #599: 1: Success after binutils: 10 commits new a3da827f59 140: onsuccess: #600: 1: Success after gcc: 23 commits new c43bc1086c 141: onsuccess: #601: 1: Success after linux: 794 commits new 48daffc821 142: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new ce6ba7e259 143: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 7095d558cf 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 commits new c8d4b6bd76 145: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 82348c2c86 146: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new efb10c0b7f 147: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] new 60dbb8350b 148: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new e8113a4497 149: onsuccess: #609: 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 (b123bdeff0) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1740 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 52760 -> 52572 bytes 04-build_abe-gcc/console.log.xz | Bin 234388 -> 239292 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8768 -> 8752 bytes 07-build_abe-glibc/console.log.xz | Bin 236860 -> 236744 bytes 08-build_abe-gdb/console.log.xz | Bin 51140 -> 51712 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3808 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2556 -> 2612 bytes 11-check_regression/console.log.xz | Bin 6788 -> 7264 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 7 + 11-check_regression/mail-body.txt | 27 + 11-check_regression/results.compare | 26 +- 11-check_regression/results.compare2 | 195 +- 11-check_regression/results.regressions | 27 + 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 | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 27 + sumfiles/g++.log.xz | Bin 2941044 -> 2941300 bytes sumfiles/g++.sum | 138 +- sumfiles/gcc.log.xz | Bin 2601276 -> 2573948 bytes sumfiles/gcc.sum | 4182 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 947196 -> 951168 bytes sumfiles/gfortran.sum | 77 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 230512 -> 229420 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 464564 -> 475484 bytes sumfiles/libstdc++.sum | 60 +- 42 files changed, 2608 insertions(+), 2300 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022