Tcwg-commits February 2023

tcwg-commits@lists.linaro.org

5 participants
3393 discussions

[linux] branch master updated (7b753a909f42 -> 0136d86b7852)

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 linux. from 7b753a909f42 Merge tag 'ceph-for-6.2-rc7' of https://github.com/ceph/ce [...] new b600de2d7d3a block, bfq: fix uaf for bfqq in bic_set_bfqq() new 29baef789c83 block: ublk: extending queue_size to fix overflow new 81ea42b9c3d6 block: Fix the blk_mq_destroy_queue() documentation new 0416f3be58c6 blk-cgroup: don't update io stat for root cgroup new 0cab4404874f nvme-fc: fix a missing queue put in nvmet_fc_ls_create_ass [...] new fd62678ab55c nvme: clear the request_queue pointers on failure in nvme_ [...] new 6fbf13c0e24f nvme: clear the request_queue pointers on failure in nvme_ [...] new bd97a59da6a8 nvme-auth: use workqueue dedicated to authentication new e02bbac74cdd Merge tag 'nvme-6.2-2023-02-02' of git://git.infradead.org [...] new 0136d86b7852 Merge tag 'block-6.2-2023-02-03' of git://git.kernel.dk/linux The 10 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: block/bfq-cgroup.c | 2 +- block/bfq-iosched.c | 4 +++- block/blk-cgroup.c | 4 ++++ block/blk-mq.c | 5 +++-- drivers/block/ublk_drv.c | 2 +- drivers/nvme/host/auth.c | 14 ++++++++++++-- drivers/nvme/host/core.c | 5 ++++- drivers/nvme/target/fc.c | 4 +++- 8 files changed, 31 insertions(+), 9 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[gcc] branch master updated (27ac6a707e7 -> 093e2e1b201)

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 27ac6a707e7 c++: wrong error with constexpr array and value-init [PR108158] new 093e2e1b201 Reset SCEV before removing unreachable globals. 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/testsuite/gcc.dg/pr107570.c | 25 +++++++++++++++++++++++++ gcc/tree-vrp.cc | 4 ++++ 2 files changed, 29 insertions(+) create mode 100644 gcc/testsuite/gcc.dg/pr107570.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-coremark/gnu_eabi-arm_eabi-master-Os updated (16c61dca5e -> 0663beef05)

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-code_size-coremark/gnu_eabi-arm_eabi-master-Os in repository toolchain/ci/base-artifacts. from 16c61dca5e 46: onsuccess: #6: 1: [TCWG CI] No change after binutils/gcc [...] new 0663beef05 47: onsuccess: #7: 1: [TCWG CI] No change after binutils/gcc [...] 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 1784 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 31272 -> 31280 bytes 04-build_abe-stage1/console.log.xz | Bin 90612 -> 89420 bytes 06-build_abe-newlib/console.log.xz | Bin 14672 -> 14884 bytes 07-build_abe-stage2/console.log.xz | Bin 167176 -> 164948 bytes 08-benchmark/benchmark-build.log | 96 ++++++++++----------- 08-benchmark/benchmark.log | 94 ++++++++++---------- 08-benchmark/console.log.xz | Bin 3828 -> 3812 bytes 09-check_regression/console.log.xz | Bin 4808 -> 5000 bytes 09-check_regression/results-vs-first.log | 8 +- 09-check_regression/results-vs-prev.log | 6 +- dashboard/dashboard-generate.sh | 2 +- .../squad-vs-first/Mean/results-metadata.json | 12 +-- .../squad-vs-first/coremark/results-metadata.json | 12 +-- dashboard/squad-vs-first/dashboard-push-squad.sh | 10 +-- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/newlib_rev | 2 +- mail/jira-body.txt | 33 +++---- mail/mail-body.txt | 33 +++---- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++---- results_id | 2 +- 24 files changed, 176 insertions(+), 170 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (8520220efa -> 9d857a223c)

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 8520220efa 385: onsuccess: #2120: 7: Success after binutils/gcc/gdb/qem [...] discards f88f7c7591 384: onsuccess: #2119: 7: Success after binutils/gcc/linux/g [...] discards a57e35b17d 383: onsuccess: #2118: 7: Success after binutils/gcc/glibc/g [...] discards e9f985ecff 382: onsuccess: #2117: 7: Success after binutils/gcc/linux/g [...] discards eb8df42b06 381: onsuccess: #2116: 7: Success after binutils/gcc/linux/g [...] discards 3aaafdd367 380: onsuccess: #2115: 7: Success after binutils/gcc/linux/g [...] discards bf03864cf8 379: onsuccess: #2114: 7: Success after binutils/gcc/linux/g [...] discards 0f1ad3687e 378: onsuccess: #2113: 7: Success after binutils/gcc/linux/g [...] discards b58f2697c0 377: onsuccess: #2112: 7: Success after binutils/gcc/gdb: 16 [...] discards e8f7fc8ff3 376: onsuccess: #2111: 7: Success after binutils/gcc/linux/g [...] discards f122234e40 375: onsuccess: #2110: 7: Success after binutils/gcc/linux/g [...] discards 0bcd129495 374: onsuccess: #2109: 7: Success after binutils/gcc/linux/g [...] discards b8c8c8b2d0 373: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] discards d46259e3ef 372: onsuccess: #2106: 7: Success after binutils/gcc/linux/g [...] discards 70ef3cbd1d 371: onsuccess: #2105: 7: Success after binutils/gcc/gdb/qem [...] discards dcd1e52da0 370: onsuccess: #2104: 7: Success after binutils/gcc/linux/g [...] discards 7cf8c40755 369: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] discards fac68744dc 368: onsuccess: #2102: 7: Success after binutils/gcc/linux/g [...] discards bece919e1e 367: onsuccess: #2101: 7: Success after binutils/gcc/linux/g [...] discards 0a2f6bda8d 366: onsuccess: #2100: 7: Success after binutils/gcc/glibc/g [...] discards 0fd9335a04 365: onsuccess: #2099: 7: Success after gcc/linux: 21 commits discards 5f6bd39634 364: onsuccess: #2098: 7: Success after binutils/gdb: 4 commits discards cb1714b79e 363: onsuccess: #2097: 7: Success after binutils/gcc/gdb: 25 [...] discards 1bff045c63 362: onsuccess: #2096: 7: Success after binutils/gcc/linux/g [...] discards e2790a4a9b 361: onsuccess: #2095: 7: Success after gcc/linux: 15 commits discards efa1ac9f9a 360: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] discards 74a92f5402 359: onsuccess: #2093: 7: Success after binutils/gcc/linux/g [...] discards fe9e69e899 358: onsuccess: #2092: 7: Success after binutils/gcc/gdb: 10 [...] discards da3bc5b1c3 357: onsuccess: #2091: 7: Success after binutils/gcc/linux/g [...] discards 5ac69f7934 356: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] discards 49646de690 355: onsuccess: #2089: 7: Success after binutils/gcc/linux/g [...] discards 7bb02f09b5 354: onsuccess: #2088: 7: Success after binutils/gcc/gdb: 7 commits discards a41bc52287 353: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] discards d6d92a34fa 352: onsuccess: #2086: 7: Success after binutils/gcc/gdb: 9 commits discards 96b3f493b5 351: onsuccess: #2085: 7: Success after binutils/gcc/gdb: 19 [...] discards 35d40144a9 350: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits discards f9163ef94b 349: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] discards 6f8d537ab9 348: onsuccess: #2082: 7: Success after binutils/gcc/glibc/g [...] discards 8276bb9d9b 347: onsuccess: #2081: 7: Success after binutils/gcc/linux/g [...] discards 381e3a9e92 346: onsuccess: #2080: 7: Success after binutils/gdb: 142 commits discards d7d9e1f2ee 345: onsuccess: #2079: 7: Success after binutils/gcc/linux/g [...] discards 9353854efe 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 commits discards 29122b037a 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...] discards 49c4ed1bee 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits discards d09052c619 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits discards 0f3a97221a 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits discards 5a73bf234a 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits discards 8dee9f1779 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] discards 67f22106d7 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] discards b8ae72ab76 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] discards 3d32004580 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards b460459117 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] discards 08e356fca2 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] discards e56ccb7729 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] discards 674bc9b512 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards 4a7a8310e7 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits discards 4e81508d08 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] discards 88194a8a63 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards 794d4d5d5f 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards 212db053db 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] discards 7bf4706f34 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits discards 32c37c81ea 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards 193a8891c7 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] discards b3a339bc1c 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] discards dc721f2c0b 321: force: #2055: 7: Success after gdb: 2 commits discards 1cd9447172 320: onsuccess: #2050: 7: Success after gcc: 4 commits discards b7322689dc 319: onsuccess: #2049: 7: Success after binutils: 4 commits discards 9951699834 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] discards 3c9342ecb7 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits discards e9ced38f3e 316: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards c664d95f92 315: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards 3149e9b8a0 314: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 15 [...] discards 058527a4c1 313: onsuccess: #2042: 7: Success after binutils/gcc/gdb: 4 commits discards 39842fab74 312: onsuccess: #2041: 7: Success after gcc/linux: 13 commits discards eaa5307218 311: onsuccess: #2040: 7: Success after binutils/gdb: 20 commits discards 155e40504a 310: onsuccess: #2039: 7: Success after binutils/gdb: 6 commits discards b24c74ea37 309: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 3 commits discards 159b49a87e 308: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards 320d93fc4a 307: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 7 commits discards 7217b753e2 306: onsuccess: #2035: 7: Success after basepoints/gcc-13-49 [...] discards c3c926da6f 305: onsuccess: #2034: 7: Success after binutils/gcc/linux/g [...] discards a93e20cd39 304: onsuccess: #2033: 7: Success after gcc/linux: 60 commits discards 678c5322a9 303: onsuccess: #2032: 7: Success after binutils/gdb: 2 commits discards 55b651b071 302: onsuccess: #2031: 7: Success after binutils/gcc/gdb: 3 commits discards 59356fe740 301: onsuccess: #2030: 7: Success after binutils/gcc/gdb: 4 commits discards a844b22b0f 300: onsuccess: #2029: 7: Success after binutils/gcc/gdb: 4 commits discards 090d21a300 299: onsuccess: #2028: 7: Success after binutils/gcc/gdb: 6 commits discards d5cd21c7de 298: onsuccess: #2027: 7: Success after binutils/gcc/gdb: 18 [...] discards 4b69c22376 297: onsuccess: #2026: 7: Success after binutils/gcc/gdb: 19 [...] discards e2e9cfe6be 296: onsuccess: #2025: 7: Success after binutils/gcc/gdb: 5 commits discards 37fc09839a 295: onsuccess: #2024: 7: Success after basepoints/gcc-13-48 [...] discards d67e5036f1 294: onsuccess: #2023: 7: Success after binutils/gdb: 4 commits discards fbee26e715 293: onsuccess: #2022: 7: Success after gcc: 2 commits discards 9020d8bcc2 292: onsuccess: #2021: 7: Success after binutils/linux/gdb: [...] discards d953f757e3 291: onsuccess: #2020: 7: Success after binutils/gcc/gdb: 3 commits discards bc4af89b6b 290: onsuccess: #2019: 7: Success after binutils/gdb: 20 commits discards 182a5cdfdb 289: onsuccess: #2018: 7: Success after binutils/gcc/gdb: 17 [...] discards c8c7ceadcd 288: onsuccess: #2017: 7: Success after binutils/gcc/gdb: 9 commits discards 414968000e 287: onsuccess: #2016: 7: Success after binutils/gcc/gdb: 6 commits discards 97d09cc273 286: onsuccess: #2015: 7: Success after binutils/gcc/linux/g [...] discards dc729805fc 285: onsuccess: #2014: 7: Success after binutils/gcc/gdb: 74 [...] new 909d85e5b0 285: onsuccess: #2014: 7: Success after binutils/gcc/gdb: 74 [...] new 5a1a709a60 286: onsuccess: #2015: 7: Success after binutils/gcc/linux/g [...] new 35a0664a8b 287: onsuccess: #2016: 7: Success after binutils/gcc/gdb: 6 commits new f8e9e63348 288: onsuccess: #2017: 7: Success after binutils/gcc/gdb: 9 commits new 5b219fc131 289: onsuccess: #2018: 7: Success after binutils/gcc/gdb: 17 [...] new b22b19f2cf 290: onsuccess: #2019: 7: Success after binutils/gdb: 20 commits new a0c5d4c6eb 291: onsuccess: #2020: 7: Success after binutils/gcc/gdb: 3 commits new 8b9a23fb5c 292: onsuccess: #2021: 7: Success after binutils/linux/gdb: [...] new 640b6a9a98 293: onsuccess: #2022: 7: Success after gcc: 2 commits new 1c05805c91 294: onsuccess: #2023: 7: Success after binutils/gdb: 4 commits new 933459637f 295: onsuccess: #2024: 7: Success after basepoints/gcc-13-48 [...] new 5dda2a1a2f 296: onsuccess: #2025: 7: Success after binutils/gcc/gdb: 5 commits new 53829a6d32 297: onsuccess: #2026: 7: Success after binutils/gcc/gdb: 19 [...] new 3908eecfae 298: onsuccess: #2027: 7: Success after binutils/gcc/gdb: 18 [...] new b507fa2d52 299: onsuccess: #2028: 7: Success after binutils/gcc/gdb: 6 commits new 858ccfcfff 300: onsuccess: #2029: 7: Success after binutils/gcc/gdb: 4 commits new 62e3c8dc4a 301: onsuccess: #2030: 7: Success after binutils/gcc/gdb: 4 commits new 9db1f2a91e 302: onsuccess: #2031: 7: Success after binutils/gcc/gdb: 3 commits new 6d8878ced6 303: onsuccess: #2032: 7: Success after binutils/gdb: 2 commits new 4d33540b50 304: onsuccess: #2033: 7: Success after gcc/linux: 60 commits new fb0d362e12 305: onsuccess: #2034: 7: Success after binutils/gcc/linux/g [...] new 3f4dd83f58 306: onsuccess: #2035: 7: Success after basepoints/gcc-13-49 [...] new 256a2dea6a 307: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 7 commits new 5bbbf743dc 308: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new 8f045e839b 309: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 3 commits new 5b6950d7a9 310: onsuccess: #2039: 7: Success after binutils/gdb: 6 commits new 4024912b8b 311: onsuccess: #2040: 7: Success after binutils/gdb: 20 commits new 68ad968dc8 312: onsuccess: #2041: 7: Success after gcc/linux: 13 commits new 89c4265113 313: onsuccess: #2042: 7: Success after binutils/gcc/gdb: 4 commits new 24d7e5178e 314: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 15 [...] new 30f9890343 315: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new ffe63bc182 316: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new f8d7653533 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits new b486b5b1a6 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] new 88ba9ab4d8 319: onsuccess: #2049: 7: Success after binutils: 4 commits new 5fb5e57b9a 320: onsuccess: #2050: 7: Success after gcc: 4 commits new 1f1899aee3 321: force: #2055: 7: Success after gdb: 2 commits new ab15bae02b 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] new 7452ef5b72 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] new 8be6157c75 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new ab05b4ce2b 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits new ad118ec805 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] new 590a299c21 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new 0528712b84 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new 04efcf3d29 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] new 58a9f8fae2 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits new b9d51c22ef 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new 29fa4c6963 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] new e4797042d0 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] new a81ef8b48d 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] new d8cfb750b5 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new ef13ecb01d 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] new 8cddcf6fe6 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] new f040e1c6d3 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] new 35051060cc 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits new b9a8e7fa3a 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits new d6aabdc329 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits new b0568acd28 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits new 8f08a52315 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...] new 046ddf2d2e 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 commits new 9cdde774ff 345: onsuccess: #2079: 7: Success after binutils/gcc/linux/g [...] new 3b3a529bff 346: onsuccess: #2080: 7: Success after binutils/gdb: 142 commits new fd8cc1b98d 347: onsuccess: #2081: 7: Success after binutils/gcc/linux/g [...] new 8124b7a504 348: onsuccess: #2082: 7: Success after binutils/gcc/glibc/g [...] new 303db8b6e6 349: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] new 7e4d705dca 350: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits new 26f748a3da 351: onsuccess: #2085: 7: Success after binutils/gcc/gdb: 19 [...] new ff630a945b 352: onsuccess: #2086: 7: Success after binutils/gcc/gdb: 9 commits new f1abf998e2 353: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] new 54243365f9 354: onsuccess: #2088: 7: Success after binutils/gcc/gdb: 7 commits new 74c6aa5cf4 355: onsuccess: #2089: 7: Success after binutils/gcc/linux/g [...] new 8b2440d1d1 356: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] new 32741818ef 357: onsuccess: #2091: 7: Success after binutils/gcc/linux/g [...] new dbe14f44f2 358: onsuccess: #2092: 7: Success after binutils/gcc/gdb: 10 [...] new 72bf96c19c 359: onsuccess: #2093: 7: Success after binutils/gcc/linux/g [...] new 9b7bd7dd6d 360: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] new 3574b163a3 361: onsuccess: #2095: 7: Success after gcc/linux: 15 commits new 2f09ff0a54 362: onsuccess: #2096: 7: Success after binutils/gcc/linux/g [...] new 385be6ea70 363: onsuccess: #2097: 7: Success after binutils/gcc/gdb: 25 [...] new 3eaf4234c6 364: onsuccess: #2098: 7: Success after binutils/gdb: 4 commits new f9faf8bb3c 365: onsuccess: #2099: 7: Success after gcc/linux: 21 commits new 42e37a1834 366: onsuccess: #2100: 7: Success after binutils/gcc/glibc/g [...] new e8873a9155 367: onsuccess: #2101: 7: Success after binutils/gcc/linux/g [...] new 13616f5493 368: onsuccess: #2102: 7: Success after binutils/gcc/linux/g [...] new 43094dd592 369: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] new 4bd522892a 370: onsuccess: #2104: 7: Success after binutils/gcc/linux/g [...] new 7bddb1101d 371: onsuccess: #2105: 7: Success after binutils/gcc/gdb/qem [...] new e92eeecd02 372: onsuccess: #2106: 7: Success after binutils/gcc/linux/g [...] new 06e04cfa3d 373: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] new 929a1adaa9 374: onsuccess: #2109: 7: Success after binutils/gcc/linux/g [...] new 326ff5de15 375: onsuccess: #2110: 7: Success after binutils/gcc/linux/g [...] new 2636e499ef 376: onsuccess: #2111: 7: Success after binutils/gcc/linux/g [...] new 9a466df985 377: onsuccess: #2112: 7: Success after binutils/gcc/gdb: 16 [...] new a0f9e736bc 378: onsuccess: #2113: 7: Success after binutils/gcc/linux/g [...] new 20afdd838e 379: onsuccess: #2114: 7: Success after binutils/gcc/linux/g [...] new 9f78e6fae2 380: onsuccess: #2115: 7: Success after binutils/gcc/linux/g [...] new 3d87eabcda 381: onsuccess: #2116: 7: Success after binutils/gcc/linux/g [...] new 4be7f9f61e 382: onsuccess: #2117: 7: Success after binutils/gcc/linux/g [...] new 5e4758ab7e 383: onsuccess: #2118: 7: Success after binutils/gcc/glibc/g [...] new 273b7b02c5 384: onsuccess: #2119: 7: Success after binutils/gcc/linux/g [...] new 5fedc44428 385: onsuccess: #2120: 7: Success after binutils/gcc/gdb/qem [...] new 9d857a223c 386: onsuccess: #2121: 7: Success after binutils/gcc/glibc/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (8520220efa) \ 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 1776 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2768 bytes 04-build_abe-binutils/console.log.xz | Bin 31896 -> 31376 bytes 05-build_abe-stage1/console.log.xz | Bin 94024 -> 91792 bytes 07-build_abe-linux/console.log.xz | Bin 8652 -> 8636 bytes 08-build_abe-glibc/console.log.xz | Bin 237964 -> 236776 bytes 09-build_abe-stage2/console.log.xz | Bin 231456 -> 228564 bytes 10-build_abe-gdb/console.log.xz | Bin 39132 -> 38708 bytes 11-build_abe-qemu/console.log.xz | Bin 31648 -> 31892 bytes 12-check_regression/console.log.xz | Bin 4408 -> 4424 bytes 13-update_baseline/console.log | 68 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 44 +++++++++++------------ 21 files changed, 65 insertions(+), 65 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allyesconfig updated (e66f2c1af3 -> f3082ae8d1)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allyesconfig in repository toolchain/ci/base-artifacts. from e66f2c1af3 59: onsuccess: #547: all: Success after binutils/llvm/linux/ [...] new f3082ae8d1 60: onsuccess: #548: all: Success after binutils/llvm/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1796 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2812 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 31648 -> 31848 bytes 04-build_kernel_llvm/console.log.xz | Bin 65332 -> 65964 bytes 05-build_abe-qemu/console.log.xz | Bin 31660 -> 32524 bytes 06-build_linux/console.log.xz | Bin 3528 -> 3552 bytes 07-boot_linux/console.log.xz | Bin 576 -> 576 bytes 08-check_regression/console.log.xz | Bin 4384 -> 4468 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[gcc] branch master updated (f0065f207cf -> 27ac6a707e7)

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 f0065f207cf libstdc++: Mark pieces of gnu-linux/os_support.h linux-specific new 60fca1802a2 c++: Add fixed test [PR101071] new 27ac6a707e7 c++: wrong error with constexpr array and value-init [PR108158] The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/cp/constexpr.cc | 4 --- .../cpp0x/{variadic-alias2.C => variadic-alias8.C} | 14 ++-------- gcc/testsuite/g++.dg/cpp1y/constexpr-108158.C | 32 ++++++++++++++++++++++ 3 files changed, 35 insertions(+), 15 deletions(-) copy gcc/testsuite/g++.dg/cpp0x/{variadic-alias2.C => variadic-alias8.C} (81%) create mode 100644 gcc/testsuite/g++.dg/cpp1y/constexpr-108158.C -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (7648b6883f -> 27b9aa1ce0)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm in repository toolchain/ci/base-artifacts. discards 7648b6883f 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 4bae07c9d4 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 14135d3d53 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards d10151bd41 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 33f4b68ba1 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards b5818ba815 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards d6e6cdbd62 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 262ff63bb9 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 04d81fe487 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 3393a0f742 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 1707806d49 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 90248795f4 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 50f1426006 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards bd0ef2b4ee 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 8e74adad57 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 06b0cae56a 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 83b308a1c7 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 94ed397748 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards a52451e7dd 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards d08f5091b3 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards dbe1acc45c 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 20c4ab5062 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 85fe015faf 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 4b91a0c70e 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 03b6b875dc 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 2951687b18 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards f1da25b218 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 8c1e7d9046 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards c3ded8017e 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 762b8fb1ed 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 0d18ee9033 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards e39f8743ea 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 7871016b40 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards d30ed013f6 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 72c585a761 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 96aebc0841 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 6564558f9e 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards b2b4ee206f 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 0f0d699c1d 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 8bcaab3a6f 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 9e705a2135 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 12c8b29e2a 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards db7052e94a 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards ffc980e0fb 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards fddd424347 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 3ab007b090 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards f4dde31721 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 23c5afea07 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 2f60b3a87d 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 0d38e83c95 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards f205548f71 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards ce35131288 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 593c6da656 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards c4c4c71954 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 7b61852fee 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 8d02b991ac 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 012adafc8d 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards d2e2d897d0 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 5a99c02876 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 674a96bf67 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 4ddbf6764e 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards e1848c0351 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards feadc89cbd 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards ddc15f0567 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards c6625bec67 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 8658e59939 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 5872a01556 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 0c29bf4193 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 6514f62902 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards c71631652b 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 9d0c15b53c 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards dc37b52263 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 6ae9dad1bc 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 6e5d1e7e70 301: onsuccess: #2118: 1: Success after linux: 16 commits discards c3bbec5c43 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards adb48d06f2 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 479c90895f 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards a9671bc509 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards b51f7da26a 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards aedf19a57a 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 2b44788f98 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 3c08286279 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 3dab3144da 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 2cd3a87cee 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 5530c403c4 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 3d68b5a653 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards f9635cf324 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards ffa6286571 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards cf40d2fe17 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 701a56e8ac 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards ab074430e1 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 8ab2931bb6 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 06041aac5a 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards b91889af5f 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 5afebd2189 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards ffc19544b4 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 883c4bbb02 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 14518628a7 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 4912d77c82 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 988827bffb 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 1e16f4aa70 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new cbb8808726 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new add5856efe 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new addc644f89 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 71d1e4784c 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 047667aadc 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 09a39da940 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 5f60d9b4cc 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 8a589daea1 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 10f6716afe 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new e6c924a279 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new c49dfed4fd 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 99729e871f 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new e3b0292051 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 226bffc646 287: onsuccess: #2103: 1: Success after gcc: 9 commits new d916a7a80d 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new a9b67afeed 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 27bcc7ed08 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 130fafce7b 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 542705ab64 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new ba9582baf6 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new faa31e0434 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 38fcf18588 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 927a30fdb7 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 0e12e02ed1 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 322c31e4d4 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new b795fda38a 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new f0c07b92dd 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 851675e935 301: onsuccess: #2118: 1: Success after linux: 16 commits new 7475f386c5 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 3c428cca48 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new a84fc40a14 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 68e9e1139f 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 4aa26d632f 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new a195b24c55 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 5638c84bb4 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 5ffaf63ad0 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 934989e53e 310: onsuccess: #2129: 1: Success after binutils: 4 commits new bca09203f9 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 54a8239ed6 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 8da6743af9 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new f2e5d9e7c9 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 90e4967773 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 3f7c239b32 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 62790d3aad 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new bcb023cb54 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 8f969a4b2d 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new a0b1a11622 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 0b769093b6 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 82476d6327 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 5183326d8f 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new e55c107ba7 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 1c20e75198 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 6209b23083 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new cdf8a96dd1 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 5886c08b26 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 03e201a0cb 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new c0d1518d87 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new a8a695566c 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 2855af6bbc 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new a28214cc0b 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 4edfa97792 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 5e4634ebe9 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new f358e7f8dc 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 037e1b1d2f 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 19dff4c7fd 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 6ad315550e 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 6d86818c3f 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 3ba3d20ee5 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 71a535758b 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 9baa208bc7 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 0764cb23db 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new ce3f3c668a 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new d77f0d3b58 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 686e619c57 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new a8fbbd59cf 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 9711620ecd 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new b52313a056 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new a3dbf2ae20 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 787f2c1c2a 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new a0167786c3 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 4db6313191 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 82e007a8a0 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 3be662e298 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new a8d6febdf3 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new efaca7e9b8 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 87f1842418 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new bbc50f78e2 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 649314864d 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new a59cb3296b 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 56cc15e847 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 5fff3f6e13 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new c5b1eafc06 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 4554e619b0 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new bb3b0b085f 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new abfff5cdff 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 98dedec843 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new a06af9c92d 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new de293b75e6 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 100cab134e 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new e7f4ca86b4 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new f67a5785b1 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 27b9aa1ce0 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] 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 (7648b6883f) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1820 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31128 -> 30864 bytes 04-build_abe-stage1/console.log.xz | Bin 91784 -> 91456 bytes 06-build_abe-linux/console.log.xz | Bin 8616 -> 8624 bytes 07-build_abe-glibc/console.log.xz | Bin 237412 -> 236256 bytes 08-build_abe-stage2/console.log.xz | Bin 228436 -> 227556 bytes 09-build_abe-gdb/console.log.xz | Bin 38512 -> 38064 bytes 10-build_abe-qemu/console.log.xz | Bin 32108 -> 31868 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2680 -> 2892 bytes 13-check_regression/console.log.xz | Bin 7328 -> 6292 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 44 +- 13-check_regression/results.compare | 35 +- 13-check_regression/results.compare2 | 154 +-- 13-check_regression/results.regressions | 40 - 14-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 46 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 40 - sumfiles/g++.log.xz | Bin 2656784 -> 2652092 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 2222284 -> 2219936 bytes sumfiles/gcc.sum | 2192 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 897312 -> 888348 bytes sumfiles/gfortran.sum | 54 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214344 -> 214460 bytes sumfiles/libgomp.sum | 6 +- sumfiles/libitm.log.xz | Bin 2668 -> 2676 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 443996 -> 444076 bytes sumfiles/libstdc++.sum | 26 +- 43 files changed, 1230 insertions(+), 1554 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[linux] branch master updated (66a87fff1a87 -> 7b753a909f42)

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 linux. from 66a87fff1a87 Merge tag 'ata-6.2-rc7' of git://git.kernel.org/pub/scm/li [...] new bd86d2ea369b Sync with v6.2-rc4 new 49d6d7fb6313 mm/uffd: fix pte marker when fork() without fork event new 7e3ce3f8d2d2 mm: fix a few rare cases of using swapin error pte marker new 0ca2c535f5a0 selftests/vm: remove __USE_GNU in hugetlb-madvise.c new 24b5308cf5ee selftests/filesystems: grant executable permission to run_ [...] new 7327e8111adb maple_tree: fix mas_empty_area_rev() lower bound validation new 023f47a8250c mm/khugepaged: fix ->anon_vma race new 85b325815b56 zsmalloc: fix a race with deferred_handles storing new 55ab834a86a9 Revert "mm: add nodes= arg to memory.reclaim" new de08eaa61564 mm: multi-gen LRU: fix crash during cgroup migration new 6f28a2613497 ia64: fix build error due to switch case label appearing n [...] new 72e544b1b283 squashfs: harden sanity check in squashfs_read_xattr_id_table new d014cd7c1c35 mm, mremap: fix mremap() expanding for vma's with vm_ops->close() new 889a904fe34d .mailmap: update e-mail address for Eugen Hristev new ab6ef70a8b0d maple_tree: should get pivots boundary by type new 0d7866eace86 freevxfs: Kconfig: fix spelling new 8ef852f1cb42 Revert "mm: kmemleak: alloc gray object for reserved regio [...] new edb5d0cf5525 mm/MADV_COLLAPSE: catch !none !huge !bad pmd lookups new 3489dbb696d2 mm: hugetlb: proc: check for hugetlb shared PMD in /proc/P [...] new 73bdf65ea748 migrate: hugetlb: check for hugetlb shared PMD in node migration new 88d7b12068b9 highmem: round down the address passed to kunmap_flush_on_unmap() new c1c551bebf92 sh: define RUNTIME_DISCARD_EXIT new f65c4bbbd682 Squashfs: fix handling and sanity checking of xattr_ids count new 993f57e0277b mm: use stack_depot_early_init for kmemleak new 7717fc1a12f8 mm/swapfile: add cond_resched() in get_swap_pages() new 1e90e35b6205 Kconfig.debug: fix the help description in SCHED_DEBUG new ac86f547ca10 mm: memcg: fix NULL pointer in mem_cgroup_track_foreign_di [...] new 0c272a1d3396 Merge tag 'mm-hotfixes-stable-2023-02-02-19-24-2' of git:/ [...] new 51128c3f2a7c drm/vc4: hdmi: make CEC adapter name unique new 343c70048098 drm/ssd130x: Init display before the SSD130X_DISPLAY_ON command new d2ceea0eb6e1 dma-buf: actually set signaling bit for private stub fences new d22915d22ded drm/nouveau/devinit/tu102-: wait for GFW_BOOT_PROGRESS == [...] new b48060098818 drm/nouveau/fb/tu102-: fix register used to determine scru [...] new 90741096769b drm/nouveau/acr/gm20b: regression fixes new a3ee9e0b57f8 drm/panel: boe-tv101wum-nl6: Ensure DSI writes succeed dur [...] new abf301e14e42 Merge tag 'drm-misc-fixes-2023-02-02' of git://anongit.fre [...] new 41d419382ec7 drm/i915: Avoid potential vm use-after-free new 87b04e53daf8 drm/i915/guc: Fix locking when searching for a hung request new 86d8ddc74124 drm/i915: Fix request ref counting during error capture & [...] new 5bc4b43d5c6c drm/i915: Fix up locking around dumping requests lists new 7057a8f126f1 drm/i915: Fix potential bit_17 double-free new 47a2bd9d985b drm/i915/adlp: Fix typo for reference clock new 74d6c8ea183e Merge tag 'drm-intel-fixes-2023-02-02' of git://anongit.fr [...] new ed8e793c65e4 drm/amdgpu: update wave data type to 3 for gfx11 new ea062fd28f92 drm/amd/display: Add missing brackets in calculation new dd2db2dc4bd2 drm/amd/display: Adjust downscaling limits for dcn314 new 275d8a1db261 drm/amd/display: Unassign does_plane_fit_in_mall function [...] new 154711aa5759 drm/amd/display: Reset DMUB mailbox SW state after HW reset new 1538709c9f1c drm/amd/pm: drop unneeded dpm features disablement for SMU [...] new bb25849c0fa5 drm/amdgpu: enable HDP SD for gfx 11.0.3 new 5048fa1ebf89 drm/amd: Fix initialization for nbio 4.3.0 new ac7170082c0e drm/amdgpu: Enable vclk dclk node for gc11.0.3 new 6fc547a5a2ef drm/amd/display: Properly handle additional cases where DC [...] new f1a9e82a1203 Merge tag 'amd-drm-fixes-6.2-2023-02-01' of https://gitlab [...] new bffede38f82c Merge tag 'drm-fixes-2023-02-03' of git://anongit.freedesk [...] new 0b1d60d6dd9e riscv: Fix build with CONFIG_CC_OPTIMIZE_FOR_SIZE=y new 3c349eacc559 Merge patch "riscv: Fix build with CONFIG_CC_OPTIMIZE_FOR_SIZE=y" new 87f48c7ccc73 riscv: kprobe: Fixup kernel panic when probing an illegal [...] new 2f394c0e7d11 riscv: disable generation of unwind tables new a30df1ea94ad Merge tag 'riscv-for-linus-6.2-rc7' of git://git.kernel.or [...] new 636ab417a7ae efi: Accept version 2 of memory attributes table new 966d47e1f27c efi: fix potential NULL deref in efi_mem_reserve_persistent new a0880c33794b Merge tag 'efi-fixes-for-v6.2-3' of git://git.kernel.org/p [...] new b38b17b6a01c ceph: move mount state enum to super.h new a68e564adcaa ceph: blocklist the kclient when receiving corrupted snap trace new 7b753a909f42 Merge tag 'ceph-for-6.2-rc7' of https://github.com/ceph/ce [...] The 66 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: .mailmap | 1 + Documentation/admin-guide/cgroup-v2.rst | 15 +- arch/ia64/kernel/sys_ia64.c | 7 +- arch/riscv/Makefile | 3 + arch/riscv/include/asm/hwcap.h | 3 - arch/riscv/include/asm/vdso/processor.h | 28 ++- arch/riscv/kernel/probes/kprobes.c | 18 ++ arch/sh/kernel/vmlinux.lds.S | 1 + drivers/dma-buf/dma-fence.c | 2 +- drivers/firmware/efi/efi.c | 2 + drivers/firmware/efi/memattr.c | 2 +- drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c | 4 +- drivers/gpu/drm/amd/amdgpu/nbio_v4_3.c | 8 +- drivers/gpu/drm/amd/amdgpu/soc21.c | 3 +- drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 11 + .../drm/amd/display/dc/dcn314/dcn314_resource.c | 5 +- drivers/gpu/drm/amd/display/dc/dcn32/dcn32_init.c | 2 +- .../display/dc/dml/dcn314/display_mode_vba_314.c | 2 +- drivers/gpu/drm/amd/display/dmub/src/dmub_srv.c | 12 ++ drivers/gpu/drm/amd/pm/amdgpu_pm.c | 6 +- drivers/gpu/drm/amd/pm/swsmu/amdgpu_smu.c | 14 ++ drivers/gpu/drm/i915/display/intel_cdclk.c | 2 +- drivers/gpu/drm/i915/gem/i915_gem_context.c | 14 +- drivers/gpu/drm/i915/gem/i915_gem_tiling.c | 9 +- drivers/gpu/drm/i915/gt/intel_context.c | 4 +- drivers/gpu/drm/i915/gt/intel_context.h | 3 +- drivers/gpu/drm/i915/gt/intel_engine.h | 4 +- drivers/gpu/drm/i915/gt/intel_engine_cs.c | 74 ++++--- .../gpu/drm/i915/gt/intel_execlists_submission.c | 27 +++ .../gpu/drm/i915/gt/intel_execlists_submission.h | 4 + drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c | 14 +- drivers/gpu/drm/i915/i915_gpu_error.c | 33 +-- drivers/gpu/drm/nouveau/include/nvkm/subdev/fb.h | 1 + drivers/gpu/drm/nouveau/nvkm/core/firmware.c | 3 + drivers/gpu/drm/nouveau/nvkm/engine/device/base.c | 10 +- drivers/gpu/drm/nouveau/nvkm/falcon/gm200.c | 14 +- .../gpu/drm/nouveau/nvkm/subdev/devinit/tu102.c | 23 ++ drivers/gpu/drm/nouveau/nvkm/subdev/fb/Kbuild | 1 + drivers/gpu/drm/nouveau/nvkm/subdev/fb/ga102.c | 8 +- drivers/gpu/drm/nouveau/nvkm/subdev/fb/gv100.c | 5 - drivers/gpu/drm/nouveau/nvkm/subdev/fb/priv.h | 2 + .../nouveau/nvkm/subdev/fb/{gv100.c => tu102.c} | 15 +- drivers/gpu/drm/nouveau/nvkm/subdev/pmu/gm20b.c | 2 +- drivers/gpu/drm/panel/panel-boe-tv101wum-nl6.c | 16 +- drivers/gpu/drm/solomon/ssd130x.c | 18 +- drivers/gpu/drm/vc4/vc4_hdmi.c | 3 +- drivers/of/fdt.c | 6 +- fs/ceph/addr.c | 17 +- fs/ceph/caps.c | 16 +- fs/ceph/file.c | 3 + fs/ceph/mds_client.c | 30 ++- fs/ceph/snap.c | 36 +++- fs/ceph/super.h | 11 + fs/freevxfs/Kconfig | 2 +- fs/proc/task_mmu.c | 4 +- fs/squashfs/squashfs_fs.h | 2 +- fs/squashfs/squashfs_fs_sb.h | 2 +- fs/squashfs/xattr.h | 4 +- fs/squashfs/xattr_id.c | 4 +- include/linux/ceph/libceph.h | 10 - include/linux/highmem-internal.h | 4 +- include/linux/hugetlb.h | 13 ++ include/linux/memcontrol.h | 5 +- include/linux/swap.h | 3 +- lib/Kconfig.debug | 3 +- lib/maple_tree.c | 22 +- lib/test_maple_tree.c | 89 ++++++++ mm/hugetlb.c | 3 + mm/khugepaged.c | 22 +- mm/kmemleak.c | 5 +- mm/memcontrol.c | 67 ++---- mm/memory.c | 14 +- mm/mempolicy.c | 3 +- mm/mprotect.c | 8 +- mm/mremap.c | 25 ++- mm/swapfile.c | 1 + mm/vmscan.c | 9 +- mm/zsmalloc.c | 237 ++++++++++++++++++--- .../selftests/filesystems/fat/run_fat_tests.sh | 0 tools/testing/selftests/vm/hugetlb-madvise.c | 1 - 80 files changed, 817 insertions(+), 322 deletions(-) copy drivers/gpu/drm/nouveau/nvkm/subdev/fb/{gv100.c => tu102.c} (84%) mode change 100644 => 100755 tools/testing/selftests/filesystems/fat/run_fat_tests.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[gcc] branch releases/gcc-10 updated (1722e6e4803 -> f835376a1c6)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-10 in repository gcc. from 1722e6e4803 Daily bump. new f835376a1c6 varasm: Fix type confusion bug 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/varasm.c | 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, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-stable-allyesconfig updated (cdbe1a85fd -> d17c551588)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-stable-allyesconfig in repository toolchain/ci/base-artifacts. from cdbe1a85fd 50: onsuccess: #534: 21422: Success after llvm: 451 commits new d17c551588 51: onsuccess: #535: 21422: Success after binutils/llvm/linu [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1752 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 31164 -> 31420 bytes 04-build_kernel_llvm/console.log.xz | Bin 64288 -> 66820 bytes 05-build_abe-qemu/console.log.xz | Bin 31460 -> 32512 bytes 06-build_linux/console.log.xz | Bin 3744 -> 3744 bytes 08-check_regression/console.log.xz | Bin 2900 -> 4456 bytes 08-check_regression/mail-body.txt | 13 +------------ 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 15 ++------------- mail/mail-subject.txt | 2 +- manifest.sh | 31 +++++++++++++++++-------------- 18 files changed, 31 insertions(+), 50 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

Jump to page: