Tcwg-commits March 2023

tcwg-commits@lists.linaro.org

5 participants
3834 discussions

[gcc] branch master updated (8e9c65d34c7 -> 538a0d0f29b)

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 8e9c65d34c7 Docs: Fix double 'See' in zero-length-bounds docs. new 538a0d0f29b c++: handle _FloatNN redeclaration like bool [PR107128] 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/cp/parser.cc | 2 ++ gcc/testsuite/g++.dg/warn/pragma-system_header6.C | 1 + .../{gcc.dg/pr36901-system.h => g++.dg/warn/pragma-system_header6.h} | 2 +- 3 files changed, 4 insertions(+), 1 deletion(-) create mode 100644 gcc/testsuite/g++.dg/warn/pragma-system_header6.C copy gcc/testsuite/{gcc.dg/pr36901-system.h => g++.dg/warn/pragma-system_header6.h} (52%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-allyesconfig updated (382359cde4d -> 443ff017b47)

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-master-aarch64-stable-allyesconfig in repository toolchain/ci/base-artifacts. from 382359cde4d 53: onsuccess: #4: 21789: Success after binutils/gcc/qemu: [...] new 443ff017b47 54: onsuccess: #5: 21796: 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 1976 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2860 bytes 03-build_abe-binutils/console.log.xz | Bin 31120 -> 31180 bytes 04-build_abe-stage1/console.log.xz | Bin 71480 -> 71644 bytes 05-build_abe-qemu/console.log.xz | Bin 32592 -> 32676 bytes 06-build_linux/console.log.xz | Bin 11600 -> 10100 bytes 08-check_regression/console.log.xz | Bin 4004 -> 4252 bytes 08-check_regression/mail-body.txt | 2 +- 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 | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 18 files changed, 27 insertions(+), 27 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[gcc] branch master updated (23532dac3f6 -> 8e9c65d34c7)

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 23532dac3f6 testsuite: add test coverage for analyzer leak false +ve [P [...] new 8e9c65d34c7 Docs: Fix double 'See' in zero-length-bounds docs. 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/doc/invoke.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled_lto updated (a48c0ecd87b -> 7dadbe80e88)

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_profiled_lto in repository toolchain/ci/base-artifacts. discards a48c0ecd87b 203: onsuccess: #18: 2: Success after binutils/gcc: 9 commits discards d8a6066c823 202: onsuccess: #17: 2: Success after binutils/gcc: 25 commits discards 4a5cb393c0c 201: onsuccess: #16: 2: Success after binutils/gcc: 55 commits discards 9d222ad85cf 200: onsuccess: #15: 2: Success after binutils/gcc: 26 commits discards de9728e6af2 199: onsuccess: #14: 2: Success after binutils/gcc: 31 commits discards 8b46aaf0502 198: onsuccess: #13: 2: Success after binutils/gcc: 58 commits discards b45d08fe2f0 197: onsuccess: #12: 2: Success after binutils/gcc: 29 commits discards 79fbe8ff469 196: onsuccess: #11: 2: Success after binutils/gcc: 16 commits discards 4d9a22866ef 195: onsuccess: #10: 2: Success after binutils/gcc: 28 commits discards 88be7d5a4ef 194: onsuccess: #9: 2: Success after binutils/gcc: 48 commits discards 4252d1f6c48 193: onsuccess: #8: 2: Success after binutils/gcc: 37 commits discards 144202d0918 192: onsuccess: #7: 2: Success after binutils/gcc: 22 commits discards 9952068d8e3 191: onsuccess: #6: 2: Success after binutils/gcc: 65 commits discards 115caf0ea9c 190: onsuccess: #5: 2: Success after binutils/gcc: 23 commits discards abb056cdd27 189: onsuccess: #4: 2: Success after binutils/gcc: 8 commits discards 4609dedc6f3 188: onsuccess: #3: 2: Success after binutils/gcc: 5 commits discards 0bce73cf276 187: onsuccess: #2: 2: Success after binutils/gcc: 22 commits discards 73f4c0ce133 186: onsuccess: #1: 2: Success after binutils/gcc: 54 commits discards a6a4c852d34 185: onsuccess: #605: 2: Success after binutils/gcc: 38 commits discards 1a5e84198e4 184: onsuccess: #604: 2: Success after binutils/gcc: 138 commits discards 8159996f170 183: onsuccess: #603: 2: Success after binutils/gcc: 33 commits discards b67616984a3 182: onsuccess: #602: 2: Success after binutils/gcc: 32 commits discards b23850004f3 181: onsuccess: #601: 2: Success after binutils/gcc: 13 commits discards 50f67c2d865 180: onsuccess: #600: 2: Success after binutils/gcc: 32 commits discards dc9fb79102d 179: onsuccess: #599: 2: Success after binutils/gcc: 27 commits discards 77969967e90 178: onsuccess: #598: 2: Success after binutils/gcc: 54 commits discards 9e88f40ad17 177: onsuccess: #597: 2: Success after binutils/gcc: 86 commits discards dff2187ae38 176: onsuccess: #596: 2: Success after binutils/gcc: 84 commits discards 07f6243b6e2 175: onsuccess: #595: 2: Success after binutils/gcc: 30 commits discards 8505ce326b4 174: onsuccess: #594: 2: Success after binutils/gcc: 147 commits discards ead7b477527 173: onsuccess: #593: 2: Success after binutils/gcc: 74 commits discards f1d20a32078 172: onsuccess: #592: 2: Success after binutils/gcc: 57 commits discards cbe446ed617 171: onsuccess: #590: 2: Success after binutils/gcc: 21 commits discards ddbf34dbb1b 170: onsuccess: #589: 2: Success after binutils/gcc: 28 commits discards 8bdee6e204b 169: onsuccess: #588: 2: Success after binutils/gcc: 7 commits discards fa82e47a6a8 168: onsuccess: #587: 2: Success after binutils/gcc: 2 commits discards dc50d97575a 167: onsuccess: #586: 2: Success after binutils/gcc: 16 commits discards 49234c26e95 166: onsuccess: #585: 2: Success after binutils/gcc: 59 commits discards f1c8455b06d 165: onsuccess: #584: 2: Success after binutils/gcc: 45 commits discards c551f33f32e 164: onsuccess: #583: 2: Success after binutils/gcc: 110 commits discards 70e32b17d9d 163: onsuccess: #582: 2: Success after binutils/gcc: 55 commits discards 68564f701f9 162: onsuccess: #581: 2: Success after binutils/gcc: 6 commits discards 3b8e07a69b5 161: onsuccess: #580: 2: Success after binutils/gcc: 10 commits discards af0a68e2c4f 160: onsuccess: #579: 2: Success after binutils/gcc: 17 commits discards 5747e887af9 159: onsuccess: #578: 2: Success after binutils/gcc: 130 commits discards 29c93788a99 158: onsuccess: #577: 2: Success after binutils/gcc: 27 commits discards 4e54682f895 157: onsuccess: #576: 2: Success after binutils/gcc: 80 commits discards c4319630988 156: onsuccess: #575: 2: Success after binutils/gcc: 27 commits discards 064d78a3c00 155: onsuccess: #574: 2: Success after binutils/gcc: 36 commits discards 35a99f5f80b 154: onsuccess: #573: 2: Success after binutils/gcc: 6 commits discards 4a3151a201b 153: onsuccess: #572: 2: Success after binutils/gcc: 28 commits discards d0ec5d41ba2 152: onsuccess: #571: 2: Success after binutils/gcc: 43 commits discards 88116eb757f 151: onsuccess: #570: 2: Success after binutils/gcc: 36 commits discards 7b3a4866940 150: onsuccess: #569: 2: Success after binutils/gcc: 32 commits discards a5639076f71 149: onsuccess: #568: 2: Success after binutils/gcc: 69 commits discards 080cc31c3cb 148: onsuccess: #567: 2: Success after binutils/gcc: 128 commits discards e99b6f1e6e7 147: onsuccess: #566: 2: Success after binutils/gcc: 50 commits discards ab3346340c8 146: onsuccess: #565: 2: Success after binutils/gcc: 115 commits discards d898d2ded83 145: onsuccess: #564: 2: Success after binutils/gcc: 30 commits discards f52451bb27c 144: onsuccess: #563: 2: Success after binutils/gcc: 4 commits discards 94bacb8d4e0 143: onsuccess: #562: 2: Success after binutils/gcc: 6 commits discards 6b5f2466c8b 142: onsuccess: #561: 2: Success after binutils/gcc: 176 commits discards 8f5fee604d7 141: onsuccess: #559: 1: Success after gcc: 4 commits discards d3eea401d83 140: force: #558: 1: Failure after basepoints/gcc-13-4953-g [...] discards 0e51806bb04 139: force: #557: 2: Success after gcc: 6 commits discards 2e0f5197cc4 138: onsuccess: #554: 2: Success after binutils: 10 commits discards a7a6526a698 137: onsuccess: #552: 2: Success after binutils/gcc: 18 commits discards f2181161768 136: onsuccess: #551: 2: Success after binutils/gcc: 18 commits discards 9376f856ce6 135: onsuccess: #550: 2: Success after binutils/gcc: 31 commits discards a987d4c2495 134: onsuccess: #549: 2: Success after binutils/gcc: 9 commits discards dd643e697dd 133: onsuccess: #548: 2: Success after binutils/gcc: 29 commits discards 24f59bfdc06 132: onsuccess: #547: 2: Success after binutils/gcc: 7 commits discards 6c378d82afa 131: onsuccess: #546: 2: Success after binutils/gcc: 24 commits discards 3eca0fd6739 130: onsuccess: #545: 2: Success after binutils/gcc: 9 commits discards f9423d57a52 129: onsuccess: #544: 2: Success after binutils/gcc: 79 commits discards a4638fb306b 128: onsuccess: #543: 2: Success after binutils/gcc: 52 commits discards 6df39d69282 127: onsuccess: #542: 2: Success after binutils/gcc: 66 commits discards 5fc6a5a5650 126: onsuccess: #541: 2: Success after binutils/gcc: 17 commits discards 003cd19c6b8 125: onsuccess: #540: 2: Success after binutils/gcc: 53 commits discards 72c6ca1c8f4 124: onsuccess: #539: 2: Success after binutils/gcc: 9 commits discards d8e299c1268 123: onsuccess: #538: 2: Success after binutils/gcc: 14 commits discards 27fc8ffcff0 122: onsuccess: #537: 2: Success after binutils/gcc: 36 commits discards 83791eb7ed9 121: onsuccess: #536: 1: Success after binutils/gcc: 76 commits discards 96607df7205 120: onsuccess: #535: 1: Success after binutils: 10 commits discards af00e2162d5 119: force: #534: 1: Failure after gdb-12-branchpoint-3046- [...] discards fcb6c5abac6 118: force: #533: 2: Success after binutils: 4 commits discards fe242527004 117: onsuccess: #531: 2: Success after gcc: 65 commits discards cd3add71750 116: onsuccess: #528: 2: Success after binutils/gcc: 48 commits discards d67e43990fc 115: onsuccess: #527: 2: Success after binutils/gcc: 11 commits discards 225560b46e1 114: onsuccess: #526: 2: Success after binutils/gcc: 3 commits discards 811345d32df 113: onsuccess: #525: 2: Success after binutils/gcc: 35 commits discards 5f2a1b4c700 112: onsuccess: #524: 2: Success after binutils/gcc: 32 commits discards c353e8be6c1 111: onsuccess: #523: 2: Success after binutils/gcc: 26 commits discards b1e6448d534 110: onsuccess: #522: 2: Success after binutils/gcc: 47 commits discards d34e9e619af 109: onsuccess: #521: 2: Success after binutils/gcc: 32 commits discards 59f37721b50 108: onsuccess: #520: 2: Success after binutils/gcc: 13 commits discards dbb3ac9906c 107: onsuccess: #519: 2: Success after binutils/gcc: 8 commits discards 18828bd1eb7 106: onsuccess: #518: 2: Success after binutils/gcc: 31 commits discards a98c9d4abed 105: onsuccess: #517: 2: Success after binutils/gcc: 52 commits discards cb2d1320508 104: onsuccess: #516: 2: Success after binutils/gcc: 44 commits discards 4a49a430501 103: onsuccess: #515: 2: Success after binutils/gcc: 22 commits new 05751d4c26b 103: onsuccess: #515: 2: Success after binutils/gcc: 22 commits new e39f1d13cc8 104: onsuccess: #516: 2: Success after binutils/gcc: 44 commits new c01d386ffe4 105: onsuccess: #517: 2: Success after binutils/gcc: 52 commits new ee9748e89e1 106: onsuccess: #518: 2: Success after binutils/gcc: 31 commits new 299f9f292c8 107: onsuccess: #519: 2: Success after binutils/gcc: 8 commits new 82852795794 108: onsuccess: #520: 2: Success after binutils/gcc: 13 commits new 6ff52db010c 109: onsuccess: #521: 2: Success after binutils/gcc: 32 commits new 0c4d7c02dd8 110: onsuccess: #522: 2: Success after binutils/gcc: 47 commits new dde2fa2b2b0 111: onsuccess: #523: 2: Success after binutils/gcc: 26 commits new e5c4c8d6f85 112: onsuccess: #524: 2: Success after binutils/gcc: 32 commits new 2fd35be69b5 113: onsuccess: #525: 2: Success after binutils/gcc: 35 commits new e9e905fe4fb 114: onsuccess: #526: 2: Success after binutils/gcc: 3 commits new 70e3349ea9e 115: onsuccess: #527: 2: Success after binutils/gcc: 11 commits new 0157d37106c 116: onsuccess: #528: 2: Success after binutils/gcc: 48 commits new 81059504243 117: onsuccess: #531: 2: Success after gcc: 65 commits new 2ce235a5f8a 118: force: #533: 2: Success after binutils: 4 commits new f0b0d2211b9 119: force: #534: 1: Failure after gdb-12-branchpoint-3046- [...] new 7a9a816af0a 120: onsuccess: #535: 1: Success after binutils: 10 commits new 9882b2a1802 121: onsuccess: #536: 1: Success after binutils/gcc: 76 commits new 69da24e7438 122: onsuccess: #537: 2: Success after binutils/gcc: 36 commits new f40939589ab 123: onsuccess: #538: 2: Success after binutils/gcc: 14 commits new 586c58d5353 124: onsuccess: #539: 2: Success after binutils/gcc: 9 commits new d1b7eb73699 125: onsuccess: #540: 2: Success after binutils/gcc: 53 commits new ac7b38ade62 126: onsuccess: #541: 2: Success after binutils/gcc: 17 commits new a3d91bde10e 127: onsuccess: #542: 2: Success after binutils/gcc: 66 commits new 329cdea2939 128: onsuccess: #543: 2: Success after binutils/gcc: 52 commits new 698491552fa 129: onsuccess: #544: 2: Success after binutils/gcc: 79 commits new e1c0f222774 130: onsuccess: #545: 2: Success after binutils/gcc: 9 commits new decc9a96dc6 131: onsuccess: #546: 2: Success after binutils/gcc: 24 commits new 7be3fa754d2 132: onsuccess: #547: 2: Success after binutils/gcc: 7 commits new ce0df17cce2 133: onsuccess: #548: 2: Success after binutils/gcc: 29 commits new f249fbadf98 134: onsuccess: #549: 2: Success after binutils/gcc: 9 commits new 94078479582 135: onsuccess: #550: 2: Success after binutils/gcc: 31 commits new 68c3819b761 136: onsuccess: #551: 2: Success after binutils/gcc: 18 commits new e12171bd5ea 137: onsuccess: #552: 2: Success after binutils/gcc: 18 commits new 98dceb904b4 138: onsuccess: #554: 2: Success after binutils: 10 commits new 5479b0121b8 139: force: #557: 2: Success after gcc: 6 commits new 575b681cd7f 140: force: #558: 1: Failure after basepoints/gcc-13-4953-g [...] new b931dcd7277 141: onsuccess: #559: 1: Success after gcc: 4 commits new 40a67f5e053 142: onsuccess: #561: 2: Success after binutils/gcc: 176 commits new 6f68eb2032f 143: onsuccess: #562: 2: Success after binutils/gcc: 6 commits new b856ef49cb7 144: onsuccess: #563: 2: Success after binutils/gcc: 4 commits new f550d808962 145: onsuccess: #564: 2: Success after binutils/gcc: 30 commits new 6555d912726 146: onsuccess: #565: 2: Success after binutils/gcc: 115 commits new 68a7cfeb75f 147: onsuccess: #566: 2: Success after binutils/gcc: 50 commits new b1f970262c8 148: onsuccess: #567: 2: Success after binutils/gcc: 128 commits new 28da786238f 149: onsuccess: #568: 2: Success after binutils/gcc: 69 commits new 6d4b60d8e7a 150: onsuccess: #569: 2: Success after binutils/gcc: 32 commits new 4cfff56f9af 151: onsuccess: #570: 2: Success after binutils/gcc: 36 commits new e87c5bf9115 152: onsuccess: #571: 2: Success after binutils/gcc: 43 commits new 7ab2e6dc00e 153: onsuccess: #572: 2: Success after binutils/gcc: 28 commits new 8cf4cd80e86 154: onsuccess: #573: 2: Success after binutils/gcc: 6 commits new ad735b9f6b4 155: onsuccess: #574: 2: Success after binutils/gcc: 36 commits new 2c5fbf89040 156: onsuccess: #575: 2: Success after binutils/gcc: 27 commits new 6ce627db7ed 157: onsuccess: #576: 2: Success after binutils/gcc: 80 commits new 670d4d96e99 158: onsuccess: #577: 2: Success after binutils/gcc: 27 commits new b75daacf031 159: onsuccess: #578: 2: Success after binutils/gcc: 130 commits new ca668697302 160: onsuccess: #579: 2: Success after binutils/gcc: 17 commits new 3bc512cc4d7 161: onsuccess: #580: 2: Success after binutils/gcc: 10 commits new 26305fa73d6 162: onsuccess: #581: 2: Success after binutils/gcc: 6 commits new e21cccb65a4 163: onsuccess: #582: 2: Success after binutils/gcc: 55 commits new 3cd59cda5aa 164: onsuccess: #583: 2: Success after binutils/gcc: 110 commits new 4bd7a9b7f06 165: onsuccess: #584: 2: Success after binutils/gcc: 45 commits new 496819c9fde 166: onsuccess: #585: 2: Success after binutils/gcc: 59 commits new b58d368ace4 167: onsuccess: #586: 2: Success after binutils/gcc: 16 commits new 71eedd73ba5 168: onsuccess: #587: 2: Success after binutils/gcc: 2 commits new 9968c2aecad 169: onsuccess: #588: 2: Success after binutils/gcc: 7 commits new 247d8479f38 170: onsuccess: #589: 2: Success after binutils/gcc: 28 commits new 54fce7c8220 171: onsuccess: #590: 2: Success after binutils/gcc: 21 commits new bfd5865b150 172: onsuccess: #592: 2: Success after binutils/gcc: 57 commits new 1335e282946 173: onsuccess: #593: 2: Success after binutils/gcc: 74 commits new 529d30f1dc0 174: onsuccess: #594: 2: Success after binutils/gcc: 147 commits new c664d343ad9 175: onsuccess: #595: 2: Success after binutils/gcc: 30 commits new d5b5bfe8054 176: onsuccess: #596: 2: Success after binutils/gcc: 84 commits new 51e1b770746 177: onsuccess: #597: 2: Success after binutils/gcc: 86 commits new ab05d8508d9 178: onsuccess: #598: 2: Success after binutils/gcc: 54 commits new 40c12a09e9e 179: onsuccess: #599: 2: Success after binutils/gcc: 27 commits new 69d40560b9b 180: onsuccess: #600: 2: Success after binutils/gcc: 32 commits new 1168c7f0d82 181: onsuccess: #601: 2: Success after binutils/gcc: 13 commits new f23980b1d5e 182: onsuccess: #602: 2: Success after binutils/gcc: 32 commits new 9457ea37c69 183: onsuccess: #603: 2: Success after binutils/gcc: 33 commits new 000a303f094 184: onsuccess: #604: 2: Success after binutils/gcc: 138 commits new 7f4ac874287 185: onsuccess: #605: 2: Success after binutils/gcc: 38 commits new 8a925f52bd7 186: onsuccess: #1: 2: Success after binutils/gcc: 54 commits new ec1b76e8730 187: onsuccess: #2: 2: Success after binutils/gcc: 22 commits new eed6a266ea1 188: onsuccess: #3: 2: Success after binutils/gcc: 5 commits new 9aa662a3e9f 189: onsuccess: #4: 2: Success after binutils/gcc: 8 commits new f77c58b81ab 190: onsuccess: #5: 2: Success after binutils/gcc: 23 commits new 58249810bcb 191: onsuccess: #6: 2: Success after binutils/gcc: 65 commits new a292f888673 192: onsuccess: #7: 2: Success after binutils/gcc: 22 commits new d6e01377f7d 193: onsuccess: #8: 2: Success after binutils/gcc: 37 commits new ba0a9f57a72 194: onsuccess: #9: 2: Success after binutils/gcc: 48 commits new e2b35df0e75 195: onsuccess: #10: 2: Success after binutils/gcc: 28 commits new b1d60e6605d 196: onsuccess: #11: 2: Success after binutils/gcc: 16 commits new db5490a9c8b 197: onsuccess: #12: 2: Success after binutils/gcc: 29 commits new 5409a2cf189 198: onsuccess: #13: 2: Success after binutils/gcc: 58 commits new 6c956006061 199: onsuccess: #14: 2: Success after binutils/gcc: 31 commits new 981bdbaf2bd 200: onsuccess: #15: 2: Success after binutils/gcc: 26 commits new 9e8a94c9c53 201: onsuccess: #16: 2: Success after binutils/gcc: 55 commits new 6fde3fd9f29 202: onsuccess: #17: 2: Success after binutils/gcc: 25 commits new c5d0063ae37 203: onsuccess: #18: 2: Success after binutils/gcc: 9 commits new 7dadbe80e88 204: onsuccess: #19: 2: Success after binutils/gcc: 39 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 (a48c0ecd87b) \ 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 1764 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2776 bytes 04-build_abe-binutils/console.log.xz | Bin 38920 -> 39632 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 304580 -> 304980 bytes 06-check_regression/console.log.xz | Bin 2840 -> 2988 bytes 07-update_baseline/console.log | 68 ++++++++++----------- 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 | 20 +++--- 13 files changed, 50 insertions(+), 50 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O2_LTO updated (02b0ed791b3 -> 333e827d09e)

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-code_speed-spec2k6/gnu-aarch64-master-O2_LTO in repository toolchain/ci/base-artifacts. from 02b0ed791b3 81: onsuccess: #6: 1: [TCWG CI] No change after binutils/gc [...] new 333e827d09e 82: onsuccess: #7: 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 1868 -> 1848 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 31588 -> 31296 bytes 04-build_abe-stage1/console.log.xz | Bin 72988 -> 71820 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 7872 -> 7868 bytes 07-build_abe-glibc/console.log.xz | Bin 245608 -> 245560 bytes 08-build_abe-stage2/console.log.xz | Bin 177200 -> 176448 bytes 09-benchmark/benchmark-build.log | 144 +- 09-benchmark/benchmark.log | 142 +- 09-benchmark/console.log.xz | Bin 4112 -> 4188 bytes .../compare-results-vs-first-internal.csv | 78 +- .../compare-results-vs-prev-internal.csv | 80 +- 10-check_regression/console.log.xz | Bin 8008 -> 7996 bytes .../csv-results-vs-first-1/perf.csv | 175 +- .../csv-results-vs-first-1/results.csv | 17047 +- .../csv-results-vs-first-1/size.csv | 481243 ++++++++-------- 10-check_regression/csv-results-vs-first-1/sve.csv | 18576 +- .../csv-results-vs-first-1/vect.csv | 194 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 178 +- .../csv-results-vs-prev-0/results.csv | 33909 +- 10-check_regression/csv-results-vs-prev-0/size.csv | 544945 +++++++++--------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 19140 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 320 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 175 +- .../csv-results-vs-prev-1/results.csv | 17047 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 481243 ++++++++-------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 18576 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 194 +- 10-check_regression/results-vs-first-brief.csv | 68 +- 10-check_regression/results-vs-first-full.csv | 189 +- 10-check_regression/results-vs-first-internal.csv | 80 +- 10-check_regression/results-vs-first.csv | 80 +- 10-check_regression/results-vs-first.log | 1302 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-full.csv | 195 +- 10-check_regression/results-vs-prev-internal.csv | 80 +- 10-check_regression/results-vs-prev.csv | 80 +- 10-check_regression/results-vs-prev.log | 1584 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 16 +- .../squad-vs-first/401.bzip2/results-metadata.json | 16 +- .../squad-vs-first/403.gcc/results-metadata.json | 16 +- .../410.bwaves/results-metadata.json | 16 +- .../416.gamess/results-metadata.json | 16 +- .../squad-vs-first/429.mcf/results-metadata.json | 16 +- .../squad-vs-first/433.milc/results-metadata.json | 16 +- .../434.zeusmp/results-metadata.json | 16 +- .../435.gromacs/results-metadata.json | 16 +- .../436.cactusADM/results-metadata.json | 16 +- .../437.leslie3d/results-metadata.json | 16 +- .../squad-vs-first/444.namd/results-metadata.json | 16 +- .../squad-vs-first/445.gobmk/results-metadata.json | 16 +- .../447.dealII/results-metadata.json | 16 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 16 +- .../453.povray/results-metadata.json | 16 +- .../454.calculix/results-metadata.json | 16 +- .../squad-vs-first/456.hmmer/results-metadata.json | 16 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 16 +- .../squad-vs-first/458.sjeng/results-metrics.json | 2 +- .../459.GemsFDTD/results-metadata.json | 16 +- .../459.GemsFDTD/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 16 +- .../464.h264ref/results-metadata.json | 16 +- .../squad-vs-first/465.tonto/results-metadata.json | 16 +- .../squad-vs-first/470.lbm/results-metadata.json | 16 +- .../471.omnetpp/results-metadata.json | 16 +- .../squad-vs-first/473.astar/results-metadata.json | 16 +- .../squad-vs-first/481.wrf/results-metadata.json | 16 +- .../482.sphinx3/results-metadata.json | 16 +- .../483.xalancbmk/results-metadata.json | 16 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 16 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 48 +- mail/mail-body.txt | 48 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results_id | 2 +- 85 files changed, 832697 insertions(+), 805193 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm updated (9eba0786858 -> 89e82856564)

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_gcc/master-arm in repository toolchain/ci/base-artifacts. discards 9eba0786858 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] discards 0865a2574ea 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards c5c5af2a2e0 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards ec2bc3913bd 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 56814ea7227 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 8fcaf951bc3 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 436edc4e589 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 84ee57739bf 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards c6ee421b86c 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] discards 264de065b07 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 42aefab7bee 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 56dec98c1fc 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 4c199cde8c3 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 96bb61506ce 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 67e0e7df045 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] discards 6c80135832b 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards f6a6b7f0e85 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 3ba4ec9e18d 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 105ff778a0a 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 0e5d2e1b3d9 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 5280b69656a 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 0533882953d 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 94e396de706 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 6a3fb2cd5db 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 9d6675601cb 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 753e017e84e 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 13817fd698a 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 9b48762ca5b 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards cdb7eac0d86 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 98921baa001 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 8c0689b205f 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards e0082fe6392 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards d03a3e6c630 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 20c083eb902 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 20c0caaae18 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 72122b3c279 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 5aaae497f2c 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 9234af26b57 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] discards 15bd62006b0 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] discards 82717ee9b12 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] discards ea1b7845968 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 5baf0994bbf 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 6fe4dc6f08f 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards c78af9a1bfd 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards b3b9420b87f 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 2737e447fff 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards ba871bc142d 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards aeab41f8f9f 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 13de028dc00 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 8c40255fa7e 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 3eba04f43e6 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 57f47854f89 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] discards 243335bb55e 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards b858003a326 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards af6880e8c39 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 12b697b6212 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards be1048c69af 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards c3f69eb8674 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards c7c64594959 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] discards c8551931a10 162: onsuccess: #624: 1: Success after linux: 10 commits discards 2d98d9aed2b 161: onsuccess: #623: 1: Success after glibc: 9 commits discards 26d08e1bf37 160: onsuccess: #621: 1: Success after gcc: 11 commits discards dbb330bbe1a 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 7b477f79a75 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 35b8b9c0ff7 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards eea73e8d8dd 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards b0ed6f94f73 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 5e5d733cbe4 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] discards c82375f6793 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] discards 0a5d3b27652 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] discards b163930ed51 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards d9af29bf50e 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 730e56f2976 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 1024f55b5dd 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards e9908c81abe 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 5563d915481 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards d182059e96e 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 4622df71f6e 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] discards 4f627023b26 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 166f90e48b3 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 7535f6aa078 141: onsuccess: #601: 1: Success after linux: 794 commits discards 1061c4925e8 140: onsuccess: #600: 1: Success after gcc: 23 commits discards f1d643a4b4b 139: onsuccess: #599: 1: Success after binutils: 10 commits discards e4ea349fb82 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 07d7cb9acec 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards a3bd9f5751c 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 58fad518146 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards e6c4a214b86 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards ce60fa72d85 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 92df92e83fd 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards cf019f47d42 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 000b2ec6068 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 037fdf281cd 129: onsuccess: #588: 1: Success after linux: 4 commits discards 8256a8402a1 128: onsuccess: #586: 1: Success after binutils: 22 commits discards d906b0158a5 127: onsuccess: #584: 1: Success after linux: 21 commits discards 6293dcc56c4 126: onsuccess: #582: 1: Success after gcc: 9 commits discards 2bb7683c9bc 125: onsuccess: #581: 1: Success after binutils: 4 commits discards f10bfcbb9e5 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards 525400d30f4 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] discards 532751927de 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 394db57dfe7 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new f71328cfd35 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 7264176f163 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 1e7fc9e02cb 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] new 2e86a033bcf 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new 4a3410132f5 125: onsuccess: #581: 1: Success after binutils: 4 commits new 07acbbbc987 126: onsuccess: #582: 1: Success after gcc: 9 commits new c2e1657319d 127: onsuccess: #584: 1: Success after linux: 21 commits new 445afa3e651 128: onsuccess: #586: 1: Success after binutils: 22 commits new e988bec1365 129: onsuccess: #588: 1: Success after linux: 4 commits new c6d681c3326 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 83bc4a5032c 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 2afa1d5e88b 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 135d7c76b26 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new cebe12c29ff 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 296387481be 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new c23003abaad 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 35a9cf9725c 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 64e42c5f4b2 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 8ddaa780728 139: onsuccess: #599: 1: Success after binutils: 10 commits new c108a1b82a2 140: onsuccess: #600: 1: Success after gcc: 23 commits new 5d4b8973bf8 141: onsuccess: #601: 1: Success after linux: 794 commits new 9a7635192e1 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 6c90840b02e 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 54e9fb21d47 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] new 624b5d70bd7 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 03af869af42 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 14b6e1bad51 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 22e103e2da3 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new a4fa651c870 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 6b82e20f299 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 2d96c373717 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 8bfc35e04b1 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] new 6d6d8c41ca8 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] new ab229be65e3 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] new 68851d6d643 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new a5821473bfe 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 489118db965 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 16a44a69156 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 149a95f9ed2 159: onsuccess: #620: 1: Success after binutils: 12 commits new 1f0d67be324 160: onsuccess: #621: 1: Success after gcc: 11 commits new 1e23a0b19ba 161: onsuccess: #623: 1: Success after glibc: 9 commits new 544750e9a7c 162: onsuccess: #624: 1: Success after linux: 10 commits new 4b82226050a 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] new a04262bbaee 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new c6555379db6 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 095b1bff3e2 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 36e30fddacd 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new b670559f634 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 3860f2d1980 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new fc7f0748d18 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] new 7ac02325c5a 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new d9a316f1d7e 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 450349bec94 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 903f4f0abdc 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 6e09665fef9 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 180fdff387a 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 76e631fb684 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new d8efbb62d5a 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 8942872ba94 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 61e89d003a2 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 3eeed93ec1d 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 8ff534c29dc 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] new 6e0eaaad83c 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] new 2e062922ecf 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] new 4caabf32173 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 24d6734a657 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new b951b694db1 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 1db3feedc8b 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 95c582ee6b4 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 2a2a44bcd97 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new c1300bcf7bc 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 70dd5a71a2b 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 5c20cfd0a05 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 7c7ffe9e1f7 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 9246f817db7 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 5b0a25dd873 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new eea0b6550aa 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 4b11cb36701 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 20789c535d5 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 677aae9325b 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new f2a84b53c56 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 74e0ef15e76 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new d9a5d4b77d5 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 7b7eb8abe74 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new c4438505ab7 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 81283c18878 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 8099d95243a 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] new 7c4fa887058 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 13f2ca4d4d0 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 57c898cd113 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 7dc84be3176 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new f73c4710bc8 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 618931e195e 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] new 9ec2df28faf 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new af8f7ff3bca 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 8bdcc52f6d5 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 1b4e9821d6a 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new b141cb3f372 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new b07e6959cbd 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 47e746f7ebf 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new ed2f4f05971 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] new 89e82856564 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] 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 (9eba0786858) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...] 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 1756 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 52840 -> 52644 bytes 04-build_abe-gcc/console.log.xz | Bin 237428 -> 238228 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8520 -> 8352 bytes 07-build_abe-glibc/console.log.xz | Bin 235572 -> 237316 bytes 08-build_abe-gdb/console.log.xz | Bin 51164 -> 51332 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3748 -> 3832 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3812 -> 2664 bytes 11-check_regression/console.log.xz | Bin 5884 -> 6956 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 6 + 11-check_regression/mail-body.txt | 54 +++-- 11-check_regression/results.compare | 25 ++- 11-check_regression/results.compare2 | 68 +++++- 11-check_regression/results.regressions | 26 +++ 12-update_baseline/console.log | 64 +++--- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 56 +++-- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++-- results | 26 +++ sumfiles/g++.log.xz | Bin 2907112 -> 2888232 bytes sumfiles/g++.sum | 119 ++++++----- sumfiles/gcc.log.xz | Bin 2495892 -> 2482528 bytes sumfiles/gcc.sum | 363 +++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 952564 -> 957196 bytes sumfiles/gfortran.sum | 38 ++-- sumfiles/libatomic.log.xz | Bin 2276 -> 2276 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 233952 -> 234256 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2692 -> 2696 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 476848 -> 469440 bytes sumfiles/libstdc++.sum | 8 +- 43 files changed, 535 insertions(+), 399 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[gcc] branch master updated (c981f61c071 -> 23532dac3f6)

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 c981f61c071 xtensa: Remove REG_OK_STRICT and its derivatives new fa9d3aa6789 analyzer, testsuite: add test coverage for various builtins new 129664c67b7 testsuite: add test coverage for PR analyzer/108045 new 23532dac3f6 testsuite: add test coverage for analyzer leak false +ve [P [...] The 3 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/testsuite/gcc.dg/analyzer/exec-1.c | 43 +++++++++ gcc/testsuite/gcc.dg/analyzer/leak-pr105906.c | 32 ++++++ .../analyzer/leak-pr108045-with-call-summaries.c | 106 ++++++++++++++++++++ .../leak-pr108045-without-call-summaries.c | 107 +++++++++++++++++++++ .../{sprintf-concat.c => snprintf-concat.c} | 8 +- gcc/testsuite/gcc.dg/analyzer/vsnprintf-1.c | 11 +++ 6 files changed, 303 insertions(+), 4 deletions(-) create mode 100644 gcc/testsuite/gcc.dg/analyzer/exec-1.c create mode 100644 gcc/testsuite/gcc.dg/analyzer/leak-pr105906.c create mode 100644 gcc/testsuite/gcc.dg/analyzer/leak-pr108045-with-call-summaries.c create mode 100644 gcc/testsuite/gcc.dg/analyzer/leak-pr108045-without-call-summaries.c copy gcc/testsuite/gcc.dg/analyzer/{sprintf-concat.c => snprintf-concat.c} (68%) create mode 100644 gcc/testsuite/gcc.dg/analyzer/vsnprintf-1.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-arm updated (20aa69ef099 -> bfa8b76453e)

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_fast_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards 20aa69ef099 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 45fe97df612 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards 1b0cdcd4cff 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 508b9bfb88f 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 0c2074f1212 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 21a341e931d 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards a2b233654bd 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 3d1552fc000 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 59f1230b805 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards c95620dc150 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards a752abfeb54 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards 2dddc281032 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards f738a4aabe7 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards ad0319b72ae 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 2eb18287d56 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards a5f92988cb9 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 3b7f1a3cdec 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards ebb3e9b6969 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards a71107508ba 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards 97c09ca871f 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards c3718a19ad6 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards 54a8000b745 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards 2635b5bde2f 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 2d3070ba814 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards 4aca07ffbd9 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 309f98952bb 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards b7474e29dcc 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards 7248f3e620a 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards 04a2550293f 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards 8238eccbfeb 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards e88ea63ccda 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards 03e2d47bdeb 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards f9ccc745e0e 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards 5e3fa3bbe87 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 62b2f3ebd1d 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards e618c1db353 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards eae2ed91a00 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards b91c08ac394 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards 3110e7c5bc5 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 3a0a74218e4 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards d739f9cb32b 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 4c8733da6f5 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards e5f57966195 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards ec963556763 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards 98efb89399e 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards 9bed91787ce 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 23cf339ad0f 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards 38cb8d67c7d 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards b6ed672f7e7 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards 35f551e1755 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards 0054d9ba97e 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards 0677376f0d1 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 7998c4506a0 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards c332572c2fb 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards 3d218c3b0c7 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards 7224e341370 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 00721b37397 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards 3f00b200768 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards e8b5d92068e 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 88995276154 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards bf3b4959b2e 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards 895f4334038 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 34c00197a38 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 7e300a2f0a5 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards c33554f18b6 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 55ac63d1011 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards e53290b4138 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards 6d70b10a11a 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards b9b11fc912a 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards 4b608cbcbce 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards 836f92aea6f 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards bc6bfa50e23 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 25f579f9fa4 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards 5ce318569e2 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards 815067a8ccd 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards bd6ac125422 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards e4b0d1a08dc 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards 7cf9d55e576 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards e4bda099a20 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards d4d343a7f5b 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards 31685603e94 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards 24337a0d4fe 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards 4d49721db59 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 5ce81aaba08 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 3f4df179440 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards 01f14ffa845 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] discards 45e8b4e9638 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards 3c38605822b 31: onsuccess: #38: 1: Success after linux: 14 commits discards 491339085d4 30: onsuccess: #36: 1: Success after binutils: 18 commits discards ee758f106be 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 3d61a22e1fc 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 5bfa791e975 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 2ecc62004a4 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards f033a5a929e 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] discards 8f9e623a9a4 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] discards 29a679fdc1b 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] discards aee2e47a29a 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards ca98fcdaf8a 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards e5d6a98cd22 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] discards 3ee96fe0303 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb [...] discards ccf1e8131d6 18: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] new 5d732194ac0 18: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] new f8d50cd97e7 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb [...] new 960c388bb23 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] new 200217fd44b 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new ae1552496cb 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 97d1316642e 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new d7f4245ebbc 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] new 88fd6d50c9b 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] new fd9d2354ecd 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 172b59ec7b4 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 87f7721ab59 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 0f73b74e5c4 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 35abb5d85e0 30: onsuccess: #36: 1: Success after binutils: 18 commits new 4039528a0b9 31: onsuccess: #38: 1: Success after linux: 14 commits new 8852001971e 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new d5dfdeedad2 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new 696cf57b510 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 86e87cac14b 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 3d5d9bbe9d2 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new e8ca4698a00 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 04a627d57dc 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new 6505dc5e47a 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new 5d600236e6e 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new 4b2cb7ed22e 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new fc71be48e8f 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new b4836a1b3bf 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new d2d05a1500f 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 98c68eb3d6b 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new 7d8cf27d4c1 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new 62d008ca077 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 54b44e70cc5 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new b1b3526131c 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new e32619fb2a1 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new e3f627ff693 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new a967bfea29a 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new a7c44791afd 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 4053e8c88ab 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 1b06ca78e8a 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new 46f7f1dc102 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new e6c47a0361b 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new 3b24a9ba51f 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new 19f9e78b643 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new 338c337bd4f 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 56385904c10 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new fd8cc37e878 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new fe942c759ad 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 280aa83a77b 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new 622db248d8d 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new deb4c5ec230 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new c40bcc24d87 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 1939b60e9ee 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new 11b4f4fe667 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new d034afff71a 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new 94cc050870a 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 2abba98757b 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new 77122be8fc8 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 8bea0d40daa 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new adbe2548b23 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new 1f99f0ad03a 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new af492a3f8ca 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new d587000d43f 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new ea284dc68e7 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new e1fd64faea5 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new d22db1cf0f2 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new 7e484db4c2b 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new 72757c6d3f5 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 3ed80257e47 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 99f61f2924f 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new 653fe13e804 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new ff202ff8e13 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new 183491ecc00 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 3518323a920 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new 506740141f6 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new 8a339daee9c 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new 050f3f03787 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 9c7e48d510b 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new ed36a95dcce 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 66d9746ec43 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new b090318addb 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 1ab1b551cad 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new d082c300d9f 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 93c12b0e95d 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 0b74028b4ed 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new 26218f3c6ec 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new 7f7a86b4f33 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new f2edb3f86c8 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new d29081e3788 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 526dc3adc31 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 14c5081a03d 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new ed05188115e 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 2e23a531ad3 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new 6a96af5c29d 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 2b188667caa 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 4b84ae309c6 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 5090c42e513 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 805b8b87f56 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new 43c8ca71595 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new dadabdd9797 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new b570a8165be 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 8abfa449c75 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new 01265d697b3 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new bfa8b76453e 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] 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 (20aa69ef099) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_fast_check_gd [...] 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 1784 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2804 bytes 03-build_abe-binutils/console.log.xz | Bin 53544 -> 53908 bytes 04-build_abe-gcc/console.log.xz | Bin 239860 -> 238688 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8544 -> 8272 bytes 07-build_abe-glibc/console.log.xz | Bin 235624 -> 235692 bytes 08-build_abe-gdb/console.log.xz | Bin 50164 -> 50516 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3744 -> 3748 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2384 -> 2616 bytes 11-check_regression/console.log.xz | Bin 5528 -> 6144 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 44 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++++++++++++++--------------- sumfiles/gdb.log.xz | Bin 11932 -> 11920 bytes sumfiles/gdb.sum | 30 +++++++++++------------ 26 files changed, 70 insertions(+), 70 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_vect-spec2k6/gnu-aarch64-master-O3 updated (7e20c265aec -> 0a975d4542e)

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-code_vect-spec2k6/gnu-aarch64-master-O3 in repository toolchain/ci/base-artifacts. from 7e20c265aec 1: onsuccess: #2: 1: [TCWG CI] No change after binutils/gcc [...] new 0a975d4542e 2: onsuccess: #3: 1: [TCWG CI] No change after binutils/gcc [...] 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 1764 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 31904 -> 31448 bytes 04-build_abe-stage1/console.log.xz | Bin 73392 -> 72172 bytes 06-build_abe-linux/console.log.xz | Bin 8636 -> 8632 bytes 07-build_abe-glibc/console.log.xz | Bin 246272 -> 245956 bytes 08-build_abe-stage2/console.log.xz | Bin 181568 -> 179048 bytes 09-benchmark/benchmark-build.log | 108 +- 09-benchmark/benchmark.log | 106 +- 09-benchmark/console.log.xz | Bin 3980 -> 4032 bytes .../compare-results-vs-first-internal.csv | 238 +- .../compare-results-vs-prev-internal.csv | 244 +- 10-check_regression/console.log.xz | Bin 13824 -> 13428 bytes .../csv-results-vs-first-1/md5sum.csv | 2089 +- .../csv-results-vs-first-1/perf.csv | 2588 +- .../csv-results-vs-first-1/results.csv | 4045 +- .../csv-results-vs-first-1/size.csv | 503134 +++++++++--------- 10-check_regression/csv-results-vs-first-1/sve.csv | 15478 +- .../csv-results-vs-first-1/vect.csv | 4092 +- .../csv-results-vs-prev-0/md5sum.csv | 2256 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 2592 +- .../csv-results-vs-prev-0/results.csv | 9579 +- 10-check_regression/csv-results-vs-prev-0/size.csv | 487692 ++++++++--------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 15462 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 3564 +- .../csv-results-vs-prev-1/md5sum.csv | 2089 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 2588 +- .../csv-results-vs-prev-1/results.csv | 4045 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 503134 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 15478 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 4092 +- 10-check_regression/results-vs-first-brief.csv | 66 +- 10-check_regression/results-vs-first-full.csv | 2516 +- 10-check_regression/results-vs-first-internal.csv | 238 +- 10-check_regression/results-vs-first.csv | 238 +- 10-check_regression/results-vs-first.log | 1260 +- 10-check_regression/results-vs-prev-brief.csv | 66 +- 10-check_regression/results-vs-prev-compare.csv | 6 +- 10-check_regression/results-vs-prev-full.csv | 2734 +- 10-check_regression/results-vs-prev-internal.csv | 244 +- 10-check_regression/results-vs-prev.csv | 244 +- 10-check_regression/results-vs-prev.log | 1454 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 16 +- .../400.perlbench/results-metrics.json | 2 +- .../squad-vs-first/401.bzip2/results-metadata.json | 16 +- .../squad-vs-first/401.bzip2/results-metrics.json | 2 +- .../squad-vs-first/403.gcc/results-metadata.json | 16 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../410.bwaves/results-metadata.json | 16 +- .../squad-vs-first/410.bwaves/results-metrics.json | 2 +- .../416.gamess/results-metadata.json | 16 +- .../squad-vs-first/429.mcf/results-metadata.json | 16 +- .../squad-vs-first/429.mcf/results-metrics.json | 2 +- .../squad-vs-first/433.milc/results-metadata.json | 16 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../434.zeusmp/results-metadata.json | 16 +- .../squad-vs-first/434.zeusmp/results-metrics.json | 2 +- .../435.gromacs/results-metadata.json | 16 +- .../435.gromacs/results-metrics.json | 2 +- .../436.cactusADM/results-metadata.json | 16 +- .../436.cactusADM/results-metrics.json | 2 +- .../437.leslie3d/results-metadata.json | 16 +- .../437.leslie3d/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 16 +- .../squad-vs-first/444.namd/results-metrics.json | 2 +- .../squad-vs-first/445.gobmk/results-metadata.json | 16 +- .../squad-vs-first/445.gobmk/results-metrics.json | 2 +- .../447.dealII/results-metadata.json | 16 +- .../450.soplex/results-metadata.json | 16 +- .../squad-vs-first/450.soplex/results-metrics.json | 2 +- .../453.povray/results-metadata.json | 16 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../454.calculix/results-metadata.json | 16 +- .../454.calculix/results-metrics.json | 2 +- .../squad-vs-first/456.hmmer/results-metadata.json | 16 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 16 +- .../squad-vs-first/458.sjeng/results-metrics.json | 2 +- .../459.GemsFDTD/results-metadata.json | 16 +- .../459.GemsFDTD/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 16 +- .../464.h264ref/results-metadata.json | 16 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/465.tonto/results-metadata.json | 16 +- .../squad-vs-first/465.tonto/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 16 +- .../squad-vs-first/470.lbm/results-metrics.json | 2 +- .../471.omnetpp/results-metadata.json | 16 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 16 +- .../squad-vs-first/473.astar/results-metrics.json | 2 +- .../squad-vs-first/481.wrf/results-metadata.json | 16 +- .../squad-vs-first/481.wrf/results-metrics.json | 2 +- .../482.sphinx3/results-metadata.json | 16 +- .../482.sphinx3/results-metrics.json | 2 +- .../483.xalancbmk/results-metadata.json | 16 +- .../squad-vs-first/Mean/results-metadata.json | 16 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 47 +- mail/mail-body.txt | 47 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results_id | 2 +- 108 files changed, 797286 insertions(+), 797269 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[linux] branch master updated (eeac8ede1755 -> fc89d7fb499b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository linux. from eeac8ede1755 Linux 6.3-rc2 new aed8efddd39b vp_vdpa: fix the crash in hot unplug with vp_vdpa new 09e65ee9059d vdpa/mlx5: should not activate virtq object when suspended new 5a522150093a vhost-vdpa: free iommu domain after last use during cleanup new b4cca6d48eb3 vdpa_sim: set last_used_idx as last_avail_idx in vdpasim_q [...] new ae43c20da2a7 tools/virtio: Ignore virtio-trace/trace-agent new fc89d7fb499b Merge tag 'for_linus' of git://git.kernel.org/pub/scm/linu [...] The 6 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: drivers/vdpa/mlx5/core/mlx5_vdpa.h | 1 + drivers/vdpa/mlx5/net/mlx5_vnet.c | 6 +++++- drivers/vdpa/vdpa_sim/vdpa_sim.c | 11 +++++++++++ drivers/vdpa/virtio_pci/vp_vdpa.c | 2 +- drivers/vhost/vdpa.c | 3 ++- tools/virtio/.gitignore | 1 + 6 files changed, 21 insertions(+), 3 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits March 2023