Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[gcc] branch master updated (c263c3eba89 -> e205ec03f07)

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 c263c3eba89 gcov: annotate uncovered branches [PR107537] new e205ec03f07 libgfortran's ISO_Fortran_binding.c: Use GCC11 version for [...] 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: libgfortran/runtime/ISO_Fortran_binding.c | 151 ++++------------------- libgomp/testsuite/libgomp.fortran/allocate-4.f90 | 42 +++++++ 2 files changed, 64 insertions(+), 129 deletions(-) create mode 100644 libgomp/testsuite/libgomp.fortran/allocate-4.f90 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_O1 updated (5b022c959f1 -> 8950c5c4251)

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_O1 in repository toolchain/ci/base-artifacts. discards 5b022c959f1 131: onsuccess: #531: 2: Success after binutils/gcc: 47 commits discards bca34dea5b0 130: onsuccess: #530: 2: Success after binutils/gcc: 12 commits discards d771132f635 129: onsuccess: #529: 2: Success after binutils/gcc: 3 commits discards e69b409c89f 128: onsuccess: #528: 2: Success after binutils/gcc: 31 commits discards bb67d11ad74 127: onsuccess: #527: 2: Success after binutils/gcc: 33 commits discards fb601f8edd6 126: onsuccess: #526: 2: Success after binutils/gcc: 27 commits discards 34de9e4cfb6 125: onsuccess: #525: 2: Success after binutils/gcc: 47 commits discards b9ae28e9724 124: onsuccess: #524: 2: Success after binutils/gcc: 34 commits discards 54b2d79ebaa 123: onsuccess: #523: 2: Success after binutils/gcc: 13 commits discards 32c35f37434 122: onsuccess: #522: 2: Success after binutils/gcc: 6 commits discards 0d7d27a4bb3 121: onsuccess: #521: 2: Success after binutils/gcc: 31 commits discards 3e3966d1973 120: onsuccess: #520: 2: Success after binutils/gcc: 54 commits discards 399f26f2897 119: onsuccess: #519: 2: Success after binutils/gcc: 41 commits discards 785f10feac0 118: onsuccess: #518: 2: Success after binutils/gcc: 25 commits discards 5c8411fb409 117: onsuccess: #517: 2: Success after binutils/gcc: 117 commits discards f6cb67f202e 116: onsuccess: #516: 2: Success after binutils/gcc: 7 commits discards 0fbeb919dd3 115: onsuccess: #515: 2: Success after binutils/gcc: 7 commits discards 4127899eec9 114: onsuccess: #514: 2: Success after binutils/gcc: 20 commits discards 6b153730a1e 113: onsuccess: #513: 2: Success after binutils/gcc: 43 commits discards 18144c04ff1 112: onsuccess: #512: 2: Success after binutils/gcc: 29 commits discards 5986713a811 111: onsuccess: #511: 1: Success after gcc: 4 commits discards b200022ffe5 110: force: #510: 1: Failure after basepoints/gcc-13-4252-g [...] discards ddbcb966193 109: force: #509: 2: Success after gcc: 28 commits discards 214dddbd8c1 108: onsuccess: #507: 2: Success after binutils: 15 commits discards ad515961a95 107: onsuccess: #505: 2: Success after binutils/gcc: 53 commits discards 24bbb1444d4 106: onsuccess: #504: 2: Success after binutils/gcc: 13 commits discards a7155d3b3a6 105: onsuccess: #503: 2: Success after binutils/gcc: 56 commits discards d42c8df7fd0 104: onsuccess: #501: 2: Success after binutils/gcc: 38 commits discards a3a35e911ce 103: onsuccess: #500: 2: Success after binutils/gcc: 65 commits discards 5db782cd6fc 102: onsuccess: #498: 2: Success after binutils/gcc: 162 commits discards c8e044b2b14 101: onsuccess: #497: 1: Success after binutils/gcc: 15 commits discards a81b0869951 100: onsuccess: #496: 1: Success after binutils/gcc: 23 commits discards 8f2f971e66a 99: onsuccess: #495: 1: Success after baseline build: no ne [...] discards e39e2ff0337 98: force: #494: 1: Failure after basepoints/gcc-13-3918-gb [...] discards 756925bfa04 97: force: #493: 2: Success after gcc: 32 commits discards 6d33067cc21 96: onsuccess: #491: 2: Success after binutils: 25 commits discards c7f61a37cbb 95: onsuccess: #489: 2: Success after binutils/gcc: 49 commits discards 6714b169b81 94: onsuccess: #488: 2: Success after binutils/gcc: 63 commits discards 8c0cf529a45 93: onsuccess: #487: 2: Success after binutils/gcc: 66 commits discards d9539ef6292 92: onsuccess: #486: 2: Success after binutils/gcc: 73 commits discards f86ce76c7e6 91: onsuccess: #485: 2: Success after binutils/gcc: 12 commits discards f55208a2a4f 90: onsuccess: #484: 2: Success after binutils/gcc: 24 commits discards 67ccf2f1e61 89: onsuccess: #483: 2: Success after binutils/gcc: 64 commits discards 046458fa2be 88: onsuccess: #482: 2: Success after binutils/gcc: 49 commits discards ef0bee4d903 87: onsuccess: #481: 2: Success after binutils/gcc: 27 commits discards 2c307eebe0c 86: onsuccess: #480: 2: Success after binutils/gcc: 28 commits discards 5334fadbf89 85: onsuccess: #479: 2: Success after binutils/gcc: 43 commits discards 64af45f7ef4 84: onsuccess: #478: 2: Success after binutils/gcc: 3 commits discards f5e52fe9d66 83: onsuccess: #477: 2: Success after binutils/gcc: 24 commits discards add96b6485a 82: onsuccess: #476: 2: Success after binutils/gcc: 33 commits discards b668a48ad16 81: onsuccess: #475: 2: Success after binutils/gcc: 29 commits discards 8a63cc2b9d5 80: onsuccess: #474: 2: Success after binutils/gcc: 34 commits discards 2a9a1ce6bef 79: onsuccess: #473: 2: Success after binutils/gcc: 35 commits discards d6920e3b398 78: onsuccess: #472: 2: Success after binutils/gcc: 43 commits discards 8b424e638cb 77: onsuccess: #471: 2: Success after binutils/gcc: 6 commits discards e333ea0912a 76: onsuccess: #470: 2: Success after binutils/gcc: 6 commits discards f07ad948726 75: onsuccess: #469: 2: Success after binutils/gcc: 38 commits discards 9d7f385a6af 74: onsuccess: #468: 2: Success after binutils/gcc: 46 commits discards 380878cde7e 73: onsuccess: #467: 2: Success after binutils/gcc: 49 commits discards dc8072e6234 72: onsuccess: #466: 2: Success after binutils/gcc: 43 commits discards 363cf932f96 71: onsuccess: #465: 2: Success after binutils/gcc: 46 commits discards d84756abc3d 70: onsuccess: #464: 2: Success after binutils/gcc: 9 commits discards d09da6379fa 69: onsuccess: #463: 2: Success after binutils/gcc: 6 commits discards 58a5576c138 68: onsuccess: #462: 2: Success after binutils/gcc: 53 commits discards 0714f8babba 67: onsuccess: #461: 2: Success after binutils/gcc: 27 commits discards d910aa0c6a2 66: onsuccess: #460: 2: Success after binutils/gcc: 41 commits discards cf1e98582a9 65: onsuccess: #459: 2: Success after binutils/gcc: 61 commits discards 9bb4146e21b 64: onsuccess: #458: 1: Success after binutils/gcc: 49 commits discards 133811f2291 63: onsuccess: #457: 1: Success after binutils/gcc: 7 commits discards 44bb2d7c9a9 62: onsuccess: #456: 1: Success after binutils/gcc: 5 commits discards a6d029b90ba 61: onsuccess: #455: 1: Success after gcc: 3 commits discards 938abbeb88f 60: force: #454: 1: Failure after basepoints/gcc-13-3172-gf [...] discards 93648a8a4e6 59: force: #453: 2: Success after gcc: 29 commits discards f8ce07877b6 58: onsuccess: #451: 2: Success after binutils: 8 commits discards dd0d0b5b9dd 57: onsuccess: #449: 2: Success after binutils/gcc: 54 commits discards ba167817ed8 56: onsuccess: #448: 2: Success after binutils/gcc: 31 commits discards 952e91806f2 55: onsuccess: #447: 2: Success after binutils/gcc: 46 commits discards 1087e49e52c 54: onsuccess: #446: 2: Success after binutils/gcc: 40 commits discards cca3ad049dd 53: onsuccess: #445: 2: Success after binutils/gcc: 28 commits discards 9eb95f2635c 52: onsuccess: #444: 2: Success after binutils/gcc: 145 commits discards b7588e4a3f1 51: onsuccess: #443: 1: Success after gcc: 22 commits discards c14df82ad8f 50: force: #442: 1: Failure after basepoints/gcc-13-2887-gb [...] discards a35ad110e39 49: force: #441: 2: Success after basepoints/gcc-13-2886-g8 [...] discards ad72b74c188 48: onsuccess: #438: 2: Success after binutils: 8 commits discards 2e749928a1d 47: onsuccess: #436: 2: Success after binutils/gcc: 55 commits discards 5d9195f210d 46: onsuccess: #435: 2: Success after binutils/gcc: 12 commits discards 1805bdae26b 45: onsuccess: #434: 2: Success after binutils/gcc: 9 commits discards ca105a8ec03 44: onsuccess: #433: 2: Success after binutils/gcc: 99 commits discards e299c16963d 43: onsuccess: #431: 2: Success after binutils/gcc: 37 commits discards 4317411c368 42: onsuccess: #430: 2: Success after binutils/gcc: 39 commits discards ad4217dab27 41: onsuccess: #429: 2: Success after binutils/gcc: 10 commits discards e752a8048dd 40: onsuccess: #428: 2: Success after binutils/gcc: 7 commits discards e2ad923dbaf 39: onsuccess: #427: 2: Success after binutils/gcc: 6 commits discards 56d5cf6c0a3 38: onsuccess: #426: 2: Success after binutils/gcc: 24 commits discards a0ba9164f45 37: onsuccess: #425: 2: Success after binutils/gcc: 18 commits discards e88c3d2e579 36: onsuccess: #424: 2: Success after binutils/gcc: 30 commits discards a66ef8c5382 35: onsuccess: #423: 2: Success after binutils/gcc: 35 commits discards 3015eb62dc1 34: onsuccess: #422: 2: Success after binutils/gcc: 68 commits discards 290541ce191 33: onsuccess: #421: 2: Success after binutils/gcc: 4 commits discards 91e162e6a8b 32: onsuccess: #420: 2: Success after binutils/gcc: 7 commits discards dcd483a7d96 31: onsuccess: #419: 2: Success after binutils/gcc: 25 commits new 6ee7482b6c6 31: onsuccess: #419: 2: Success after binutils/gcc: 25 commits new 5692e80d4c5 32: onsuccess: #420: 2: Success after binutils/gcc: 7 commits new 80fe34de2d0 33: onsuccess: #421: 2: Success after binutils/gcc: 4 commits new 6e5ff963ebe 34: onsuccess: #422: 2: Success after binutils/gcc: 68 commits new a4edf382585 35: onsuccess: #423: 2: Success after binutils/gcc: 35 commits new adf58afc6de 36: onsuccess: #424: 2: Success after binutils/gcc: 30 commits new 95597784c6e 37: onsuccess: #425: 2: Success after binutils/gcc: 18 commits new 596367a5678 38: onsuccess: #426: 2: Success after binutils/gcc: 24 commits new 049ffaaae15 39: onsuccess: #427: 2: Success after binutils/gcc: 6 commits new 47e7c6c2aa3 40: onsuccess: #428: 2: Success after binutils/gcc: 7 commits new a004f5cdc28 41: onsuccess: #429: 2: Success after binutils/gcc: 10 commits new c11a2bc5779 42: onsuccess: #430: 2: Success after binutils/gcc: 39 commits new 80f812e42e1 43: onsuccess: #431: 2: Success after binutils/gcc: 37 commits new 3e5cde70d28 44: onsuccess: #433: 2: Success after binutils/gcc: 99 commits new 0e0b5e0f826 45: onsuccess: #434: 2: Success after binutils/gcc: 9 commits new 8d38a07858b 46: onsuccess: #435: 2: Success after binutils/gcc: 12 commits new aafd751c009 47: onsuccess: #436: 2: Success after binutils/gcc: 55 commits new 32dd4719df7 48: onsuccess: #438: 2: Success after binutils: 8 commits new 754a5bb2b84 49: force: #441: 2: Success after basepoints/gcc-13-2886-g8 [...] new fe22d657edb 50: force: #442: 1: Failure after basepoints/gcc-13-2887-gb [...] new 0321421f421 51: onsuccess: #443: 1: Success after gcc: 22 commits new 326088b604c 52: onsuccess: #444: 2: Success after binutils/gcc: 145 commits new 96ebb228df9 53: onsuccess: #445: 2: Success after binutils/gcc: 28 commits new 0a6ac3119dd 54: onsuccess: #446: 2: Success after binutils/gcc: 40 commits new 8b6e7ee9380 55: onsuccess: #447: 2: Success after binutils/gcc: 46 commits new 193ba0dd309 56: onsuccess: #448: 2: Success after binutils/gcc: 31 commits new 9c2c2f1e33b 57: onsuccess: #449: 2: Success after binutils/gcc: 54 commits new 6d9c4195e08 58: onsuccess: #451: 2: Success after binutils: 8 commits new c31557fa116 59: force: #453: 2: Success after gcc: 29 commits new 1f8c009340e 60: force: #454: 1: Failure after basepoints/gcc-13-3172-gf [...] new 3701d3795ca 61: onsuccess: #455: 1: Success after gcc: 3 commits new e73f3039b9b 62: onsuccess: #456: 1: Success after binutils/gcc: 5 commits new 0231710b901 63: onsuccess: #457: 1: Success after binutils/gcc: 7 commits new df3625b3972 64: onsuccess: #458: 1: Success after binutils/gcc: 49 commits new 2b4b54dc452 65: onsuccess: #459: 2: Success after binutils/gcc: 61 commits new b81be11cf74 66: onsuccess: #460: 2: Success after binutils/gcc: 41 commits new 8e7b3cc9673 67: onsuccess: #461: 2: Success after binutils/gcc: 27 commits new 5b06bdfd8bc 68: onsuccess: #462: 2: Success after binutils/gcc: 53 commits new ba12039abee 69: onsuccess: #463: 2: Success after binutils/gcc: 6 commits new 7476b31765f 70: onsuccess: #464: 2: Success after binutils/gcc: 9 commits new 4d8712792f4 71: onsuccess: #465: 2: Success after binutils/gcc: 46 commits new 45dfb36ec27 72: onsuccess: #466: 2: Success after binutils/gcc: 43 commits new c8e4eda4fe8 73: onsuccess: #467: 2: Success after binutils/gcc: 49 commits new eab93abca62 74: onsuccess: #468: 2: Success after binutils/gcc: 46 commits new caab06f5fff 75: onsuccess: #469: 2: Success after binutils/gcc: 38 commits new 5eedaa1fe2f 76: onsuccess: #470: 2: Success after binutils/gcc: 6 commits new 10a49f70661 77: onsuccess: #471: 2: Success after binutils/gcc: 6 commits new f7d12cc1d6f 78: onsuccess: #472: 2: Success after binutils/gcc: 43 commits new d419c392566 79: onsuccess: #473: 2: Success after binutils/gcc: 35 commits new f01a07f4bee 80: onsuccess: #474: 2: Success after binutils/gcc: 34 commits new f9b31159570 81: onsuccess: #475: 2: Success after binutils/gcc: 29 commits new 1332a937d3f 82: onsuccess: #476: 2: Success after binutils/gcc: 33 commits new 508ba799f70 83: onsuccess: #477: 2: Success after binutils/gcc: 24 commits new 7ffffc1d5c0 84: onsuccess: #478: 2: Success after binutils/gcc: 3 commits new 1f02bdc9e1a 85: onsuccess: #479: 2: Success after binutils/gcc: 43 commits new 29cfc407025 86: onsuccess: #480: 2: Success after binutils/gcc: 28 commits new 71a1a54c3fa 87: onsuccess: #481: 2: Success after binutils/gcc: 27 commits new 1101480f7c2 88: onsuccess: #482: 2: Success after binutils/gcc: 49 commits new dd5b42e7687 89: onsuccess: #483: 2: Success after binutils/gcc: 64 commits new 9b545821891 90: onsuccess: #484: 2: Success after binutils/gcc: 24 commits new 6a4548e94d8 91: onsuccess: #485: 2: Success after binutils/gcc: 12 commits new 1b027abaa52 92: onsuccess: #486: 2: Success after binutils/gcc: 73 commits new f337da787c3 93: onsuccess: #487: 2: Success after binutils/gcc: 66 commits new 8740c5a61d9 94: onsuccess: #488: 2: Success after binutils/gcc: 63 commits new dff47b8936a 95: onsuccess: #489: 2: Success after binutils/gcc: 49 commits new 8300605366c 96: onsuccess: #491: 2: Success after binutils: 25 commits new 94b582bd586 97: force: #493: 2: Success after gcc: 32 commits new fc67e890f52 98: force: #494: 1: Failure after basepoints/gcc-13-3918-gb [...] new ab823213667 99: onsuccess: #495: 1: Success after baseline build: no ne [...] new 6efb84af3b3 100: onsuccess: #496: 1: Success after binutils/gcc: 23 commits new 9831c0e1ca4 101: onsuccess: #497: 1: Success after binutils/gcc: 15 commits new dc992ccec98 102: onsuccess: #498: 2: Success after binutils/gcc: 162 commits new c2ef81b7bfa 103: onsuccess: #500: 2: Success after binutils/gcc: 65 commits new 17b73003c72 104: onsuccess: #501: 2: Success after binutils/gcc: 38 commits new 8b5f02aa946 105: onsuccess: #503: 2: Success after binutils/gcc: 56 commits new 19776ae1303 106: onsuccess: #504: 2: Success after binutils/gcc: 13 commits new b089e6e3e30 107: onsuccess: #505: 2: Success after binutils/gcc: 53 commits new a997e84d0be 108: onsuccess: #507: 2: Success after binutils: 15 commits new ea16c873fa5 109: force: #509: 2: Success after gcc: 28 commits new 4c38a0b1e41 110: force: #510: 1: Failure after basepoints/gcc-13-4252-g [...] new 61e31fce8a3 111: onsuccess: #511: 1: Success after gcc: 4 commits new aee4f89ea2d 112: onsuccess: #512: 2: Success after binutils/gcc: 29 commits new 5fd4bc6f421 113: onsuccess: #513: 2: Success after binutils/gcc: 43 commits new cdff676ea25 114: onsuccess: #514: 2: Success after binutils/gcc: 20 commits new 46cb0d2f2bf 115: onsuccess: #515: 2: Success after binutils/gcc: 7 commits new a2037e40298 116: onsuccess: #516: 2: Success after binutils/gcc: 7 commits new c59e0e798c0 117: onsuccess: #517: 2: Success after binutils/gcc: 117 commits new d5fcc273bf8 118: onsuccess: #518: 2: Success after binutils/gcc: 25 commits new 97f46a07a4b 119: onsuccess: #519: 2: Success after binutils/gcc: 41 commits new 8333d07ac33 120: onsuccess: #520: 2: Success after binutils/gcc: 54 commits new 4dbcc74fabb 121: onsuccess: #521: 2: Success after binutils/gcc: 31 commits new 897cd7e6132 122: onsuccess: #522: 2: Success after binutils/gcc: 6 commits new 9a19249286b 123: onsuccess: #523: 2: Success after binutils/gcc: 13 commits new 4ae9f3a1397 124: onsuccess: #524: 2: Success after binutils/gcc: 34 commits new 57e9599ad86 125: onsuccess: #525: 2: Success after binutils/gcc: 47 commits new e83a5db9283 126: onsuccess: #526: 2: Success after binutils/gcc: 27 commits new e4fdbca240a 127: onsuccess: #527: 2: Success after binutils/gcc: 33 commits new 05cceebd9b7 128: onsuccess: #528: 2: Success after binutils/gcc: 31 commits new 0b05cd0c470 129: onsuccess: #529: 2: Success after binutils/gcc: 3 commits new 60c0d58e295 130: onsuccess: #530: 2: Success after binutils/gcc: 12 commits new 21e31582700 131: onsuccess: #531: 2: Success after binutils/gcc: 47 commits new 8950c5c4251 132: onsuccess: #534: 2: Success after gcc: 66 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 (5b022c959f1) \ 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 1920 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2748 bytes 04-build_abe-binutils/console.log.xz | Bin 39436 -> 39592 bytes 05-build_abe-bootstrap_O1/console.log.xz | Bin 275140 -> 273008 bytes 06-check_regression/console.log.xz | Bin 3008 -> 2676 bytes 07-update_baseline/console.log | 64 +++++++++++++++---------------- 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 | 17 ++++---- 12 files changed, 45 insertions(+), 46 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch master updated (930b3d6948f -> c263c3eba89)

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 930b3d6948f middle-end/108086 - reduce operand scanner use from inliner new c263c3eba89 gcov: annotate uncovered branches [PR107537] 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/gcov.cc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_O1 updated (aed58fc382f -> b0a4590c74c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_O1 in repository toolchain/ci/base-artifacts. from aed58fc382f 38: onsuccess: #144: 2: Success after binutils/gcc: 10 commits new b0a4590c74c 39: onsuccess: #145: 2: Success after binutils/gcc: 18 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 1768 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2760 bytes 04-build_abe-binutils/console.log.xz | Bin 51968 -> 52444 bytes 05-build_abe-bootstrap_O1/console.log.xz | Bin 461152 -> 461340 bytes 06-check_regression/console.log.xz | Bin 2788 -> 2780 bytes 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 +++++++++--------- 12 files changed, 15 insertions(+), 15 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch devel/modula-2 updated (2e0ff34783a -> 4f27bc50e66)

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/modula-2 in repository gcc. from 2e0ff34783a Add modula-2 into doc/install.texi and doc/sourcebuild.texi. new 4f27bc50e66 PR-108123 Rebuilt gcc/m2/gm2config.h.in 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/configure | 4 +-- gcc/m2/gm2config.h.in | 90 +++++++++++++++++++++++++++++---------------------- 2 files changed, 54 insertions(+), 40 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch master updated (bf3ce6f84a7 -> 930b3d6948f)

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 bf3ce6f84a7 into-ssa: Fix emitting debug stmts after asm goto [PR108095] new 930b3d6948f middle-end/108086 - reduce operand scanner use from inliner 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/tree-inline.cc | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-defconfig updated (e3064174d6f -> b91654a02ce)

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-next-defconfig in repository toolchain/ci/base-artifacts. from e3064174d6f 27: onsuccess: #496: boot: Success after binutils/llvm/linu [...] new b91654a02ce 28: onsuccess: #497: boot: Success after binutils/llvm/linu [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1772 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 31652 -> 31992 bytes 04-build_kernel_llvm/console.log.xz | Bin 66584 -> 67072 bytes 05-build_abe-qemu/console.log.xz | Bin 31176 -> 31272 bytes 06-build_linux/console.log.xz | Bin 3744 -> 3800 bytes 07-boot_linux/console.log.xz | Bin 6200 -> 6232 bytes 08-check_regression/console.log.xz | Bin 3896 -> 4276 bytes 08-check_regression/mail-body.txt | 2 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- results | 2 +- 19 files changed, 26 insertions(+), 26 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm updated (b50f86dcc71 -> 4a71c3cf663)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm in repository toolchain/ci/base-artifacts. discards b50f86dcc71 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards 17d0b368f26 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards f87366b4eba 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards 15c245cb342 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards 83c18282b6b 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards 2a0413a3f05 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 06f4515ad41 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards 997dff76554 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards b66dce54788 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards 8d574028e9a 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards c8b616772ca 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards 9aa1a977eff 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards 38a6cf639da 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards d99551f07b9 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards 0bb3f6076ec 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] discards ef220e96599 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards 66ee00b800e 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards c66a62870a4 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] discards 33930147471 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] discards a81c59cf1c5 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] discards 1cf1fa06786 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] discards 9588ed89c24 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] discards a9c8c3c9f05 109: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] discards 3059e7cbefb 108: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] discards a4e9ee17d34 107: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] discards 69015803881 106: onsuccess: #532: 1: Success after binutils/gcc/linux/g [...] discards cd571ab8ae1 105: onsuccess: #531: 1: Success after binutils/gcc/linux/g [...] discards 115e968fe1c 104: onsuccess: #530: 1: Success after gcc: 7 commits discards 1e17f25efbd 103: onsuccess: #529: 1: Success after binutils/gcc/linux/g [...] discards bd1d75205a1 102: onsuccess: #527: 1: Success after binutils: 5 commits discards db4c960e1c3 101: onsuccess: #524: 1: Success after binutils: 2 commits discards b296ee8916c 100: onsuccess: #521: 1: Success after binutils: 10 commits discards b4afe8cc85b 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] discards 91e4a722c1a 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gl [...] discards f3be7a4a4ce 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] discards 24194afe25c 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] discards 754c3015b01 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gd [...] discards 10ad1fcd779 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gd [...] discards efa71fd9f43 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] discards 7a8973d6a2b 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gl [...] discards 498733b6ccc 91: onsuccess: #511: 1: Success after linux: 27 commits discards b7e9d267e47 90: onsuccess: #510: 1: Success after glibc: 5 commits discards f38816321f9 89: onsuccess: #508: 1: Success after binutils: 12 commits discards 8de54e518a9 88: onsuccess: #506: 1: Success after linux: 34 commits discards 8969e999db3 87: onsuccess: #505: 1: Success after glibc: 7 commits discards c7227bbc817 86: onsuccess: #503: 1: Success after binutils: 12 commits discards 6e6b342859b 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] discards 60a71ac2fd7 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] discards 14981cba7e5 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gd [...] discards ae59f224a3f 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gl [...] discards 2aa1cd54028 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] discards 0da39dc63a0 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] discards ba7d65c7911 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] discards 59ac6c1d04f 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] discards b2e4c2ec028 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gd [...] discards 2112150c9fb 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gd [...] discards bd87afca723 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gd [...] discards 7d4b06ab15c 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gl [...] discards c9a1421c50a 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gd [...] discards b460706cceb 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gl [...] discards f9dd4270521 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gd [...] discards ed3728c8337 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gl [...] discards 70c75a880f0 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] discards 61a4e38cdc7 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gl [...] discards 8a6c657958c 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] discards 6c5cdfbb140 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gl [...] discards 370a9fa6d53 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gd [...] discards 74b0aaa775a 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] discards 5c019d82030 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gl [...] discards 9cd5fbb1c55 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gl [...] discards f2b60a1fe07 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gl [...] discards 50701cccb28 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gl [...] discards 723f76debb9 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gl [...] discards 9a31a17409d 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gl [...] discards 8ffe7df6b69 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gl [...] discards f5381b9f412 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gd [...] discards ab1be927526 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gl [...] discards 8846eea761c 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gl [...] discards 6dfb8db2987 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gl [...] discards fff216c05de 52: onsuccess: #467: 1: Success after binutils: 9 commits discards 8ebb6094521 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 8592fda3826 50: onsuccess: #461: 1: Success after binutils: 12 commits discards 0404a187729 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gd [...] discards 283379e41a3 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gd [...] discards 42b613b2b3a 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gl [...] discards 7db2627073f 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gl [...] discards cd246357fb2 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gl [...] discards 56ef6b887d1 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gd [...] discards c2cce1171fe 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gd [...] discards 64e49a4ae1d 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gd [...] discards 7b4ea13be47 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gl [...] discards 6524b784dc4 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g [...] discards 187d46807ae 39: onsuccess: #447: 1: Success after binutils: 5 commits discards 0f75b8982e5 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g [...] discards c9a71cd7da4 37: onsuccess: #443: 1: Success after binutils: 2 commits discards 9063c3ede79 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gl [...] discards 2d659e2a9e0 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gl [...] discards 878864fd453 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gl [...] discards 583bd0cff46 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gd [...] discards 15ea8682eff 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gl [...] discards 11c4330a388 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gl [...] new 838b24a2bf4 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gl [...] new 0fda9cda8b2 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gl [...] new 33d81840e2e 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gd [...] new 7dfd867b591 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gl [...] new c7599c6d42b 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gl [...] new 42125cab368 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gl [...] new 7d3d2eba98c 37: onsuccess: #443: 1: Success after binutils: 2 commits new 79cde35d553 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g [...] new d075307227f 39: onsuccess: #447: 1: Success after binutils: 5 commits new b599db4525b 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g [...] new 7db8421700d 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gl [...] new f0d6d672f10 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gd [...] new 751f9aedfd7 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gd [...] new c3f6f2c305b 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gd [...] new cd818cca87a 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gl [...] new 029823cf532 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gl [...] new edf34aa8ddd 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gl [...] new ddee4b23e3b 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gd [...] new 390a8f584a9 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gd [...] new d991b040314 50: onsuccess: #461: 1: Success after binutils: 12 commits new d33b17bcd93 51: onsuccess: #464: 1: Success after binutils: 6 commits new 1bd2f49f6df 52: onsuccess: #467: 1: Success after binutils: 9 commits new bd447e2f96e 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gl [...] new 2606734c36a 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gl [...] new a1aaceade78 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gl [...] new fe542b714f4 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gd [...] new 79d54ab301f 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gl [...] new e4f175b98d8 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gl [...] new 3aba8f14b29 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gl [...] new fabde7ecdca 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gl [...] new d843fdbced9 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gl [...] new f7f1901b134 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gl [...] new 4e2f3f57e11 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gl [...] new 4a06a1c687d 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] new fea9cfd7a1f 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gd [...] new 77f6d182edc 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gl [...] new 21c6442ebdb 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] new 960838a332a 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gl [...] new 523337a0257 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] new dacb08ab813 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gl [...] new 16c7ddf92ad 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gd [...] new a962670f3fe 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gl [...] new 77bb7cfd9ae 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gd [...] new e2d16304d1e 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gl [...] new 8967cfa49a1 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gd [...] new d1bc40863c1 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gd [...] new a2a758adb77 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gd [...] new e06bc7343f8 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] new ad413a402fd 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] new fea9804163f 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] new cf5cd9377b6 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] new e827cb42a84 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gl [...] new 9f00d3622d1 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gd [...] new a3ea098c6dc 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] new fa7847fad01 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new 6d39bcfdf07 86: onsuccess: #503: 1: Success after binutils: 12 commits new 5dd2a2df48d 87: onsuccess: #505: 1: Success after glibc: 7 commits new 5842442ad20 88: onsuccess: #506: 1: Success after linux: 34 commits new c53dcd52fab 89: onsuccess: #508: 1: Success after binutils: 12 commits new c442c955448 90: onsuccess: #510: 1: Success after glibc: 5 commits new aa51b0f80d8 91: onsuccess: #511: 1: Success after linux: 27 commits new 089123c52b5 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gl [...] new 9b4d69be66c 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] new f3bec1d2dec 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gd [...] new 6cda6a77ca9 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gd [...] new 5ccc05e50b0 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] new 1bc0f264529 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] new 27c85001dbd 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gl [...] new b145af4b16c 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] new fbe38ea3197 100: onsuccess: #521: 1: Success after binutils: 10 commits new 436f5e2d4c2 101: onsuccess: #524: 1: Success after binutils: 2 commits new efecf50b0d1 102: onsuccess: #527: 1: Success after binutils: 5 commits new 180ece6188a 103: onsuccess: #529: 1: Success after binutils/gcc/linux/g [...] new cee8b125497 104: onsuccess: #530: 1: Success after gcc: 7 commits new 31ff540e673 105: onsuccess: #531: 1: Success after binutils/gcc/linux/g [...] new 2f004e50296 106: onsuccess: #532: 1: Success after binutils/gcc/linux/g [...] new a4c8f613204 107: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] new 1eaac83bdad 108: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] new 6d9b098664e 109: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] new b3321b3b0e2 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/g [...] new 53c45654697 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 [...] new dd91dff22f3 112: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new b03044a3e51 113: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new 2e94d590c80 114: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new d47d2910cdb 115: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new fbf953a857d 116: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new 924711cf94f 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new dc69fb90268 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new cb0dbb64bfe 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new 01aedc41d18 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new 84cddee566d 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new 3f654ac4e1b 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new 5aef46c1998 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new cc0de29d6fe 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 54f8f685121 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 9dfc291520c 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new d4cd526ff63 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new 0d1a0f0dc21 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new 6de2dbde535 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new 7e3ef183360 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new dcdb3f30159 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new 4a71c3cf663 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (b50f86dcc71) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1752 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 53564 -> 52244 bytes 04-build_abe-gcc/console.log.xz | Bin 234220 -> 235380 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 10216 -> 9560 bytes 07-build_abe-glibc/console.log.xz | Bin 235212 -> 234920 bytes 08-build_abe-gdb/console.log.xz | Bin 52760 -> 51624 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3812 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2460 -> 2124 bytes 11-check_regression/console.log.xz | Bin 6076 -> 5868 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 40 ++-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +-- sumfiles/binutils.log.xz | Bin 62572 -> 62824 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 100556 -> 100316 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 131536 -> 131556 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 29 files changed, 390 insertions(+), 390 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_llvm_sq/llvm-master-arm-spec2k6-O3_VECT updated (38e2c895ced -> cc0c0877af4)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk_llvm_sq/llvm-master-arm-spec2k6-O3_VECT in repository toolchain/ci/base-artifacts. from 38e2c895ced 5: onsuccess: #38: 1: [TCWG CI] No change after binutils/gc [...] new cc0c0877af4 6: onsuccess: #47: 1: [TCWG CI] No change after binutils/gc [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1724 -> 1832 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 31800 -> 31876 bytes 04-build_abe-stage1/console.log.xz | Bin 92484 -> 92916 bytes 06-build_abe-linux/console.log.xz | Bin 8700 -> 8688 bytes 07-build_abe-glibc/console.log.xz | Bin 237376 -> 236588 bytes 08-build_abe-stage2/console.log.xz | Bin 213404 -> 213992 bytes 09-build_llvm-true-false-/console.log.xz | Bin 63788 -> 0 bytes 09-build_llvm-true-false-cflags-/console.log.xz | Bin 0 -> 64520 bytes 10-benchmark/benchmark-build.log | 102 +- 10-benchmark/benchmark.log | 100 +- 10-benchmark/console.log.xz | Bin 3808 -> 3976 bytes 11-check_regression/console.log.xz | Bin 11516 -> 11860 bytes .../csv-results-vs-first-1/md5sum.csv | 1696 +- .../csv-results-vs-first-1/perf.csv | 2178 +- .../csv-results-vs-first-1/results.csv | 31498 +++++++------------ .../csv-results-vs-first-1/size.csv | 16328 ++++------ .../csv-results-vs-first-1/vect.csv | 10448 ------ .../csv-results-vs-prev-0/md5sum.csv | 1109 +- 11-check_regression/csv-results-vs-prev-0/perf.csv | 2202 +- .../csv-results-vs-prev-0/results.csv | 9314 +++--- 11-check_regression/csv-results-vs-prev-0/size.csv | 7006 +++-- .../csv-results-vs-prev-1/md5sum.csv | 1696 +- 11-check_regression/csv-results-vs-prev-1/perf.csv | 2178 +- .../csv-results-vs-prev-1/results.csv | 31498 +++++++------------ 11-check_regression/csv-results-vs-prev-1/size.csv | 16328 ++++------ 11-check_regression/csv-results-vs-prev-1/vect.csv | 10448 ------ 11-check_regression/results-vs-first-brief.csv | 42 +- 11-check_regression/results-vs-first-full.csv | 2314 +- 11-check_regression/results-vs-first-internal.csv | 163 +- 11-check_regression/results-vs-first.csv | 163 +- 11-check_regression/results-vs-first.log | 738 +- 11-check_regression/results-vs-prev-brief.csv | 42 +- 11-check_regression/results-vs-prev-compare.csv | 24 - 11-check_regression/results-vs-prev-full.csv | 2370 +- 11-check_regression/results-vs-prev-internal.csv | 163 +- 11-check_regression/results-vs-prev.csv | 163 +- 11-check_regression/results-vs-prev.log | 722 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 18 +- .../400.perlbench/results-metrics.json | 1 - .../squad-vs-first/401.bzip2/results-metadata.json | 18 +- .../squad-vs-first/401.bzip2/results-metrics.json | 3 +- .../squad-vs-first/403.gcc/results-metadata.json | 18 +- .../squad-vs-first/403.gcc/results-metrics.json | 3 +- .../squad-vs-first/429.mcf/results-metadata.json | 18 +- .../squad-vs-first/429.mcf/results-metrics.json | 3 +- .../squad-vs-first/433.milc/results-metadata.json | 18 +- .../squad-vs-first/433.milc/results-metrics.json | 3 +- .../squad-vs-first/444.namd/results-metadata.json | 18 +- .../squad-vs-first/444.namd/results-metrics.json | 3 +- .../squad-vs-first/445.gobmk/results-metadata.json | 18 +- .../squad-vs-first/445.gobmk/results-metrics.json | 5 +- .../447.dealII/results-metadata.json | 18 +- .../squad-vs-first/447.dealII/results-metrics.json | 3 +- .../450.soplex/results-metadata.json | 18 +- .../squad-vs-first/450.soplex/results-metrics.json | 5 +- .../453.povray/results-metadata.json | 18 +- .../squad-vs-first/453.povray/results-metrics.json | 5 +- .../squad-vs-first/456.hmmer/results-metadata.json | 18 +- .../squad-vs-first/456.hmmer/results-metrics.json | 3 +- .../squad-vs-first/458.sjeng/results-metadata.json | 18 +- .../squad-vs-first/458.sjeng/results-metrics.json | 5 +- .../462.libquantum/results-metadata.json | 18 +- .../462.libquantum/results-metrics.json | 3 +- .../464.h264ref/results-metadata.json | 18 +- .../464.h264ref/results-metrics.json | 3 +- .../squad-vs-first/470.lbm/results-metadata.json | 18 +- .../471.omnetpp/results-metadata.json | 18 +- .../471.omnetpp/results-metrics.json | 3 +- .../squad-vs-first/473.astar/results-metadata.json | 18 +- .../squad-vs-first/473.astar/results-metrics.json | 5 +- .../482.sphinx3/results-metadata.json | 18 +- .../482.sphinx3/results-metrics.json | 3 +- .../483.xalancbmk/results-metadata.json | 18 +- .../483.xalancbmk/results-metrics.json | 3 +- .../squad-vs-first/Mean/results-metadata.json | 18 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 82 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 56 +- mail/mail-body.txt | 56 +- mail/mail-subject.txt | 2 +- manifest.sh | 43 +- results | 2 +- results_id | 2 +- 89 files changed, 51914 insertions(+), 99796 deletions(-) delete mode 100644 09-build_llvm-true-false-/console.log.xz create mode 100644 09-build_llvm-true-false-cflags-/console.log.xz -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-lts-allnoconfig updated (144f67feefe -> ee0181156bc)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-lts-allnoconfig in repository toolchain/ci/base-artifacts. from 144f67feefe 28: onsuccess: #434: boot: Success after binutils/gcc/linux [...] new ee0181156bc 29: onsuccess: #435: boot: Success after binutils/gcc/linux [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1768 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 30800 -> 30344 bytes 04-build_abe-stage1/console.log.xz | Bin 68736 -> 68408 bytes 05-build_abe-qemu/console.log.xz | Bin 30948 -> 31236 bytes 06-build_linux/console.log.xz | Bin 3308 -> 3328 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 3780 -> 3828 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, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022