Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-norov-allnoconfig updated (98063d87bf -> 732d2c2358)

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-norov-allnoconfig in repository toolchain/ci/base-artifacts. from 98063d87bf 10: onsuccess: #37: all: Success after binutils/gcc: 14 commits new 732d2c2358 11: onsuccess: #38: all: Success after binutils/gcc/linux/qe [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1876 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 29948 -> 29900 bytes 04-build_abe-stage1/console.log.xz | Bin 86688 -> 87324 bytes 05-build_abe-qemu/console.log.xz | Bin 31472 -> 30792 bytes 06-build_linux/console.log.xz | Bin 3420 -> 3428 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 2360 -> 3096 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- 17 files changed, 23 insertions(+), 23 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_bootstrap/master-aarch64-bootstrap_profiled_lto_lean updated (8bee5af047 -> 96b04d9b2d)

by git＠git.linaro.org

2 years, 2 months

[binutils-gdb] branch master updated (df86565b31b -> 6f1d2f789bf)

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 df86565b31b gdb: remove TYPE_LENGTH new 6f1d2f789bf gdbsupport: change path_join parameter to array_view<const char *> 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: gdb/dwarf2/line-header.c | 4 ++-- gdbsupport/pathstuff.cc | 8 ++++---- gdbsupport/pathstuff.h | 8 ++++---- 3 files changed, 10 insertions(+), 10 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-arm updated (4295f79e55 -> 8951cb1211)

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 4295f79e55 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards c64c22092d 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 0693167dcc 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 5c1c8749fa 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 911cf1e730 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards d6e23de3b0 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 9673b4cc42 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards f5f564fb9d 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards bbfb5000fa 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 6285072f5c 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 0ba3f4642e 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 83ea0d70d6 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards d7db83f7f7 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 5f91c72652 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards ed9e5bd445 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 23173bc951 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 179c13da99 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards f102c71c4b 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 5d6bfd2170 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 7a5737bed3 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 2e74e36ed4 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 944337a501 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 1352b2982d 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards ecba37b355 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 36ea96096f 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 28167d145b 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 464be1435f 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 66682a5ff4 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 41b9ee528a 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 9bae6315e6 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 17d6d23b8f 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards c5ebc13203 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 9be404302d 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 3cd06bb21a 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 501ecb0583 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 53950fe463 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 7197b48fdb 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 3241b3011a 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3904cd9199 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 913056ecb7 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 67b22e9815 74: onsuccess: 1: Successful build after linux: 44 commits discards 07d8f0077b 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards f925c969a2 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d52b457973 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 196f77858c 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 7c6e19a12f 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 2b3791ce55 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 37d0ae7cdb 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b707dcaf7e 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b42214a025 65: onsuccess: 1: Successful build after gcc: 4 commits discards 6692fd55c3 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 25df9e05b2 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1c040fdc30 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 3bd541f569 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 3ea7cb212e 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 31d0cb7495 59: onsuccess: 1: Successful build after glibc: 2 commits discards febc09e666 58: onsuccess: 1: Successful build after binutils: 2 commits discards cd9a5dde46 57: onsuccess: 1: Successful build after gcc: 7 commits discards 6acb25b3b1 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b0616415b0 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5c26ec39f6 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 99efa48a61 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 754affe219 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards bc0ee367a1 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards fc9fb03bcc 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards beac5ff029 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 194c676161 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards e30d41c173 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 36e067856a 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 8f143a9d02 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 357bcc321a 44: onsuccess: 1: Successful build after linux: 34 commits discards d553567c8d 43: onsuccess: 1: Successful build after gcc: 2 commits discards 39209c36b4 42: onsuccess: 1: Successful build after baseline build: no [...] discards 411891ee81 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6da93313bb 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8c2a772e97 39: onsuccess: 1: Successful build after gcc: 2 commits discards 3cf3c450d8 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4b66e64b86 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d3c8b43079 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 77dd8e85c0 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 498b1348a1 34: onsuccess: 1: Successful build after gcc: 3 commits discards 63b7405b6d 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7b66b72009 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 12d156e026 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c3a92baafe 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards f347b0c8b0 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards eb121694e2 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards c1b87eb841 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7f20773363 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 914dd2871f 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a76d46e59a 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 513c4ac70e 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 1d414b4cf9 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9186d1ce2c 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards bbd0ad04ab 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 900e54b311 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards da56d38615 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 92446d3c90 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 4b7894a323 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 1055b92185 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 0d27672b2a 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d0b2104d5e 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c37f6dd739 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c1990a215b 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 6fa90aaea6 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 885365f013 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new dbcc7e1b04 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new bcb4b33d98 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c348cff7a7 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ea0a43e52d 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 1d538682a1 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9cad606403 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new dff22a8816 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ddd7d5328d 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 37fd1ed701 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 53560cddd2 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new e3e6afbd28 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 41223042b8 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new a898b3866b 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 2ff0c5658a 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new ad6ef1572a 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0e4a21757c 34: onsuccess: 1: Successful build after gcc: 3 commits new c139193a7c 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 1f280f8e14 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cf21f7e836 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 46e8555097 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 961b4e4771 39: onsuccess: 1: Successful build after gcc: 2 commits new dde7048ea1 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b63a42b384 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e35e72af2b 42: onsuccess: 1: Successful build after baseline build: no [...] new b85a38097c 43: onsuccess: 1: Successful build after gcc: 2 commits new a1263b2ab5 44: onsuccess: 1: Successful build after linux: 34 commits new 55eec78d72 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 37091e3372 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 5b24dd1667 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 14a677087c 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new e3cc5ab46e 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 6c0e1c5715 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f3a56eac37 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 9030bb9ec1 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new c1abade936 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new f85031977a 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new f5423acd8a 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3c236f934f 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 52429cad71 57: onsuccess: 1: Successful build after gcc: 7 commits new 73014c8f01 58: onsuccess: 1: Successful build after binutils: 2 commits new 36f7d44f6a 59: onsuccess: 1: Successful build after glibc: 2 commits new cd847ce8e9 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new ed9271ca96 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new e50ed1f887 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new c690072421 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0c07987928 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 68b7657cea 65: onsuccess: 1: Successful build after gcc: 4 commits new a20e4cbb95 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 528dec24fb 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 33e9b715df 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 05dce66314 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new f9e416aab1 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new e6d7dd6d8d 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 257656f603 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4eca1653c8 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new e84c5ee539 74: onsuccess: 1: Successful build after linux: 44 commits new a8607140ae 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cae37149f4 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 633a76f092 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new edf4420d0d 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 6dc9581d31 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new a32035bac2 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 173cafbcce 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 7932f56e82 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new d2e83efa2f 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 97d60c5edf 84: onsuccess: 1: Success after gcc/glibc: 9 commits new b3f8a9c342 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 8b51e4710a 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 2eb5e1a2d2 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 09069ef13e 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new a6080c82bd 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 56e258142f 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new abeecc1480 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new c23a748906 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 030c257708 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 17dbba7a4a 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new ced4d781b3 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 4ea3858454 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new ada44696e3 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 47e7a1003c 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 358ae9079e 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new d297d07d69 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 39b548c971 101: onsuccess: #1693: 1: Success after glibc: 14 commits new ea4ee4c261 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 204465d41e 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new c89b44bc43 104: onsuccess: #1697: 1: Success after gcc: 4 commits new f075624441 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 8169e93820 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new e7d901c2b5 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new e9677b8b07 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 35943c8bd5 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 499cc9eb9c 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 99961427b8 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 2bdc20b1d3 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 0058ae816e 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 60c696e45c 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 8951cb1211 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] 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 (4295f79e55) \ 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 1688 -> 1884 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30628 -> 29952 bytes 04-build_abe-stage1/console.log.xz | Bin 91212 -> 90564 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8624 -> 8600 bytes 07-build_abe-glibc/console.log.xz | Bin 234380 -> 233832 bytes 08-build_abe-stage2/console.log.xz | Bin 223076 -> 222932 bytes 09-build_abe-gdb/console.log.xz | Bin 37664 -> 37220 bytes 10-build_abe-qemu/console.log.xz | Bin 31488 -> 30924 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3852 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2436 -> 2644 bytes 13-check_regression/console.log.xz | Bin 4900 -> 5632 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 11 +- 13-check_regression/mail-body.txt | 80 +- 13-check_regression/results.compare | 50 +- 13-check_regression/results.compare2 | 75 +- 13-check_regression/results.regressions | 50 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 82 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 50 +- sumfiles/g++.log.xz | Bin 2679412 -> 2678388 bytes sumfiles/g++.sum | 126 +- sumfiles/gcc.log.xz | Bin 2204080 -> 2207716 bytes sumfiles/gcc.sum | 2613 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 880428 -> 882024 bytes sumfiles/gfortran.sum | 79 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201120 -> 201344 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 421828 -> 421944 bytes sumfiles/libstdc++.sum | 14 +- 43 files changed, 1790 insertions(+), 1580 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_bootstrap/master-arm-bootstrap updated (3025cd5256 -> 21b9e76506)

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 3025cd5256 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards 7ea6aa4b9f 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards e5dc3b12eb 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards d74864b0ea 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards 61eb9863ae 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards 09b9ce9a35 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards e28036ba93 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards 02c60d7b9e 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards 320f9d6b00 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] discards b5345f3c50 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards 5c09c8c976 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] discards 2447e6aea6 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards 542f730330 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards d07b1acf1a 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards 42a7b76c2a 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards 41cb931aa8 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards 91883d2102 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards b9c6a2af31 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards 94b0b1da8f 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] discards 795573e16b 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] discards c20b685adf 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards dffb14082c 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards 11448ebb5b 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] discards d2a14fda7a 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] discards 7f39086e4e 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards 07cc3d1bae 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards a059b602bd 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards b3b124562d 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards bbba1b3586 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards d45863c09c 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards 223bed5817 87: onsuccess: 2: Success after gcc: 4 commits discards 5c18195cd5 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards 1ffbc87c1a 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards c405c93a14 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards 31e9d28cbe 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards 015f553da5 82: onsuccess: 1: Successful build after gcc: 3 commits discards e330dedbb3 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 6f18257571 80: force: 2: Successful build after gcc: 14 commits discards eb853c4114 79: onsuccess: 2: Successful build after binutils: 5 commits discards d162974070 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards e91b8d6663 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 34a979b1cc 76: onsuccess: 2: Successful build after gcc: 12 commits discards e1c7fc6aae 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 1a816e3d89 74: onsuccess: 2: Successful build after baseline build: no [...] discards e7a8b6f616 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards fcee9c4385 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 8f188d571f 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards eec03e0593 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards a661427d18 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 57af034c5e 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards b4f7683d62 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 195b2742c2 66: onsuccess: 2: Successful build after gcc: 9 commits discards 89ed072072 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 81f694819f 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 974a3f6d85 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards ebd7a17e05 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 1e02c6eed5 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards 2a707777c8 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards aa0f987d8f 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards f26eb41ac6 58: force: 2: Successful build after gcc: 6 commits discards 581b07ca4b 57: onsuccess: 2: Successful build after binutils: gdb: new [...] discards 9deff790ee 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards c176be928b 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards fceb7a6f75 54: onsuccess: 2: Successful build after gcc: 5 commits discards 81583377d8 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 1b4eef99db 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards bd95c889e8 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards daf7efada0 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards cf3a4731cd 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 8e4d46d29d 48: onsuccess: 2: Successful build after gcc: 4 commits discards dfc41596f5 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 1f18ab8ee1 46: onsuccess: 2: Successful build after baseline build: no [...] discards 678eba76a1 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards 99a23b4a5f 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards a607801c7c 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] discards c2f4f6ade8 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] discards 23128448cd 41: onsuccess: 2: Successful build after gcc: libcpp: Implem [...] discards 667ce6f26a 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 8b15204bfe 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 902ef23394 38: onsuccess: 2: Successful build after gcc: 2 commits discards 5e01e9484f 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards e7481b09e8 36: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards cbc74acc9c 35: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 748b7de687 34: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 079e58722b 33: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards fc50e931a8 32: onsuccess: 2: Successful build after gcc: 6 commits discards 205a05158b 31: onsuccess: 2: Successful build after gcc: 6 commits discards 1e94ef3328 30: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 19bbe8fce3 29: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 961495b866 28: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 6c54dc5c1a 27: onsuccess: 2: Successful build after binutils/gcc: 14 commits discards ef012521ef 26: onsuccess: binutils-gcc: 2 discards f4a3674a50 25: onsuccess: binutils-gcc: 2 discards b578fc26a4 24: onsuccess: binutils-gcc: 2 discards 38ccaa69fc 23: onsuccess: binutils-gcc: 2 discards 16a13a007a 22: onsuccess: binutils-gcc: 2 discards 351bd62866 21: onsuccess: binutils-gcc: 2 discards 2df38b1f14 20: onsuccess: binutils-gcc: 2 discards 4e4c0a6d9c 19: onsuccess: binutils-gcc: 2 discards 00b2595d64 18: onsuccess: binutils-gcc: 2 discards 27b4ba9b93 17: onsuccess: binutils-gcc: 2 new b5f749fa80 17: onsuccess: binutils-gcc: 2 new cdf04916e2 18: onsuccess: binutils-gcc: 2 new ff54eec5e6 19: onsuccess: binutils-gcc: 2 new 5919834a40 20: onsuccess: binutils-gcc: 2 new 2801b46e79 21: onsuccess: binutils-gcc: 2 new 9c90115816 22: onsuccess: binutils-gcc: 2 new aaedbb1130 23: onsuccess: binutils-gcc: 2 new 8fe3680473 24: onsuccess: binutils-gcc: 2 new ede95d7655 25: onsuccess: binutils-gcc: 2 new 43e9f64e34 26: onsuccess: binutils-gcc: 2 new 6d04ce7584 27: onsuccess: 2: Successful build after binutils/gcc: 14 commits new 43b9ad3379 28: onsuccess: 2: Successful build after binutils/gcc: 8 commits new ffef4fb032 29: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 8beec80542 30: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 4c9d05c9c9 31: onsuccess: 2: Successful build after gcc: 6 commits new 856f02cddb 32: onsuccess: 2: Successful build after gcc: 6 commits new e185584c90 33: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 454d55b72b 34: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 199ec5aba0 35: onsuccess: 2: Successful build after binutils/gcc: 11 commits new bb9c6e528d 36: onsuccess: 2: Successful build after binutils/gcc: 8 commits new c0bbab43a9 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 9589a6f6f2 38: onsuccess: 2: Successful build after gcc: 2 commits new 4d0dfb1191 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 71ad6759ce 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new fe620ea4d0 41: onsuccess: 2: Successful build after gcc: libcpp: Implem [...] new af4c71910f 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] new 13b80be649 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new 01b2c1d997 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 4386afcf66 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 8c853bce76 46: onsuccess: 2: Successful build after baseline build: no [...] new 69a117ce79 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits new a03dc6ef29 48: onsuccess: 2: Successful build after gcc: 4 commits new ad547ec447 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 9332239159 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 2dbb70cfca 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 4ecb9379a0 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 1d75e7b112 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 15ca5c2bcd 54: onsuccess: 2: Successful build after gcc: 5 commits new e2c72298c2 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 5f0fb09337 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits new d9767e59bd 57: onsuccess: 2: Successful build after binutils: gdb: new [...] new ccb2f77a9a 58: force: 2: Successful build after gcc: 6 commits new ca523678d3 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new a15d8d3278 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new 71472a644d 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new f108813ff5 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 1debff8bd4 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 155c67250e 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 8e98146d5d 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 32f3cfa0b4 66: onsuccess: 2: Successful build after gcc: 9 commits new 13ca0cc6b4 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 4d9408e5c3 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 58e4d2f753 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new fb110fd6f5 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new cb36ce0101 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new e6a2f46523 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 0bf39a18e2 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] new fe98181461 74: onsuccess: 2: Successful build after baseline build: no [...] new d6d86054d0 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new a1d0e2bea5 76: onsuccess: 2: Successful build after gcc: 12 commits new 74451bc82b 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 8958da0e97 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new d645a74361 79: onsuccess: 2: Successful build after binutils: 5 commits new 1799b45bbe 80: force: 2: Successful build after gcc: 14 commits new 490b6bcb93 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new aff9e3ae71 82: onsuccess: 1: Successful build after gcc: 3 commits new 1e02210918 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new 61dbc1d9ee 84: onsuccess: 2: Success after binutils/gcc: 15 commits new 72b96e133b 85: onsuccess: 2: Success after binutils/gcc: 25 commits new 8139bf559e 86: onsuccess: 2: Success after binutils/gcc: 10 commits new 7b88c346ff 87: onsuccess: 2: Success after gcc: 4 commits new e46ccf042e 88: onsuccess: 2: Success after binutils/gcc: 25 commits new 42e0eb00c4 89: onsuccess: 2: Success after binutils/gcc: 4 commits new 53eac3ffd1 90: onsuccess: 2: Success after binutils/gcc: 16 commits new 955668013a 91: onsuccess: 2: Success after binutils/gcc: 7 commits new a5936ece3f 92: onsuccess: 2: Success after binutils/gcc: 9 commits new 7fc03699e8 93: onsuccess: 2: Success after binutils/gcc: 3 commits new e8ba681ce6 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] new 3c0bf23a40 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] new 0ab670b70c 96: onsuccess: #1452: 2: Success after gcc: 2 commits new 67cb4c6ae9 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new 5bd2b8c27d 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] new d6ff45aee0 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] new 56e325ccef 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new c633776b37 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new 294434d4e5 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new ac089fa4b4 103: onsuccess: #1504: 2: Success after gcc: 2 commits new 276cd663c3 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new b614ce784e 105: onsuccess: #1506: 2: Success after gcc: 2 commits new 4d529ac472 106: onsuccess: #1507: 2: Success after gcc: 2 commits new 1b95552f64 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] new d739d32436 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new ac104fbac2 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] new 1d146103d9 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new f376a863ad 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new c147d663b8 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new e6359ce4b5 113: onsuccess: #1514: 2: Success after gcc: 5 commits new bb5fe266d6 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new 345fbf4d6b 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new adfc0b0cc2 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new 09018cce40 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new 21b9e76506 118: onsuccess: #1519: 2: 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 (3025cd5256) \ 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 1700 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2704 bytes 04-build_abe-binutils/console.log.xz | Bin 51072 -> 50476 bytes 05-build_abe-bootstrap/console.log.xz | Bin 463000 -> 466292 bytes 06-check_regression/console.log.xz | Bin 2364 -> 2244 bytes 07-update_baseline/console.log | 36 +++++++++++++++++----------------- 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, 33 insertions(+), 33 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[glibc] branch release/2.36/master updated (52c037f357 -> 2628500f5d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch release/2.36/master in repository glibc. from 52c037f357 gconv: Use 64-bit interfaces in gconv_parseconfdir (bug 29583) new 2628500f5d m68k: Enforce 4-byte alignment on internal locks (BZ #29537) 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: NEWS | 1 + .../{arm/unwind-resume.c => generic/libc-lock-arch.h} | 16 ++++++++-------- sysdeps/nptl/libc-lock.h | 8 +++++++- sysdeps/nptl/libc-lockP.h | 3 ++- .../sysv/linux/m68k/libc-lock-arch.h} | 16 ++++++++-------- 5 files changed, 26 insertions(+), 18 deletions(-) copy sysdeps/{arm/unwind-resume.c => generic/libc-lock-arch.h} (72%) copy sysdeps/{arm/unwind-resume.c => unix/sysv/linux/m68k/libc-lock-arch.h} (71%) -- 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-stable-allyesconfig updated (7f71fa4031 -> bf9b819c10)

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-stable-allyesconfig in repository toolchain/ci/base-artifacts. from 7f71fa4031 9: onsuccess: #373: all: Success after binutils/gcc/linux: 2 [...] new bf9b819c10 10: onsuccess: #374: all: Success after binutils/gcc/linux/q [...] 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 1692 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30040 -> 29852 bytes 04-build_abe-stage1/console.log.xz | Bin 86892 -> 86892 bytes 05-build_abe-qemu/console.log.xz | Bin 31488 -> 31032 bytes 06-build_linux/console.log.xz | Bin 3296 -> 3296 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 2784 -> 3140 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- 17 files changed, 23 insertions(+), 23 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[binutils-gdb] branch master updated (0242db993f8 -> df86565b31b)

