Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_profiled_lto updated (f4d9914f7 -> b52f4a8ea)

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/release-arm-bootstrap_profiled_lto in repository toolchain/ci/base-artifacts. from f4d9914f7 12: onsuccess: #122: 2: Success after binutils/gcc: 10 commits new b52f4a8ea 13: onsuccess: #123: 2: Success after binutils/gcc: 8 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1704 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 51260 -> 52608 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 944244 -> 946400 bytes 06-check_regression/console.log.xz | Bin 2156 -> 2136 bytes 07-update_baseline/console.log | 2 +- 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, 16 insertions(+), 16 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[gcc] branch master updated (2438b6a4c8d -> be60aa5b608)

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 2438b6a4c8d frange::maybe_isnan() should return FALSE for undefined ranges. new be60aa5b608 Fortran: Fix function attributes [PR100132] 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/fortran/trans-types.cc | 15 ++++++- gcc/testsuite/gfortran.dg/PR100132.f90 | 75 ++++++++++++++++++++++++++++++++++ 2 files changed, 88 insertions(+), 2 deletions(-) create mode 100644 gcc/testsuite/gfortran.dg/PR100132.f90 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[gcc] branch master updated (10d6109fe18 -> 2438b6a4c8d)

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 10d6109fe18 frange::set_nonnegative should not contain -NAN. new 2438b6a4c8d frange::maybe_isnan() should return FALSE for undefined ranges. 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/value-range.h | 2 ++ 1 file changed, 2 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-stable-allmodconfig updated (a7b3edab8 -> 76b075ba4)

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-stable-allmodconfig in repository toolchain/ci/base-artifacts. from a7b3edab8 20: onsuccess: #489: 22763: Success after binutils/llvm/linux [...] new 76b075ba4 21: onsuccess: #490: 22763: 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 1724 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30712 -> 30484 bytes 04-build_kernel_llvm/console.log.xz | Bin 63904 -> 64028 bytes 05-build_abe-qemu/console.log.xz | Bin 31608 -> 31244 bytes 06-build_linux/console.log.xz | Bin 5048 -> 4568 bytes 08-check_regression/console.log.xz | Bin 3164 -> 3368 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 | 30 +++++++++++++++--------------- 17 files changed, 25 insertions(+), 25 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-next-allmodconfig updated (657dc0c5f -> 0433cb81f)

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-arm-next-allmodconfig in repository toolchain/ci/base-artifacts. from 657dc0c5f 12: onsuccess: #868: 23108: Success after binutils/gcc/qemu: [...] new 0433cb81f 13: force: #870: all: Success after linux: 14 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1716 -> 1624 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 29900 -> 29844 bytes 04-build_abe-stage1/console.log.xz | Bin 86408 -> 86428 bytes 05-build_abe-qemu/console.log.xz | Bin 31424 -> 31072 bytes 06-build_linux/console.log.xz | Bin 4304 -> 2960 bytes 07-boot_linux/console.log.xz | Bin 0 -> 496 bytes 08-check_regression/console.log.xz | Bin 2676 -> 1860 bytes 08-check_regression/mail-body.txt | 4 +++- 09-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 6 ++++-- mail/mail-subject.txt | 2 +- manifest.sh | 22 ++++++++++------------ results | 4 +++- 17 files changed, 25 insertions(+), 21 deletions(-) create mode 100644 07-boot_linux/console.log.xz -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/master-arm updated (25a50791bf -> 71d64753a5)

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_build/master-arm in repository toolchain/ci/base-artifacts. from 25a50791bf 50: onsuccess: #451: 6: Success after binutils/gcc/linux/gli [...] new 71d64753a5 51: onsuccess: #452: 6: Success after binutils/gcc/glibc/gdb [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1684 -> 1632 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 51564 -> 51292 bytes 05-build_abe-gcc/console.log.xz | Bin 233600 -> 232740 bytes 07-build_abe-linux/console.log.xz | Bin 8444 -> 8260 bytes 08-build_abe-glibc/console.log.xz | Bin 234908 -> 231984 bytes 09-build_abe-gdb/console.log.xz | Bin 49716 -> 49136 bytes 10-check_regression/console.log.xz | Bin 3156 -> 3232 bytes 11-update_baseline/console.log | 9 --------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 18 files changed, 24 insertions(+), 33 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-arm updated (cc8cf479c5 -> 656dffcd4b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/master-arm in repository toolchain/ci/base-artifacts. discards cc8cf479c5 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits discards ba96ea456d 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits discards 0f9c69d949 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits discards e739adbd2f 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits discards 3895d49799 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] discards d531491d2c 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits discards 53034fdeba 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] discards 9a6a8cd0eb 106: onsuccess: #1702: 1: Success after gcc: 4 commits discards 4b590eced3 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits discards e78566308a 104: onsuccess: #1700: 1: Success after gcc: 2 commits discards 212e6d39f3 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits discards 5b2450794c 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits discards 07194c7d95 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits discards cc09fc9255 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] discards 8903ed1896 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits discards 9616d955c1 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits discards 84aa8f0122 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits discards a59540d666 96: onsuccess: #1654: 1: Success after gcc: 5 commits discards 12ec151c20 95: onsuccess: #1653: 1: Success after gcc: 13 commits discards b97f74a4ad 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits discards 163fcc6f5a 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] discards e5a3e4a8b0 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits discards cefecf0648 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] discards 0a6ab5c805 90: onsuccess: #1645: 1: Success after gcc: 2 commits discards db0b713667 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] discards 57c3e2c11b 88: onsuccess: 1: Success after binutils/gcc: 2 commits discards 773f081516 87: onsuccess: 1: Success after gcc: 6 commits discards 6d549b180e 86: onsuccess: 1: Success after binutils/gcc: 8 commits discards 5cfbf522af 85: onsuccess: 1: Success after binutils/gcc: 19 commits discards f4a9c23cec 84: onsuccess: 1: Success after binutils/gcc: 2 commits discards f51a29eb2b 83: onsuccess: 1: Success after gcc: 14 commits discards 605429fd83 82: onsuccess: 1: Success after binutils/gcc: 9 commits discards dfb4d4a419 81: onsuccess: 1: Success after binutils/gcc: 8 commits discards a3c07965e5 80: onsuccess: 1: Success after binutils/gcc: 8 commits discards cc2b5ba975 79: onsuccess: 1: Success after binutils/gcc: 23 commits discards fec83b428a 78: onsuccess: 1: Success after binutils/gcc: 17 commits discards 16f0674e2b 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 4f0e9414f1 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 1d2caa086f 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 41a40b9ce2 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits discards 96d081d40f 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 24fbd8780b 72: onsuccess: 1: Successful build after baseline build: no [...] discards d0b3d8213c 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards 055c7f5633 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards f91a9a79d7 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] discards 6ca5f43125 68: onsuccess: 1: Successful build after gcc: 2 commits discards 304279d323 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 5683191472 66: onsuccess: 1: Successful build after gcc: 4 commits discards 86e2b9fd5c 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards 3c19472f90 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards 68ca9fe483 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 6a8ff4bd34 62: onsuccess: 1: Successful build after gcc: 4 commits discards 293b5f8db9 61: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 6431437ffb 60: onsuccess: 1: Successful build after binutils/gcc: 12 commits discards 2930214e1a 59: onsuccess: 1: Successful build after binutils/gcc: 29 commits discards a2129c896d 58: onsuccess: 1: Successful build after binutils: ld: pe: M [...] discards 6792324322 57: onsuccess: 1: Successful build after binutils: 2 commits discards 019fee0be1 56: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards d1862abffc 55: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 0fb9b0947b 54: onsuccess: 1: Successful build after gcc: 5 commits discards 183bb458a1 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards 3dc6d5e04e 52: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 8f8b2003ec 51: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 554efd7e7c 50: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 93e0de5745 49: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 0ceaeefe6f 48: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards a86ef4998c 47: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 4aac2858c2 46: onsuccess: 1: Successful build after baseline build: no [...] discards 9c9e99a80a 45: onsuccess: 1: Successful build after binutils: Fix crash [...] discards ebf9b61e7e 44: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards a62154f923 43: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 82c5ef980b 42: onsuccess: 1: Successful build after baseline build: no [...] discards d87cbcb19f 41: onsuccess: 1: Successful build after gcc: 2 commits discards d9ec6fda5d 40: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 5db20023a9 39: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 7cd82052ca 38: onsuccess: 1: Successful build after gcc: 2 commits discards 323e05c1ad 37: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards fa1d335d2d 36: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards e82bdabd2f 35: onsuccess: 1: Successful build after binutils/gcc: 12 commits discards dc31b00fca 34: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 4a2fc14328 33: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 6c1e7f227f 32: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards f315dfaca9 31: onsuccess: 1: Successful build after gcc: 9 commits discards 3e29b6265e 30: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards d0ab5e734a 29: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 5fdab94e89 28: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards db0c21e204 27: onsuccess: 1: Successful build after binutils/gcc: 12 commits discards ef91d7a07c 26: onsuccess: 1: Successful build after binutils/gcc: 22 commits discards 08edbf974b 25: onsuccess: binutils-gcc: 1 discards aa90cdb260 24: onsuccess: binutils-gcc: 1 discards 4ed26716bc 23: onsuccess: binutils-gcc: 1 discards 1ae9230377 22: onsuccess: binutils-gcc: 1 discards ff7d2a649c 21: onsuccess: binutils-gcc: 1 discards 3ce9546aec 20: onsuccess: binutils-gcc: 1 discards 6be1801252 19: onsuccess: binutils-gcc: 1 discards eb9f45fd2b 18: onsuccess: binutils-gcc: 1 discards d23218e1b4 17: onsuccess: binutils-gcc: 1 discards 34af043566 16: onsuccess: binutils-gcc: 1 discards 9e579e4c7a 15: onsuccess: binutils-gcc: 1 discards 2e4c0d62d6 14: onsuccess: binutils-gcc: 1 discards 038fc79817 13: onsuccess: binutils-gcc: 1 new 4a6aeb56f4 13: onsuccess: binutils-gcc: 1 new 9829959bdb 14: onsuccess: binutils-gcc: 1 new 534b59b2ea 15: onsuccess: binutils-gcc: 1 new 154ecc732f 16: onsuccess: binutils-gcc: 1 new 678f050c1e 17: onsuccess: binutils-gcc: 1 new c9e534adae 18: onsuccess: binutils-gcc: 1 new 6ab9a368bb 19: onsuccess: binutils-gcc: 1 new 1f31eec8a0 20: onsuccess: binutils-gcc: 1 new 0977c562c4 21: onsuccess: binutils-gcc: 1 new 5cc8d4c17a 22: onsuccess: binutils-gcc: 1 new c9db1ad4f5 23: onsuccess: binutils-gcc: 1 new 2fcb1f34c3 24: onsuccess: binutils-gcc: 1 new 84c0e00666 25: onsuccess: binutils-gcc: 1 new 56a9fdce17 26: onsuccess: 1: Successful build after binutils/gcc: 22 commits new c624169ddb 27: onsuccess: 1: Successful build after binutils/gcc: 12 commits new aa259b6f7b 28: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 4ecce2a7b4 29: onsuccess: 1: Successful build after binutils/gcc: 3 commits new d3bea119ad 30: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 82819f3751 31: onsuccess: 1: Successful build after gcc: 9 commits new 114dd26f07 32: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 5993b525f2 33: onsuccess: 1: Successful build after binutils/gcc: 5 commits new a2470fbbdd 34: onsuccess: 1: Successful build after binutils/gcc: 10 commits new dd3fd3b867 35: onsuccess: 1: Successful build after binutils/gcc: 12 commits new ddb4efbb80 36: onsuccess: 1: Successful build after binutils/gcc: 3 commits new b739b3f2ed 37: onsuccess: 1: Successful build after binutils/gcc: 6 commits new c1dadf447c 38: onsuccess: 1: Successful build after gcc: 2 commits new d950facbe2 39: onsuccess: 1: Successful build after binutils/gcc: 6 commits new a4110e8ea6 40: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 2ca74b5567 41: onsuccess: 1: Successful build after gcc: 2 commits new e00f444b12 42: onsuccess: 1: Successful build after baseline build: no [...] new e26a2c9180 43: onsuccess: 1: Successful build after binutils/gcc: 3 commits new f31fc37a87 44: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 8f1c4e3fb5 45: onsuccess: 1: Successful build after binutils: Fix crash [...] new a2b9b91bf7 46: onsuccess: 1: Successful build after baseline build: no [...] new ad5b74f6c3 47: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 853b534bf5 48: onsuccess: 1: Successful build after binutils/gcc: 6 commits new c7cdbb157e 49: onsuccess: 1: Successful build after binutils/gcc: 3 commits new c8086e9d67 50: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 6521314fa5 51: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 6c9bd8e7c7 52: onsuccess: 1: Successful build after binutils/gcc: 6 commits new e9b8a9d7fd 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 16908a0c6b 54: onsuccess: 1: Successful build after gcc: 5 commits new 33174089ed 55: onsuccess: 1: Successful build after binutils/gcc: 2 commits new ea356f49e7 56: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 0b55b2b93e 57: onsuccess: 1: Successful build after binutils: 2 commits new 0610534350 58: onsuccess: 1: Successful build after binutils: ld: pe: M [...] new 209167ba1e 59: onsuccess: 1: Successful build after binutils/gcc: 29 commits new 9117b21750 60: onsuccess: 1: Successful build after binutils/gcc: 12 commits new 9295697be6 61: onsuccess: 1: Successful build after binutils/gcc: 8 commits new fec14f42e2 62: onsuccess: 1: Successful build after gcc: 4 commits new afe92e6c3f 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 5784e8cfec 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits new 9141490dcc 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits new ddcaa25c6f 66: onsuccess: 1: Successful build after gcc: 4 commits new b89da10416 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 859c621463 68: onsuccess: 1: Successful build after gcc: 2 commits new 26fe64a9b4 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] new 791af2afea 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 0dee97f25b 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] new f960814426 72: onsuccess: 1: Successful build after baseline build: no [...] new 9d9f37fce7 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits new 58048f759c 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits new 3b431c7753 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits new f03a0c2489 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 84814a6e29 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 572816edf7 78: onsuccess: 1: Success after binutils/gcc: 17 commits new 0d2301f0ad 79: onsuccess: 1: Success after binutils/gcc: 23 commits new 645ae0ba7c 80: onsuccess: 1: Success after binutils/gcc: 8 commits new f727a1fb0f 81: onsuccess: 1: Success after binutils/gcc: 8 commits new 51b418cf27 82: onsuccess: 1: Success after binutils/gcc: 9 commits new fd5acd7e87 83: onsuccess: 1: Success after gcc: 14 commits new 403d605631 84: onsuccess: 1: Success after binutils/gcc: 2 commits new 4ef5d21848 85: onsuccess: 1: Success after binutils/gcc: 19 commits new 176c23e9c3 86: onsuccess: 1: Success after binutils/gcc: 8 commits new 5a1a2b9017 87: onsuccess: 1: Success after gcc: 6 commits new d1222ebbf2 88: onsuccess: 1: Success after binutils/gcc: 2 commits new 40ef71a763 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] new 6341d3d4f5 90: onsuccess: #1645: 1: Success after gcc: 2 commits new 8a6ff602cf 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] new 5a6c0e3cab 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits new b953d51e6f 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] new 6482263d4c 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits new 1b1152224c 95: onsuccess: #1653: 1: Success after gcc: 13 commits new 1e5bfbc22d 96: onsuccess: #1654: 1: Success after gcc: 5 commits new 67862a69b5 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits new 54889d4f59 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits new 2e847e28b3 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits new 13078e4be7 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] new 379977d892 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits new 3d3ca21055 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits new 0b449ffa53 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits new 1e08accabc 104: onsuccess: #1700: 1: Success after gcc: 2 commits new 57aaae84b4 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits new 2aeed5fd74 106: onsuccess: #1702: 1: Success after gcc: 4 commits new 967faace85 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] new c6f10dd753 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits new 7474ed9d5b 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] new 0d9c82481a 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits new dbb89df013 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits new 63c3da7c5a 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits new 4a33a1d7bb 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits new 656dffcd4b 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (cc8cf479c5) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (65 [...] 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 1656 -> 1600 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 51372 -> 51812 bytes 04-build_abe-gcc/console.log.xz | Bin 233664 -> 234132 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3824 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2476 -> 2348 bytes 07-check_regression/console.log.xz | Bin 4632 -> 4524 bytes 07-check_regression/mail-body.txt | 27 - 07-check_regression/results.compare | 13 +- 07-check_regression/results.compare2 | 59 +- 08-update_baseline/console.log | 58 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/g++.log.xz | Bin 2768428 -> 2777912 bytes sumfiles/g++.sum | 71 +- sumfiles/gcc.log.xz | Bin 2390988 -> 2367684 bytes sumfiles/gcc.sum | 4575 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 907208 -> 904036 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2168 -> 2172 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 204412 -> 204552 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2536 -> 2528 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 466840 -> 465384 bytes sumfiles/libstdc++.sum | 2 +- 32 files changed, 2430 insertions(+), 2440 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (0b7f234e66 -> 38c9380166)

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-aarch64 in repository toolchain/ci/base-artifacts. discards 0b7f234e66 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards d9a68f12ca 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards cec535ac10 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards a8ef81e6de 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 7974292b44 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 326878f270 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 7d770591f6 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards fef88f93a5 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards c17185157c 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 9ecb273082 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 660b2f01e1 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards ac6a932857 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 152d285f31 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards db20621345 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 46cfcdf4b5 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards c9341312e2 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards b6d53599ba 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards c7627ad3d4 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards a7d84478cb 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 8ccabf58aa 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards cba3899af0 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 83e4e8ca30 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards c6c6a9b00e 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 355b8bce96 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 6f3bbc95ce 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards a18f694bd3 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 1dcc094e0a 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 2c6f448400 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards b591ff7c33 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 3e0ce88b25 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 98970cc7ca 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards f41c81fd5d 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 56a27c0ee6 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 6e453ed778 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 048c37b1c0 75: onsuccess: 1: Successful build after linux: 44 commits discards 6306121aa9 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 661d8f896f 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 29a410774f 72: onsuccess: 1: Successful build after linux: 12 commits discards a086d0281f 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 8617e9627e 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 6114ce37f4 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 816249dff4 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 98771a61ab 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 4fcd6fd675 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 20839aae5c 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d1b0253707 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1008b6ba41 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 04e30b36d0 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards ca0f253b47 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 64b31c6ab2 60: onsuccess: 1: Successful build after glibc: 2 commits discards f626cead90 59: onsuccess: 1: Successful build after binutils: 2 commits discards fe14d54208 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 670df0a2a5 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b152428c29 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6791e8c85a 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 2d624befad 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards ec3bb000c7 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 6489160a9c 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 8d889c8471 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9841ba8d55 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b26d8a66a6 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 547c45fa74 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1a80542ece 47: onsuccess: 1: Successful build after linux: 10 commits discards ec1bd74933 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 8442cbb912 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ede787e82b 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 8ec7103c27 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards e6e7baa1f5 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] discards f9404ff9fb 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e9dfe1b5b5 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards 19ed19e8ea 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 7afa6edc8c 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards 2160017c60 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b68be05fa2 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards de1fa9a745 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 85959550d8 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 72ddf63d9c 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bb546348fc 32: onsuccess: 1: Successful build after gcc: 7 commits discards 979869e24e 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 4d56c3cd48 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards c9e0b56948 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 59925859eb 28: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 637843f84f 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards c7b1a539e3 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5016aabda3 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 3a4c2dffd0 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 4dbcfe994e 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 647370a88a 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 0f300bfe9f 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f8e9b862d2 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f2908fba4a 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9dfff13c44 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b25e798311 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a3873884bb 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards d6e25b1ebe 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f469c52248 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 17fba60fb2 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ee714cd5c5 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5e29734930 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards dda3af23e2 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e03565e9d1 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f62919d7bd 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 788e7ba0b4 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8fc41c4b68 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9d02ef1797 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8edd3bcc26 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 69e1393402 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 77bf2711ae 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f75ad1e51f 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d4bba6d8da 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 775bd7d3df 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 0b1c5099f5 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 6922d7ea48 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 3e3506e3c8 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2fa3feba09 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 15f8cd1458 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b11b970527 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5a8f82daba 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4df0fe6105 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b80d9e1cc4 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 793f7d35d7 28: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 1c75285192 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d5222cca6b 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 4a638f9845 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 5417633295 32: onsuccess: 1: Successful build after gcc: 7 commits new 3055bd492f 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 53b0d1d4b3 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ad79e8ab63 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 87837ced40 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 74900233f4 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 19f2fb7a88 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new b85c2f9d34 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new adff658d25 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new ecab89e08e 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0ec8088adb 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new 43e594e854 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new f3a62b2cdc 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new bb557981e3 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cd312007be 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new e12d3d9174 47: onsuccess: 1: Successful build after linux: 10 commits new 56b01ba376 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7a4deb6c71 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new bc3099adf1 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 2a9a12fedf 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9065a1c126 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new dc8db3b38a 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new bb46c11234 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 9b96cbb23b 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 51f37fddf0 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 86f09d0ece 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 1a12e1dd37 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 7242771ee9 59: onsuccess: 1: Successful build after binutils: 2 commits new b376bceaae 60: onsuccess: 1: Successful build after glibc: 2 commits new 608f1898ae 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 1865821cc7 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 43a32fa0db 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new abe3ea425b 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 288723b132 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3f95ff0ff1 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new e61cb7123b 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 4af94ef4ed 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a6b698a16e 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new f5c49ea6db 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new ef62e3b6c3 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 443970e542 72: onsuccess: 1: Successful build after linux: 12 commits new d1bed5486c 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1c0606b46f 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new cfe488de65 75: onsuccess: 1: Successful build after linux: 44 commits new 0ae01d55ea 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a6e5bcd77e 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 5bad0cc710 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 184e98e7eb 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b2ff276ceb 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 7572e63dc2 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 980f16d27d 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 6c218e8d77 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new dfc6501058 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 88a4339392 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new bb6421df5f 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 460ca8aec1 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 045d15e976 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 9402b6003d 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new dc4e962b57 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 3d73c97342 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new e3d97b25c1 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 4038d48dd9 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new fa1d76b2f7 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 3108e25dbd 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 4bb63c625d 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 3645d46ed7 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 864e596b38 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 17f459729d 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 5d8e79a8fd 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new e068e3265c 101: onsuccess: #2130: 1: Success after binutils: 81 commits new a1bf6a6f26 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new a599fa2b45 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 06b0ba82ab 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 1237189271 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new d96d0ed09a 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new c03e17349c 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new becbf22228 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new c187aa2683 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 38c9380166 110: onsuccess: #2142: 1: 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 (0b7f234e66) \ 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 1684 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30104 -> 30740 bytes 04-build_abe-stage1/console.log.xz | Bin 72164 -> 72836 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8280 -> 8316 bytes 07-build_abe-glibc/console.log.xz | Bin 239652 -> 239796 bytes 08-build_abe-stage2/console.log.xz | Bin 201920 -> 203140 bytes 09-build_abe-gdb/console.log.xz | Bin 37360 -> 37844 bytes 10-build_abe-qemu/console.log.xz | Bin 31592 -> 31760 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2532 -> 3016 bytes 13-check_regression/console.log.xz | Bin 5188 -> 6304 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 35 +- 13-check_regression/mail-body.txt | 127 +- 13-check_regression/results.compare | 65 +- 13-check_regression/results.compare2 | 94 +- 13-check_regression/results.regressions | 65 +- 14-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 129 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 65 +- sumfiles/g++.log.xz | Bin 3396200 -> 3418228 bytes sumfiles/g++.sum | 230 +- sumfiles/gcc.log.xz | Bin 3022332 -> 3000048 bytes sumfiles/gcc.sum | 4874 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1023508 -> 1024840 bytes sumfiles/gfortran.sum | 92 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201860 -> 201892 bytes sumfiles/libgomp.sum | 21 +- sumfiles/libitm.log.xz | Bin 2660 -> 2656 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 427092 -> 424084 bytes sumfiles/libstdc++.sum | 15 +- 44 files changed, 3095 insertions(+), 2817 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[linux] branch master updated (521a547ced64 -> 60891ec99e14)

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 521a547ced64 Linux 6.0-rc6 new 2b1e8921fc35 Revert "selftests/timens: add a test for vfork+exit" new 33a2d6bc3480 Revert "fs/exec: allow to unshare a time namespace on vfork+exec" new f489921dba46 Merge tag 'execve-v6.0-rc7' of git://git.kernel.org/pub/sc [...] new f52d74b190f8 open: always initialize ownership fields new 84a31938831f Merge tag 'fs.fixes.v6.0-rc7' of git://git.kernel.org/pub/ [...] new 8a1f1e3d1eec btrfs: fix hang during unmount when stopping block group r [...] new a362bb864b8d btrfs: fix hang during unmount when stopping a space recla [...] new 2dd7e7bc0282 btrfs: zoned: wait for extent buffer IOs before finishing a zone new 60891ec99e14 Merge tag 'for-6.0-rc6-tag' of git://git.kernel.org/pub/sc [...] The 9 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: fs/btrfs/disk-io.c | 42 ++++++++++++-- fs/btrfs/zoned.c | 40 ++++++++++++- fs/exec.c | 7 --- fs/open.c | 2 + kernel/fork.c | 5 +- kernel/nsproxy.c | 3 +- tools/testing/selftests/timens/Makefile | 2 +- tools/testing/selftests/timens/vfork_exec.c | 90 ----------------------------- 8 files changed, 79 insertions(+), 112 deletions(-) delete mode 100644 tools/testing/selftests/timens/vfork_exec.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[gcc] branch master updated (d812e8cb2a9 -> 10d6109fe18)

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 d812e8cb2a9 fortran: add link to ISO_VARYING_STRING module [PR106636] new 10d6109fe18 frange::set_nonnegative should not contain -NAN. 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/value-range.cc | 9 +++++++++ gcc/value-range.h | 14 ++++++++++++++ 2 files changed, 23 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits September 2022