Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-defconfig updated (5d8febdbe7 -> 094fbe09ae)

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 5d8febdbe7 35: onsuccess: #507: 7630: Success after llvm: 23 commits new 094fbe09ae 36: onsuccess: #509: boot: Success after binutils/llvm: 223 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 1744 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 32472 -> 32072 bytes 04-build_kernel_llvm/console.log.xz | Bin 65464 -> 64124 bytes 05-build_abe-qemu/console.log.xz | Bin 32252 -> 31904 bytes 06-build_linux/console.log.xz | Bin 6048 -> 3196 bytes 07-boot_linux/console.log.xz | Bin 0 -> 6184 bytes 08-check_regression/console.log.xz | Bin 2916 -> 3280 bytes 08-check_regression/mail-body.txt | 15 +++++---------- 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 17 ++++++----------- mail/mail-subject.txt | 2 +- manifest.sh | 25 +++++++++++++------------ results | 6 +++++- 18 files changed, 38 insertions(+), 43 deletions(-) create mode 100644 07-boot_linux/console.log.xz -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[gcc] branch devel/omp/gcc-12 updated (38d6201af06 -> 30a1cd1e468)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch devel/omp/gcc-12 in repository gcc. from 38d6201af06 Merge branch 'releases/gcc-12' into devel/omp/gcc-12 adds df5fb956289 Daily bump. adds c6a1f7e00cd Factor out jobserver_active_p. adds e4b5fec75aa lto: support --jobserver-style=fifo for recent GNU make adds 6e09c1d71d2 bootstrap/106482 - document minimal GCC version adds 7773d43cc8a Daily bump. adds 4600a343c07 Daily bump. adds d862a689ca1 Skip guality tests on hppa-hpux. adds c082e49dce2 Daily bump. adds b63cdd35072 Daily bump. adds a3fbfc1027e Daily bump. new 30a1cd1e468 Merge branch 'releases/gcc-12' into devel/omp/gcc-12 The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/ChangeLog | 30 +++++++++++++++ gcc/DATESTAMP | 2 +- gcc/doc/install.texi | 6 ++- gcc/gcc.cc | 37 +++--------------- gcc/lto-wrapper.cc | 44 +++++----------------- gcc/opts-common.cc | 54 +++++++++++++++++++++++++++ gcc/opts-jobserver.h | 46 +++++++++++++++++++++++ gcc/testsuite/ChangeLog | 6 +++ gcc/testsuite/g++.dg/guality/guality.exp | 4 ++ gcc/testsuite/gcc.dg/guality/guality.exp | 4 ++ gcc/testsuite/gfortran.dg/guality/guality.exp | 4 ++ libgfortran/ChangeLog | 7 ++++ libstdc++-v3/ChangeLog | 27 ++++++++++++++ 13 files changed, 201 insertions(+), 70 deletions(-) create mode 100644 gcc/opts-jobserver.h -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled_lto updated (a2c2ea4ffc -> 5462359935)

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 a2c2ea4ffc 131: onsuccess: #546: 2: Success after binutils/gcc: 24 commits discards 16c052233f 130: onsuccess: #545: 2: Success after binutils/gcc: 9 commits discards 5b375c7c27 129: onsuccess: #544: 2: Success after binutils/gcc: 79 commits discards 2d069a929c 128: onsuccess: #543: 2: Success after binutils/gcc: 52 commits discards 6440317059 127: onsuccess: #542: 2: Success after binutils/gcc: 66 commits discards 85293fb76c 126: onsuccess: #541: 2: Success after binutils/gcc: 17 commits discards f86f925896 125: onsuccess: #540: 2: Success after binutils/gcc: 53 commits discards cd0c1d6ed7 124: onsuccess: #539: 2: Success after binutils/gcc: 9 commits discards 89892d9687 123: onsuccess: #538: 2: Success after binutils/gcc: 14 commits discards 5180c9be68 122: onsuccess: #537: 2: Success after binutils/gcc: 36 commits discards f4da2fd4a1 121: onsuccess: #536: 1: Success after binutils/gcc: 76 commits discards b8e858a6a1 120: onsuccess: #535: 1: Success after binutils: 10 commits discards c71622fa72 119: force: #534: 1: Failure after gdb-12-branchpoint-3046-g [...] discards 6624d1f8ec 118: force: #533: 2: Success after binutils: 4 commits discards 65484466f5 117: onsuccess: #531: 2: Success after gcc: 65 commits discards 95af6ff7aa 116: onsuccess: #528: 2: Success after binutils/gcc: 48 commits discards 9b2d3695a9 115: onsuccess: #527: 2: Success after binutils/gcc: 11 commits discards c44cbb9e12 114: onsuccess: #526: 2: Success after binutils/gcc: 3 commits discards c576684f93 113: onsuccess: #525: 2: Success after binutils/gcc: 35 commits discards 168880da74 112: onsuccess: #524: 2: Success after binutils/gcc: 32 commits discards 4d080cde04 111: onsuccess: #523: 2: Success after binutils/gcc: 26 commits discards 9a8f0eb811 110: onsuccess: #522: 2: Success after binutils/gcc: 47 commits discards b0df5f4765 109: onsuccess: #521: 2: Success after binutils/gcc: 32 commits discards 7956b6aa10 108: onsuccess: #520: 2: Success after binutils/gcc: 13 commits discards db2c833bb8 107: onsuccess: #519: 2: Success after binutils/gcc: 8 commits discards 07c3b6cc67 106: onsuccess: #518: 2: Success after binutils/gcc: 31 commits discards 7b9eb323e0 105: onsuccess: #517: 2: Success after binutils/gcc: 52 commits discards 194862c29d 104: onsuccess: #516: 2: Success after binutils/gcc: 44 commits discards 849e8ed57d 103: onsuccess: #515: 2: Success after binutils/gcc: 22 commits discards ff703b0b7c 102: onsuccess: #514: 2: Success after binutils/gcc: 118 commits discards f7ff450bed 101: onsuccess: #513: 2: Success after binutils/gcc: 6 commits discards 8a466f28f5 100: onsuccess: #512: 2: Success after binutils/gcc: 27 commits discards 2c47dff816 99: onsuccess: #510: 2: Success after binutils/gcc: 48 commits discards b4e1c6418a 98: onsuccess: #509: 2: Success after binutils/gcc: 27 commits discards f723f615cc 97: onsuccess: #508: 2: Success after binutils/gcc: 46 commits discards 0ad09fbef7 96: onsuccess: #507: 2: Success after binutils/gcc: 55 commits discards 4f1dd9354a 95: onsuccess: #506: 2: Success after binutils/gcc: 29 commits discards af8e6aba29 94: onsuccess: #502: 2: Success after binutils/gcc: 37 commits discards b39cf96e4f 93: onsuccess: #501: 2: Success after binutils/gcc: 301 commits discards 7344cc8b70 92: onsuccess: #499: 2: Success after binutils: 4 commits discards e998b076fd 91: onsuccess: #497: 2: Success after binutils/gcc: 58 commits discards 5980c27506 90: onsuccess: #496: 2: Success after binutils/gcc: 49 commits discards b830f680df 89: onsuccess: #495: 2: Success after binutils/gcc: 62 commits discards d21452d9af 88: onsuccess: #494: 2: Success after binutils/gcc: 139 commits discards 83651014f0 87: onsuccess: #493: 2: Success after binutils/gcc: 13 commits discards 79ed03fcdb 86: onsuccess: #492: 2: Success after binutils/gcc: 22 commits discards 6dde31e1c3 85: onsuccess: #491: 2: Success after binutils/gcc: 71 commits discards ac39f4e1f3 84: onsuccess: #490: 2: Success after binutils/gcc: 42 commits discards bf12572dd9 83: onsuccess: #489: 2: Success after binutils/gcc: 33 commits discards 6d74c9d596 82: onsuccess: #488: 2: Success after binutils/gcc: 65 commits discards 020ec34b0a 81: onsuccess: #486: 2: Success after binutils/gcc: 3 commits discards 0c0440e35c 80: onsuccess: #485: 2: Success after binutils/gcc: 24 commits discards 0480812c18 79: onsuccess: #484: 2: Success after binutils/gcc: 34 commits discards e01400b50c 78: onsuccess: #483: 2: Success after binutils/gcc: 30 commits discards dd74b0938f 77: onsuccess: #482: 2: Success after binutils/gcc: 34 commits discards b08327b89c 76: onsuccess: #481: 2: Success after binutils/gcc: 76 commits discards 76d8978776 75: onsuccess: #480: 2: Success after binutils/gcc: 6 commits discards 90edbbf7aa 74: onsuccess: #479: 2: Success after binutils/gcc: 6 commits discards 3432429fd0 73: onsuccess: #478: 2: Success after binutils/gcc: 39 commits discards 9ee90d8016 72: onsuccess: #477: 2: Success after binutils/gcc: 47 commits discards 57bccf9819 71: onsuccess: #476: 2: Success after binutils/gcc: 47 commits discards b20ac141db 70: onsuccess: #475: 2: Success after binutils/gcc: 44 commits discards 47eefcae4f 69: onsuccess: #474: 2: Success after binutils/gcc: 46 commits discards 88905b3089 68: onsuccess: #473: 2: Success after binutils/gcc: 9 commits discards 0256e8abab 67: onsuccess: #472: 2: Success after binutils/gcc: 5 commits discards 22c217d7f0 66: onsuccess: #471: 2: Success after binutils/gcc: 53 commits discards 4673217854 65: onsuccess: #470: 2: Success after binutils/gcc: 28 commits discards 62082412f5 64: onsuccess: #469: 2: Success after binutils/gcc: 41 commits discards 393cfcfcfc 63: onsuccess: #468: 2: Success after binutils/gcc: 61 commits discards b60713e21a 62: onsuccess: #467: 1: Success after binutils/gcc: 50 commits discards c09ecca253 61: onsuccess: #466: 1: Success after binutils/gcc: 12 commits discards c1ef01eced 60: onsuccess: #465: 1: Success after basepoints/gcc-13-3173 [...] discards 7350fdf4b9 59: force: #464: 1: Failure after basepoints/gcc-13-3172-gf3 [...] discards 04caad3c5e 58: force: #463: 2: Success after gcc: 30 commits discards edfb3df043 57: onsuccess: #460: 2: Success after binutils: 8 commits discards 0199a298ef 56: onsuccess: #458: 2: Success after binutils/gcc: 54 commits discards 5c17f92a6a 55: onsuccess: #457: 2: Success after binutils/gcc: 30 commits discards bdf5a24852 54: onsuccess: #456: 2: Success after binutils/gcc: 47 commits discards 1f30bc2a89 53: onsuccess: #455: 2: Success after binutils/gcc: 34 commits discards e97b9924eb 52: onsuccess: #454: 2: Success after binutils/gcc: 183 commits discards 301b0f37fa 51: onsuccess: #453: 1: Success after gcc: 20 commits discards 7c0b79de7b 50: force: #452: 1: Failure after basepoints/gcc-13-2887-gb0 [...] discards 299c2d6d64 49: force: #451: 2: Success after basepoints/gcc-13-2886-g8b [...] discards 1a6e153e49 48: onsuccess: #448: 2: Success after binutils: 6 commits discards 1e17b228e8 47: onsuccess: #446: 2: Success after binutils/gcc: 54 commits discards f08e8d148c 46: onsuccess: #445: 2: Success after binutils/gcc: 12 commits discards facfffd4c4 45: onsuccess: #444: 2: Success after binutils/gcc: 9 commits discards a70f614668 44: onsuccess: #443: 2: Success after binutils/gcc: 100 commits discards 950059a397 43: onsuccess: #441: 2: Success after binutils/gcc: 36 commits discards e6d58ebd11 42: onsuccess: #440: 2: Success after binutils/gcc: 41 commits discards 0b46d0fe98 41: onsuccess: #439: 2: Success after binutils/gcc: 8 commits discards e8d73a103b 40: onsuccess: #438: 2: Success after binutils/gcc: 7 commits discards e597d62c90 39: onsuccess: #437: 2: Success after binutils/gcc: 6 commits discards 0fd2447c54 38: onsuccess: #436: 2: Success after binutils/gcc: 25 commits discards 656d13d8e1 37: onsuccess: #435: 2: Success after binutils/gcc: 19 commits discards b27632e65a 36: onsuccess: #434: 2: Success after binutils/gcc: 34 commits discards c3d4f95fc0 35: onsuccess: #433: 2: Success after binutils/gcc: 29 commits discards 61ba61c440 34: onsuccess: #432: 2: Success after binutils/gcc: 68 commits discards c8f63000d7 33: onsuccess: #431: 2: Success after binutils/gcc: 4 commits discards 2a338dfa88 32: onsuccess: #430: 2: Success after binutils/gcc: 7 commits discards 19a50e34a9 31: onsuccess: #429: 2: Success after binutils/gcc: 25 commits new f63871fd84 31: onsuccess: #429: 2: Success after binutils/gcc: 25 commits new 9734ab526a 32: onsuccess: #430: 2: Success after binutils/gcc: 7 commits new d2847c2e1d 33: onsuccess: #431: 2: Success after binutils/gcc: 4 commits new 48b3830979 34: onsuccess: #432: 2: Success after binutils/gcc: 68 commits new f5a916f2b4 35: onsuccess: #433: 2: Success after binutils/gcc: 29 commits new be4c41a7be 36: onsuccess: #434: 2: Success after binutils/gcc: 34 commits new 5dafd2d072 37: onsuccess: #435: 2: Success after binutils/gcc: 19 commits new 9a0ed883ca 38: onsuccess: #436: 2: Success after binutils/gcc: 25 commits new 43545270bf 39: onsuccess: #437: 2: Success after binutils/gcc: 6 commits new 44be5f03d5 40: onsuccess: #438: 2: Success after binutils/gcc: 7 commits new 4796348b4d 41: onsuccess: #439: 2: Success after binutils/gcc: 8 commits new 7e062304b1 42: onsuccess: #440: 2: Success after binutils/gcc: 41 commits new be16f53c2a 43: onsuccess: #441: 2: Success after binutils/gcc: 36 commits new 62350fed1b 44: onsuccess: #443: 2: Success after binutils/gcc: 100 commits new 3ca51c1bc4 45: onsuccess: #444: 2: Success after binutils/gcc: 9 commits new e1ac1ae729 46: onsuccess: #445: 2: Success after binutils/gcc: 12 commits new 02652d64e6 47: onsuccess: #446: 2: Success after binutils/gcc: 54 commits new 3b95e957a5 48: onsuccess: #448: 2: Success after binutils: 6 commits new 466143fd18 49: force: #451: 2: Success after basepoints/gcc-13-2886-g8b [...] new 20ab7c6758 50: force: #452: 1: Failure after basepoints/gcc-13-2887-gb0 [...] new 2cbd2e0186 51: onsuccess: #453: 1: Success after gcc: 20 commits new eb85050ce9 52: onsuccess: #454: 2: Success after binutils/gcc: 183 commits new e128784edc 53: onsuccess: #455: 2: Success after binutils/gcc: 34 commits new aa28f55590 54: onsuccess: #456: 2: Success after binutils/gcc: 47 commits new 87cd17b917 55: onsuccess: #457: 2: Success after binutils/gcc: 30 commits new 4813fea9e7 56: onsuccess: #458: 2: Success after binutils/gcc: 54 commits new f08b91f5a7 57: onsuccess: #460: 2: Success after binutils: 8 commits new 27f302e28e 58: force: #463: 2: Success after gcc: 30 commits new b48e0854be 59: force: #464: 1: Failure after basepoints/gcc-13-3172-gf3 [...] new fb76548c96 60: onsuccess: #465: 1: Success after basepoints/gcc-13-3173 [...] new 004d8b81d5 61: onsuccess: #466: 1: Success after binutils/gcc: 12 commits new f8f519eb0e 62: onsuccess: #467: 1: Success after binutils/gcc: 50 commits new 8996e9ea10 63: onsuccess: #468: 2: Success after binutils/gcc: 61 commits new a37706e913 64: onsuccess: #469: 2: Success after binutils/gcc: 41 commits new 6d903235ce 65: onsuccess: #470: 2: Success after binutils/gcc: 28 commits new 4ee20844ab 66: onsuccess: #471: 2: Success after binutils/gcc: 53 commits new cb271d8264 67: onsuccess: #472: 2: Success after binutils/gcc: 5 commits new 4563f08595 68: onsuccess: #473: 2: Success after binutils/gcc: 9 commits new 71d4d7b19a 69: onsuccess: #474: 2: Success after binutils/gcc: 46 commits new 756bbac3ea 70: onsuccess: #475: 2: Success after binutils/gcc: 44 commits new 11aab9d43c 71: onsuccess: #476: 2: Success after binutils/gcc: 47 commits new 48646ea337 72: onsuccess: #477: 2: Success after binutils/gcc: 47 commits new 579ec4c2b5 73: onsuccess: #478: 2: Success after binutils/gcc: 39 commits new 535b5411a2 74: onsuccess: #479: 2: Success after binutils/gcc: 6 commits new ed4fb4a0fe 75: onsuccess: #480: 2: Success after binutils/gcc: 6 commits new ce04b733c7 76: onsuccess: #481: 2: Success after binutils/gcc: 76 commits new 21774e98cb 77: onsuccess: #482: 2: Success after binutils/gcc: 34 commits new fbccf27df3 78: onsuccess: #483: 2: Success after binutils/gcc: 30 commits new 7c39c0b646 79: onsuccess: #484: 2: Success after binutils/gcc: 34 commits new 347c72ca24 80: onsuccess: #485: 2: Success after binutils/gcc: 24 commits new 46594c25e9 81: onsuccess: #486: 2: Success after binutils/gcc: 3 commits new 497f05d7b6 82: onsuccess: #488: 2: Success after binutils/gcc: 65 commits new 87bc3599df 83: onsuccess: #489: 2: Success after binutils/gcc: 33 commits new c8ccce72dc 84: onsuccess: #490: 2: Success after binutils/gcc: 42 commits new f28a25046a 85: onsuccess: #491: 2: Success after binutils/gcc: 71 commits new c9d2a23f83 86: onsuccess: #492: 2: Success after binutils/gcc: 22 commits new 757723994f 87: onsuccess: #493: 2: Success after binutils/gcc: 13 commits new 13ea1f8510 88: onsuccess: #494: 2: Success after binutils/gcc: 139 commits new 7735891117 89: onsuccess: #495: 2: Success after binutils/gcc: 62 commits new 7ad70e5bec 90: onsuccess: #496: 2: Success after binutils/gcc: 49 commits new 3606fd8f7f 91: onsuccess: #497: 2: Success after binutils/gcc: 58 commits new 854c5f9189 92: onsuccess: #499: 2: Success after binutils: 4 commits new 04e9a3721b 93: onsuccess: #501: 2: Success after binutils/gcc: 301 commits new 70e333222f 94: onsuccess: #502: 2: Success after binutils/gcc: 37 commits new 5b08aaa415 95: onsuccess: #506: 2: Success after binutils/gcc: 29 commits new 4582c4edd4 96: onsuccess: #507: 2: Success after binutils/gcc: 55 commits new 7442ec8162 97: onsuccess: #508: 2: Success after binutils/gcc: 46 commits new c3383579a2 98: onsuccess: #509: 2: Success after binutils/gcc: 27 commits new bbe9f99bd2 99: onsuccess: #510: 2: Success after binutils/gcc: 48 commits new 7774d2dfa7 100: onsuccess: #512: 2: Success after binutils/gcc: 27 commits new d389a75370 101: onsuccess: #513: 2: Success after binutils/gcc: 6 commits new 3baae445dc 102: onsuccess: #514: 2: Success after binutils/gcc: 118 commits new 3ff1f2d053 103: onsuccess: #515: 2: Success after binutils/gcc: 22 commits new 5174a092b0 104: onsuccess: #516: 2: Success after binutils/gcc: 44 commits new 9c22851e78 105: onsuccess: #517: 2: Success after binutils/gcc: 52 commits new 462bcac55d 106: onsuccess: #518: 2: Success after binutils/gcc: 31 commits new dae52b8e36 107: onsuccess: #519: 2: Success after binutils/gcc: 8 commits new 314ea07cec 108: onsuccess: #520: 2: Success after binutils/gcc: 13 commits new 773ce06b58 109: onsuccess: #521: 2: Success after binutils/gcc: 32 commits new 2f422e3e3c 110: onsuccess: #522: 2: Success after binutils/gcc: 47 commits new 28c60b1539 111: onsuccess: #523: 2: Success after binutils/gcc: 26 commits new eef3038501 112: onsuccess: #524: 2: Success after binutils/gcc: 32 commits new def2ab60c6 113: onsuccess: #525: 2: Success after binutils/gcc: 35 commits new 93de1619a3 114: onsuccess: #526: 2: Success after binutils/gcc: 3 commits new 37bc74417c 115: onsuccess: #527: 2: Success after binutils/gcc: 11 commits new b95b5759e2 116: onsuccess: #528: 2: Success after binutils/gcc: 48 commits new b96cccc86c 117: onsuccess: #531: 2: Success after gcc: 65 commits new 7ddc87540f 118: force: #533: 2: Success after binutils: 4 commits new dc7ad82e5c 119: force: #534: 1: Failure after gdb-12-branchpoint-3046-g [...] new 4f030885ac 120: onsuccess: #535: 1: Success after binutils: 10 commits new 4d027cf4a7 121: onsuccess: #536: 1: Success after binutils/gcc: 76 commits new 90d522f41b 122: onsuccess: #537: 2: Success after binutils/gcc: 36 commits new fee95bcef4 123: onsuccess: #538: 2: Success after binutils/gcc: 14 commits new 11920a2d91 124: onsuccess: #539: 2: Success after binutils/gcc: 9 commits new 0ed32830eb 125: onsuccess: #540: 2: Success after binutils/gcc: 53 commits new 4ddf362edc 126: onsuccess: #541: 2: Success after binutils/gcc: 17 commits new 07bf9e4044 127: onsuccess: #542: 2: Success after binutils/gcc: 66 commits new 4bc316125f 128: onsuccess: #543: 2: Success after binutils/gcc: 52 commits new 0250961e1a 129: onsuccess: #544: 2: Success after binutils/gcc: 79 commits new 0aa0f8b6c0 130: onsuccess: #545: 2: Success after binutils/gcc: 9 commits new 567149d943 131: onsuccess: #546: 2: Success after binutils/gcc: 24 commits new 5462359935 132: onsuccess: #547: 2: Success after binutils/gcc: 7 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 (a2c2ea4ffc) \ 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 1732 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2752 bytes 04-build_abe-binutils/console.log.xz | Bin 39676 -> 39952 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 532512 -> 533616 bytes 06-check_regression/console.log.xz | Bin 2908 -> 2808 bytes 07-update_baseline/console.log | 40 ++++++++++----------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++----- 13 files changed, 35 insertions(+), 35 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_O1 updated (0ee20fd741 -> 95c2a7a52f)

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 0ee20fd741 42: onsuccess: #148: 2: Success after binutils/gcc: 11 commits new 95c2a7a52f 43: onsuccess: #149: 2: Success after binutils/gcc: 7 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 1708 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2756 bytes 04-build_abe-binutils/console.log.xz | Bin 51860 -> 50824 bytes 05-build_abe-bootstrap_O1/console.log.xz | Bin 460388 -> 461200 bytes 06-check_regression/console.log.xz | Bin 2796 -> 2668 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 | 20 ++++++++++---------- 12 files changed, 16 insertions(+), 16 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-lts-defconfig updated (3d05480b61 -> 4a7fa74e77)

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-release-aarch64-lts-defconfig in repository toolchain/ci/base-artifacts. from 3d05480b61 31: onsuccess: #274: boot: Success after binutils/linux/qemu [...] new 4a7fa74e77 32: onsuccess: #275: boot: Success after binutils: 4 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 1784 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2804 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 31024 -> 30676 bytes 04-build_kernel_llvm/console.log.xz | Bin 66056 -> 65588 bytes 05-build_abe-qemu/console.log.xz | Bin 32216 -> 32228 bytes 06-build_linux/console.log.xz | Bin 3504 -> 3568 bytes 07-boot_linux/console.log.xz | Bin 6056 -> 6088 bytes 08-check_regression/console.log.xz | Bin 3812 -> 3064 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++++++---------- 15 files changed, 19 insertions(+), 19 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (5aa8d8aa29 -> 8cb236f236)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards 5aa8d8aa29 279: onsuccess: #1976: 7: Success after binutils/gcc/gdb: 5 commits discards b25e3d6480 278: onsuccess: #1975: 7: Success after basepoints/gcc-13-48 [...] discards a265b4b494 277: onsuccess: #1974: 7: Success after binutils/gdb: 4 commits discards 9d24477b12 276: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] discards 751fd20b96 275: onsuccess: #1972: 7: Success after binutils/gcc/gdb: 23 [...] discards 6266cbc31a 274: onsuccess: #1971: 7: Success after binutils/gcc/gdb: 21 [...] discards 925b8854cd 273: onsuccess: #1970: 7: Success after binutils/gcc/gdb: 5 commits discards 438c50943b 272: onsuccess: #1969: 7: Success after binutils/gcc/linux/g [...] discards 20d7d81e94 271: onsuccess: #1968: 7: Success after binutils/gcc/linux/g [...] discards 3c361d2a3f 270: onsuccess: #1967: 7: Success after binutils/gcc/gdb: 71 [...] discards e54a58e0f7 269: onsuccess: #1966: 7: Success after binutils/gcc/gdb: 43 [...] discards 9fc2d45548 268: onsuccess: #1965: 7: Success after binutils/gcc/linux/g [...] discards 53d1bcefb2 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] discards 6755c9dd38 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] discards eef1631c0d 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] discards ac18249bc6 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] discards 0316a3fb4b 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] discards ea0f261e19 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] discards 205c5524f8 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] discards 2081f328ad 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits discards 405a5fb282 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] discards 4acdd78233 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits discards b6bae602d8 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits discards aead34af31 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] discards ec3062b14e 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] discards ae18d38e13 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] discards 7900dc885c 253: onsuccess: #1950: 7: Success after glibc: 2 commits discards f73c3c4bfc 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] discards 8b78565e4e 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] discards 5a85ab06f1 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits discards 0b372fc383 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits discards 43f406e6fa 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] discards 0c0701d8b9 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits discards 6a07aaead6 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits discards da11d77d8e 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] discards e9241505c2 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] discards c5fd0d1974 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] discards d859903099 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] discards 71c3cdcd68 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] discards b2bcbb973c 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] discards 2d90b4aa76 239: onsuccess: #1936: 7: Success after binutils/gcc/linux/g [...] discards 2ba7c3db29 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/qem [...] discards 02762f03bf 237: onsuccess: #1934: 7: Success after basepoints/gcc-13-47 [...] discards 6295133d4e 236: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] discards 6d33ed3d5a 235: onsuccess: #1932: 7: Success after binutils/gcc/linux/g [...] discards 32af30d10c 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: 22 [...] discards ef7a0d7671 233: onsuccess: #1930: 7: Success after binutils/gcc/linux/g [...] discards 149f1baf9c 232: onsuccess: #1929: 7: Success after binutils/gcc/linux/g [...] discards 39b8b1cfad 231: onsuccess: #1928: 3: Success after gcc: 8 commits discards 3f12b2b23c 230: force: #1927: 3: Failure after basepoints/gcc-13-4618-g [...] discards 7aba6524a8 229: force: #1926: 7: Success after gcc: 7 commits discards 2920bcc886 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint-3 [...] discards aa23e4bc06 227: onsuccess: #1906: 7: Success after binutils: 9 commits discards 71a8878f41 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: 38 [...] discards 102b96ffd3 225: onsuccess: #1903: 7: Success after binutils/gcc/linux/g [...] discards a19ff0ecbd 224: onsuccess: #1902: 7: Success after binutils/gcc/linux/g [...] discards 40dcafb878 223: onsuccess: #1901: 7: Success after basepoints/gcc-13-45 [...] discards 0eb36044e1 222: onsuccess: #1900: 7: Success after binutils/gcc/linux/g [...] discards 61c1cae7ed 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: 15 [...] discards 4ae711b51b 220: onsuccess: #1898: 7: Success after binutils/linux/glibc [...] discards 5c876aa4f1 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: 8 commits discards 267de8c09f 218: onsuccess: #1896: 7: Success after binutils/gcc/linux/g [...] discards 8ae69f64e4 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: 10 [...] discards 5aee8c1767 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits discards 6233bc89a9 215: onsuccess: #1891: 7: Success after binutils/gcc/linux/g [...] discards 33e6b6629f 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc/g [...] discards 142b99035c 213: onsuccess: #1889: 7: Success after gcc: 5 commits discards 00324c4f76 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc/g [...] discards 9226b3e6b6 211: onsuccess: #1887: 7: Success after binutils/gcc/linux/g [...] discards 705b6624de 210: onsuccess: #1868: 7: Success after binutils: 7 commits discards 409a5fa104 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/qem [...] discards 4fe58dd61e 208: onsuccess: #1865: 7: Success after linux: 12 commits discards 062c4cef2a 207: onsuccess: #1862: 7: Success after binutils: 4 commits discards 2cefb633cb 206: onsuccess: #1860: 7: Success after gcc: 2 commits discards 6f8c8d81fb 205: onsuccess: #1859: 7: Success after gcc: 3 commits discards 37478579d3 204: onsuccess: #1858: 7: Success after binutils/gcc/linux/g [...] discards 999b09f35f 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: 7 commits discards 62d7c00b19 202: onsuccess: #1856: 7: Success after gcc: 2 commits discards 0967bda7ce 201: onsuccess: #1855: 7: Success after binutils/gcc/linux/g [...] discards 6c8e585c35 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits discards aa9b5cdc44 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: 18 [...] discards 0bef3d951f 198: onsuccess: #1852: 7: Success after gcc: 5 commits discards ddcaf825c9 197: onsuccess: #1851: 7: Success after binutils/gcc/linux/g [...] discards b68d798234 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: 42 [...] discards 5195227dee 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: 11 [...] discards 83ce3d72ca 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: 16 [...] discards f6890a4379 193: onsuccess: #1847: 7: Success after binutils/gcc/linux/g [...] discards 404c6c4b86 192: onsuccess: #1816: 7: Success after binutils/gcc/linux/g [...] discards 8bab672e08 191: onsuccess: #1808: 7: Success after binutils/gcc/linux/g [...] discards 9d4499d16a 190: onsuccess: #1774: 7: Success after binutils: 10 commits discards 294b34abc0 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: 37 [...] discards fc8e1fe9f5 188: onsuccess: #1765: 7: Success after binutils/gcc/linux/g [...] discards 445f479b16 187: onsuccess: #1763: 7: Success after binutils/gcc/linux/g [...] discards 078d4f2534 186: onsuccess: #1761: 7: Success after binutils/gcc/linux/g [...] discards f2c8323a27 185: onsuccess: #1716: 7: Success after binutils/linux/gdb: [...] discards 144938bddb 184: onsuccess: #1715: 7: Success after binutils/gcc/linux/g [...] discards 765c66cbad 183: onsuccess: #1712: 7: Success after binutils/gcc/linux/g [...] discards 20890ca613 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/g [...] discards d6bc8ab4a6 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/g [...] discards eff9a32e1f 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] discards 5340cec439 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new 0048ab7f09 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new 000f800e60 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] new 3e6d5536a1 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/g [...] new 219203669c 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/g [...] new 2f521539b1 183: onsuccess: #1712: 7: Success after binutils/gcc/linux/g [...] new e25d84cd4e 184: onsuccess: #1715: 7: Success after binutils/gcc/linux/g [...] new 2f6532643b 185: onsuccess: #1716: 7: Success after binutils/linux/gdb: [...] new b7c2bbaf74 186: onsuccess: #1761: 7: Success after binutils/gcc/linux/g [...] new b4ab804cd5 187: onsuccess: #1763: 7: Success after binutils/gcc/linux/g [...] new 59715ea7a6 188: onsuccess: #1765: 7: Success after binutils/gcc/linux/g [...] new ed36eb40b3 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: 37 [...] new dbe8870902 190: onsuccess: #1774: 7: Success after binutils: 10 commits new 3a905d04c4 191: onsuccess: #1808: 7: Success after binutils/gcc/linux/g [...] new a3cbae7eab 192: onsuccess: #1816: 7: Success after binutils/gcc/linux/g [...] new 6faa9d84bc 193: onsuccess: #1847: 7: Success after binutils/gcc/linux/g [...] new a0aa4d0928 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: 16 [...] new e18ac8b0b7 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: 11 [...] new e9e853dbfe 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: 42 [...] new 6bbbf63cd5 197: onsuccess: #1851: 7: Success after binutils/gcc/linux/g [...] new 68c920c986 198: onsuccess: #1852: 7: Success after gcc: 5 commits new ee55d9217a 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: 18 [...] new b19ab12f22 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits new d55965f0a2 201: onsuccess: #1855: 7: Success after binutils/gcc/linux/g [...] new 3d0575d853 202: onsuccess: #1856: 7: Success after gcc: 2 commits new b5c195af41 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: 7 commits new 1d7bfa4829 204: onsuccess: #1858: 7: Success after binutils/gcc/linux/g [...] new bfc69329d8 205: onsuccess: #1859: 7: Success after gcc: 3 commits new aa15767d97 206: onsuccess: #1860: 7: Success after gcc: 2 commits new a78ed8d78c 207: onsuccess: #1862: 7: Success after binutils: 4 commits new 994a13cfe4 208: onsuccess: #1865: 7: Success after linux: 12 commits new 9e785a6dcb 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/qem [...] new 3a7d12fd83 210: onsuccess: #1868: 7: Success after binutils: 7 commits new a7e2bcfb2f 211: onsuccess: #1887: 7: Success after binutils/gcc/linux/g [...] new 9ccc5ddc69 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc/g [...] new bf8d880d19 213: onsuccess: #1889: 7: Success after gcc: 5 commits new 74bf33271d 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc/g [...] new 9078244f1f 215: onsuccess: #1891: 7: Success after binutils/gcc/linux/g [...] new def9c1628b 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits new 35d1f89ff1 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: 10 [...] new e02ef42b73 218: onsuccess: #1896: 7: Success after binutils/gcc/linux/g [...] new 2adc485ea9 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: 8 commits new 0fc79313cf 220: onsuccess: #1898: 7: Success after binutils/linux/glibc [...] new ca479f781a 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: 15 [...] new 1bcb842c66 222: onsuccess: #1900: 7: Success after binutils/gcc/linux/g [...] new 8f04ec1570 223: onsuccess: #1901: 7: Success after basepoints/gcc-13-45 [...] new 6bae828d6b 224: onsuccess: #1902: 7: Success after binutils/gcc/linux/g [...] new 274fb8abf5 225: onsuccess: #1903: 7: Success after binutils/gcc/linux/g [...] new 11bdc3bfcb 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: 38 [...] new efe0de9811 227: onsuccess: #1906: 7: Success after binutils: 9 commits new fb18fbad0d 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint-3 [...] new ca22ed7208 229: force: #1926: 7: Success after gcc: 7 commits new 1916b8c2ab 230: force: #1927: 3: Failure after basepoints/gcc-13-4618-g [...] new 095866165c 231: onsuccess: #1928: 3: Success after gcc: 8 commits new 794103be05 232: onsuccess: #1929: 7: Success after binutils/gcc/linux/g [...] new f49cd2a7d2 233: onsuccess: #1930: 7: Success after binutils/gcc/linux/g [...] new fc1e532b01 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: 22 [...] new 8d6e1e2928 235: onsuccess: #1932: 7: Success after binutils/gcc/linux/g [...] new e13be96b84 236: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] new 66d510f1c9 237: onsuccess: #1934: 7: Success after basepoints/gcc-13-47 [...] new 8e9321106d 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/qem [...] new b874fdc0b1 239: onsuccess: #1936: 7: Success after binutils/gcc/linux/g [...] new 2a45dc872e 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] new d72c0a6d7e 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] new 77a8ed48b5 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] new 41d530e52f 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] new 8ba70e3dce 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] new e6be37d0bc 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] new 4b0a0e9078 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits new a92d2691a1 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits new 93367835a4 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] new c9be52af0f 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits new 0c073e421a 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits new 3752fd7731 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] new 6ae61c4b78 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] new ab21345572 253: onsuccess: #1950: 7: Success after glibc: 2 commits new 85d88ade64 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] new 94039cb2aa 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] new a73c83e3a9 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] new 010f4af6a1 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits new ccea2f739a 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits new 1d5ce84bcd 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] new 13b8fecb1e 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits new c38330516e 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] new 5198589153 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] new 6e262cc6c8 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] new db0cb36fbd 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] new 36c36b5b24 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] new d1defbcdbc 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] new 331bc5626e 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] new 5a7115d9f4 268: onsuccess: #1965: 7: Success after binutils/gcc/linux/g [...] new 5a0e25c555 269: onsuccess: #1966: 7: Success after binutils/gcc/gdb: 43 [...] new bed3dbd515 270: onsuccess: #1967: 7: Success after binutils/gcc/gdb: 71 [...] new fb2bc84556 271: onsuccess: #1968: 7: Success after binutils/gcc/linux/g [...] new 5f92c923ab 272: onsuccess: #1969: 7: Success after binutils/gcc/linux/g [...] new 7a844b4d03 273: onsuccess: #1970: 7: Success after binutils/gcc/gdb: 5 commits new 4e33092f43 274: onsuccess: #1971: 7: Success after binutils/gcc/gdb: 21 [...] new 25ec4d4061 275: onsuccess: #1972: 7: Success after binutils/gcc/gdb: 23 [...] new 9d2fa2f994 276: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] new ab1ffe5dab 277: onsuccess: #1974: 7: Success after binutils/gdb: 4 commits new 920088c79b 278: onsuccess: #1975: 7: Success after basepoints/gcc-13-48 [...] new 6b5375928d 279: onsuccess: #1976: 7: Success after binutils/gcc/gdb: 5 commits new 8cb236f236 280: onsuccess: #1977: 7: Success after binutils/gdb: 18 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 (5aa8d8aa29) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1772 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2760 bytes 04-build_abe-binutils/console.log.xz | Bin 32508 -> 32164 bytes 05-build_abe-stage1/console.log.xz | Bin 73880 -> 73028 bytes 07-build_abe-linux/console.log.xz | Bin 8348 -> 8396 bytes 08-build_abe-glibc/console.log.xz | Bin 245640 -> 245268 bytes 09-build_abe-stage2/console.log.xz | Bin 205552 -> 204688 bytes 10-build_abe-gdb/console.log.xz | Bin 39660 -> 39456 bytes 11-build_abe-qemu/console.log.xz | Bin 31744 -> 31976 bytes 12-check_regression/console.log.xz | Bin 3472 -> 3340 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +++++++-------- 18 files changed, 53 insertions(+), 53 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[gcc] branch master updated (e2acff49fb2 -> acc727cf02a)

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 e2acff49fb2 Daily bump. new acc727cf02a rs6000: Rework option -mpowerpc64 handling [PR106680] 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/common/config/rs6000/rs6000-common.cc | 11 -------- gcc/config/rs6000/rs6000.cc | 37 ++++++++++++++++++++------- gcc/testsuite/gcc.target/powerpc/pr106680-1.c | 13 ++++++++++ gcc/testsuite/gcc.target/powerpc/pr106680-2.c | 14 ++++++++++ gcc/testsuite/gcc.target/powerpc/pr106680-3.c | 13 ++++++++++ gcc/testsuite/gcc.target/powerpc/pr106680-4.c | 17 ++++++++++++ 6 files changed, 85 insertions(+), 20 deletions(-) create mode 100644 gcc/testsuite/gcc.target/powerpc/pr106680-1.c create mode 100644 gcc/testsuite/gcc.target/powerpc/pr106680-2.c create mode 100644 gcc/testsuite/gcc.target/powerpc/pr106680-3.c create mode 100644 gcc/testsuite/gcc.target/powerpc/pr106680-4.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm updated (cb38c21e46 -> af364b70f0)

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 cb38c21e46 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] discards 8156aa1f9d 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits discards 488ff35e0d 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] discards dffeaaeb72 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards e9b89597cb 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards 4680de4964 138: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards f66c506a1f 137: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards d162a39d48 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/gd [...] discards b2d9175ba7 135: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards bc7ee7047d 134: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards 7a6801987a 133: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards 753863b237 132: onsuccess: #559: 1: Success after binutils/gcc/linux/gd [...] discards f01d761b37 131: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] discards 8d648ae5ff 130: onsuccess: #557: 1: Success after binutils/gcc/linux/gl [...] discards 081adf1144 129: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] discards 39603a6819 128: onsuccess: #555: 1: Success after binutils/gcc/linux/gd [...] discards 1560f2717a 127: onsuccess: #554: 1: Success after binutils/gcc/linux/gl [...] discards 3f1edfb3f0 126: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] discards a10ecb8ac1 125: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards cc1ddc0949 124: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards f27da2c8d9 123: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] discards 5be63b5d19 122: onsuccess: #549: 1: Success after binutils/gcc/linux/gd [...] discards 671d8dbf7e 121: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] discards 292c085ac1 120: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] discards f9a5ee5a67 119: onsuccess: #546: 1: Success after binutils/gcc/linux/gd [...] discards dc4ae3c132 118: onsuccess: #545: 1: Success after binutils/gcc/linux/gd [...] discards dc49114802 117: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] discards 74c6a33bdc 116: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards bbd2458d43 115: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards 3be16595ab 114: onsuccess: #541: 1: Success after binutils/gcc/linux/gd [...] discards abe65281cb 113: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards e47deb2bcc 112: onsuccess: #538: 1: Success after binutils/gcc/linux/gd [...] discards 4b770bd2f7 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 commits discards 90b2b2c031 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards 665ca4966e 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] discards e71f9c072e 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] discards 7983695e8e 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards 60d5113730 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] discards f2d3ef2ad9 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] discards 797bdb4aab 104: onsuccess: #530: 1: Success after gcc: 7 commits discards 6e0398b2c0 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards 80eb8718f9 102: onsuccess: #527: 1: Success after binutils: 5 commits discards 5b07893a55 101: onsuccess: #524: 1: Success after binutils: 2 commits discards 737ab6f5b7 100: onsuccess: #521: 1: Success after binutils: 10 commits discards 74e3698c0b 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 27fde2aebe 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] discards e912b613e6 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 025e8240fe 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 5f76829ce4 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] discards bd147f2888 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] discards 387909e9f0 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 7c71c4efb8 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] discards cb5b418a49 91: onsuccess: #511: 1: Success after linux: 27 commits discards f0bff5cb68 90: onsuccess: #510: 1: Success after glibc: 5 commits discards 6286017776 89: onsuccess: #508: 1: Success after binutils: 12 commits discards 685d3a52a9 88: onsuccess: #506: 1: Success after linux: 34 commits discards f88e74fb8d 87: onsuccess: #505: 1: Success after glibc: 7 commits discards a0620e438b 86: onsuccess: #503: 1: Success after binutils: 12 commits discards e890c8aea7 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 6bc32d902c 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards 7407ae8bd3 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] discards e94e6de140 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] discards b8838b4832 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards a33ff08e18 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards de49c06a1a 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards ddf5e81b46 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards e885e29f93 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] discards 0ee2719dd7 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] discards 4871bda58c 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards edec63cdc8 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] discards 3ed1a93b32 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] discards c35a040a6d 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] discards ca1704a139 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] discards 04f5414f2d 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] discards 8c0cac866c 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards 0214ffbb99 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] discards 9a6cd0019f 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards dc731866fb 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] discards 6b0213b97d 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] discards 8cc7d43ff3 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards bb53393e27 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] discards 6d99884948 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] discards d06c0dc726 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] discards 4244aea789 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] discards 3b4979ee1c 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] discards 186478d661 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] discards a3b263f2e4 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] discards 7e80f02e41 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] discards 6964231f95 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] discards 551a0f9903 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] discards c60ca59e99 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] discards da294e271d 52: onsuccess: #467: 1: Success after binutils: 9 commits discards 0923b5c111 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 3349d96b90 50: onsuccess: #461: 1: Success after binutils: 12 commits discards 57902345a5 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] discards 0fa21603b5 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] discards 586749eccd 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards 8d8bfab392 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards 8074c3f448 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] discards 6eba0ba048 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] discards 01ea5ce1fc 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] new 5d6f72aa95 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] new 656b89bcfd 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] new 7cc8574d0d 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] new af277850e4 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new c7784068a1 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new c2d271f013 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] new 613e06f53e 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] new 4a8f82a6e5 50: onsuccess: #461: 1: Success after binutils: 12 commits new ce0cba02eb 51: onsuccess: #464: 1: Success after binutils: 6 commits new be299147c5 52: onsuccess: #467: 1: Success after binutils: 9 commits new e836584557 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] new 66d3f657a7 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] new a1ad9f59db 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] new df3dac13ce 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] new 0321746c60 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] new 47756304eb 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] new 40c99d6701 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] new 29891bd461 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] new 7bb37ca3be 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] new 6807830caa 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] new 50719a47b1 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] new 775be82870 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new f9e9474df5 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] new 28bfb24f9c 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] new 702ce1b27e 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 4a188a2b13 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] new b0fc7af118 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 46afc6d716 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] new ca35ceb922 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] new 535e29cf5d 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] new c9d264ca99 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] new f880e51a12 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] new b1949a6788 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 4e5c4bfe53 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] new 0c283cda13 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] new 104e397279 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new e287abeeeb 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new ea7bc82297 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 3abad9ae88 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 14fd3b2333 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] new ff7e061a38 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] new a5e590785c 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new a39d898c18 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new a885737a5d 86: onsuccess: #503: 1: Success after binutils: 12 commits new d70d79213f 87: onsuccess: #505: 1: Success after glibc: 7 commits new 2ec217ff5b 88: onsuccess: #506: 1: Success after linux: 34 commits new 6c2f8638f4 89: onsuccess: #508: 1: Success after binutils: 12 commits new 3f1db04105 90: onsuccess: #510: 1: Success after glibc: 5 commits new ba5a1d4f42 91: onsuccess: #511: 1: Success after linux: 27 commits new 703394ff84 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] new d21ca4f993 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new 2060f6bae6 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] new ba1bc3a077 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] new a7ee1576c9 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 91b5d6ed71 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new 9200dc60e1 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] new 9679457614 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 416a8cb02c 100: onsuccess: #521: 1: Success after binutils: 10 commits new 5d812fc43a 101: onsuccess: #524: 1: Success after binutils: 2 commits new c35d74d074 102: onsuccess: #527: 1: Success after binutils: 5 commits new 177b4a01f5 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new acfe66361c 104: onsuccess: #530: 1: Success after gcc: 7 commits new b8cac28776 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] new 308584bfd9 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] new b0b4a7e084 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new 6761eda95c 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] new c614cd166a 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] new bfd4b608a5 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new badd710c35 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 commits new c6148674b2 112: onsuccess: #538: 1: Success after binutils/gcc/linux/gd [...] new d07718f53e 113: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new 065f85b132 114: onsuccess: #541: 1: Success after binutils/gcc/linux/gd [...] new ccffa5a7a4 115: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new 1408fce6ef 116: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new 0097c420fd 117: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] new 76b96940f0 118: onsuccess: #545: 1: Success after binutils/gcc/linux/gd [...] new f96248673a 119: onsuccess: #546: 1: Success after binutils/gcc/linux/gd [...] new b3dce25ba8 120: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] new 261a08ca9c 121: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] new eebd41fbaf 122: onsuccess: #549: 1: Success after binutils/gcc/linux/gd [...] new b53e7bd071 123: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] new f41893f160 124: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new cf7a2fa7b7 125: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 586ceb8724 126: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] new c95b53e46e 127: onsuccess: #554: 1: Success after binutils/gcc/linux/gl [...] new df1fa00642 128: onsuccess: #555: 1: Success after binutils/gcc/linux/gd [...] new cf40a94f94 129: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] new 369ecd3020 130: onsuccess: #557: 1: Success after binutils/gcc/linux/gl [...] new c18d7f1500 131: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] new 9ee85e1db3 132: onsuccess: #559: 1: Success after binutils/gcc/linux/gd [...] new 74337f2131 133: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 66540731ca 134: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new 155e14f63a 135: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new c3d6257182 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/gd [...] new ebb672d5de 137: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new 16e897cef6 138: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new b0488b17e2 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new a7c2fef4d6 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new 47e5d245ab 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] new 0dab3d4628 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits new d0f24c0493 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new af364b70f0 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 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 (cb38c21e46) \ 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 1768 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 52536 -> 52760 bytes 04-build_abe-gcc/console.log.xz | Bin 237508 -> 237448 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8324 -> 8292 bytes 07-build_abe-glibc/console.log.xz | Bin 236232 -> 236844 bytes 08-build_abe-gdb/console.log.xz | Bin 51340 -> 51264 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3816 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2080 -> 2168 bytes 11-check_regression/console.log.xz | Bin 5292 -> 5132 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +-- sumfiles/binutils.log.xz | Bin 62652 -> 62540 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 100408 -> 100892 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 132204 -> 132284 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 28 files changed, 387 insertions(+), 387 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-stable-allmodconfig updated (eba5963855 -> 0afa7a83e5)

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-release-arm-stable-allmodconfig in repository toolchain/ci/base-artifacts. from eba5963855 38: onsuccess: #285: 22859: Success after binutils/linux/qem [...] new 0afa7a83e5 39: onsuccess: #286: 22859: Success after binutils: 4 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 1988 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 30616 -> 30252 bytes 04-build_kernel_llvm/console.log.xz | Bin 64844 -> 64348 bytes 05-build_abe-qemu/console.log.xz | Bin 31596 -> 31648 bytes 06-build_linux/console.log.xz | Bin 3976 -> 3916 bytes 08-check_regression/console.log.xz | Bin 3792 -> 3092 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++++++---------- 13 files changed, 15 insertions(+), 15 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-mainline-allnoconfig updated (68c805dd73 -> b99debdde2)

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-release-aarch64-mainline-allnoconfig in repository toolchain/ci/base-artifacts. from 68c805dd73 31: onsuccess: #449: boot: Success after binutils/linux/qemu [...] new b99debdde2 32: onsuccess: #450: boot: Success after binutils/linux: 154 [...] 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 1760 -> 2020 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30276 -> 30460 bytes 04-build_kernel_llvm/console.log.xz | Bin 66152 -> 64820 bytes 05-build_abe-qemu/console.log.xz | Bin 31572 -> 32196 bytes 06-build_linux/console.log.xz | Bin 3088 -> 3072 bytes 08-check_regression/console.log.xz | Bin 3704 -> 3252 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 ++++++++++++------------ 15 files changed, 22 insertions(+), 22 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022