Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap updated (d61ddcbb13 -> b721a53d64)

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 d61ddcbb13 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] discards 1557265622 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits discards dcc8751c7d 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits discards 7a7a922740 139: onsuccess: #1566: 1: Success after gcc: 5 commits discards af0dbee057 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] discards eba784f4c0 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] discards fb041ba4c0 136: onsuccess: #1561: 2: Success after binutils: 3 commits discards 52046ff7cd 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits discards 01d8bb6c1d 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits discards 8067ae23d9 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits discards 0d65924b1d 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits discards 8d6eae0e0b 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits discards a6876737f3 130: onsuccess: #1554: 2: Success after gcc: 9 commits discards e79be4da83 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] discards 1a5fffa944 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards e4f6a77ff3 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] discards c059c6c5ad 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] discards 5d2dff8ca1 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards f91cb76422 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards 307573428c 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards 24f0d3370a 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 6ec32935de 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards 18a59dc3f4 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards 8273d194d8 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards 0ac402a1f4 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards 65248d2428 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards b258f715d9 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards 0681bbd016 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards 81eb149ae2 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards 483e6b5694 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards 8f1eb3b2f3 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards 0b507b3288 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards 673723d14a 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 542f8c4d6e 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards c522c61181 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards 400e8e6c56 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 2d0e5ace5d 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards e03d06225f 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards ed704332f0 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards a4c5e08857 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards 939b417c7a 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards 56a4fc0388 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards fbc33d5928 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards 3dd3ee9576 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards 70295c8fd8 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards e07fda5110 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards d07507c268 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards e6a8df4eee 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards aaa095dd46 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards 8ae88b5e5d 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards b3cde0353c 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 910e8bff15 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards 10d20ae65c 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards 1b37ac2fdc 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards 48302773a3 88: onsuccess: 1: Success after gcc: 20 commits discards 15cdd1eb2c 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards e006cab64c 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards 05baa890cf 85: onsuccess: 2: Success after binutils: 4 commits discards 40072a2a39 84: onsuccess: 2: Success after gcc: 9 commits discards 181e222a81 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards c7ac9bbd36 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards 2c54e1ea16 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards 0be4202811 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 25914de365 79: onsuccess: 1: Successful build after gcc: 3 commits discards 9698ccefce 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 17b90a2539 77: force: 2: Successful build after gcc: 32 commits discards 5d9d7c6fa0 76: onsuccess: 2: Successful build after binutils: 10 commits discards d4dda51522 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 3de611b9dc 74: onsuccess: 2: Successful build after gcc: 13 commits discards b14b850b71 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards d694358cc6 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards cef193f809 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 17b233b1e1 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 079337575e 69: onsuccess: 2: Successful build after baseline build: no [...] discards 82df31960d 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards eff327312c 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 3fcb3b306c 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards 0586d8b9b6 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 4333b2800d 64: onsuccess: 2: Successful build after gcc: 7 commits discards 850a74c629 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 4758f8de94 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards a46f45d2e2 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards 0e2b130125 60: onsuccess: 1: Successful build after gcc: 15 commits discards 21b291f444 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards ef6e76c601 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards 746a589261 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards 5b53a91141 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards ce72b8dc9f 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 71c3ebfc9a 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 4c1657efc0 53: onsuccess: 2: Successful build after gcc: 5 commits discards 9cbb37b7d4 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards d0c83457c7 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 098f8f7aec 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 744599b3da 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 470ee5df1d 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards aa392cb1ad 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 79a0125829 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 06e4b189c9 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards ddc7f5613c 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards d45bfae2b7 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] discards 49311f5c3a 42: onsuccess: 2: Successful build after gcc: 2 commits new d82e367d8f 42: onsuccess: 2: Successful build after gcc: 2 commits new 8ebc7de16b 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new d6015fd7b5 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new f11ef52def 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new a88c518f96 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new ce85bff53a 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new a4e7c553aa 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 0b80d778e8 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 2681a96aca 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new c3ff845b96 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new a92791edc4 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 8859bd7423 53: onsuccess: 2: Successful build after gcc: 5 commits new 302df28d35 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 16b9478125 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new d723014e30 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 8bab4aea72 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 59c4c0c747 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new 3e6dfd59b9 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 799a54e448 60: onsuccess: 1: Successful build after gcc: 15 commits new a1ef177779 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new a105c79cb9 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 645d55db21 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 9ef0685b0e 64: onsuccess: 2: Successful build after gcc: 7 commits new 5c64e704ae 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new d119904856 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 68fda19d4f 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 776859926b 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new f77e97724c 69: onsuccess: 2: Successful build after baseline build: no [...] new c7140e48b3 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 7abd7065f8 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 2da2369004 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 25d6b2d336 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 8549b36f9d 74: onsuccess: 2: Successful build after gcc: 13 commits new 934c73b244 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new f3e5e06dbf 76: onsuccess: 2: Successful build after binutils: 10 commits new 3f9b94e076 77: force: 2: Successful build after gcc: 32 commits new b018776a85 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 0ec2b1aecc 79: onsuccess: 1: Successful build after gcc: 3 commits new f241733788 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 40a8fcf668 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 1c788a79cc 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 28b471ff0a 83: onsuccess: 2: Success after binutils/gcc: 7 commits new 9f9d7a0c33 84: onsuccess: 2: Success after gcc: 9 commits new b3533c1cfe 85: onsuccess: 2: Success after binutils: 4 commits new 597d5bae0f 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new 22db97d9fd 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new ac87c3d470 88: onsuccess: 1: Success after gcc: 20 commits new 91d79f3538 89: onsuccess: 2: Success after binutils/gcc: 39 commits new 15c77bbf8e 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 9efdb80e6f 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 6c0fba64f9 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 996d3c4887 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new b04940768e 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new 8020a54b39 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new 4e1b8d523a 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 9e5fc61408 97: onsuccess: #1481: 2: Success after gcc: 8 commits new f736f1f98c 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new d8948cda8d 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new 41e03433e7 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new a7486bdffd 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new 654d968bfd 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new 6db0bdbb1f 103: onsuccess: #1524: 2: Success after gcc: 2 commits new 57e28253ed 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 4333429aff 105: onsuccess: #1526: 2: Success after gcc: 2 commits new a685304c92 106: onsuccess: #1527: 2: Success after gcc: 2 commits new 9137420bea 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new 669f8c689e 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new 6fc9a2be25 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new 0b71ac8643 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new d8164a8a45 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new caf4f9af2f 112: onsuccess: #1533: 2: Success after gcc: 5 commits new 96e3f4a1cc 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new 37fabfd79b 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new bfac9a1fec 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new 41e65df0da 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 935571ad1d 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new 83cf4376dd 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new efad3665d5 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new f3869da67b 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new 4023415c52 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new be50ea5e24 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new a70152c538 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new c5e487bc0b 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new 334a74405e 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new 6959193559 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] new 2f45cad5ac 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] new e9c3847eda 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new 61d2e43fb9 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] new f81385134f 130: onsuccess: #1554: 2: Success after gcc: 9 commits new a1072df597 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits new 95ecfe5d38 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits new 4a3d6a598f 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits new e3dc3263a6 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits new 816b54f8ce 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits new 46fc25c5fe 136: onsuccess: #1561: 2: Success after binutils: 3 commits new eeeae63b7f 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] new 787df8d6d6 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] new 8f31cf030e 139: onsuccess: #1566: 1: Success after gcc: 5 commits new 3bf2cdcb54 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits new 60d42435ef 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits new 6686a2cca7 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] new b721a53d64 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 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 (d61ddcbb13) \ 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 1676 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2716 bytes 04-build_abe-binutils/console.log.xz | Bin 37768 -> 37652 bytes 05-build_abe-bootstrap/console.log.xz | Bin 79884 -> 272200 bytes 06-check_regression/console.log.xz | Bin 2536 -> 2844 bytes 06-check_regression/mail-body.txt | 2 +- 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 | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 18 ++++++++-------- results | 2 +- 15 files changed, 37 insertions(+), 37 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_O3 updated (88dd459c9a -> 3b14253afe)

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_O3 in repository toolchain/ci/base-artifacts. from 88dd459c9a 47: onsuccess: #463: 2: Success after binutils: 11 commits new 3b14253afe 48: force: #466: 2: Success after gcc: 2 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 1616 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2712 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 50732 -> 50936 bytes 05-build_abe-bootstrap_O3/console.log.xz | Bin 461924 -> 461516 bytes 06-check_regression/console.log.xz | Bin 2684 -> 2500 bytes 07-update_baseline/console.log | 9 +++++++++ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++++--------- 12 files changed, 23 insertions(+), 14 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (8ace67ddb97 -> 2813f529ab8)

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 8ace67ddb97 OpenACC: whole struct vs. component mappings (PR107028) new 2813f529ab8 Robustify DWARF2_UNWIND_INFO handling in vx-common.h The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/config/vx-common.h | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch devel/omp/gcc-12 updated (d21bfef9867 -> c455181c13a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch devel/omp/gcc-12 in repository gcc. from d21bfef9867 OpenMP: Fix ICE with OMP metadirectives adds 6a59baca1f2 aarch64: Add Arm Neoverse V2 support adds 7f323c284f7 Daily bump. adds afea1ae84f0 OpenACC: Fix reduction tree-sharing issue [PR106982] adds 85adc2ec2b0 libstdc++: Disable volatile-qualified std::bind for C++20 new c455181c13a Merge branch 'releases/gcc-12' into devel/omp/gcc-12 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/ChangeLog | 24 +++++++++++++ gcc/DATESTAMP | 2 +- gcc/config/aarch64/aarch64-cores.def | 3 +- gcc/config/aarch64/aarch64-tune.md | 2 +- gcc/config/aarch64/aarch64.cc | 40 +++++++++++----------- gcc/doc/invoke.texi | 2 +- gcc/omp-low.cc | 3 +- gcc/testsuite/c-c++-common/goacc/reduction-10.c | 12 +++++++ gcc/testsuite/c-c++-common/goacc/reduction-9.c | 22 ++++++++++++ libstdc++-v3/doc/html/index.html | 2 +- libstdc++-v3/doc/html/manual/api.html | 5 +++ libstdc++-v3/doc/html/manual/appendix.html | 2 +- libstdc++-v3/doc/html/manual/appendix_porting.html | 2 +- libstdc++-v3/doc/html/manual/bugs.html | 6 ++++ libstdc++-v3/doc/html/manual/index.html | 2 +- libstdc++-v3/doc/html/manual/using_macros.html | 5 +-- libstdc++-v3/doc/xml/manual/evolution.xml | 13 +++++++ libstdc++-v3/doc/xml/manual/intro.xml | 9 +++++ libstdc++-v3/doc/xml/manual/using.xml | 5 +-- libstdc++-v3/include/std/functional | 32 ++++++++++++----- libstdc++-v3/testsuite/20_util/bind/cv_quals.cc | 25 +++++++------- libstdc++-v3/testsuite/20_util/bind/cv_quals_2.cc | 12 ++++--- 22 files changed, 172 insertions(+), 58 deletions(-) create mode 100644 gcc/testsuite/c-c++-common/goacc/reduction-10.c create mode 100644 gcc/testsuite/c-c++-common/goacc/reduction-9.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (1139d8ac3b -> b3a3eda6d3)

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 1139d8ac3b 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 463c766e66 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards bc891b5142 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 3b5f35ecd7 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 9d218c2a3d 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 80aa576bab 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 39f72b6698 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 158071ea41 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards b9632f663a 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 8ed8d32624 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards ca4d6a6510 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 0da1a44124 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 0e23b05463 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 671003c5c2 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 866dbb0d68 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 5ca3ee394e 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 9b0b1126ab 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 334d891da9 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 4a37007b09 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 0f9d9b1723 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 4a14d4b46d 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards aebdf38b4d 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 0579d8a661 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 54a61dbdbe 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards e24f858d82 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 6e2493710e 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 9bbe76e978 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards b466195bda 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 5484c39d43 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards d47cdf8ccd 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 6d85b2fc45 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 41126571a4 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards b6061acb2c 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 3c88a53a57 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards a7855cdba0 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards c315f8eac1 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards e11aeb06fe 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 98eb215c0a 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 63b0fbbfd9 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards f77a9b92ad 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 5e8f5447f0 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 88ee46ad07 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards faffd6ae1a 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards fbd01253f9 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards c5619311d7 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 71d9cb2fb1 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 0fe6f1395d 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards a54dbe5655 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards a708f21d00 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 0ec5dda0d4 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards b661267529 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 8a251fcaed 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards c109b84786 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards f41b4ee6bc 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 78563de238 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 0c43d5dc4c 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards a0fa58a3d4 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 72e536a5e6 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 53151de7f2 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards d89313c804 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 215f852926 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards a1c6a74bbd 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 12a022585a 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 5e28550051 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 03c0446036 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards be06f36853 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 373f42b739 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2020e67970 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d7151ff46f 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 9b340b71e9 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 92128c097f 74: onsuccess: 1: Successful build after linux: 44 commits discards d9349784b2 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 98fd3995e7 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e3486a7870 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 90433f65c6 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 42892ec333 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 041a5ce933 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 60a24b5f50 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f63fb509da 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2f7cb3b3ef 65: onsuccess: 1: Successful build after gcc: 4 commits discards 507147954a 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 91df097aa8 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f0f5b3b4c8 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 9d0884c8fa 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards b0a4cf828c 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 0cedca4746 59: onsuccess: 1: Successful build after glibc: 2 commits discards 89cfa01365 58: onsuccess: 1: Successful build after binutils: 2 commits discards 8f26877a37 57: onsuccess: 1: Successful build after gcc: 7 commits discards 63acfad8e2 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 943dae5422 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b72b8a190c 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 5e2f7eacd0 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 544e84aabe 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 76f85c34a9 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 694635dd55 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0ba2e9e9ec 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b35490f38b 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 0220b075c2 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 554f22c21b 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 2e71989c2b 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d2d281ad8b 44: onsuccess: 1: Successful build after linux: 34 commits new 1920b959e7 44: onsuccess: 1: Successful build after linux: 34 commits new 91792a0685 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5610f5c660 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new f9144999a3 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ce30b6eb82 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 10901925c3 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4823d07ac3 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 113e03b9bf 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 1d58eee885 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 59cf0a1927 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 42e9663b57 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new c9d7f03c01 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 10e868562e 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3371a33d13 57: onsuccess: 1: Successful build after gcc: 7 commits new 157e52e7e5 58: onsuccess: 1: Successful build after binutils: 2 commits new 8145fb89ef 59: onsuccess: 1: Successful build after glibc: 2 commits new 9c69f3243d 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 46a063874e 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 550f38123f 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new ea8e97acf3 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4c7fca1d0f 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5b980fcdc4 65: onsuccess: 1: Successful build after gcc: 4 commits new 8653184f9d 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 7a0f5e6848 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b498021980 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 45a8afc39f 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 652bc1f8f0 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 9e0c672c91 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 480ee871f6 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c872ba969c 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 564dd1b825 74: onsuccess: 1: Successful build after linux: 44 commits new b729e6ff33 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c7574b31e6 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 23163b8a6e 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ffa685b59c 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d2d515a769 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new c75900cec8 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new a5b9795816 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 568f9af514 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new cba390dde4 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 551455183a 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 413adb07e2 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 25350e8523 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 0d0de87a90 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 349e2f6b7e 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 740efe8f33 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new e2d0c4c5b1 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 67eca9c795 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new fe4a1797fc 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 6a645fd8af 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new c7382f5076 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new c371120b3b 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 50f5454927 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 9cb4f6456e 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new c8cec07c41 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 265f9593f9 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new a1d28eb9f7 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new b779edb46e 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 30a6d55f2c 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new f3d583b9e0 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 8b5b1bfdf8 104: onsuccess: #1697: 1: Success after gcc: 4 commits new d3a210355a 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 7a85376ae6 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new fbe9ae9613 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new ddb8cc6711 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new e3d833e7ac 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 24178bf72c 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 91d5299be2 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 76bbe6403c 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 3c628c7570 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new a10cbad86f 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 74cda48d2c 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 12a8623527 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 6bfa4391a1 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 478311b062 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 8c362f4a71 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 3d6e6fd3e1 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new e6e1039018 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 9abae44c4e 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 41e460cbfb 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new a60d90b19a 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new a56e504664 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 600564e810 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 351fbd6001 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 73d756dc16 128: onsuccess: #1723: 1: Success after linux: 12 commits new 47f5b4b18a 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 79634f672f 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 4ef8f496eb 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new a197939054 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 4c0a87fef4 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 4547d0653d 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 2027e73ee8 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 274efb7543 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 98585fa269 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 82e0cf73e0 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 1247ce43f5 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 604ea28b7d 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 6c7b32e490 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new ef3940e156 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 48281eb9fc 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new cd1476d2ff 144: onsuccess: #1743: 1: Success after glibc: 2 commits new b3a3eda6d3 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] 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 (1139d8ac3b) \ 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 1696 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30072 -> 29976 bytes 04-build_abe-stage1/console.log.xz | Bin 90416 -> 90404 bytes 06-build_abe-linux/console.log.xz | Bin 8740 -> 8740 bytes 07-build_abe-glibc/console.log.xz | Bin 233824 -> 233500 bytes 08-build_abe-stage2/console.log.xz | Bin 223580 -> 223708 bytes 09-build_abe-gdb/console.log.xz | Bin 37208 -> 37104 bytes 10-build_abe-qemu/console.log.xz | Bin 31400 -> 31188 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2444 -> 2784 bytes 13-check_regression/console.log.xz | Bin 5344 -> 6116 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 7 + 13-check_regression/mail-body.txt | 53 +- 13-check_regression/results.compare | 25 +- 13-check_regression/results.compare2 | 65 +- .../results.regressions | 60 +- 14-update_baseline/console.log | 40 +- 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 | 55 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 27 + sumfiles/g++.log.xz | Bin 2656996 -> 2662716 bytes sumfiles/g++.sum | 53 +- sumfiles/gcc.log.xz | Bin 2191892 -> 2225572 bytes sumfiles/gcc.sum | 2310 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 881792 -> 883416 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201280 -> 201160 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 427888 -> 421504 bytes sumfiles/libstdc++.sum | 10 +- 42 files changed, 1400 insertions(+), 1360 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum copy mail/mail-body.txt => 13-check_regression/results.regressions (73%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch releases/gcc-12 updated (afea1ae84f0 -> 85adc2ec2b0)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-12 in repository gcc. from afea1ae84f0 OpenACC: Fix reduction tree-sharing issue [PR106982] new 85adc2ec2b0 libstdc++: Disable volatile-qualified std::bind for C++20 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: libstdc++-v3/doc/html/index.html | 2 +- libstdc++-v3/doc/html/manual/api.html | 5 ++++ libstdc++-v3/doc/html/manual/appendix.html | 2 +- libstdc++-v3/doc/html/manual/appendix_porting.html | 2 +- libstdc++-v3/doc/html/manual/bugs.html | 6 ++++ libstdc++-v3/doc/html/manual/index.html | 2 +- libstdc++-v3/doc/html/manual/using_macros.html | 5 ++-- libstdc++-v3/doc/xml/manual/evolution.xml | 13 +++++++++ libstdc++-v3/doc/xml/manual/intro.xml | 9 ++++++ libstdc++-v3/doc/xml/manual/using.xml | 5 ++-- libstdc++-v3/include/std/functional | 32 ++++++++++++++++------ libstdc++-v3/testsuite/20_util/bind/cv_quals.cc | 25 +++++++++-------- libstdc++-v3/testsuite/20_util/bind/cv_quals_2.cc | 12 ++++---- 13 files changed, 87 insertions(+), 33 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (9ca14715407 -> 8ace67ddb97)

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 9ca14715407 c++: implement __remove_cv, __remove_reference and __remove_cvref new 8ace67ddb97 OpenACC: whole struct vs. component mappings (PR107028) 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/gimplify.cc | 177 ++++++++++++++++----- .../c-c++-common/goacc/struct-component-kind-1.c | 72 +++++++++ gcc/testsuite/g++.dg/goacc/pr107028-1.C | 14 ++ gcc/testsuite/g++.dg/goacc/pr107028-2.C | 27 ++++ .../gfortran.dg/goacc/mapping-tests-5.f90 | 15 ++ 5 files changed, 268 insertions(+), 37 deletions(-) create mode 100644 gcc/testsuite/c-c++-common/goacc/struct-component-kind-1.c create mode 100644 gcc/testsuite/g++.dg/goacc/pr107028-1.C create mode 100644 gcc/testsuite/g++.dg/goacc/pr107028-2.C create mode 100644 gcc/testsuite/gfortran.dg/goacc/mapping-tests-5.f90 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (0e450c4050 -> d6530f261f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-arm in repository toolchain/ci/base-artifacts. discards 0e450c4050 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards c74269847b 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] discards dfa46f0bc7 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] discards 8cb73a2704 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] discards 2b75270ead 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits discards e9adc6be33 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] discards a2fce2d045 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] discards aab6586d07 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards ffe157781c 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] discards 0ffaa7d557 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards de28e2da7a 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards 2f9f6e1c94 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards 78401fc033 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 0b1d344518 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards 24a1b46f5c 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards 0eccba9e39 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards ac4b44cbe8 132: onsuccess: #1645: 7: Success after linux: 23 commits discards f5ef1b8a73 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards 01fe335a9c 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards 15d129d94f 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards ed1a334ab0 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards a8a646d7d7 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards 7d1ef7d08d 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards 699026b62d 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards 5d3aa416c9 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards 8c7409c203 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards b35e71bf2e 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards 1eb774690f 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards e6cbf57003 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards e6c3a0e3d2 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards eb7cc6938d 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards 28a04c87b4 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards c61efe34a6 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards 329e62e261 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 6195437743 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards 8a17e6d3a6 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 92486f3329 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards c83fb5d894 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 2d95d44627 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards bf50503a4e 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards 2013e02010 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards adc833bb7a 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 95fb0de08c 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 6f6ee50ba2 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards bb999932ec 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 8f10e6136f 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards 7246b5c67c 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards ee18cf8992 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards a2c2127b23 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 26dfef6cdb 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 6d37a8bf18 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 409276c33d 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards c17cf89d05 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards 8712785abe 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards d2bc86ee03 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 444b594cb9 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards 8b34b0b212 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 44b98830db 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 844c5f0559 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2d751ecb9b 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards d6157808c3 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 6aa4cbf6e1 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards d4bd1f2b55 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards f7227d66a1 85: onsuccess: 7: Success after gcc: 9 commits discards eddfe90183 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 71030aca5d 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards ea44cea991 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards badb0cb0d2 81: onsuccess: 7: Successful build after gcc: 2 commits discards b70ae6f1d5 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 59821011b6 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards e288ddc198 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 2c63a0c121 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards f9c374547c 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards cc62366a99 75: onsuccess: 7: Successful build after linux: 44 commits discards e2a3972772 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 964c15b440 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 2e91e3e9bc 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards f9b886f8f7 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards cc447a4578 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards a936552b19 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards b77953f8ac 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards fe71749136 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards d1d8ea4296 66: onsuccess: 7: Successful build after gcc: 3 commits discards 2a00ba64ad 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards a42e9293d2 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 702ac8ac91 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards a4b370ab50 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 248e298876 61: onsuccess: 4: Successful build after gcc: 15 commits discards cafb1df2e5 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 32a7e61b7b 59: force: 7: Successful build after gcc: 2 commits discards e3f3997672 58: onsuccess: 7: Successful build after glibc: 2 commits discards 62d7d469fd 57: onsuccess: 7: Successful build after gcc: 7 commits discards 21a3fa3df3 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 7a659584ad 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 57a4d2ecfa 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards 17e35fac2e 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards d8669aba3f 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards f57dde32af 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 5345ba7cb0 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 7fbeb13d12 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 19c7454b79 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new 4fc04d0fbe 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new 53b44d0a0f 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 1f8ff07fa0 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new d76a646edd 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 69274a5aef 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 720b238f81 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 68d77a174b 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new f512d3f4dd 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 6a3208a7b3 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new a09b4234a3 57: onsuccess: 7: Successful build after gcc: 7 commits new c62006d1f9 58: onsuccess: 7: Successful build after glibc: 2 commits new 1be39ec317 59: force: 7: Successful build after gcc: 2 commits new 2582c51851 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 1f77b5de7b 61: onsuccess: 4: Successful build after gcc: 15 commits new a6bdaa32cd 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new f4a0ae7fca 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 9ac2396cc8 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 22a29326a4 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 119f12ca9d 66: onsuccess: 7: Successful build after gcc: 3 commits new 1d9d1c6075 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 61aaa4d033 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new e5baf782cf 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 4ec89117de 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 25420a705e 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 804b1ad909 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new b8d6a3aa9b 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new e7e91712f8 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 98de1353e0 75: onsuccess: 7: Successful build after linux: 44 commits new 3bf23d4a55 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new c0a8c6d78b 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 9e853744d6 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 37e89df739 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 1309e5aa52 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new dea433b0bf 81: onsuccess: 7: Successful build after gcc: 2 commits new b1665ed8f6 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 8ecaf0ee5f 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 2504d485c1 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 506896a745 85: onsuccess: 7: Success after gcc: 9 commits new c3a7903478 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 4bb1925841 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new d96080d56e 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 8c27c939c6 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 1d7de50a5d 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new a5de335d1b 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new b3c9b397bb 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 7b100e76c9 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new c40eabec47 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 7b65713e6d 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new 8c3b333966 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new b4359b6b05 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new 88cdb26c38 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 32fdf7d18e 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new 1c2606693b 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new 7380c3392c 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 4316464788 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 8aeebbfdbf 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 01a9c4283e 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new d3ea949392 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new a7ca685515 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 942e893117 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 7e603acff7 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new dcc6688543 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new c5ec308fc3 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new ef727d7ad1 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 400bbd6ab7 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 3265a194bb 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 1ad91195be 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new 63197181b6 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 656d76f4cf 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new d012f54652 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new bdf77a9a77 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new df2634c3d0 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 269119eee2 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 138dd11ce8 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new 78268e2576 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new 925befb799 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new 1bfe9ae672 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new 6f7508f0d7 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new 1a065730fd 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new aa10567db8 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new e101ca99d0 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new ceea326da7 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new 9dea480071 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new 64c4e22f2e 131: onsuccess: #1644: 7: Success after gcc: 10 commits new b247abb051 132: onsuccess: #1645: 7: Success after linux: 23 commits new 0a7d9940e2 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new a1d426551e 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new 93221a84a8 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new e477e1b269 136: onsuccess: #1650: 7: Success after binutils: 2 commits new e86e925866 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new 0d866e2382 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new b93336df1b 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 4ef3ca9455 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] new 0276a34e79 141: onsuccess: #1656: 7: Success after gcc: 7 commits new ff2d4fd0ad 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] new 6f9ead865a 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] new bcc0bd7205 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits new f868739e05 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] new 0462501b71 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] new 066f13e31c 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] new 6345e70693 148: onsuccess: #1663: 7: Success after glibc: 2 commits new d6530f261f 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] 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 (0e450c4050) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1672 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2748 bytes 04-build_abe-binutils/console.log.xz | Bin 30000 -> 30156 bytes 05-build_abe-stage1/console.log.xz | Bin 90620 -> 90744 bytes 07-build_abe-linux/console.log.xz | Bin 8740 -> 8752 bytes 08-build_abe-glibc/console.log.xz | Bin 233984 -> 234296 bytes 09-build_abe-stage2/console.log.xz | Bin 224076 -> 224192 bytes 10-build_abe-gdb/console.log.xz | Bin 37256 -> 37360 bytes 11-build_abe-qemu/console.log.xz | Bin 30752 -> 30724 bytes 12-check_regression/console.log.xz | Bin 3208 -> 3616 bytes 13-update_baseline/console.log | 40 +++++++++++++++++------------------ 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++-------------- 19 files changed, 43 insertions(+), 43 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (1608fb57ac -> 1e19841957)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards 1608fb57ac 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards a392e8e189 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] discards 5eb202c8b7 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards 0b83a73933 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards 677bcf0a43 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards 6c1fe8d597 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards b35bc69880 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards 77a62676b8 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards 660c7d4063 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards 4e640a60d5 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards 61c42f75a2 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards 2ce318254f 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards 657bee8521 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards 276193ae86 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards 28c197beb1 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards c20ff71e7d 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards 6fbc39707a 128: onsuccess: #1579: 7: Success after linux: 12 commits discards a0904b0c8b 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards ed775bfba5 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards 114b1294d9 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards ab207b91d8 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards fa2c81136e 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards ab53b54ba2 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards 2114849a56 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards 41267028a9 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards 94ae4fe79b 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards 5814124d80 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards 5ee6fc3ca8 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards 9f36d754ae 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards 016ddfb593 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards 2ead423aec 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards e70ae3ce9a 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards e62132ff72 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards 73fa349dc0 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards 7b64d923f6 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 1070d964fd 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards ba4c46b155 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards 91c5e1659a 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards 80eba1bdec 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards 63601c2254 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards a077d5a6ad 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards 595a263522 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards cefe1a691a 102: force: #1551: 1: Failure after gcc: 306 commits discards c13360c68b 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 6e9548f9e1 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards 2ac0c58945 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 0b9dd6b174 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards 4235756c93 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards d135ea501e 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards c3ce5fd723 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 7fc467c9bb 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 4a8e9f05c8 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards c4b39892c1 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards ca474b655a 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards f9fd814ab3 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 506e496c5e 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 7a71dd83ed 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 7f4b69f097 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards a3bd21fbe3 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 130307f612 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 67c485e519 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 9217f494e9 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 582d40ad1c 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards e2d1de9ace 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 21f3ddefe2 80: onsuccess: 7: Successful build after linux: 44 commits discards 7d60429efa 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards d44d959349 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards 1eb4c378ab 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 0e0e237234 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 94217c442d 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards b1b3e267f6 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 306a952b5f 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards c8dc40ff62 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 26e0a19bd5 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 7a5b5e7ab3 70: onsuccess: 7: Successful build after gcc: 4 commits discards d51846f44c 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 5c2e90038e 68: onsuccess: 7: Successful build after linux: 6 commits discards 30d41f8878 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards e1fae8d8df 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards a90ed9a9a9 65: onsuccess: 7: Successful build after binutils: 3 commits discards e2021d0319 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards f9b8ec8227 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 26aab64ddb 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 4c55885145 61: onsuccess: 4: Successful build after gcc: 5 commits discards f3a0adbb9f 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 11f227a670 59: force: 7: Successful build after gcc: 3 commits discards 14d03ece5f 58: onsuccess: 7: Successful build after glibc: 2 commits discards d3dda06e55 57: onsuccess: 7: Successful build after gcc: 7 commits discards 80142a75d2 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 5c3017c3ea 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 3e5e413ab1 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards b734e0af4e 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards d9f1dc8164 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] discards bdb7de9528 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 5be8be9670 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 47f1257626 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 7c1b8dd748 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards c3161ec54c 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards a296b10e5b 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 69a7f80a3c 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 3cc7d88334 44: onsuccess: 7: Successful build after linux: 34 commits new 33c9990c8b 44: onsuccess: 7: Successful build after linux: 34 commits new c611eabc94 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b4b9960730 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new c3fec7a673 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 47f81de66d 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new dcab99e659 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new b136fab777 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 51a18cd7be 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 23b189f4ad 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] new 983922fdd1 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 482fd9e4b0 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new b14c382d1f 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ecac08c760 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 25a0b93676 57: onsuccess: 7: Successful build after gcc: 7 commits new 1102529db2 58: onsuccess: 7: Successful build after glibc: 2 commits new 81f75dbd2f 59: force: 7: Successful build after gcc: 3 commits new ff397ebab8 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 7f46bd7839 61: onsuccess: 4: Successful build after gcc: 5 commits new e600e6c018 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 84d97e89fc 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new b1bec66a1d 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 60ac9f40f5 65: onsuccess: 7: Successful build after binutils: 3 commits new e9b915a12d 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new 0de15cc67c 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new 0d42a69d7e 68: onsuccess: 7: Successful build after linux: 6 commits new 72518cc697 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new a2f315256a 70: onsuccess: 7: Successful build after gcc: 4 commits new e0762cb537 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 9d18a29244 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 38d6712da6 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 07b81f00e3 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new b3d61e6d3b 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new ee7ac12794 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new e39a611953 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 9f4aba3808 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new 899e3094d6 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new b2d43795f0 80: onsuccess: 7: Successful build after linux: 44 commits new 03aefd0e13 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f96731877e 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 11f85e1080 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 42cd5b2d91 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 79c25311fc 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new e26edace3f 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new ff709cda05 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new f4c82a3fc9 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 6a4d2a7448 89: onsuccess: 7: Success after gcc/glibc: 8 commits new 825e5eae66 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new f977f75e71 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new fdec9fd056 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 619135dfda 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new e22ff0c592 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 00553caef0 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 62fa0b9299 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 19fb64dd87 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new e4642183c0 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 7b003cb7b0 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new ae41d796b8 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new 0893cec85a 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 1641d792ec 102: force: #1551: 1: Failure after gcc: 306 commits new c25c0e6a29 103: onsuccess: #1552: 1: Success after gcc: 5 commits new 61ec1f70e3 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new 3af62f8585 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new 4f9bfec796 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new f6a9c8d18b 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new f56dd7cc93 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new e92e43fe81 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 03e6824170 110: onsuccess: #1559: 7: Success after gcc: 4 commits new cb23a3f2aa 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new 661a67ccb7 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new 4b34706f94 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new fe462ea881 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new 6ee0f030cc 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new 72a6fbe92b 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new 0f3f621714 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new 924862b98a 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new dee536bf13 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new 39b47aa86c 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new 988c2d9e86 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new 0ecd6e53f6 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new 746392038d 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new 99778d7bb6 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new a9a841a24c 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new 54c4068be2 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new 3af2f0cea6 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new 202287a651 128: onsuccess: #1579: 7: Success after linux: 12 commits new 24cd24bedb 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new 5b4a734a68 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new 8d384e115c 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new 2189cf906b 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new 2d3c935584 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new 1d1ff103a9 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new c13df413e7 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new 803e535ca4 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new 89dff9c728 137: onsuccess: #1588: 7: Success after gcc: 5 commits new a5141addeb 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new 9a2041b260 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new 4d4ee9c7ed 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new 377969a37c 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new d5e8d43b52 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new 14182854ad 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] new 4d6c4da64a 144: onsuccess: #1595: 7: Success after glibc: 2 commits new 1e19841957 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] 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 (1608fb57ac) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1720 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2752 bytes 04-build_abe-binutils/console.log.xz | Bin 30208 -> 30260 bytes 05-build_abe-stage1/console.log.xz | Bin 72192 -> 72600 bytes 06-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 07-build_abe-linux/console.log.xz | Bin 8732 -> 8740 bytes 08-build_abe-glibc/console.log.xz | Bin 239840 -> 239624 bytes 09-build_abe-stage2/console.log.xz | Bin 202672 -> 203140 bytes 10-build_abe-gdb/console.log.xz | Bin 37300 -> 37444 bytes 11-build_abe-qemu/console.log.xz | Bin 31544 -> 31544 bytes 12-check_regression/console.log.xz | Bin 3328 -> 3616 bytes 13-update_baseline/console.log | 38 +++++++++++++++++------------------ 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++--------------- 20 files changed, 42 insertions(+), 42 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-stable-allyesconfig updated (7ad1c65299 -> 6d4d7c38e9)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-stable-allyesconfig in repository toolchain/ci/base-artifacts. from 7ad1c65299 13: onsuccess: #486: all: Success after binutils: 25 commits new 6d4d7c38e9 14: onsuccess: #488: all: Success after v7.1.0-446-g99d6b11b [...] 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 1892 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30364 -> 30436 bytes 04-build_kernel_llvm/console.log.xz | Bin 65044 -> 64884 bytes 05-build_abe-qemu/console.log.xz | Bin 32144 -> 32232 bytes 06-build_linux/console.log.xz | Bin 3368 -> 3364 bytes 07-boot_linux/console.log.xz | Bin 576 -> 576 bytes 08-check_regression/console.log.xz | Bin 2912 -> 2752 bytes dashboard/dashboard-generate.sh | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++++++---------- 14 files changed, 15 insertions(+), 15 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits September 2022