Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/release-arm updated (472de902b7e -> 71df3b5e7a4)

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/release-arm in repository toolchain/ci/base-artifacts. from 472de902b7e 19: onsuccess: #136: 7: Success after binutils/gcc/linux/gl [...] new 71df3b5e7a4 20: onsuccess: #141: 7: Success after binutils/gcc/linux/gl [...] 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 1684 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 30036 -> 30072 bytes 05-build_abe-stage1/console.log.xz | Bin 86828 -> 87596 bytes 07-build_abe-linux/console.log.xz | Bin 8700 -> 8684 bytes 08-build_abe-glibc/console.log.xz | Bin 229984 -> 230312 bytes 09-build_abe-stage2/console.log.xz | Bin 220712 -> 221596 bytes 10-build_abe-gdb/console.log.xz | Bin 36680 -> 36896 bytes 11-build_abe-qemu/console.log.xz | Bin 31236 -> 30636 bytes 12-check_regression/console.log.xz | Bin 4872 -> 5480 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_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 | 48 +++++++++++++++++------------------ 21 files changed, 34 insertions(+), 34 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-lts-allmodconfig updated (dacbb2d2d7b -> 8a48187315c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-lts-allmodconfig in repository toolchain/ci/base-artifacts. from dacbb2d2d7b 39: onsuccess: #453: boot: Success after qemu: 32 commits new 8a48187315c 40: onsuccess: #454: boot: Success after binutils/gcc/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 1680 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30392 -> 30508 bytes 04-build_abe-stage1/console.log.xz | Bin 68456 -> 69324 bytes 05-build_abe-qemu/console.log.xz | Bin 30780 -> 31376 bytes 06-build_linux/console.log.xz | Bin 3388 -> 3400 bytes 07-boot_linux/console.log.xz | Bin 508 -> 508 bytes 08-check_regression/console.log.xz | Bin 2964 -> 4420 bytes 09-update_baseline/console.log | 8 ++++---- 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 | 31 +++++++++++++++++-------------- 18 files changed, 29 insertions(+), 26 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-next-allnoconfig updated (07e4c50b4d6 -> 58c07a63e00)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-arm-next-allnoconfig in repository toolchain/ci/base-artifacts. from 07e4c50b4d6 24: onsuccess: #323: all: Success after binutils/llvm/linux [...] new 58c07a63e00 25: onsuccess: #325: 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 1688 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 30104 -> 30392 bytes 04-build_kernel_llvm/console.log.xz | Bin 64612 -> 64340 bytes 05-build_abe-qemu/console.log.xz | Bin 30812 -> 31472 bytes 06-build_linux/console.log.xz | Bin 3112 -> 3104 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 3888 -> 4352 bytes 08-check_regression/mail-body.txt | 2 +- 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 | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 19 files changed, 27 insertions(+), 27 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm updated (d796e670843 -> d493aca65aa)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm in repository toolchain/ci/base-artifacts. discards d796e670843 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards 779c9f7bda9 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] discards eedf705bbe8 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards 8496a7a543f 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards 75eb377be33 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] discards 74e7c2023d6 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] discards 10982dcf830 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] discards 5f848206be6 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] discards b3412c14d89 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] discards 41d39d0ccb2 109: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] discards c5b95688231 108: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] discards 63c439eba06 107: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] discards 51b0982133d 106: onsuccess: #532: 1: Success after binutils/gcc/linux/g [...] discards 578b94980a2 105: onsuccess: #531: 1: Success after binutils/gcc/linux/g [...] discards a128a49c20b 104: onsuccess: #530: 1: Success after gcc: 7 commits discards 403676d811c 103: onsuccess: #529: 1: Success after binutils/gcc/linux/g [...] discards 2451ec39109 102: onsuccess: #527: 1: Success after binutils: 5 commits discards 86323fe42c8 101: onsuccess: #524: 1: Success after binutils: 2 commits discards d0e590b3e25 100: onsuccess: #521: 1: Success after binutils: 10 commits discards defd608cabd 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] discards fe6a6b7cfe9 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gl [...] discards ef0fbe4f043 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] discards 1d828a4175e 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] discards d40754abdf8 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gd [...] discards 7c5911da1c6 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gd [...] discards bad70ebc89f 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] discards dcf08098d96 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gl [...] discards a8b52dec3e6 91: onsuccess: #511: 1: Success after linux: 27 commits discards b847489a7c9 90: onsuccess: #510: 1: Success after glibc: 5 commits discards 863cb7666d5 89: onsuccess: #508: 1: Success after binutils: 12 commits discards e3b83709c29 88: onsuccess: #506: 1: Success after linux: 34 commits discards b3be59dfe4c 87: onsuccess: #505: 1: Success after glibc: 7 commits discards 5669822829a 86: onsuccess: #503: 1: Success after binutils: 12 commits discards 6e88fc8c94f 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] discards 9da39a67fa9 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] discards dbe74d4515b 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gd [...] discards 9c620af90cc 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gl [...] discards 9343de665c2 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] discards dffa995adbb 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] discards af5bc497ac1 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] discards da4f831b0b8 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] discards 02768e35950 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gd [...] discards 0e5a5513488 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gd [...] discards e045b3bee91 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gd [...] discards 88f30002af3 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gl [...] discards c27de402e76 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gd [...] discards c71bf02a62e 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gl [...] discards 508f4ec39b0 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gd [...] discards 209ad7120b2 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gl [...] discards 30a8eb94eeb 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] discards 4a3a8d1e1bb 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gl [...] discards 4511e800d39 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] discards 3ae0f81856c 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gl [...] discards 85f933acb83 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gd [...] discards 6a50d5bf8c3 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] discards fa3efd808fd 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gl [...] discards aeed450ebba 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gl [...] discards 5735f54b16a 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gl [...] discards e2be4f9a591 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gl [...] discards 152abaf9f04 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gl [...] discards ce7ffff2d96 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gl [...] discards cea112d45a4 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gl [...] discards 649fca77049 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gd [...] discards 2aed125667b 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gl [...] discards 3e7ed4a559d 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gl [...] discards 4f3428de8d9 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gl [...] discards 322b3ad0c63 52: onsuccess: #467: 1: Success after binutils: 9 commits discards 664cc1ffd36 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 652bc064172 50: onsuccess: #461: 1: Success after binutils: 12 commits discards bf92c4863b3 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gd [...] discards de9f9d901ae 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gd [...] discards e8723c0742c 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gl [...] discards 8b1906b1b67 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gl [...] discards 6e1d1aae81a 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gl [...] discards c6d2a4f045e 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gd [...] discards 8dcffcd57e5 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gd [...] discards 9cce93a9283 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gd [...] discards ac5b24b16b3 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gl [...] discards af0deb4233d 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g [...] discards dc12b7435e3 39: onsuccess: #447: 1: Success after binutils: 5 commits discards bb13060613a 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g [...] discards 7faf226d81a 37: onsuccess: #443: 1: Success after binutils: 2 commits discards 29bb08814f6 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gl [...] discards c5f98139ce5 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gl [...] discards b8bf53e91f8 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gl [...] discards 34bcdeb4968 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gd [...] discards eb35381dda6 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gl [...] discards 81652217099 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gl [...] discards 40ef033bc78 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gd [...] discards a360c0a1129 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gl [...] discards 131f866bc94 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gl [...] discards 43098d46bd3 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gd [...] discards 8be99c683b2 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gd [...] discards 44c9ea0f727 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gd [...] discards 973d3e9dd3a 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 [...] discards 905a1bada62 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 653d332bba8 22: onsuccess: 1: Successful build after binutils/gcc/glibc [...] discards 8eaa767d67d 21: onsuccess: 1: Successful build after linux: 79 commits discards da854989228 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards f9d48de9ce0 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards a82f9fe82ad 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 91aebb392c7 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new b79e9f32644 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 969050d4121 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new f408f418941 21: onsuccess: 1: Successful build after linux: 79 commits new d2b315be19d 22: onsuccess: 1: Successful build after binutils/gcc/glibc [...] new 477eff0b320 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 92cc1ddf7f5 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 [...] new 60f3f54ac99 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gd [...] new b07cfe7d64d 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gd [...] new 81976971023 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gd [...] new 2739481fbd6 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gl [...] new 7d33d866b15 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gl [...] new 3b0fd2dfbaf 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gd [...] new 7a462615f09 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gl [...] new 1249695f54a 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gl [...] new 5fe30c15b6c 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gd [...] new fc0c3df2db4 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gl [...] new 8002ff8c38b 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gl [...] new 2f6eae6d677 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gl [...] new ac9640c6db8 37: onsuccess: #443: 1: Success after binutils: 2 commits new f854e85167e 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g [...] new ebb7ab3a3b1 39: onsuccess: #447: 1: Success after binutils: 5 commits new cb288ca97f3 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g [...] new d580a295879 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gl [...] new cd07330a074 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gd [...] new 943fd096ed8 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gd [...] new 919b6bc769c 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gd [...] new 8a936a61f02 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gl [...] new 70f0a32ae33 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gl [...] new 87b06dde3cc 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gl [...] new 0d9c84f68fe 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gd [...] new a698d4e678d 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gd [...] new f4c2abd7f9b 50: onsuccess: #461: 1: Success after binutils: 12 commits new c10e2da9aa8 51: onsuccess: #464: 1: Success after binutils: 6 commits new 0fbd3669cc7 52: onsuccess: #467: 1: Success after binutils: 9 commits new ebc196800e6 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gl [...] new 86bf2564ba6 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gl [...] new b0cd8db3860 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gl [...] new 41028810e24 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gd [...] new 94afef92203 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gl [...] new cfa8f3fb8f5 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gl [...] new 71269e587de 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gl [...] new 19dedf44ac9 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gl [...] new e2ba8412e5e 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gl [...] new 7c785dfe5de 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gl [...] new aad0dffc166 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gl [...] new 69962c6ee56 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] new 07b3addae3b 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gd [...] new 66669947043 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gl [...] new c92eb0ac9dc 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] new d3e9cc632c5 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gl [...] new ebdc17bec7d 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] new c32b4e8d74e 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gl [...] new 7d91b5d637e 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gd [...] new 153f3cd8a6b 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gl [...] new 7af3a0d057b 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gd [...] new 21a7d590ba9 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gl [...] new bb57868e10b 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gd [...] new e675337baf6 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gd [...] new 63976112e7c 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gd [...] new 9df172d1f1e 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] new b7a4fa4561d 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] new 0d57fb754e1 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] new 06d8cc9c737 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] new 1323ed95292 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gl [...] new 2238be33046 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gd [...] new 2a591f6cf33 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] new ee433de4a85 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new 905df51ed48 86: onsuccess: #503: 1: Success after binutils: 12 commits new b3ec1507bcc 87: onsuccess: #505: 1: Success after glibc: 7 commits new b590faac49a 88: onsuccess: #506: 1: Success after linux: 34 commits new aaee8fb37c0 89: onsuccess: #508: 1: Success after binutils: 12 commits new 1739a00a4d6 90: onsuccess: #510: 1: Success after glibc: 5 commits new 0be5c2d540e 91: onsuccess: #511: 1: Success after linux: 27 commits new 80ebd4f2ebd 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gl [...] new 84a99b57220 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] new a8fb672ccdd 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gd [...] new 1b3ec560674 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gd [...] new 6e77959dc7b 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] new 98e125d26d6 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] new 9548523c08a 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gl [...] new 21ff8303a07 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] new 828bd1e116f 100: onsuccess: #521: 1: Success after binutils: 10 commits new dea1352bece 101: onsuccess: #524: 1: Success after binutils: 2 commits new cf33c1b96fa 102: onsuccess: #527: 1: Success after binutils: 5 commits new 4e69425cf7a 103: onsuccess: #529: 1: Success after binutils/gcc/linux/g [...] new 111e4beb1b6 104: onsuccess: #530: 1: Success after gcc: 7 commits new 242696ab04f 105: onsuccess: #531: 1: Success after binutils/gcc/linux/g [...] new 81a18be62e6 106: onsuccess: #532: 1: Success after binutils/gcc/linux/g [...] new fe6242b6601 107: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] new db63c44eadb 108: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] new 612edd83be8 109: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] new fbb1b87a0f7 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] new 8656425150c 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] new 9d962d3cf52 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new 345dec5d39d 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new f360c2aed1f 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new a1f5370e4dc 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new cb16daed642 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new 442a401acc0 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new 1941c7a06af 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new d493aca65aa 119: onsuccess: #546: 1: 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 (d796e670843) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1684 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2712 -> 2704 bytes 03-build_abe-binutils/console.log.xz | Bin 52304 -> 52252 bytes 04-build_abe-gcc/console.log.xz | Bin 234028 -> 234660 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8600 -> 8696 bytes 07-build_abe-glibc/console.log.xz | Bin 236604 -> 236940 bytes 08-build_abe-gdb/console.log.xz | Bin 50948 -> 51448 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3812 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2360 -> 2276 bytes 11-check_regression/console.log.xz | Bin 5600 -> 6020 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 20 +- 12-update_baseline/console.log | 38 ++-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +-- sumfiles/binutils.log.xz | Bin 62568 -> 62888 bytes sumfiles/binutils.sum | 65 +++--- sumfiles/gas.log.xz | Bin 98032 -> 98016 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 131532 -> 131560 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 29 files changed, 404 insertions(+), 395 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[binutils-gdb] branch master updated (05909f2341a -> ac57bf55472)

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 05909f2341a x86: drop most OPERAND_TYPE_* (and rework the rest) new ac57bf55472 Add Jan Beulich as an x86_64 maintainer. 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: binutils/MAINTAINERS | 1 + 1 file changed, 1 insertion(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[gcc] branch master updated (f1330551855 -> b3237a2c684)

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 f1330551855 c++: Incremental fix for g++.dg/gomp/for-21.C [PR84469] new b3237a2c684 i386: Save/restore recog_data in ix86_vector_duplicate_valu [...] 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/i386/i386-expand.cc | 5 +++++ gcc/testsuite/gcc.target/i386/pr106577.c | 10 ++++++++++ 2 files changed, 15 insertions(+) create mode 100644 gcc/testsuite/gcc.target/i386/pr106577.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-lts-allmodconfig updated (126ac55bddc -> 990907147a4)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-lts-allmodconfig in repository toolchain/ci/base-artifacts. from 126ac55bddc 41: onsuccess: #510: 21892: Success after binutils/llvm/qem [...] new 990907147a4 42: onsuccess: #511: 21892: Success after binutils/llvm/lin [...] 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 1712 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 31252 -> 31668 bytes 04-build_kernel_llvm/console.log.xz | Bin 63640 -> 65844 bytes 05-build_abe-qemu/console.log.xz | Bin 30540 -> 30656 bytes 06-build_linux/console.log.xz | Bin 4996 -> 5020 bytes 08-check_regression/console.log.xz | Bin 4028 -> 4404 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 ++++++++++++++++---------------- 16 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap updated (dcbd44bebfc -> a7c127d0eae)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap in repository toolchain/ci/base-artifacts. discards dcbd44bebfc 374: onsuccess: #1797: 2: Success after binutils/gcc: 6 commits discards 9cb77c2da8c 373: onsuccess: #1796: 2: Success after binutils/gcc: 19 commits discards 33ce91b2ed5 372: onsuccess: #1795: 2: Success after binutils/gcc: 16 commits discards dfadaac7c16 371: onsuccess: #1794: 2: Success after binutils/gcc: 6 commits discards a32d686f9f5 370: onsuccess: #1793: 2: Success after binutils/gcc: 16 commits discards 41f6d2551f5 369: onsuccess: #1792: 2: Success after binutils/gcc: 12 commits discards 149161b6fd5 368: onsuccess: #1791: 2: Success after binutils/gcc: 13 commits discards 7548733bd68 367: onsuccess: #1790: 2: Success after binutils/gcc: 9 commits discards b903ebc81d0 366: onsuccess: #1789: 2: Success after binutils/gcc: 8 commits discards 316f5e8d9fc 365: onsuccess: #1788: 2: Success after binutils/gcc: 7 commits discards 44b8a68bf7d 364: onsuccess: #1787: 2: Success after gcc: 6 commits discards 354238f224f 363: onsuccess: #1786: 2: Success after binutils/gcc: 3 commits discards 32aab67d014 362: onsuccess: #1785: 2: Success after binutils/gcc: 19 commits discards f48b6d53629 361: onsuccess: #1784: 2: Success after binutils/gcc: 31 commits discards 22d32eb04d2 360: onsuccess: #1783: 1: Success after binutils/gcc: 62 commits discards 052da3494bb 359: onsuccess: #1782: 1: Success after basepoints/gcc-13-4 [...] discards 0ca3e588548 358: onsuccess: #1781: 1: Success after binutils/gcc: 8 commits discards ae43c46dc0f 357: onsuccess: #1780: 1: Success after binutils: 3 commits discards 6da4c30167f 356: onsuccess: #1779: 1: Success after gdb-12-branchpoint- [...] discards dc3c487cd51 355: onsuccess: #1778: 1: Success after binutils/gcc: 2 commits discards 2d009abe08c 354: onsuccess: #1777: 1: Success after basepoints/gcc-13-4 [...] discards 67ad119eca1 353: onsuccess: #1776: 1: Success after binutils: 4 commits discards b50a99d21a5 352: onsuccess: #1775: 1: Success after binutils/gcc: 124 commits discards 7a618ab5834 351: onsuccess: #1774: 1: Success after gcc: 8 commits discards 97bc08ede2f 350: force: #1773: 1: Failure after basepoints/gcc-13-4227- [...] discards 7d950d2f299 349: onsuccess: #1764: 2: Success after binutils: 3 commits discards 0dc4d7c7214 348: onsuccess: #1762: 2: Success after binutils/gcc: 4 commits discards 84c152c99c0 347: onsuccess: #1761: 2: Success after binutils/gcc: 13 commits discards bbd4c8827fc 346: onsuccess: #1760: 2: Success after binutils/gcc: 14 commits discards d7eabb9f4bc 345: onsuccess: #1759: 2: Success after binutils/gcc: 23 commits discards 2467619da9c 344: onsuccess: #1758: 2: Success after gcc: 3 commits discards 9bc0e3b5dfc 343: onsuccess: #1757: 2: Success after binutils/gcc: 5 commits discards 7b144678099 342: onsuccess: #1756: 2: Success after gcc: 4 commits discards dcf7d789774 341: onsuccess: #1755: 2: Success after binutils/gcc: 3 commits discards 88eed6486b4 340: onsuccess: #1754: 2: Success after binutils/gcc: 3 commits discards b78f11ef739 339: onsuccess: #1753: 2: Success after binutils/gcc: 7 commits discards df473e8b3f5 338: onsuccess: #1752: 2: Success after binutils/gcc: 5 commits discards 66f222f873a 337: onsuccess: #1751: 2: Success after binutils/gcc: 2 commits discards 877a1941f64 336: onsuccess: #1750: 2: Success after binutils/gcc: 5 commits discards 32db0437837 335: onsuccess: #1749: 2: Success after binutils/gcc: 22 commits discards bd2c9b1f560 334: onsuccess: #1748: 2: Success after binutils/gcc: 9 commits discards f1391a51e37 333: onsuccess: #1747: 2: Success after binutils/gcc: 4 commits discards f789870c80b 332: onsuccess: #1746: 2: Success after binutils/gcc: 6 commits discards 3b79c9f81d6 331: onsuccess: #1745: 2: Success after binutils/gcc: 14 commits discards 308ff1f5b38 330: onsuccess: #1744: 2: Success after binutils/gcc: 11 commits discards fc435df3e2c 329: onsuccess: #1743: 2: Success after binutils/gcc: 7 commits discards b1b50d2e1b0 328: onsuccess: #1742: 2: Success after binutils/gcc: 14 commits discards cb37b744e84 327: onsuccess: #1741: 2: Success after binutils/gcc: 12 commits discards 50f62b81847 326: onsuccess: #1740: 2: Success after binutils/gcc: 19 commits discards a573db98afc 325: onsuccess: #1739: 2: Success after gcc: 4 commits discards 1e753564dfe 324: onsuccess: #1738: 2: Success after binutils/gcc: 18 commits discards ef8db5caa6d 323: onsuccess: #1737: 2: Success after binutils/gcc: 84 commits discards cb9e3a181de 322: onsuccess: #1736: 2: Success after binutils/gcc: 22 commits discards 7eb92b87dd4 321: onsuccess: #1735: 1: Success after binutils/gcc: 54 commits discards 98cc4f7d253 320: onsuccess: #1734: 1: Success after binutils/gcc: 4 commits discards 29ed67f6e19 319: onsuccess: #1733: 1: Success after binutils/gcc: 8 commits discards de6b3bac288 318: onsuccess: #1732: 1: Success after binutils/gcc: 2 commits discards 03a779dd77e 317: onsuccess: #1731: 1: Success after binutils/gcc: 8 commits discards 43bbc7a54b5 316: onsuccess: #1730: 1: Success after binutils/gcc: 16 commits discards 37c50d86325 315: onsuccess: #1729: 1: Success after baseline build: no [...] discards 769f1deffb4 314: force: #1728: 1: Failure after basepoints/gcc-13-3918- [...] discards cd167b5c5b6 313: force: #1727: 2: Success after gcc: 6 commits discards ba9594309c6 312: onsuccess: #1724: 2: Success after gdb-12-branchpoint- [...] discards 6f031293ffb 311: onsuccess: #1722: 2: Success after binutils/gcc: 8 commits discards e1ffa2ef7f8 310: onsuccess: #1721: 2: Success after binutils/gcc: 27 commits discards 5e5b40647e7 309: onsuccess: #1720: 2: Success after binutils/gcc: 14 commits discards 5f9cf1a3e69 308: onsuccess: #1719: 2: Success after binutils/gcc: 5 commits discards f9e8678e994 307: onsuccess: #1718: 2: Success after binutils/gcc: 22 commits discards 7e1a928ae91 306: onsuccess: #1717: 2: Success after binutils/gcc: 12 commits discards bbc13afcc03 305: onsuccess: #1716: 2: Success after binutils/gcc: 10 commits discards e31067ab7e0 304: onsuccess: #1715: 2: Success after binutils/gcc: 8 commits discards c05cd04cb23 303: onsuccess: #1714: 2: Success after binutils/gcc: 17 commits discards 3413d6468f5 302: onsuccess: #1713: 2: Success after binutils/gcc: 35 commits discards e1010c9c895 301: onsuccess: #1711: 2: Success after gdb-12-branchpoint- [...] discards a5c9b389ad7 300: onsuccess: #1709: 2: Success after binutils/gcc: 9 commits discards d81c950ee5f 299: onsuccess: #1708: 2: Success after binutils/gcc: 16 commits discards 3a00618a7eb 298: onsuccess: #1707: 2: Success after gcc: 32 commits discards 53f6bdd9f9f 297: onsuccess: #1706: 2: Success after binutils/gcc: 9 commits discards b81633b45a0 296: onsuccess: #1705: 2: Success after binutils/gcc: 9 commits discards 593b548c92f 295: onsuccess: #1704: 2: Success after binutils/gcc: 17 commits discards 6f35f823f4b 294: onsuccess: #1703: 2: Success after binutils/gcc: 12 commits discards d47c0630eaf 293: onsuccess: #1702: 2: Success after binutils/gcc: 37 commits discards aaa95cb1cfa 292: onsuccess: #1701: 2: Success after binutils/gcc: 3 commits discards 6455afaae32 291: onsuccess: #1700: 2: Success after gcc: 4 commits discards 6ab908e68c4 290: onsuccess: #1699: 2: Success after binutils/gcc: 5 commits discards 25f556f2c80 289: onsuccess: #1698: 2: Success after basepoints/gcc-13-3 [...] discards 7ee30c74813 288: onsuccess: #1697: 2: Success after binutils/gcc: 4 commits discards 7154b805214 287: onsuccess: #1696: 2: Success after gcc: 3 commits discards 4126ae60e34 286: onsuccess: #1695: 2: Success after binutils/gcc: 10 commits discards e3155fbc664 285: onsuccess: #1694: 2: Success after binutils: 7 commits discards 113c4f196f7 284: onsuccess: #1693: 2: Success after binutils: 2 commits discards 6fc766de6e2 283: onsuccess: #1692: 2: Success after binutils/gcc: 8 commits discards 5f7f9c92d1d 282: onsuccess: #1691: 2: Success after binutils/gcc: 44 commits discards ac30292b6c3 281: onsuccess: #1690: 2: Success after binutils/gcc: 8 commits discards 9b61ecbaaab 280: onsuccess: #1689: 2: Success after binutils/gcc: 11 commits discards c28029926bd 279: onsuccess: #1688: 2: Success after binutils/gcc: 23 commits discards 1a585cfc6af 278: onsuccess: #1687: 2: Success after binutils/gcc: 12 commits discards 3322292edcd 277: onsuccess: #1686: 2: Success after binutils/gcc: 5 commits discards a51539474b7 276: onsuccess: #1685: 2: Success after binutils/gcc: 3 commits discards a450f11190f 275: onsuccess: #1684: 2: Success after binutils/gcc: 11 commits discards 1df2369cb98 274: onsuccess: #1683: 2: Success after binutils/gcc: 10 commits new 41d0bf986a4 274: onsuccess: #1683: 2: Success after binutils/gcc: 10 commits new b3e0e7f4153 275: onsuccess: #1684: 2: Success after binutils/gcc: 11 commits new d500a867f94 276: onsuccess: #1685: 2: Success after binutils/gcc: 3 commits new cf6bda60b22 277: onsuccess: #1686: 2: Success after binutils/gcc: 5 commits new 10841e0e721 278: onsuccess: #1687: 2: Success after binutils/gcc: 12 commits new 9a42628122e 279: onsuccess: #1688: 2: Success after binutils/gcc: 23 commits new 66a22eabf25 280: onsuccess: #1689: 2: Success after binutils/gcc: 11 commits new d713f001515 281: onsuccess: #1690: 2: Success after binutils/gcc: 8 commits new cfe12c24813 282: onsuccess: #1691: 2: Success after binutils/gcc: 44 commits new f58a366d82a 283: onsuccess: #1692: 2: Success after binutils/gcc: 8 commits new 3b7ca087c16 284: onsuccess: #1693: 2: Success after binutils: 2 commits new b1bed016b96 285: onsuccess: #1694: 2: Success after binutils: 7 commits new cf5733187ce 286: onsuccess: #1695: 2: Success after binutils/gcc: 10 commits new 680027a9468 287: onsuccess: #1696: 2: Success after gcc: 3 commits new 7c0eac38f5a 288: onsuccess: #1697: 2: Success after binutils/gcc: 4 commits new 8cb95553168 289: onsuccess: #1698: 2: Success after basepoints/gcc-13-3 [...] new f8b19bb5fd5 290: onsuccess: #1699: 2: Success after binutils/gcc: 5 commits new 19b15105d50 291: onsuccess: #1700: 2: Success after gcc: 4 commits new 121f6550a1c 292: onsuccess: #1701: 2: Success after binutils/gcc: 3 commits new 4585ff721d1 293: onsuccess: #1702: 2: Success after binutils/gcc: 37 commits new 076b4f89cf8 294: onsuccess: #1703: 2: Success after binutils/gcc: 12 commits new c69170e5018 295: onsuccess: #1704: 2: Success after binutils/gcc: 17 commits new c67e02d3977 296: onsuccess: #1705: 2: Success after binutils/gcc: 9 commits new bc1838f30fe 297: onsuccess: #1706: 2: Success after binutils/gcc: 9 commits new 758608b1004 298: onsuccess: #1707: 2: Success after gcc: 32 commits new e27491585bc 299: onsuccess: #1708: 2: Success after binutils/gcc: 16 commits new 3ea35f3f0a2 300: onsuccess: #1709: 2: Success after binutils/gcc: 9 commits new 864c37d9e37 301: onsuccess: #1711: 2: Success after gdb-12-branchpoint- [...] new 1a1383acd15 302: onsuccess: #1713: 2: Success after binutils/gcc: 35 commits new 56e5a6977bc 303: onsuccess: #1714: 2: Success after binutils/gcc: 17 commits new 9a434d22e33 304: onsuccess: #1715: 2: Success after binutils/gcc: 8 commits new 6a4a891f4d5 305: onsuccess: #1716: 2: Success after binutils/gcc: 10 commits new 4042b6c1007 306: onsuccess: #1717: 2: Success after binutils/gcc: 12 commits new 1693b44d5ce 307: onsuccess: #1718: 2: Success after binutils/gcc: 22 commits new 7fe0f69e44f 308: onsuccess: #1719: 2: Success after binutils/gcc: 5 commits new ff7531b7824 309: onsuccess: #1720: 2: Success after binutils/gcc: 14 commits new 5bb7b789d16 310: onsuccess: #1721: 2: Success after binutils/gcc: 27 commits new df4504fdefc 311: onsuccess: #1722: 2: Success after binutils/gcc: 8 commits new 73ef050aca4 312: onsuccess: #1724: 2: Success after gdb-12-branchpoint- [...] new a3d234fc09e 313: force: #1727: 2: Success after gcc: 6 commits new efc903ed563 314: force: #1728: 1: Failure after basepoints/gcc-13-3918- [...] new cede9c1198d 315: onsuccess: #1729: 1: Success after baseline build: no [...] new 74967670ff6 316: onsuccess: #1730: 1: Success after binutils/gcc: 16 commits new 5f97ba1baeb 317: onsuccess: #1731: 1: Success after binutils/gcc: 8 commits new 14a25daefa3 318: onsuccess: #1732: 1: Success after binutils/gcc: 2 commits new 61300ff5a81 319: onsuccess: #1733: 1: Success after binutils/gcc: 8 commits new c964c97d811 320: onsuccess: #1734: 1: Success after binutils/gcc: 4 commits new 51164ae0843 321: onsuccess: #1735: 1: Success after binutils/gcc: 54 commits new a170bd7b401 322: onsuccess: #1736: 2: Success after binutils/gcc: 22 commits new cd05271ba48 323: onsuccess: #1737: 2: Success after binutils/gcc: 84 commits new 43cfaa85e58 324: onsuccess: #1738: 2: Success after binutils/gcc: 18 commits new 2f943a5867e 325: onsuccess: #1739: 2: Success after gcc: 4 commits new 4a528a19c81 326: onsuccess: #1740: 2: Success after binutils/gcc: 19 commits new 59db7857522 327: onsuccess: #1741: 2: Success after binutils/gcc: 12 commits new 26ac3f437de 328: onsuccess: #1742: 2: Success after binutils/gcc: 14 commits new 6e2e71d0a11 329: onsuccess: #1743: 2: Success after binutils/gcc: 7 commits new d1ccc12db4f 330: onsuccess: #1744: 2: Success after binutils/gcc: 11 commits new a8094f9ed9a 331: onsuccess: #1745: 2: Success after binutils/gcc: 14 commits new 2f665af9a31 332: onsuccess: #1746: 2: Success after binutils/gcc: 6 commits new 7d45bd89ae4 333: onsuccess: #1747: 2: Success after binutils/gcc: 4 commits new 65c7905d91b 334: onsuccess: #1748: 2: Success after binutils/gcc: 9 commits new b3bbe2e6b36 335: onsuccess: #1749: 2: Success after binutils/gcc: 22 commits new 8d2bf17a787 336: onsuccess: #1750: 2: Success after binutils/gcc: 5 commits new bbb3fb3518d 337: onsuccess: #1751: 2: Success after binutils/gcc: 2 commits new 7a56c451817 338: onsuccess: #1752: 2: Success after binutils/gcc: 5 commits new af9e48e4507 339: onsuccess: #1753: 2: Success after binutils/gcc: 7 commits new 4f6961c9c58 340: onsuccess: #1754: 2: Success after binutils/gcc: 3 commits new 12ef2cc283e 341: onsuccess: #1755: 2: Success after binutils/gcc: 3 commits new 53b118bdddc 342: onsuccess: #1756: 2: Success after gcc: 4 commits new 75f9ea799f9 343: onsuccess: #1757: 2: Success after binutils/gcc: 5 commits new 85b37584a6a 344: onsuccess: #1758: 2: Success after gcc: 3 commits new f4185483b25 345: onsuccess: #1759: 2: Success after binutils/gcc: 23 commits new 61b7853009b 346: onsuccess: #1760: 2: Success after binutils/gcc: 14 commits new c36ee3ee600 347: onsuccess: #1761: 2: Success after binutils/gcc: 13 commits new 900f26050b2 348: onsuccess: #1762: 2: Success after binutils/gcc: 4 commits new 70f40d2b7b2 349: onsuccess: #1764: 2: Success after binutils: 3 commits new fb669e893f7 350: force: #1773: 1: Failure after basepoints/gcc-13-4227- [...] new a6634abcabf 351: onsuccess: #1774: 1: Success after gcc: 8 commits new 6eb4e722070 352: onsuccess: #1775: 1: Success after binutils/gcc: 124 commits new 4fb80d1d514 353: onsuccess: #1776: 1: Success after binutils: 4 commits new 5eebe6633c6 354: onsuccess: #1777: 1: Success after basepoints/gcc-13-4 [...] new 08d8ee5dcd1 355: onsuccess: #1778: 1: Success after binutils/gcc: 2 commits new 895e3db7e68 356: onsuccess: #1779: 1: Success after gdb-12-branchpoint- [...] new d8194df110c 357: onsuccess: #1780: 1: Success after binutils: 3 commits new 178949d98b8 358: onsuccess: #1781: 1: Success after binutils/gcc: 8 commits new 63eae620db6 359: onsuccess: #1782: 1: Success after basepoints/gcc-13-4 [...] new 6b067b787e0 360: onsuccess: #1783: 1: Success after binutils/gcc: 62 commits new beb91d48feb 361: onsuccess: #1784: 2: Success after binutils/gcc: 31 commits new fcc2aabefbc 362: onsuccess: #1785: 2: Success after binutils/gcc: 19 commits new 2ed7c07bddb 363: onsuccess: #1786: 2: Success after binutils/gcc: 3 commits new 8e9a82a9341 364: onsuccess: #1787: 2: Success after gcc: 6 commits new 302df95a60a 365: onsuccess: #1788: 2: Success after binutils/gcc: 7 commits new 8d96cf9c854 366: onsuccess: #1789: 2: Success after binutils/gcc: 8 commits new 86b31f11fd4 367: onsuccess: #1790: 2: Success after binutils/gcc: 9 commits new 5057a5e911c 368: onsuccess: #1791: 2: Success after binutils/gcc: 13 commits new b066760d236 369: onsuccess: #1792: 2: Success after binutils/gcc: 12 commits new 7dba9711baa 370: onsuccess: #1793: 2: Success after binutils/gcc: 16 commits new a8274a4b132 371: onsuccess: #1794: 2: Success after binutils/gcc: 6 commits new 9ecbdb03677 372: onsuccess: #1795: 2: Success after binutils/gcc: 16 commits new a3b6df1921d 373: onsuccess: #1796: 2: Success after binutils/gcc: 19 commits new 0e73e006b0b 374: onsuccess: #1797: 2: Success after binutils/gcc: 6 commits new a7c127d0eae 375: onsuccess: #1798: 2: Success after binutils/gcc: 7 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 (dcbd44bebfc) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] 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 1668 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2716 bytes 04-build_abe-binutils/console.log.xz | Bin 52980 -> 52944 bytes 05-build_abe-bootstrap/console.log.xz | Bin 470428 -> 466448 bytes 06-check_regression/console.log.xz | Bin 2740 -> 2800 bytes 07-update_baseline/console.log | 32 ++++++++++++++++---------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++++--------- 13 files changed, 31 insertions(+), 31 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[gcc] branch master updated (6508d5e5a1a -> f1330551855)

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 6508d5e5a1a match.pd: rewrite select to branchless expression new ee4f25999f6 c++: Deduce range for structured bindings if expression is [...] new f1330551855 c++: Incremental fix for g++.dg/gomp/for-21.C [PR84469] 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/c-family/c-omp.cc | 9 +++--- gcc/cp/parser.cc | 32 +++++++++++++++----- gcc/testsuite/g++.dg/cpp1z/decomp56.C | 29 ++++++++++++++++++ gcc/testsuite/g++.dg/gomp/for-21.C | 18 +++++------ gcc/testsuite/g++.dg/gomp/for-22.C | 57 +++++++++++++++++++++++++++++++++++ gcc/testsuite/g++.dg/gomp/pr84469.C | 24 +++++++++++++++ 6 files changed, 149 insertions(+), 20 deletions(-) create mode 100644 gcc/testsuite/g++.dg/cpp1z/decomp56.C create mode 100644 gcc/testsuite/g++.dg/gomp/for-22.C create mode 100644 gcc/testsuite/g++.dg/gomp/pr84469.C -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (b620b20fda7 -> bd54b4b2f7c)

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 b620b20fda7 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] discards ad92a27093d 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] discards 6cfd342e66d 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] discards b395fa884df 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] discards 6dfa701ac89 194: onsuccess: #1995: 1: Success after linux: 517 commits discards e66ab21c429 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards f8764215218 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] discards 416788c91eb 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] discards 407a197549f 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] discards 6b0f1ce7913 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] discards 6fdf621797b 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] discards 405a545938b 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] discards f7706978cba 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] discards e7412ceebb2 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] discards 7d38bdb8dba 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] discards 4133831a08e 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] discards 5d8fad9e60f 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] discards 93fe9e676f8 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] discards 7d18b226a85 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] discards 9beeb71c9e1 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] discards e2a8782a635 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] discards f477c41cb44 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] discards 019f91abe02 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] discards a2f571fbc9a 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] discards fd5e4ba4ac3 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] discards 5e852d10db0 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] discards 3650cda5000 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] discards e394868434c 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] discards 9764aba4bd0 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] discards 449881c77ef 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] discards 373c4902c13 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] discards 6b8d67409db 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] discards e90c58108ca 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] discards 062a1f94dfb 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] discards 35d893d1898 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] discards 2ad1f011b6c 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards d741a753f9a 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] discards 19b90b3e571 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] discards fa3e8b855ef 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] discards ad3b428ce51 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] discards 3adab5c503b 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] discards 57b5e064f81 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] discards 7d7f9877326 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards b45f0f7d743 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] discards 52ff82cd718 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 5b661f072ce 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 478286d7948 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] discards 513184350a9 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] discards e797ba5e677 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] discards 52b0cf410c5 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] discards 1c3cb0671fa 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] discards 22845b55b53 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] discards d98b9ae2436 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] discards 23aae3495d3 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] discards 7355cb6d6ee 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards cad27cc1469 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] discards 482653bd62c 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] discards a7efcaa32bc 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] discards 45b0c604233 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] discards b662f048058 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] discards 85b32ba832f 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] discards 7e32ca86e03 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 5b09a6d44b0 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] discards e1cbeb270fc 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 78eb666aa9f 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards efcce43f7c5 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] discards 1921404950d 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] discards 05d94f5d8ce 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] discards 2922dafeae8 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 4880c713c6c 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] discards 9fa82276e12 128: onsuccess: #1723: 1: Success after linux: 12 commits discards bd55127d18f 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] discards f13135c0905 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards fc74a0817ce 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] discards 43162890e29 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 1313bab9ad2 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] discards 41e96e9e767 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] discards 7d819f3af0a 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] discards 405c30dec81 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] discards 9fd4b76fe4c 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] discards 17b880f727d 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] discards 2884cb83c98 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] discards b3b627dd5c1 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] discards 6845f30ca55 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] discards 62bce5446f3 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards dc099b7411a 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] discards bfc5834196c 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] discards 6242bd0bd66 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/ [...] discards d5bcf01538a 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards d69f9312579 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 [...] discards 2a525389c26 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 [...] discards 8ca2f86d7c6 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/ [...] discards 454073c5f2b 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/ [...] discards 577b516b419 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38edde [...] discards 64014de1951 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards d792c88f5a3 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/ [...] discards ba889c1909c 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/ [...] discards cee42851e27 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards a7e7426bafd 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/ [...] discards 2ea99200348 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/g [...] discards c091ab8ca8a 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/g [...] new 6fa50fbc375 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/g [...] new 7e31a82624e 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/g [...] new f2d5cf83bed 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/ [...] new 9716ce5d73c 101: onsuccess: #1693: 1: Success after glibc: 14 commits new dac682d7596 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/ [...] new 09e2a2d2363 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/ [...] new 3327b0fecd9 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 3f417e003c9 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38edde [...] new 2b1504c85af 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/ [...] new ceaa0b34a9f 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/ [...] new e17027d9603 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 [...] new 505986dc216 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 [...] new b342fdf2f6a 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 616c6b50366 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/ [...] new 81633685cb0 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] new 8c428889f8d 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] new 8dde90ec7fe 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 95b4382b4ad 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] new 9f05515e41a 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] new 9b191d834e6 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] new 0f78d217d6d 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] new 85c3c2c78f8 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] new 99c1ee66355 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] new 47d49123598 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] new 597d207b04b 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] new 50b81bd4346 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] new afe49e5a0c7 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 4f9659ca1d0 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] new 60f91895ae9 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 490c12de684 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] new 0287370828e 128: onsuccess: #1723: 1: Success after linux: 12 commits new 23a2aa1997b 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] new d51c18da13a 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new f823fe85fa0 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] new 446a8e89861 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] new 3c28ccf737e 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] new 81cb1f57534 134: onsuccess: #1730: 1: Success after binutils: 2 commits new dffe2d8ce4d 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 93e06d79306 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] new 150e49e1283 137: onsuccess: #1736: 1: Success after gcc: 5 commits new a87a48afa83 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] new ce8ea227d0c 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] new e77ae12d907 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] new 2352172c667 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new dd0eac9982c 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] new a7499d3ecfb 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] new e779c32edd9 144: onsuccess: #1743: 1: Success after glibc: 2 commits new be60fcee4e0 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] new e45d53ba5ff 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] new a29d5181a93 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] new 24d71850c24 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] new 494e024f31a 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] new 3a5ebd30623 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] new 551d05b5f95 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] new cc431e63be1 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] new c6c959ca55f 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 05bf2201507 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 568cfb6764e 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] new d566c4329a6 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 4ba947f0efd 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] new 1181ee6672d 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] new b1805485300 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] new 7f412e11593 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] new f2b189c71f4 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] new d7a240c47b5 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] new 1c879748656 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 6ed0d274ccc 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] new 5d2b37ea42d 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] new d4bdaffa5fc 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] new 789cbad2f9a 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] new c276892903a 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] new a5d3caaf8ae 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] new f7f732054c9 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] new 68a41333062 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] new b1b88f1ab8b 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] new 330668d757c 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] new 1c8d4f247d1 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] new 0576323bc71 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] new 1a628ae09d0 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] new 7052fef7d98 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] new 004e022c37a 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] new 4a029462ead 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] new 6ae65ff3f06 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] new 81921ee91f7 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] new 47361fe3b96 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] new 8e197318ab3 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] new 13a2489df34 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] new f6d16350743 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] new dce56a25463 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] new 315d1552a0d 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] new c3f4a8c2a15 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] new d593b7ce7e3 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] new 09c3ec8718e 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] new 893170d513a 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] new f599b43e03d 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] new b4d802a744d 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 88ae4b3b6d0 194: onsuccess: #1995: 1: Success after linux: 517 commits new 21561386acc 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] new 57425842403 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] new 52b50fe1edd 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] new 6ad6f7370fe 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] new bd54b4b2f7c 199: onsuccess: #2000: 1: Success after gcc: 5 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 (b620b20fda7) \ 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 1740 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 31628 -> 31352 bytes 04-build_abe-stage1/console.log.xz | Bin 91552 -> 91320 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8716 -> 8732 bytes 07-build_abe-glibc/console.log.xz | Bin 237036 -> 236760 bytes 08-build_abe-stage2/console.log.xz | Bin 225932 -> 224916 bytes 09-build_abe-gdb/console.log.xz | Bin 38736 -> 38500 bytes 10-build_abe-qemu/console.log.xz | Bin 30648 -> 30640 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3924 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2660 -> 2672 bytes 13-check_regression/console.log.xz | Bin 5940 -> 6160 bytes 13-check_regression/mail-body.txt | 101 -- 13-check_regression/results.compare | 38 +- 13-check_regression/results.compare2 | 106 +- 14-update_baseline/console.log | 78 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 103 +- mail/mail-subject.txt | 2 +- manifest.sh | 22 +- sumfiles/g++.log.xz | Bin 2711128 -> 2716712 bytes sumfiles/g++.sum | 144 +- sumfiles/gcc.log.xz | Bin 2300524 -> 2271860 bytes sumfiles/gcc.sum | 2907 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 894144 -> 887088 bytes sumfiles/gfortran.sum | 102 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 213044 -> 213132 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 436184 -> 433964 bytes sumfiles/libstdc++.sum | 14 +- 37 files changed, 1786 insertions(+), 1863 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022