by git＠git.linaro.org

2 years, 2 months

[glibc] branch release/2.35/master updated (dee4146cec -> a7d5383328)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch release/2.35/master in repository glibc. from dee4146cec gconv: Use 64-bit interfaces in gconv_parseconfdir (bug 29583) new a7d5383328 m68k: Enforce 4-byte alignment on internal locks (BZ #29537) 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: NEWS | 1 + .../{arm/unwind-resume.c => generic/libc-lock-arch.h} | 16 ++++++++-------- sysdeps/nptl/libc-lock.h | 8 +++++++- sysdeps/nptl/libc-lockP.h | 3 ++- .../sysv/linux/m68k/libc-lock-arch.h} | 16 ++++++++-------- 5 files changed, 26 insertions(+), 18 deletions(-) copy sysdeps/{arm/unwind-resume.c => generic/libc-lock-arch.h} (72%) copy sysdeps/{arm/unwind-resume.c => unix/sysv/linux/m68k/libc-lock-arch.h} (71%) -- 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_bootstrap/master-aarch64-bootstrap updated (8a4e1a8641 -> 6eb851adc9)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap in repository toolchain/ci/base-artifacts. discards 8a4e1a8641 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards 004775957c 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards 9e385a6134 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards b40f544189 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards ca1624ef35 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards cdc3d227b1 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards c8e5284759 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards f3bf10280a 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards 50b85b0fd6 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards 9ffe4fba50 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 06bc6a9e64 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards e055bdb75d 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards 648207947f 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards 13fa47062d 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards 4c9eec84e9 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards 306183a809 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards 89db6e2ea8 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards 6a4085663e 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards c25a0d922f 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards b931abaa1c 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards 41a9930b16 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards e9432f924e 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards 4552e8cd00 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards fc0713bcb3 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards 3096fb00e3 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 0922cecb2b 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards ec93dcb141 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards 3af81d5ffe 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards 042b56ae73 88: onsuccess: 1: Success after gcc: 20 commits discards 5cd3784a5a 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards 63f899a67d 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards 3ed8e94159 85: onsuccess: 2: Success after binutils: 4 commits discards ce84e46477 84: onsuccess: 2: Success after gcc: 9 commits discards 12a86a3fbf 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards 61406802be 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards 3dab8f4d26 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards 153f229d15 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 44edeebe9a 79: onsuccess: 1: Successful build after gcc: 3 commits discards 0428a923c0 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 2dae5feabc 77: force: 2: Successful build after gcc: 32 commits discards 245f9addec 76: onsuccess: 2: Successful build after binutils: 10 commits discards 5475818846 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 63dcb8c860 74: onsuccess: 2: Successful build after gcc: 13 commits discards 3198c7baa0 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards b82ecdc334 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards ec74745de7 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 9583776b18 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards a44f4ce292 69: onsuccess: 2: Successful build after baseline build: no [...] discards 9f866201c0 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards f523a9f114 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 74b172ce3c 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards d645b7f1fa 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 30bbcc85d4 64: onsuccess: 2: Successful build after gcc: 7 commits discards 1d808817ca 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 75ca825274 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 867a6f233b 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards df58b5847f 60: onsuccess: 1: Successful build after gcc: 15 commits discards 2ce2182c24 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards b0ac6e638b 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards 38f1ef942d 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards e1fbdd9608 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 091e98e651 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 68e30af3e8 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 72a1af82fb 53: onsuccess: 2: Successful build after gcc: 5 commits discards 9b34d9b1aa 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 3bf1171fe9 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 3c6eff1da4 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 6b57e5483d 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 6d022937ee 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 2f261bd108 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 7a1fad35ec 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 9380423ec9 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards dad2b31714 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 89f6c730a1 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] discards aeb7f8a55f 42: onsuccess: 2: Successful build after gcc: 2 commits discards 9a76799733 41: onsuccess: 2: Successful build after baseline build: no [...] discards c74997ef6f 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards c9e91bfd80 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 1f93b6e2c5 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards f608ef867c 37: onsuccess: 2: Successful build after gcc: 2 commits discards 20fd2b760a 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 50022581ae 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards c0b106c5f1 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 86e174385d 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 6eb729de2f 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards afdb508889 31: onsuccess: 2: Successful build after gcc: 8 commits discards 8f58d68ec4 30: onsuccess: 2: Successful build after gcc: 7 commits discards f398bdd614 29: onsuccess: 2: Successful build after binutils: 5 commits discards 9506ac23db 28: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards cf7543333b 27: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards eded4ab001 26: onsuccess: 2: Successful build after binutils/gcc: 15 commits discards 1b5f4abc85 25: onsuccess: binutils-gcc: 2 discards c993f08d21 24: onsuccess: binutils-gcc: 2 discards 0235e662f9 23: onsuccess: binutils-gcc: 2 discards 78686bf20a 22: onsuccess: binutils-gcc: 2 discards ccd875e49c 21: onsuccess: binutils-gcc: 2 discards 201104d31c 20: onsuccess: binutils-gcc: 2 discards 52bb48ff57 19: onsuccess: binutils-gcc: 2 discards 8fbd8d2d4b 18: onsuccess: binutils-gcc: 2 discards b937c02404 17: onsuccess: binutils-gcc: 2 discards 30e765af05 16: onsuccess: binutils-gcc: 2 new 4d7fe30156 16: onsuccess: binutils-gcc: 2 new 528d4cf773 17: onsuccess: binutils-gcc: 2 new 93146c87de 18: onsuccess: binutils-gcc: 2 new 280b67aae0 19: onsuccess: binutils-gcc: 2 new 40e13c3c3a 20: onsuccess: binutils-gcc: 2 new eb8043e5ed 21: onsuccess: binutils-gcc: 2 new b496bf036b 22: onsuccess: binutils-gcc: 2 new dc45269dbf 23: onsuccess: binutils-gcc: 2 new d002822eb4 24: onsuccess: binutils-gcc: 2 new 482c1842a6 25: onsuccess: binutils-gcc: 2 new ccd7e675e9 26: onsuccess: 2: Successful build after binutils/gcc: 15 commits new bb1f641225 27: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 6ae6d31e93 28: onsuccess: 2: Successful build after binutils/gcc: 4 commits new b6bdd4ee84 29: onsuccess: 2: Successful build after binutils: 5 commits new 464affaeff 30: onsuccess: 2: Successful build after gcc: 7 commits new 621c2a0c81 31: onsuccess: 2: Successful build after gcc: 8 commits new b896252b95 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 4beb591e7a 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits new c7f14c80e6 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits new d893e86903 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 642de56273 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 1d9e1860d0 37: onsuccess: 2: Successful build after gcc: 2 commits new 19a0aa6279 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 6b240d9adf 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 5474f1df66 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 9cf86505fc 41: onsuccess: 2: Successful build after baseline build: no [...] new 4d4360c8ad 42: onsuccess: 2: Successful build after gcc: 2 commits new 136f6120fc 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new b60b7941ce 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 2a43e44dac 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new f79304ddda 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new a986553715 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 62f4a423c6 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 9d41a51e37 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new a1b201a693 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 2218fa9026 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new fb8422b60f 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new a690ad0a8d 53: onsuccess: 2: Successful build after gcc: 5 commits new e2a264f946 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new da6ab3b469 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 458f9c8cf3 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new cb215e78f4 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 4748c85525 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new a7b391e0ca 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 72c2337425 60: onsuccess: 1: Successful build after gcc: 15 commits new 7dc6162faf 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 7a8d6ceff3 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 5914c7225d 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 409ad6c404 64: onsuccess: 2: Successful build after gcc: 7 commits new a40c0ee48d 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 342d418353 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 2e5cbef3da 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 3d826b81f7 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new dd56222271 69: onsuccess: 2: Successful build after baseline build: no [...] new 0093627033 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 701f39029d 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 94780886b8 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new d75e031f96 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 5993ff8014 74: onsuccess: 2: Successful build after gcc: 13 commits new d7fa134644 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 66e97f3392 76: onsuccess: 2: Successful build after binutils: 10 commits new b1be050125 77: force: 2: Successful build after gcc: 32 commits new 2165bd0130 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 55b5606e50 79: onsuccess: 1: Successful build after gcc: 3 commits new bc1c1f90cd 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new a477772c4e 81: onsuccess: 2: Success after binutils/gcc: 16 commits new e9787a0683 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 7cc9c1c241 83: onsuccess: 2: Success after binutils/gcc: 7 commits new 2f8c8156b4 84: onsuccess: 2: Success after gcc: 9 commits new c60d885d06 85: onsuccess: 2: Success after binutils: 4 commits new 2b228550a8 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new 1bb88dc246 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new caeabcc4b8 88: onsuccess: 1: Success after gcc: 20 commits new 337972be3b 89: onsuccess: 2: Success after binutils/gcc: 39 commits new 4791ab5e36 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 7652d21772 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 5641a45342 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 19e663ecf7 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new b7f518c531 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new 7d332be8ad 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new e3e6dadb4d 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new bfaecfba88 97: onsuccess: #1481: 2: Success after gcc: 8 commits new 9ae8fdff22 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new eb7709e2d7 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new e463080f07 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new 5dffd20abe 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new b627f51cdb 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new daf1c24257 103: onsuccess: #1524: 2: Success after gcc: 2 commits new 8e8dbe9194 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new c8f93a13c0 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 468a26b71b 106: onsuccess: #1527: 2: Success after gcc: 2 commits new 1923ce36e5 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new aed7d7fd67 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new 71be4773fb 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new e4d5d03b47 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 32a6aaf944 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new aefd3f3f6e 112: onsuccess: #1533: 2: Success after gcc: 5 commits new aac66b181b 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new afb860e8ec 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new 543cc4432e 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new c15c887b7c 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 6eb851adc9 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 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 (8a4e1a8641) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1660 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 38288 -> 37700 bytes 05-build_abe-bootstrap/console.log.xz | Bin 271384 -> 268944 bytes 06-check_regression/console.log.xz | Bin 2324 -> 2184 bytes 07-update_baseline/console.log | 38 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 ++++++++-------- 13 files changed, 34 insertions(+), 34 deletions(-) -- 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