Tcwg-commits January 2023

tcwg-commits@lists.linaro.org

5 participants
4127 discussions

[gcc] branch master updated (c389991432d -> 851e1ba03f9)

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 c389991432d ipa: Sort ipa_param_body_adjustments::m_replacements (PR 108110) new 851e1ba03f9 PR rtl-optimization/106421: ICE in bypass_block from non-lo [...] 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/cprop.cc | 9 ++++++--- gcc/testsuite/gcc.dg/pr106421.c | 13 +++++++++++++ 2 files changed, 19 insertions(+), 3 deletions(-) create mode 100644 gcc/testsuite/gcc.dg/pr106421.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (2c46a89e08 -> e4356f8df6)

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 2c46a89e08 346: onsuccess: #2080: 7: Success after binutils/gdb: 142 commits discards fa3f62090c 345: onsuccess: #2079: 7: Success after binutils/gcc/linux/g [...] discards 7316143646 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 commits discards 4c0c3215b1 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...] discards 38c4b2c79c 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits discards e5d9d21700 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits discards 5e275a04b1 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits discards e6a4158d8d 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits discards 71548b0575 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] discards ee982665b1 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] discards ea20cc7928 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] discards bd4ca92599 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards 3ee47e0bc0 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] discards f403987b47 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] discards 240c8dd19e 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] discards e6e26bcace 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards 62237889e0 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits discards 871cb8d414 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] discards 83603b8004 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards bacf6c8a12 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards 1edc5ddbf1 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] discards 567c81f83e 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits discards 4032cdedd1 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards 6ca1ee23de 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] discards 84960f14db 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] discards cbcff648c9 321: force: #2055: 7: Success after gdb: 2 commits discards 6c9b22f5b9 320: onsuccess: #2050: 7: Success after gcc: 4 commits discards 7f65a8193d 319: onsuccess: #2049: 7: Success after binutils: 4 commits discards 95d11267a9 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] discards d659aa9dea 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits discards 78c422d450 316: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards 7c6d9d2651 315: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards 0019c3d76a 314: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 15 [...] discards 994b04fc87 313: onsuccess: #2042: 7: Success after binutils/gcc/gdb: 4 commits discards e5977b72ee 312: onsuccess: #2041: 7: Success after gcc/linux: 13 commits discards 367fbd7e0a 311: onsuccess: #2040: 7: Success after binutils/gdb: 20 commits discards d9571beb59 310: onsuccess: #2039: 7: Success after binutils/gdb: 6 commits discards 74b5500457 309: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 3 commits discards 3c7154a28c 308: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards 4dbd8257ed 307: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 7 commits discards ae50e9c720 306: onsuccess: #2035: 7: Success after basepoints/gcc-13-49 [...] discards c98adaed24 305: onsuccess: #2034: 7: Success after binutils/gcc/linux/g [...] discards e179a47257 304: onsuccess: #2033: 7: Success after gcc/linux: 60 commits discards 0cb56ede8b 303: onsuccess: #2032: 7: Success after binutils/gdb: 2 commits discards 2cbb886c24 302: onsuccess: #2031: 7: Success after binutils/gcc/gdb: 3 commits discards 9e9036e602 301: onsuccess: #2030: 7: Success after binutils/gcc/gdb: 4 commits discards 6b8c464dcc 300: onsuccess: #2029: 7: Success after binutils/gcc/gdb: 4 commits discards beb07cbb17 299: onsuccess: #2028: 7: Success after binutils/gcc/gdb: 6 commits discards 653be3d383 298: onsuccess: #2027: 7: Success after binutils/gcc/gdb: 18 [...] discards 7fcfe09330 297: onsuccess: #2026: 7: Success after binutils/gcc/gdb: 19 [...] discards 7c67cecd39 296: onsuccess: #2025: 7: Success after binutils/gcc/gdb: 5 commits discards 9c71b72dcb 295: onsuccess: #2024: 7: Success after basepoints/gcc-13-48 [...] discards 78f0a85df2 294: onsuccess: #2023: 7: Success after binutils/gdb: 4 commits discards ab25258868 293: onsuccess: #2022: 7: Success after gcc: 2 commits discards fc0d1dead1 292: onsuccess: #2021: 7: Success after binutils/linux/gdb: [...] discards 8cb9b6de04 291: onsuccess: #2020: 7: Success after binutils/gcc/gdb: 3 commits discards 12b475c614 290: onsuccess: #2019: 7: Success after binutils/gdb: 20 commits discards a3a305124b 289: onsuccess: #2018: 7: Success after binutils/gcc/gdb: 17 [...] discards 10e5bfb28f 288: onsuccess: #2017: 7: Success after binutils/gcc/gdb: 9 commits discards dddcfd651c 287: onsuccess: #2016: 7: Success after binutils/gcc/gdb: 6 commits discards 39e2808b51 286: onsuccess: #2015: 7: Success after binutils/gcc/linux/g [...] discards dc2d5baec3 285: onsuccess: #2014: 7: Success after binutils/gcc/gdb: 74 [...] discards ed7b0923a9 284: onsuccess: #2013: 7: Success after binutils/gcc/gdb: 33 [...] discards 2f254c758d 283: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards 76a9ccd297 282: onsuccess: #2011: 7: Success after binutils/gcc/glibc/g [...] discards ff01467288 281: onsuccess: #2010: 7: Success after binutils/gcc/gdb: 30 [...] discards 38e9039fcf 280: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards fe4db5b10b 279: onsuccess: #2008: 7: Success after binutils/gcc/glibc/g [...] discards 5fbf45d9fb 278: onsuccess: #2007: 7: Success after binutils/gcc/linux/g [...] discards d0f0a0ad4b 277: onsuccess: #2006: 7: Success after binutils/gcc/gdb/qem [...] discards 300f0d0c3c 276: onsuccess: #2005: 7: Success after binutils/gcc/gdb: 69 [...] discards abf630544c 275: onsuccess: #2004: 7: Success after binutils/gcc/gdb: 6 commits discards 85330516aa 274: onsuccess: #2003: 7: Success after binutils/gcc/linux/g [...] discards 7ed93d28a9 273: onsuccess: #2002: 7: Success after binutils/gcc/gdb/qem [...] discards 12599ce3b9 272: onsuccess: #2001: 7: Success after basepoints/gcc-13-48 [...] discards e4683ff636 271: onsuccess: #2000: 7: Success after binutils/gcc/gdb: 10 [...] discards 8e55181596 270: onsuccess: #1999: 7: Success after binutils/gcc/linux/g [...] discards 551f5f6643 269: onsuccess: #1998: 7: Success after binutils/gcc/glibc/g [...] discards fc2c2f9293 268: onsuccess: #1997: 7: Success after glibc: 2 commits discards e1ff24e280 267: onsuccess: #1996: 7: Success after binutils/gcc/glibc/g [...] discards 475c260221 266: onsuccess: #1995: 7: Success after v7.2.0-211-g562d4af3 [...] discards 9e5bdd6a7a 265: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 5 commits discards e3ef2204ac 264: onsuccess: #1993: 7: Success after binutils/gcc/gdb: 5 commits discards f36418676f 263: onsuccess: #1992: 7: Success after binutils/gcc/gdb/qem [...] discards 011d759634 262: onsuccess: #1991: 7: Success after gcc/linux: 109 commits discards 9ffab897e9 261: onsuccess: #1990: 7: Success after binutils/gcc/gdb: 19 [...] discards 432b8c1bfe 260: onsuccess: #1989: 7: Success after binutils/gcc/gdb/qem [...] discards 1bd668928b 259: onsuccess: #1988: 7: Success after binutils/gcc/linux/g [...] discards c71ffbc27f 258: onsuccess: #1987: 7: Success after binutils/gcc/gdb/qem [...] discards af1908fcd4 257: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] discards c871c7ffa7 256: onsuccess: #1985: 7: Success after binutils/gcc/linux/g [...] discards 40a88743c0 255: onsuccess: #1984: 7: Success after binutils/gcc/linux/g [...] discards e6b42473ac 254: onsuccess: #1983: 7: Success after binutils/gcc/gdb/qem [...] discards 5d81165048 253: onsuccess: #1982: 7: Success after basepoints/gcc-13-47 [...] discards 84d6b984cd 252: onsuccess: #1981: 7: Success after binutils/gcc/linux/g [...] discards eefa921fe5 251: onsuccess: #1980: 7: Success after binutils/gcc/linux/g [...] discards 2fc785e6a5 250: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 21 [...] discards e88408e1e7 249: onsuccess: #1978: 7: Success after binutils/gcc/linux/g [...] discards 7678d79d25 248: onsuccess: #1977: 7: Success after binutils/gcc/linux/g [...] discards 8dcc6ace4a 247: onsuccess: #1976: 7: Success after binutils/gcc/linux/g [...] discards c595753446 246: onsuccess: #1975: 7: Success after binutils/gcc/gdb: 53 [...] new bc194409f5 246: onsuccess: #1975: 7: Success after binutils/gcc/gdb: 53 [...] new 80e6fe0673 247: onsuccess: #1976: 7: Success after binutils/gcc/linux/g [...] new 1c52f76ac7 248: onsuccess: #1977: 7: Success after binutils/gcc/linux/g [...] new 91b3850f38 249: onsuccess: #1978: 7: Success after binutils/gcc/linux/g [...] new 40c161a455 250: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 21 [...] new ab8f9485da 251: onsuccess: #1980: 7: Success after binutils/gcc/linux/g [...] new 0791899f76 252: onsuccess: #1981: 7: Success after binutils/gcc/linux/g [...] new 5a440450fe 253: onsuccess: #1982: 7: Success after basepoints/gcc-13-47 [...] new d80d20e94d 254: onsuccess: #1983: 7: Success after binutils/gcc/gdb/qem [...] new 89416ecd08 255: onsuccess: #1984: 7: Success after binutils/gcc/linux/g [...] new 6f4f7d98b3 256: onsuccess: #1985: 7: Success after binutils/gcc/linux/g [...] new 2bfc103579 257: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] new f0642e08f7 258: onsuccess: #1987: 7: Success after binutils/gcc/gdb/qem [...] new bb3fe13b48 259: onsuccess: #1988: 7: Success after binutils/gcc/linux/g [...] new 39e901a01d 260: onsuccess: #1989: 7: Success after binutils/gcc/gdb/qem [...] new 4d9d3e6dc6 261: onsuccess: #1990: 7: Success after binutils/gcc/gdb: 19 [...] new 5e1c5a1e9f 262: onsuccess: #1991: 7: Success after gcc/linux: 109 commits new 9e898bd727 263: onsuccess: #1992: 7: Success after binutils/gcc/gdb/qem [...] new 7afd1de8cb 264: onsuccess: #1993: 7: Success after binutils/gcc/gdb: 5 commits new d732c2a688 265: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 5 commits new bfee84b012 266: onsuccess: #1995: 7: Success after v7.2.0-211-g562d4af3 [...] new 0fe087a487 267: onsuccess: #1996: 7: Success after binutils/gcc/glibc/g [...] new cfa73df3e0 268: onsuccess: #1997: 7: Success after glibc: 2 commits new baedac2041 269: onsuccess: #1998: 7: Success after binutils/gcc/glibc/g [...] new f05533950a 270: onsuccess: #1999: 7: Success after binutils/gcc/linux/g [...] new 040ac1eceb 271: onsuccess: #2000: 7: Success after binutils/gcc/gdb: 10 [...] new 87e6c34250 272: onsuccess: #2001: 7: Success after basepoints/gcc-13-48 [...] new 22d9d96858 273: onsuccess: #2002: 7: Success after binutils/gcc/gdb/qem [...] new 1d6fa5159c 274: onsuccess: #2003: 7: Success after binutils/gcc/linux/g [...] new 7ed1f3df9a 275: onsuccess: #2004: 7: Success after binutils/gcc/gdb: 6 commits new 153f48a510 276: onsuccess: #2005: 7: Success after binutils/gcc/gdb: 69 [...] new cf9515a536 277: onsuccess: #2006: 7: Success after binutils/gcc/gdb/qem [...] new daa5bfde22 278: onsuccess: #2007: 7: Success after binutils/gcc/linux/g [...] new dbdbe6f08f 279: onsuccess: #2008: 7: Success after binutils/gcc/glibc/g [...] new 754dd7e49a 280: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new 91dfc9219b 281: onsuccess: #2010: 7: Success after binutils/gcc/gdb: 30 [...] new 6a56d3742b 282: onsuccess: #2011: 7: Success after binutils/gcc/glibc/g [...] new d3d5bfc351 283: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new 70c842f0fd 284: onsuccess: #2013: 7: Success after binutils/gcc/gdb: 33 [...] new 5a9ef55f72 285: onsuccess: #2014: 7: Success after binutils/gcc/gdb: 74 [...] new 0c82cc8c0e 286: onsuccess: #2015: 7: Success after binutils/gcc/linux/g [...] new f56d864d82 287: onsuccess: #2016: 7: Success after binutils/gcc/gdb: 6 commits new 105841cc21 288: onsuccess: #2017: 7: Success after binutils/gcc/gdb: 9 commits new 550163d1e7 289: onsuccess: #2018: 7: Success after binutils/gcc/gdb: 17 [...] new 7eb823845a 290: onsuccess: #2019: 7: Success after binutils/gdb: 20 commits new 23aa89c118 291: onsuccess: #2020: 7: Success after binutils/gcc/gdb: 3 commits new bcfdfa0633 292: onsuccess: #2021: 7: Success after binutils/linux/gdb: [...] new a67c306002 293: onsuccess: #2022: 7: Success after gcc: 2 commits new aa0c551daa 294: onsuccess: #2023: 7: Success after binutils/gdb: 4 commits new 2c8d0da6de 295: onsuccess: #2024: 7: Success after basepoints/gcc-13-48 [...] new 57386d12bf 296: onsuccess: #2025: 7: Success after binutils/gcc/gdb: 5 commits new aae5adde47 297: onsuccess: #2026: 7: Success after binutils/gcc/gdb: 19 [...] new fa6ca28a45 298: onsuccess: #2027: 7: Success after binutils/gcc/gdb: 18 [...] new ebf034a55e 299: onsuccess: #2028: 7: Success after binutils/gcc/gdb: 6 commits new 22f0da72bf 300: onsuccess: #2029: 7: Success after binutils/gcc/gdb: 4 commits new c02b2d1cd5 301: onsuccess: #2030: 7: Success after binutils/gcc/gdb: 4 commits new 1de0b0b066 302: onsuccess: #2031: 7: Success after binutils/gcc/gdb: 3 commits new 7a1c4a6521 303: onsuccess: #2032: 7: Success after binutils/gdb: 2 commits new cb18397c5f 304: onsuccess: #2033: 7: Success after gcc/linux: 60 commits new e361838978 305: onsuccess: #2034: 7: Success after binutils/gcc/linux/g [...] new 84b65955aa 306: onsuccess: #2035: 7: Success after basepoints/gcc-13-49 [...] new c1f216d816 307: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 7 commits new b2f0c17865 308: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new f4c7390959 309: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 3 commits new 2a815efbbf 310: onsuccess: #2039: 7: Success after binutils/gdb: 6 commits new b400f98263 311: onsuccess: #2040: 7: Success after binutils/gdb: 20 commits new c0b016878e 312: onsuccess: #2041: 7: Success after gcc/linux: 13 commits new 7ed9f4ae6a 313: onsuccess: #2042: 7: Success after binutils/gcc/gdb: 4 commits new b80168ea27 314: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 15 [...] new 588841e783 315: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new a9d9e726d0 316: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new c412b60134 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits new 44efa7abd7 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] new 033b8eaecd 319: onsuccess: #2049: 7: Success after binutils: 4 commits new ff2963410c 320: onsuccess: #2050: 7: Success after gcc: 4 commits new ce6fc54edd 321: force: #2055: 7: Success after gdb: 2 commits new 24fa3526c0 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] new 739ab4d7d5 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] new c8a94a56e8 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new 846bc8246d 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits new c8b965ba34 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] new 0efd0071a2 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new b2963e1cd8 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new e4fc1ee43d 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] new 1c609ddf91 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits new 0da07577ae 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new b626fc9719 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] new 68ea8c7593 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] new 3da28a2db1 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] new 5614b5c321 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new 21edcf0a2d 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] new 424493d1db 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] new 550f06b3fc 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] new 859538dcd3 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits new 226660a97a 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits new 839411135f 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits new 31eddcf727 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits new 4dba969184 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...] new 168c461bf8 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 commits new 9f1d826f82 345: onsuccess: #2079: 7: Success after binutils/gcc/linux/g [...] new ea1cad721b 346: onsuccess: #2080: 7: Success after binutils/gdb: 142 commits new e4356f8df6 347: onsuccess: #2081: 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 (2c46a89e08) \ 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 1772 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2772 bytes 04-build_abe-binutils/console.log.xz | Bin 32640 -> 31680 bytes 05-build_abe-stage1/console.log.xz | Bin 92764 -> 92048 bytes 07-build_abe-linux/console.log.xz | Bin 8860 -> 8616 bytes 08-build_abe-glibc/console.log.xz | Bin 238564 -> 236172 bytes 09-build_abe-stage2/console.log.xz | Bin 230540 -> 228444 bytes 10-build_abe-gdb/console.log.xz | Bin 39756 -> 39116 bytes 11-build_abe-qemu/console.log.xz | Bin 31340 -> 31580 bytes 12-check_regression/console.log.xz | Bin 3496 -> 4056 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 | 40 ++++++++++----------- 20 files changed, 61 insertions(+), 61 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[binutils-gdb] branch binutils-2_40-branch updated (ddf8d80aef8 -> 38775ca9a73)

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_40-branch in repository binutils-gdb. from ddf8d80aef8 Automatic date update in version.in new 38775ca9a73 IBM zSystems: Fix offset relative to static TLS 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/elf32-s390.c | 4 ++-- bfd/elf64-s390.c | 4 ++-- ld/testsuite/ld-s390/reloctlsle-1.d | 6 ++++++ ld/testsuite/ld-s390/reloctlsle-1.s | 14 ++++++++++++++ 4 files changed, 24 insertions(+), 4 deletions(-) create mode 100644 ld/testsuite/ld-s390/reloctlsle-1.d create mode 100644 ld/testsuite/ld-s390/reloctlsle-1.s -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[binutils-gdb] branch binutils-2_39-branch updated (cab2aac9546 -> 4e3ee240162)

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 cab2aac9546 x86-64: Allocate input section memory if needed new 4e3ee240162 IBM zSystems: Fix offset relative to static TLS 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/elf32-s390.c | 4 ++-- bfd/elf64-s390.c | 4 ++-- ld/testsuite/ld-s390/reloctlsle-1.d | 6 ++++++ ld/testsuite/ld-s390/reloctlsle-1.s | 14 ++++++++++++++ 4 files changed, 24 insertions(+), 4 deletions(-) create mode 100644 ld/testsuite/ld-s390/reloctlsle-1.d create mode 100644 ld/testsuite/ld-s390/reloctlsle-1.s -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-mainline-allmodconfig updated (fe9393368b -> 88141df965)

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-allmodconfig in repository toolchain/ci/base-artifacts. from fe9393368b 46: onsuccess: #428: 23231: Success after binutils/linux/qem [...] new 88141df965 47: onsuccess: #429: 23233: Success after llvm/linux/qemu: 3 [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1756 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2804 bytes 03-build_abe-binutils/console.log.xz | Bin 30296 -> 30548 bytes 04-build_kernel_llvm/console.log.xz | Bin 62596 -> 63044 bytes 05-build_abe-qemu/console.log.xz | Bin 30672 -> 31500 bytes 06-build_linux/console.log.xz | Bin 3808 -> 3720 bytes 08-check_regression/console.log.xz | Bin 3808 -> 3936 bytes 08-check_regression/mail-body.txt | 2 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- results | 2 +- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[binutils-gdb] branch master updated (18737d14799 -> aefebe82dc8)

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 18737d14799 PR 29981 references to init.texi new aefebe82dc8 IBM zSystems: Fix offset relative to static TLS 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/elf32-s390.c | 4 ++-- bfd/elf64-s390.c | 4 ++-- ld/testsuite/ld-s390/reloctlsle-1.d | 6 ++++++ ld/testsuite/ld-s390/reloctlsle-1.s | 14 ++++++++++++++ 4 files changed, 24 insertions(+), 4 deletions(-) create mode 100644 ld/testsuite/ld-s390/reloctlsle-1.d create mode 100644 ld/testsuite/ld-s390/reloctlsle-1.s -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[gcc] branch releases/gcc-12 updated (849c3cf7b41 -> 25edc76f2af)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-12 in repository gcc. from 849c3cf7b41 aarch64: PR target/108140 Handle NULL target in data intrin [...] new 25edc76f2af Fix memory constraint on MVE v[ld/st][2/4] instructions [PR107714] 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/arm/arm-protos.h | 1 + gcc/config/arm/arm.cc | 18 ++ gcc/config/arm/constraints.md | 5 + gcc/config/arm/mve.md | 8 +- gcc/config/arm/predicates.md | 4 + .../arm/mve/intrinsics/vldst24q_reg_offset.c | 300 +++++++++++++++++++++ 6 files changed, 332 insertions(+), 4 deletions(-) create mode 100644 gcc/testsuite/gcc.target/arm/mve/intrinsics/vldst24q_reg_offset.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[gcc] branch releases/gcc-11 updated (cedc5812df7 -> 08842ad274f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-11 in repository gcc. from cedc5812df7 Daily bump. new 08842ad274f Fix memory constraint on MVE v[ld/st][2/4] instructions [PR107714] 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/arm/arm-protos.h | 1 + gcc/config/arm/arm.c | 18 ++ gcc/config/arm/constraints.md | 5 + gcc/config/arm/mve.md | 8 +- gcc/config/arm/predicates.md | 4 + .../arm/mve/intrinsics/vldst24q_reg_offset.c | 300 +++++++++++++++++++++ 6 files changed, 332 insertions(+), 4 deletions(-) create mode 100644 gcc/testsuite/gcc.target/arm/mve/intrinsics/vldst24q_reg_offset.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_O1 updated (da71381f2e -> 05c3437539)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_O1 in repository toolchain/ci/base-artifacts. discards da71381f2e 163: onsuccess: #568: 2: Success after binutils/gcc: 4 commits discards 5c1790a213 162: onsuccess: #567: 2: Success after binutils/gcc: 6 commits discards 00a0abebc8 161: onsuccess: #566: 2: Success after binutils/gcc: 27 commits discards 57c51d7928 160: onsuccess: #565: 2: Success after binutils/gcc: 51 commits discards afe1880b5d 159: onsuccess: #564: 2: Success after binutils/gcc: 36 commits discards 7f28685617 158: onsuccess: #563: 2: Success after binutils/gcc: 53 commits discards efb68011d2 157: onsuccess: #562: 1: Success after gcc: 4 commits discards 5f85ae304b 156: force: #561: 1: Failure after basepoints/gcc-13-4953-g3 [...] discards 9ad8d009ae 155: force: #560: 2: Success after gcc: 6 commits discards f21b6d19f3 154: onsuccess: #558: 2: Success after binutils: 19 commits discards 39eac5ed81 153: onsuccess: #556: 2: Success after binutils/gcc: 18 commits discards a7a747463d 152: onsuccess: #555: 2: Success after binutils/gcc: 18 commits discards 4d61f965a8 151: onsuccess: #554: 2: Success after binutils/gcc: 11 commits discards 54c8d78704 150: onsuccess: #553: 2: Success after binutils/gcc: 20 commits discards b80a5ac5f5 149: onsuccess: #552: 2: Success after binutils/gcc: 8 commits discards 5b8b40269d 148: onsuccess: #551: 2: Success after binutils/gcc: 30 commits discards 16fb168f46 147: onsuccess: #550: 2: Success after binutils/gcc: 6 commits discards 7497726c47 146: onsuccess: #549: 2: Success after binutils/gcc: 24 commits discards 1326bd26d0 145: onsuccess: #548: 2: Success after binutils/gcc: 8 commits discards 28ec9e0f44 144: onsuccess: #547: 2: Success after binutils/gcc: 74 commits discards 84d35f88e1 143: onsuccess: #546: 2: Success after binutils/gcc: 58 commits discards 32ba849a19 142: onsuccess: #545: 2: Success after binutils/gcc: 67 commits discards c3339410ac 141: onsuccess: #544: 2: Success after binutils/gcc: 14 commits discards bab3bc2ec1 140: onsuccess: #543: 2: Success after binutils/gcc: 56 commits discards dd1f9a617b 139: onsuccess: #542: 2: Success after binutils/gcc: 9 commits discards b31f78d61c 138: onsuccess: #541: 2: Success after binutils/gcc: 14 commits discards 48c7fea098 137: onsuccess: #540: 2: Success after binutils/gcc: 39 commits discards e0b80aac30 136: onsuccess: #539: 1: Success after binutils/gcc: 72 commits discards 45cb4ea14f 135: onsuccess: #538: 1: Success after binutils: 10 commits discards dc80518981 134: force: #537: 1: Failure after gdb-12-branchpoint-3046-g [...] discards 2d9e20c33c 133: force: #536: 2: Success after binutils: 4 commits discards 549eabbf95 132: onsuccess: #534: 2: Success after gcc: 66 commits discards b9caa63d8c 131: onsuccess: #531: 2: Success after binutils/gcc: 47 commits discards 5f81e34bf2 130: onsuccess: #530: 2: Success after binutils/gcc: 12 commits discards e638336208 129: onsuccess: #529: 2: Success after binutils/gcc: 3 commits discards bc54e59c21 128: onsuccess: #528: 2: Success after binutils/gcc: 31 commits discards 6b9306d46a 127: onsuccess: #527: 2: Success after binutils/gcc: 33 commits discards a9ebcec9a9 126: onsuccess: #526: 2: Success after binutils/gcc: 27 commits discards 0bfd029fa1 125: onsuccess: #525: 2: Success after binutils/gcc: 47 commits discards b1d93a407f 124: onsuccess: #524: 2: Success after binutils/gcc: 34 commits discards 7a600e3294 123: onsuccess: #523: 2: Success after binutils/gcc: 13 commits discards 77e85fee17 122: onsuccess: #522: 2: Success after binutils/gcc: 6 commits discards 88c910526f 121: onsuccess: #521: 2: Success after binutils/gcc: 31 commits discards cc1b4f98dc 120: onsuccess: #520: 2: Success after binutils/gcc: 54 commits discards 98ef394209 119: onsuccess: #519: 2: Success after binutils/gcc: 41 commits discards 02f92372f3 118: onsuccess: #518: 2: Success after binutils/gcc: 25 commits discards e4ef53f379 117: onsuccess: #517: 2: Success after binutils/gcc: 117 commits discards 27d3762f90 116: onsuccess: #516: 2: Success after binutils/gcc: 7 commits discards d070a24a28 115: onsuccess: #515: 2: Success after binutils/gcc: 7 commits discards 3cb8836e79 114: onsuccess: #514: 2: Success after binutils/gcc: 20 commits discards 8419949a61 113: onsuccess: #513: 2: Success after binutils/gcc: 43 commits discards f0ed7891ee 112: onsuccess: #512: 2: Success after binutils/gcc: 29 commits discards f5bd651f8f 111: onsuccess: #511: 1: Success after gcc: 4 commits discards 83691aa431 110: force: #510: 1: Failure after basepoints/gcc-13-4252-ga [...] discards 93ca502904 109: force: #509: 2: Success after gcc: 28 commits discards d2b9ea8f8b 108: onsuccess: #507: 2: Success after binutils: 15 commits discards 5b01de69c1 107: onsuccess: #505: 2: Success after binutils/gcc: 53 commits discards bfed9733ee 106: onsuccess: #504: 2: Success after binutils/gcc: 13 commits discards dc83f5592c 105: onsuccess: #503: 2: Success after binutils/gcc: 56 commits discards 527cc5acd1 104: onsuccess: #501: 2: Success after binutils/gcc: 38 commits discards 08391e22d1 103: onsuccess: #500: 2: Success after binutils/gcc: 65 commits discards f16972e178 102: onsuccess: #498: 2: Success after binutils/gcc: 162 commits discards 978fc9f924 101: onsuccess: #497: 1: Success after binutils/gcc: 15 commits discards 9b5939c39c 100: onsuccess: #496: 1: Success after binutils/gcc: 23 commits discards d95f461fa2 99: onsuccess: #495: 1: Success after baseline build: no new [...] discards 7fee75ee76 98: force: #494: 1: Failure after basepoints/gcc-13-3918-gba [...] discards 466f361d55 97: force: #493: 2: Success after gcc: 32 commits discards 20cdcff529 96: onsuccess: #491: 2: Success after binutils: 25 commits discards 12bc5500f0 95: onsuccess: #489: 2: Success after binutils/gcc: 49 commits discards b9a034b44c 94: onsuccess: #488: 2: Success after binutils/gcc: 63 commits discards 2e53cf4c5f 93: onsuccess: #487: 2: Success after binutils/gcc: 66 commits discards 2ce4eee08e 92: onsuccess: #486: 2: Success after binutils/gcc: 73 commits discards 6851c6e8c1 91: onsuccess: #485: 2: Success after binutils/gcc: 12 commits discards f8ed843c66 90: onsuccess: #484: 2: Success after binutils/gcc: 24 commits discards e98eb960a4 89: onsuccess: #483: 2: Success after binutils/gcc: 64 commits discards 5645abec27 88: onsuccess: #482: 2: Success after binutils/gcc: 49 commits discards d8f161308d 87: onsuccess: #481: 2: Success after binutils/gcc: 27 commits discards f6e400d410 86: onsuccess: #480: 2: Success after binutils/gcc: 28 commits discards 8541cb40e2 85: onsuccess: #479: 2: Success after binutils/gcc: 43 commits discards e018ccec25 84: onsuccess: #478: 2: Success after binutils/gcc: 3 commits discards c21b750470 83: onsuccess: #477: 2: Success after binutils/gcc: 24 commits discards 0d9714be56 82: onsuccess: #476: 2: Success after binutils/gcc: 33 commits discards 03a4bdee5a 81: onsuccess: #475: 2: Success after binutils/gcc: 29 commits discards d8f7350b26 80: onsuccess: #474: 2: Success after binutils/gcc: 34 commits discards 52e0b02657 79: onsuccess: #473: 2: Success after binutils/gcc: 35 commits discards c5ef463a0a 78: onsuccess: #472: 2: Success after binutils/gcc: 43 commits discards 7a19c77f62 77: onsuccess: #471: 2: Success after binutils/gcc: 6 commits discards 67857e059b 76: onsuccess: #470: 2: Success after binutils/gcc: 6 commits discards 0a59f11c04 75: onsuccess: #469: 2: Success after binutils/gcc: 38 commits discards 6c2e6c8260 74: onsuccess: #468: 2: Success after binutils/gcc: 46 commits discards 17424ccf17 73: onsuccess: #467: 2: Success after binutils/gcc: 49 commits discards 3627ec0286 72: onsuccess: #466: 2: Success after binutils/gcc: 43 commits discards 5adec45425 71: onsuccess: #465: 2: Success after binutils/gcc: 46 commits discards a9c48432e3 70: onsuccess: #464: 2: Success after binutils/gcc: 9 commits discards 403739cebf 69: onsuccess: #463: 2: Success after binutils/gcc: 6 commits discards 9667f7c53d 68: onsuccess: #462: 2: Success after binutils/gcc: 53 commits discards 27bf078fd3 67: onsuccess: #461: 2: Success after binutils/gcc: 27 commits discards 902ef55fec 66: onsuccess: #460: 2: Success after binutils/gcc: 41 commits discards f35bdaec45 65: onsuccess: #459: 2: Success after binutils/gcc: 61 commits discards 4af16de284 64: onsuccess: #458: 1: Success after binutils/gcc: 49 commits discards 89826d4118 63: onsuccess: #457: 1: Success after binutils/gcc: 7 commits new ef5f4e4cf1 63: onsuccess: #457: 1: Success after binutils/gcc: 7 commits new 6a6d6d03ab 64: onsuccess: #458: 1: Success after binutils/gcc: 49 commits new ea19509733 65: onsuccess: #459: 2: Success after binutils/gcc: 61 commits new 8b4e975b5b 66: onsuccess: #460: 2: Success after binutils/gcc: 41 commits new cc9f201850 67: onsuccess: #461: 2: Success after binutils/gcc: 27 commits new 6c9b0782f3 68: onsuccess: #462: 2: Success after binutils/gcc: 53 commits new f614d0e62f 69: onsuccess: #463: 2: Success after binutils/gcc: 6 commits new d7a9e35ea8 70: onsuccess: #464: 2: Success after binutils/gcc: 9 commits new c3e38d6474 71: onsuccess: #465: 2: Success after binutils/gcc: 46 commits new 456d68ff7f 72: onsuccess: #466: 2: Success after binutils/gcc: 43 commits new 0497e2336b 73: onsuccess: #467: 2: Success after binutils/gcc: 49 commits new 7e9c793f1c 74: onsuccess: #468: 2: Success after binutils/gcc: 46 commits new 2f7d1f250c 75: onsuccess: #469: 2: Success after binutils/gcc: 38 commits new b816ec32aa 76: onsuccess: #470: 2: Success after binutils/gcc: 6 commits new 5bb6354f3b 77: onsuccess: #471: 2: Success after binutils/gcc: 6 commits new fc877a9c7b 78: onsuccess: #472: 2: Success after binutils/gcc: 43 commits new 85a404cf4e 79: onsuccess: #473: 2: Success after binutils/gcc: 35 commits new be2b3de181 80: onsuccess: #474: 2: Success after binutils/gcc: 34 commits new f15edd636e 81: onsuccess: #475: 2: Success after binutils/gcc: 29 commits new e58eae2e91 82: onsuccess: #476: 2: Success after binutils/gcc: 33 commits new 5bb27a1d90 83: onsuccess: #477: 2: Success after binutils/gcc: 24 commits new 187c172607 84: onsuccess: #478: 2: Success after binutils/gcc: 3 commits new aa6768e364 85: onsuccess: #479: 2: Success after binutils/gcc: 43 commits new 01688f3391 86: onsuccess: #480: 2: Success after binutils/gcc: 28 commits new 8d4784fa6c 87: onsuccess: #481: 2: Success after binutils/gcc: 27 commits new ba22aff20c 88: onsuccess: #482: 2: Success after binutils/gcc: 49 commits new d8e8d15fd1 89: onsuccess: #483: 2: Success after binutils/gcc: 64 commits new c83b503388 90: onsuccess: #484: 2: Success after binutils/gcc: 24 commits new 6fd4423b83 91: onsuccess: #485: 2: Success after binutils/gcc: 12 commits new 1c3eaee4a7 92: onsuccess: #486: 2: Success after binutils/gcc: 73 commits new 1e31454db3 93: onsuccess: #487: 2: Success after binutils/gcc: 66 commits new 1eb39bcfa6 94: onsuccess: #488: 2: Success after binutils/gcc: 63 commits new 5ac15882d8 95: onsuccess: #489: 2: Success after binutils/gcc: 49 commits new 3f11d4b9b9 96: onsuccess: #491: 2: Success after binutils: 25 commits new de3733d522 97: force: #493: 2: Success after gcc: 32 commits new a41b34fc4a 98: force: #494: 1: Failure after basepoints/gcc-13-3918-gba [...] new c05e1eccaf 99: onsuccess: #495: 1: Success after baseline build: no new [...] new fa880a38cf 100: onsuccess: #496: 1: Success after binutils/gcc: 23 commits new 561b00d641 101: onsuccess: #497: 1: Success after binutils/gcc: 15 commits new 10f18d1ad0 102: onsuccess: #498: 2: Success after binutils/gcc: 162 commits new a1e0819d31 103: onsuccess: #500: 2: Success after binutils/gcc: 65 commits new 852b851865 104: onsuccess: #501: 2: Success after binutils/gcc: 38 commits new 0303c891a6 105: onsuccess: #503: 2: Success after binutils/gcc: 56 commits new f04104ec4a 106: onsuccess: #504: 2: Success after binutils/gcc: 13 commits new 8ab9708a7f 107: onsuccess: #505: 2: Success after binutils/gcc: 53 commits new fccbadcc46 108: onsuccess: #507: 2: Success after binutils: 15 commits new 5b9e8c22b2 109: force: #509: 2: Success after gcc: 28 commits new 4cb8c3f893 110: force: #510: 1: Failure after basepoints/gcc-13-4252-ga [...] new 4ce1b14892 111: onsuccess: #511: 1: Success after gcc: 4 commits new f17e509686 112: onsuccess: #512: 2: Success after binutils/gcc: 29 commits new b39555b33f 113: onsuccess: #513: 2: Success after binutils/gcc: 43 commits new 132ea1dc0e 114: onsuccess: #514: 2: Success after binutils/gcc: 20 commits new 7d62e4f73f 115: onsuccess: #515: 2: Success after binutils/gcc: 7 commits new 6a4140e7ba 116: onsuccess: #516: 2: Success after binutils/gcc: 7 commits new d8595d5d1b 117: onsuccess: #517: 2: Success after binutils/gcc: 117 commits new 7b09fa4fe7 118: onsuccess: #518: 2: Success after binutils/gcc: 25 commits new c483cf02bd 119: onsuccess: #519: 2: Success after binutils/gcc: 41 commits new 161bd899b7 120: onsuccess: #520: 2: Success after binutils/gcc: 54 commits new 6c7046bc7c 121: onsuccess: #521: 2: Success after binutils/gcc: 31 commits new 28d0d9da00 122: onsuccess: #522: 2: Success after binutils/gcc: 6 commits new 58a30d760e 123: onsuccess: #523: 2: Success after binutils/gcc: 13 commits new d597f00b90 124: onsuccess: #524: 2: Success after binutils/gcc: 34 commits new a77e0ba91a 125: onsuccess: #525: 2: Success after binutils/gcc: 47 commits new 734bff0dd2 126: onsuccess: #526: 2: Success after binutils/gcc: 27 commits new b6a7a19835 127: onsuccess: #527: 2: Success after binutils/gcc: 33 commits new a27b02236a 128: onsuccess: #528: 2: Success after binutils/gcc: 31 commits new 2f657a0e09 129: onsuccess: #529: 2: Success after binutils/gcc: 3 commits new c128c9a91b 130: onsuccess: #530: 2: Success after binutils/gcc: 12 commits new 489b31c39e 131: onsuccess: #531: 2: Success after binutils/gcc: 47 commits new 188ffcc962 132: onsuccess: #534: 2: Success after gcc: 66 commits new 22e83d7367 133: force: #536: 2: Success after binutils: 4 commits new e91a598992 134: force: #537: 1: Failure after gdb-12-branchpoint-3046-g [...] new 80de394af2 135: onsuccess: #538: 1: Success after binutils: 10 commits new ce86b5dca6 136: onsuccess: #539: 1: Success after binutils/gcc: 72 commits new df19e94790 137: onsuccess: #540: 2: Success after binutils/gcc: 39 commits new fa60ea8bd3 138: onsuccess: #541: 2: Success after binutils/gcc: 14 commits new c7a09fadb3 139: onsuccess: #542: 2: Success after binutils/gcc: 9 commits new bb2ab93f83 140: onsuccess: #543: 2: Success after binutils/gcc: 56 commits new 2b50423989 141: onsuccess: #544: 2: Success after binutils/gcc: 14 commits new e029829510 142: onsuccess: #545: 2: Success after binutils/gcc: 67 commits new 5a31635c48 143: onsuccess: #546: 2: Success after binutils/gcc: 58 commits new b5fee9ccdf 144: onsuccess: #547: 2: Success after binutils/gcc: 74 commits new f4fc910536 145: onsuccess: #548: 2: Success after binutils/gcc: 8 commits new 026e6ac2ac 146: onsuccess: #549: 2: Success after binutils/gcc: 24 commits new 60a6389114 147: onsuccess: #550: 2: Success after binutils/gcc: 6 commits new 8aa50194e9 148: onsuccess: #551: 2: Success after binutils/gcc: 30 commits new 19126cd8da 149: onsuccess: #552: 2: Success after binutils/gcc: 8 commits new 04e53227b8 150: onsuccess: #553: 2: Success after binutils/gcc: 20 commits new 78655dbb9e 151: onsuccess: #554: 2: Success after binutils/gcc: 11 commits new 1eee81a601 152: onsuccess: #555: 2: Success after binutils/gcc: 18 commits new 34b4e30b3e 153: onsuccess: #556: 2: Success after binutils/gcc: 18 commits new ee1195f4fd 154: onsuccess: #558: 2: Success after binutils: 19 commits new e24b9a5577 155: force: #560: 2: Success after gcc: 6 commits new 17052962dc 156: force: #561: 1: Failure after basepoints/gcc-13-4953-g3 [...] new de602d1e33 157: onsuccess: #562: 1: Success after gcc: 4 commits new c4cad74315 158: onsuccess: #563: 2: Success after binutils/gcc: 53 commits new d70913f7c3 159: onsuccess: #564: 2: Success after binutils/gcc: 36 commits new 52868d1e7e 160: onsuccess: #565: 2: Success after binutils/gcc: 51 commits new 100b65d305 161: onsuccess: #566: 2: Success after binutils/gcc: 27 commits new e503b0a60e 162: onsuccess: #567: 2: Success after binutils/gcc: 6 commits new 18e22c55d7 163: onsuccess: #568: 2: Success after binutils/gcc: 4 commits new 05c3437539 164: onsuccess: #569: 2: Success after binutils/gcc: 115 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 (da71381f2e) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1760 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2756 bytes 04-build_abe-binutils/console.log.xz | Bin 39580 -> 39536 bytes 05-build_abe-bootstrap_O1/console.log.xz | Bin 275228 -> 271620 bytes 06-check_regression/console.log.xz | Bin 2616 -> 3032 bytes 07-update_baseline/console.log | 38 +++++++++++++++---------------- 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 ++++++++-------- 13 files changed, 35 insertions(+), 35 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-stable-allyesconfig updated (7e900cc2f8 -> ca27da70bd)

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-master-arm-stable-allyesconfig in repository toolchain/ci/base-artifacts. from 7e900cc2f8 39: onsuccess: #498: 33: Success after binutils/gcc/linux/qe [...] new ca27da70bd 40: onsuccess: #499: 33: Success after binutils/gcc/linux/qe [...] 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 -> 1816 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2796 bytes 03-build_abe-binutils/console.log.xz | Bin 32612 -> 32300 bytes 04-build_abe-stage1/console.log.xz | Bin 92988 -> 92688 bytes 05-build_abe-qemu/console.log.xz | Bin 31016 -> 31436 bytes 06-build_linux/console.log.xz | Bin 5340 -> 5236 bytes 08-check_regression/console.log.xz | Bin 4508 -> 4380 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 16 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

Jump to page: