Tcwg-commits February 2023

tcwg-commits@lists.linaro.org

5 participants
3393 discussions

[gcc] branch master updated (94c9b1bb79f -> 2dd68cddbc7)

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 94c9b1bb79f asan: adjust module name for global variables new ef22c3e90b5 Change vec<,,vl_embed>::m_vecdata refrences into address () new 2dd68cddbc7 Avoid default-initializing auto_vec<T, N> storage, fix vec< [...] The 2 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/vec.cc | 17 ++++++++++++++ gcc/vec.h | 75 +++++++++++++++++++++++++++++++++++++------------------------- 2 files changed, 62 insertions(+), 30 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm updated (9a8626d267 -> 47a4b84da4)

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 9a8626d267 204: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] discards cb77883767 203: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards d4a0143ba3 202: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] discards b6c06ce2c0 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] discards 035d45e0c8 200: onsuccess: #663: 1: Success after binutils/gcc/linux/gl [...] discards 09d8e9ddb0 199: onsuccess: #662: 1: Success after binutils/gcc/linux/gl [...] discards 0e31b59bbc 198: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards f478198356 197: onsuccess: #660: 1: Success after binutils/gcc/linux/gl [...] discards 57abfcba7c 196: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 15aefe6a1d 195: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards 9b750ac676 194: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards c8e6d4a8b7 193: onsuccess: #655: 1: Success after binutils/gcc/linux/gd [...] discards 2b6f8b578a 192: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards 8961882c1b 191: onsuccess: #653: 1: Success after binutils/gcc/linux/gl [...] discards c26f5bef07 190: onsuccess: #652: 1: Success after binutils/gcc/linux/gl [...] discards d85e90a908 189: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 5325e492cb 188: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards 4009591123 187: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards c2e065a0b6 186: onsuccess: #648: 1: Success after binutils/gcc/linux/gd [...] discards e1a528891f 185: onsuccess: #647: 1: Success after binutils/gcc/linux/gd [...] discards 6d1677240f 184: onsuccess: #646: 1: Success after binutils/gcc/linux/gl [...] discards d8f178d4c9 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 203 [...] discards 69be2440fd 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 commits discards d2918f170f 181: onsuccess: #643: 1: Success after binutils/gcc/linux/gl [...] discards baa1b688a2 180: onsuccess: #642: 1: Success after binutils/gcc/linux/gl [...] discards e71f8f8e6e 179: onsuccess: #641: 1: Success after binutils/gcc/linux/gd [...] discards e971ae9360 178: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] discards efc98d756b 177: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] discards 1ad2c25ef6 176: onsuccess: #638: 1: Success after binutils/gcc/linux/gd [...] discards 5cd1ff67ac 175: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] discards ebec28923b 174: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] discards 291e38bdbd 173: onsuccess: #635: 1: Success after binutils/gcc/linux/gl [...] discards bacc742702 172: onsuccess: #634: 1: Success after binutils/gcc/linux/gd [...] discards 03af1536fd 171: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards 32d0b41259 170: onsuccess: #632: 1: Success after binutils/gcc/linux/gl [...] discards 72e608e6a0 169: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards 20548e4685 168: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards fc56190af2 167: onsuccess: #629: 1: Success after binutils/gcc/linux/gd [...] discards 1a0a979819 166: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards 62d1133f7d 165: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] discards 75e6dd772e 164: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards ef9e31e6fe 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/gd [...] discards 6484099dc6 162: onsuccess: #624: 1: Success after linux: 10 commits discards 81862d611d 161: onsuccess: #623: 1: Success after glibc: 9 commits discards f4e866f024 160: onsuccess: #621: 1: Success after gcc: 11 commits discards 9f89bd0041 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 75f70a0b7a 158: onsuccess: #618: 1: Success after binutils/gcc/linux/gd [...] discards 1ea6cbf33e 157: onsuccess: #617: 1: Success after binutils/gcc/linux/gd [...] discards 815d4942af 156: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 36e5a93998 155: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] discards 3ba0bec520 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 commits discards bb4a3eaffa 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 commits discards ef1b528f4b 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 commits discards 14918a9c53 151: onsuccess: #611: 1: Success after binutils/gcc/linux/gd [...] discards f893308c07 150: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards dc346ab9d5 149: onsuccess: #609: 1: Success after binutils/gcc/linux/gd [...] discards 455d5b7162 148: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 4f2dc66c08 147: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] discards 5360f60d44 146: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards b4374b1235 145: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 1259a426f0 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 commits discards 0ef98c3840 143: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 2a1773e85d 142: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 24ba44fce1 141: onsuccess: #601: 1: Success after linux: 794 commits discards 6ac58a462c 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 52ced4c135 139: onsuccess: #599: 1: Success after binutils: 10 commits discards be1eabd953 138: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards 43b15b9599 137: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] discards e1116ea6cd 136: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards 073d710f44 135: onsuccess: #594: 1: Success after binutils/gcc/linux/gd [...] discards e775c1c016 134: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards fd6f9564b0 133: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] discards 8b58b4ba12 132: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 846f8fbb25 131: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] discards a8b38f849d 130: onsuccess: #589: 1: Success after binutils/gcc/linux/gl [...] discards 5da6caa6da 129: onsuccess: #588: 1: Success after linux: 4 commits discards 6467066709 128: onsuccess: #586: 1: Success after binutils: 22 commits discards 20994a81a1 127: onsuccess: #584: 1: Success after linux: 21 commits discards 9eafffc046 126: onsuccess: #582: 1: Success after gcc: 9 commits discards b182ae4c2a 125: onsuccess: #581: 1: Success after binutils: 4 commits discards 685d91ea91 124: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] discards bafc3600fa 123: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] discards c9f77a8653 122: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] discards 3d81ee4aa0 121: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] discards 38084aa8ba 120: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] discards cdb8673193 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/gd [...] discards 25f561e058 118: onsuccess: #573: 1: Success after binutils/gcc/linux/gd [...] discards 6084ce064c 117: onsuccess: #572: 1: Success after binutils/gcc/linux/gd [...] discards 15c051efb7 116: onsuccess: #571: 1: Success after binutils/gcc/linux/gd [...] discards fd1a04c778 115: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] discards 2c1cc422ee 114: onsuccess: #569: 1: Success after binutils/gcc/linux/gd [...] discards 75d41b2c71 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits discards 91cd433b40 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards 248f357d79 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] discards e25fc660a7 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] discards becd1ed931 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards 41887203a3 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards 354425ac56 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards 6e4eaabdb4 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards 8be7589f51 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards 5db8b9afb4 104: onsuccess: #558: 1: Success after binutils: 3 commits new f96a8e6a34 104: onsuccess: #558: 1: Success after binutils: 3 commits new cad695ed12 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new a0ecab0f1f 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new 6846e61cf5 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new 3d518c497f 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new b602420a34 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new e92e191118 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] new b30770d257 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] new b2b5853ad3 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new 82e7bf2cb8 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits new 5877350a5a 114: onsuccess: #569: 1: Success after binutils/gcc/linux/gd [...] new e0585b4be5 115: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new d7dbf1b0dd 116: onsuccess: #571: 1: Success after binutils/gcc/linux/gd [...] new be09deb990 117: onsuccess: #572: 1: Success after binutils/gcc/linux/gd [...] new b7d4afa8af 118: onsuccess: #573: 1: Success after binutils/gcc/linux/gd [...] new 12ef0095b9 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/gd [...] new 6bbba97b43 120: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] new 631f4f39e0 121: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] new 18388fc19d 122: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] new 37a9b76110 123: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] new 6f9a67aaba 124: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] new 22a0cae455 125: onsuccess: #581: 1: Success after binutils: 4 commits new c83b7230c1 126: onsuccess: #582: 1: Success after gcc: 9 commits new 2a1953b109 127: onsuccess: #584: 1: Success after linux: 21 commits new f12f04094e 128: onsuccess: #586: 1: Success after binutils: 22 commits new 814650fa23 129: onsuccess: #588: 1: Success after linux: 4 commits new 6bfa178e23 130: onsuccess: #589: 1: Success after binutils/gcc/linux/gl [...] new 63e215160a 131: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] new 666d51ab8c 132: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 40d5f37221 133: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] new 04f51e1d9d 134: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 7721086d6b 135: onsuccess: #594: 1: Success after binutils/gcc/linux/gd [...] new 9815097d32 136: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new ecc7137055 137: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] new f3e06b3a8d 138: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 851f65da22 139: onsuccess: #599: 1: Success after binutils: 10 commits new 5eb45b6924 140: onsuccess: #600: 1: Success after gcc: 23 commits new 216e413517 141: onsuccess: #601: 1: Success after linux: 794 commits new 3d90ee2488 142: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new cc2eb654bb 143: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 4260bfd330 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 commits new 8ab7e0fe99 145: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new dc7f26bf05 146: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 26a1eb782f 147: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] new 9acf41dcc2 148: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 0501b716e7 149: onsuccess: #609: 1: Success after binutils/gcc/linux/gd [...] new bbd956515a 150: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new a66ae41674 151: onsuccess: #611: 1: Success after binutils/gcc/linux/gd [...] new aecba3b9b5 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 commits new 2944acdc2f 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 commits new 7d70389778 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 commits new ffa7d98d1c 155: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] new 35e06bfc13 156: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 0777984823 157: onsuccess: #617: 1: Success after binutils/gcc/linux/gd [...] new b91bd2bef9 158: onsuccess: #618: 1: Success after binutils/gcc/linux/gd [...] new cc314fc9e1 159: onsuccess: #620: 1: Success after binutils: 12 commits new db7d69a380 160: onsuccess: #621: 1: Success after gcc: 11 commits new 578f6e4406 161: onsuccess: #623: 1: Success after glibc: 9 commits new 7ce6276b3c 162: onsuccess: #624: 1: Success after linux: 10 commits new 49b12831f3 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/gd [...] new bb412e783b 164: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new f289c29ea5 165: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] new c1636dccc4 166: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 7bff9bae2a 167: onsuccess: #629: 1: Success after binutils/gcc/linux/gd [...] new 9a336acb62 168: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new b0e86cf1aa 169: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new 9fcb24863f 170: onsuccess: #632: 1: Success after binutils/gcc/linux/gl [...] new 1fa9fd618c 171: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new 2f88177d6c 172: onsuccess: #634: 1: Success after binutils/gcc/linux/gd [...] new 65c5999847 173: onsuccess: #635: 1: Success after binutils/gcc/linux/gl [...] new f2372a18f2 174: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] new 2d1bbae70f 175: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] new 375936f82a 176: onsuccess: #638: 1: Success after binutils/gcc/linux/gd [...] new a8007d9cd5 177: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] new 7738418870 178: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] new 0bf975d5bf 179: onsuccess: #641: 1: Success after binutils/gcc/linux/gd [...] new 7fbc8c5914 180: onsuccess: #642: 1: Success after binutils/gcc/linux/gl [...] new 8f59c05e4f 181: onsuccess: #643: 1: Success after binutils/gcc/linux/gl [...] new d02fd40bfa 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 commits new 1a041abb3d 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 203 [...] new 190b6440a2 184: onsuccess: #646: 1: Success after binutils/gcc/linux/gl [...] new e1f34efe49 185: onsuccess: #647: 1: Success after binutils/gcc/linux/gd [...] new 8d79c97bff 186: onsuccess: #648: 1: Success after binutils/gcc/linux/gd [...] new 878702e4dc 187: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new a74568894e 188: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 9b7a85d747 189: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 305777e2a2 190: onsuccess: #652: 1: Success after binutils/gcc/linux/gl [...] new b00966f3dd 191: onsuccess: #653: 1: Success after binutils/gcc/linux/gl [...] new 258b5bb680 192: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new 6124df0b34 193: onsuccess: #655: 1: Success after binutils/gcc/linux/gd [...] new 9ecc660346 194: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new 09e0b981b5 195: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new 790d915613 196: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new cb3a91abc0 197: onsuccess: #660: 1: Success after binutils/gcc/linux/gl [...] new b5f637f834 198: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new 4dafefa874 199: onsuccess: #662: 1: Success after binutils/gcc/linux/gl [...] new 4496c78165 200: onsuccess: #663: 1: Success after binutils/gcc/linux/gl [...] new d64497ee21 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new f1e77f4356 202: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] new 8d62ca4965 203: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new 3b15471bcc 204: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] new 47a4b84da4 205: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] 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 (9a8626d267) \ 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 1752 -> 1804 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 52884 -> 53488 bytes 04-build_abe-gcc/console.log.xz | Bin 236228 -> 235600 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 11796 -> 9088 bytes 07-build_abe-glibc/console.log.xz | Bin 235456 -> 235116 bytes 08-build_abe-gdb/console.log.xz | Bin 50820 -> 50956 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3808 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2624 -> 2668 bytes 11-check_regression/console.log.xz | Bin 14252 -> 6696 bytes 11-check_regression/results.compare | 40 +- 11-check_regression/results.compare2 | 2089 +-------------------------------- 12-update_baseline/console.log | 62 +- 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/g++.log.xz | Bin 2890084 -> 2882084 bytes sumfiles/g++.sum | 125 +- sumfiles/gcc.log.xz | Bin 2463276 -> 2455060 bytes sumfiles/gcc.sum | 342 +++--- sumfiles/gfortran.log.xz | Bin 955424 -> 950068 bytes sumfiles/gfortran.sum | 38 +- sumfiles/libatomic.log.xz | Bin 2276 -> 2276 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 233388 -> 233352 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2696 -> 2692 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 467336 -> 473388 bytes sumfiles/libstdc++.sum | 8 +- 38 files changed, 369 insertions(+), 2417 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

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

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-arm in repository toolchain/ci/base-artifacts. discards 0e68fa438f 458: onsuccess: #2: 7: Success after gcc/linux/glibc: 581 commits discards 3d67d256dc 457: onsuccess: #2194: 7: Success after binutils/gcc/linux/g [...] discards d11246ea05 456: onsuccess: #1: 7: Success after binutils/gcc/linux/glib [...] discards 3fdbc3cbec 455: onsuccess: #2193: 7: Success after binutils/gcc/gdb: 13 [...] discards 8e192218a1 454: onsuccess: #2192: 7: Success after binutils/linux/glibc [...] discards 0f6ade4f8f 453: onsuccess: #2191: 7: Success after binutils/gcc/linux/g [...] discards 27cdb4e27e 452: onsuccess: #2190: 7: Success after binutils/gcc/linux/g [...] discards c2ec7d2d96 451: onsuccess: #2189: 7: Success after binutils/gcc/gdb: 11 [...] discards 4ae172f6b4 450: onsuccess: #2188: 7: Success after binutils/gcc/linux/g [...] discards 6c8aec70ae 449: onsuccess: #2186: 7: Success after binutils/gcc/linux/g [...] discards 129d3a40ef 448: onsuccess: #2185: 7: Success after binutils/gcc/gdb/qem [...] discards da4b49a254 447: onsuccess: #2184: 7: Success after binutils/gcc/linux/g [...] discards c8b8941321 446: onsuccess: #2183: 7: Success after binutils/gcc/linux/g [...] discards 92e462caf1 445: onsuccess: #2182: 7: Success after binutils/gcc/glibc/g [...] discards 6b703d6f7e 444: onsuccess: #2181: 7: Success after binutils/gcc/glibc/g [...] discards d9a5beed42 443: onsuccess: #2180: 7: Success after binutils/gdb: 2 commits discards d8c1dba9b0 442: onsuccess: #2179: 7: Success after binutils/gcc/linux/g [...] discards b9dcca535a 441: onsuccess: #2178: 7: Success after binutils/linux/gdb: [...] discards 7bf1609c48 440: onsuccess: #2177: 7: Success after binutils/gcc/gdb: 6 commits discards 88a3ed7896 439: onsuccess: #2176: 7: Success after linux: 11 commits discards dc553f9067 438: onsuccess: #2175: 7: Success after gcc: 7 commits discards ae11f8a9a1 437: onsuccess: #2174: 7: Success after gcc/linux: 9 commits discards 287f7b033e 436: onsuccess: #2173: 7: Success after binutils/gcc/linux/g [...] discards 4099a5d9e1 435: onsuccess: #2172: 7: Success after binutils/gcc/glibc/g [...] discards bc7090e7a0 434: onsuccess: #2171: 7: Success after gcc/glibc: 5 commits discards a7d1d38899 433: onsuccess: #2170: 7: Success after binutils/gcc/linux/g [...] discards 934f703db9 432: onsuccess: #2169: 7: Success after binutils/gcc/linux/g [...] discards 51ba772553 431: onsuccess: #2168: 7: Success after binutils/gcc/gdb/qem [...] discards 9dc44a74a2 430: onsuccess: #2167: 7: Success after binutils/gcc/gdb/qem [...] discards 1485930208 429: onsuccess: #2166: 7: Success after binutils/gcc/linux/g [...] discards d96598eabb 428: onsuccess: #2165: 7: Success after binutils/gcc/glibc/g [...] discards eba9787904 427: onsuccess: #2163: 7: Success after binutils/gdb: 4 commits discards 3ef285810b 426: onsuccess: #2162: 7: Success after binutils/gcc/gdb: 13 [...] discards bb75a65abf 425: onsuccess: #2161: 7: Success after binutils/gcc/linux/g [...] discards ff990ceb0d 424: onsuccess: #2160: 7: Success after binutils/gcc/glibc/g [...] discards 5cf2cf576b 423: onsuccess: #2159: 7: Success after binutils/gcc/gdb: 5 commits discards bb35ba1b43 422: onsuccess: #2158: 7: Success after binutils/gcc/linux/g [...] discards 27f784097b 421: onsuccess: #2157: 7: Success after binutils/gcc/linux/g [...] discards c6f82a843a 420: onsuccess: #2156: 7: Success after binutils/gcc/gdb: 27 [...] discards 7dfd4ce311 419: onsuccess: #2155: 7: Success after binutils/gcc/gdb: 4 commits discards 7e3c6b38e0 418: onsuccess: #2154: 7: Success after binutils/gcc/linux/g [...] discards 65b476ae30 417: onsuccess: #2153: 7: Success after linux/glibc: 27 commits discards cd35af0bf8 416: onsuccess: #2152: 7: Success after gcc: 50 commits discards b4e2d10e12 415: onsuccess: #2151: 7: Success after binutils/gcc/gdb: 93 [...] discards bf96456ba6 414: onsuccess: #2150: 7: Success after binutils/gcc/linux/g [...] discards 4d5f53c3c8 413: onsuccess: #2149: 7: Success after binutils/gcc/linux/g [...] discards 6a9f9d4767 412: onsuccess: #2148: 7: Success after binutils/gcc/gdb: 6 commits discards 6680a626d0 411: onsuccess: #2147: 7: Success after binutils/gcc/gdb: 9 commits discards 81312971ce 410: onsuccess: #2146: 7: Success after binutils/gcc/linux/g [...] discards 94ae3ac922 409: onsuccess: #2145: 7: Success after binutils/gcc/linux/g [...] discards 5a4b32b3bb 408: onsuccess: #2144: 7: Success after binutils/gcc/gdb/qem [...] discards cadab64a61 407: onsuccess: #2143: 7: Success after binutils/gcc/linux/g [...] discards 79756ef246 406: onsuccess: #2142: 7: Success after binutils/gcc/gdb: 14 [...] discards 279035decc 405: onsuccess: #2141: 7: Success after binutils/gcc/linux/g [...] discards ab46be6711 404: onsuccess: #2139: 7: Success after basepoints/gcc-13-57 [...] discards 298f56e808 403: onsuccess: #2138: 7: Success after binutils/gcc/gdb: 4 commits discards 35974fe6b1 402: onsuccess: #2137: 7: Success after binutils/gcc/gdb: 22 [...] discards 3c62662ff0 401: onsuccess: #2136: 7: Success after binutils/gcc/glibc/g [...] discards b5dc326c03 400: onsuccess: #2135: 7: Success after binutils/gcc/linux/g [...] discards 11a3e59fd1 399: onsuccess: #2134: 7: Success after binutils/gcc/linux/g [...] discards 48885b9a80 398: onsuccess: #2133: 7: Success after binutils/gcc/glibc/g [...] discards 2deb93b99c 397: onsuccess: #2132: 7: Success after gcc: 2 commits discards d157f3259f 396: onsuccess: #2131: 7: Success after binutils/gcc/linux/g [...] discards de07a90b45 395: onsuccess: #2130: 7: Success after binutils/gcc/gdb/qem [...] discards 5f3a670645 394: onsuccess: #2129: 7: Success after binutils/gcc/linux/g [...] discards 864176fecb 393: onsuccess: #2128: 7: Success after gcc/qemu: 42 commits discards fb9fef2e58 392: onsuccess: #2127: 7: Success after glibc-2.37.9000-17-g [...] discards 80e86d230d 391: onsuccess: #2126: 7: Success after binutils/gcc/linux/g [...] discards d327cf8388 390: onsuccess: #2125: 7: Success after binutils/gcc/linux/g [...] discards 2e920b733b 389: onsuccess: #2124: 7: Success after binutils/gcc/gdb: 5 commits discards 9aa511e4fd 388: onsuccess: #2123: 7: Success after binutils/gcc/gdb: 3 commits discards e9519a2a24 387: onsuccess: #2122: 7: Success after gcc/linux/qemu: 117 commits discards f0404ef338 386: onsuccess: #2121: 7: Success after binutils/gcc/glibc/g [...] discards 132457b8ba 385: onsuccess: #2120: 7: Success after binutils/gcc/gdb/qem [...] discards 203928e82d 384: onsuccess: #2119: 7: Success after binutils/gcc/linux/g [...] discards 8748e27e03 383: onsuccess: #2118: 7: Success after binutils/gcc/glibc/g [...] discards 19f95e9c4c 382: onsuccess: #2117: 7: Success after binutils/gcc/linux/g [...] discards f6cd6874ee 381: onsuccess: #2116: 7: Success after binutils/gcc/linux/g [...] discards 5480ceb09c 380: onsuccess: #2115: 7: Success after binutils/gcc/linux/g [...] discards 907c013998 379: onsuccess: #2114: 7: Success after binutils/gcc/linux/g [...] discards dd296429ec 378: onsuccess: #2113: 7: Success after binutils/gcc/linux/g [...] discards c8b9b798a2 377: onsuccess: #2112: 7: Success after binutils/gcc/gdb: 16 [...] discards bcaa704528 376: onsuccess: #2111: 7: Success after binutils/gcc/linux/g [...] discards 74c7a71f76 375: onsuccess: #2110: 7: Success after binutils/gcc/linux/g [...] discards 57d0d3c088 374: onsuccess: #2109: 7: Success after binutils/gcc/linux/g [...] discards 975ca3a32f 373: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] discards aaafdf55bc 372: onsuccess: #2106: 7: Success after binutils/gcc/linux/g [...] discards fea73b47bf 371: onsuccess: #2105: 7: Success after binutils/gcc/gdb/qem [...] discards ba03e4dded 370: onsuccess: #2104: 7: Success after binutils/gcc/linux/g [...] discards 374d121b71 369: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] discards a5fca38072 368: onsuccess: #2102: 7: Success after binutils/gcc/linux/g [...] discards 59190ebb79 367: onsuccess: #2101: 7: Success after binutils/gcc/linux/g [...] discards 4f8e99b91b 366: onsuccess: #2100: 7: Success after binutils/gcc/glibc/g [...] discards 8a15a401b0 365: onsuccess: #2099: 7: Success after gcc/linux: 21 commits discards 49d2a9c053 364: onsuccess: #2098: 7: Success after binutils/gdb: 4 commits discards 25239cded2 363: onsuccess: #2097: 7: Success after binutils/gcc/gdb: 25 [...] discards a2d5126e70 362: onsuccess: #2096: 7: Success after binutils/gcc/linux/g [...] discards 3782cfd648 361: onsuccess: #2095: 7: Success after gcc/linux: 15 commits discards f783645304 360: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] discards 2d4d713b59 359: onsuccess: #2093: 7: Success after binutils/gcc/linux/g [...] discards 644cf88b96 358: onsuccess: #2092: 7: Success after binutils/gcc/gdb: 10 [...] new b0c5c6cb03 358: onsuccess: #2092: 7: Success after binutils/gcc/gdb: 10 [...] new 0ed73849af 359: onsuccess: #2093: 7: Success after binutils/gcc/linux/g [...] new 3496b02469 360: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] new e823c0151f 361: onsuccess: #2095: 7: Success after gcc/linux: 15 commits new 679fcff312 362: onsuccess: #2096: 7: Success after binutils/gcc/linux/g [...] new e527b52bd3 363: onsuccess: #2097: 7: Success after binutils/gcc/gdb: 25 [...] new 47ca0bd0da 364: onsuccess: #2098: 7: Success after binutils/gdb: 4 commits new 94a7cc7527 365: onsuccess: #2099: 7: Success after gcc/linux: 21 commits new 1753560a03 366: onsuccess: #2100: 7: Success after binutils/gcc/glibc/g [...] new 25e526f007 367: onsuccess: #2101: 7: Success after binutils/gcc/linux/g [...] new 0e553c6485 368: onsuccess: #2102: 7: Success after binutils/gcc/linux/g [...] new a1a9c7841d 369: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] new d6fc9116eb 370: onsuccess: #2104: 7: Success after binutils/gcc/linux/g [...] new 162b026f9d 371: onsuccess: #2105: 7: Success after binutils/gcc/gdb/qem [...] new 9a7e3218a1 372: onsuccess: #2106: 7: Success after binutils/gcc/linux/g [...] new 959dce7fbb 373: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] new b358812655 374: onsuccess: #2109: 7: Success after binutils/gcc/linux/g [...] new ccabb77396 375: onsuccess: #2110: 7: Success after binutils/gcc/linux/g [...] new 44e139c4e1 376: onsuccess: #2111: 7: Success after binutils/gcc/linux/g [...] new be45739dc8 377: onsuccess: #2112: 7: Success after binutils/gcc/gdb: 16 [...] new 31e7acc3de 378: onsuccess: #2113: 7: Success after binutils/gcc/linux/g [...] new 138da84b04 379: onsuccess: #2114: 7: Success after binutils/gcc/linux/g [...] new b99492e974 380: onsuccess: #2115: 7: Success after binutils/gcc/linux/g [...] new b6248fbb14 381: onsuccess: #2116: 7: Success after binutils/gcc/linux/g [...] new e109db1f5c 382: onsuccess: #2117: 7: Success after binutils/gcc/linux/g [...] new bd61135553 383: onsuccess: #2118: 7: Success after binutils/gcc/glibc/g [...] new 17aa0dee8d 384: onsuccess: #2119: 7: Success after binutils/gcc/linux/g [...] new 189367c514 385: onsuccess: #2120: 7: Success after binutils/gcc/gdb/qem [...] new 81959c7c09 386: onsuccess: #2121: 7: Success after binutils/gcc/glibc/g [...] new 96c936f55b 387: onsuccess: #2122: 7: Success after gcc/linux/qemu: 117 commits new 9a16dc17c4 388: onsuccess: #2123: 7: Success after binutils/gcc/gdb: 3 commits new 4425e94193 389: onsuccess: #2124: 7: Success after binutils/gcc/gdb: 5 commits new 8c563da034 390: onsuccess: #2125: 7: Success after binutils/gcc/linux/g [...] new 0175f1cdff 391: onsuccess: #2126: 7: Success after binutils/gcc/linux/g [...] new 4622361d48 392: onsuccess: #2127: 7: Success after glibc-2.37.9000-17-g [...] new cf03f1329c 393: onsuccess: #2128: 7: Success after gcc/qemu: 42 commits new 163d017ebb 394: onsuccess: #2129: 7: Success after binutils/gcc/linux/g [...] new 5c59787e04 395: onsuccess: #2130: 7: Success after binutils/gcc/gdb/qem [...] new 43ac4c70c9 396: onsuccess: #2131: 7: Success after binutils/gcc/linux/g [...] new c3100188b4 397: onsuccess: #2132: 7: Success after gcc: 2 commits new cfe9bc809d 398: onsuccess: #2133: 7: Success after binutils/gcc/glibc/g [...] new c4068b9a7c 399: onsuccess: #2134: 7: Success after binutils/gcc/linux/g [...] new e3c56f9ad4 400: onsuccess: #2135: 7: Success after binutils/gcc/linux/g [...] new df45569d9c 401: onsuccess: #2136: 7: Success after binutils/gcc/glibc/g [...] new 79dc545228 402: onsuccess: #2137: 7: Success after binutils/gcc/gdb: 22 [...] new f0283546b4 403: onsuccess: #2138: 7: Success after binutils/gcc/gdb: 4 commits new 2a67b1f531 404: onsuccess: #2139: 7: Success after basepoints/gcc-13-57 [...] new 6c15be1302 405: onsuccess: #2141: 7: Success after binutils/gcc/linux/g [...] new e875088442 406: onsuccess: #2142: 7: Success after binutils/gcc/gdb: 14 [...] new 3857d32c57 407: onsuccess: #2143: 7: Success after binutils/gcc/linux/g [...] new 197ac24a42 408: onsuccess: #2144: 7: Success after binutils/gcc/gdb/qem [...] new fb5aa0f766 409: onsuccess: #2145: 7: Success after binutils/gcc/linux/g [...] new c88db05fec 410: onsuccess: #2146: 7: Success after binutils/gcc/linux/g [...] new 61df412e61 411: onsuccess: #2147: 7: Success after binutils/gcc/gdb: 9 commits new b3796d7cd7 412: onsuccess: #2148: 7: Success after binutils/gcc/gdb: 6 commits new 1c4bbf7fa9 413: onsuccess: #2149: 7: Success after binutils/gcc/linux/g [...] new e0018a0f88 414: onsuccess: #2150: 7: Success after binutils/gcc/linux/g [...] new 9a15030a80 415: onsuccess: #2151: 7: Success after binutils/gcc/gdb: 93 [...] new bfd145544a 416: onsuccess: #2152: 7: Success after gcc: 50 commits new 4100f3ffc1 417: onsuccess: #2153: 7: Success after linux/glibc: 27 commits new 57e43c6a54 418: onsuccess: #2154: 7: Success after binutils/gcc/linux/g [...] new e729c640b2 419: onsuccess: #2155: 7: Success after binutils/gcc/gdb: 4 commits new ed808d7c34 420: onsuccess: #2156: 7: Success after binutils/gcc/gdb: 27 [...] new f95ee156a2 421: onsuccess: #2157: 7: Success after binutils/gcc/linux/g [...] new 060bfb797c 422: onsuccess: #2158: 7: Success after binutils/gcc/linux/g [...] new f7a7da04d9 423: onsuccess: #2159: 7: Success after binutils/gcc/gdb: 5 commits new 3f01e13c1b 424: onsuccess: #2160: 7: Success after binutils/gcc/glibc/g [...] new f037e81dcc 425: onsuccess: #2161: 7: Success after binutils/gcc/linux/g [...] new b727cbf22b 426: onsuccess: #2162: 7: Success after binutils/gcc/gdb: 13 [...] new b5ea164421 427: onsuccess: #2163: 7: Success after binutils/gdb: 4 commits new cd412d5b1d 428: onsuccess: #2165: 7: Success after binutils/gcc/glibc/g [...] new 3b1889f66d 429: onsuccess: #2166: 7: Success after binutils/gcc/linux/g [...] new 1f48ee8793 430: onsuccess: #2167: 7: Success after binutils/gcc/gdb/qem [...] new 304cb9ff48 431: onsuccess: #2168: 7: Success after binutils/gcc/gdb/qem [...] new a967b75015 432: onsuccess: #2169: 7: Success after binutils/gcc/linux/g [...] new b2f832e45f 433: onsuccess: #2170: 7: Success after binutils/gcc/linux/g [...] new 9364a2733b 434: onsuccess: #2171: 7: Success after gcc/glibc: 5 commits new aeb1c902bf 435: onsuccess: #2172: 7: Success after binutils/gcc/glibc/g [...] new 7851c86c52 436: onsuccess: #2173: 7: Success after binutils/gcc/linux/g [...] new 4e1f81d143 437: onsuccess: #2174: 7: Success after gcc/linux: 9 commits new ec7f05a1c2 438: onsuccess: #2175: 7: Success after gcc: 7 commits new 9abcfec426 439: onsuccess: #2176: 7: Success after linux: 11 commits new d44038e5e1 440: onsuccess: #2177: 7: Success after binutils/gcc/gdb: 6 commits new 02fff538d8 441: onsuccess: #2178: 7: Success after binutils/linux/gdb: [...] new b9084bba24 442: onsuccess: #2179: 7: Success after binutils/gcc/linux/g [...] new 89281ed77a 443: onsuccess: #2180: 7: Success after binutils/gdb: 2 commits new 256211eaf9 444: onsuccess: #2181: 7: Success after binutils/gcc/glibc/g [...] new fcddf3bb3b 445: onsuccess: #2182: 7: Success after binutils/gcc/glibc/g [...] new 15915ed7c9 446: onsuccess: #2183: 7: Success after binutils/gcc/linux/g [...] new 2675faa82b 447: onsuccess: #2184: 7: Success after binutils/gcc/linux/g [...] new 0fdca535c9 448: onsuccess: #2185: 7: Success after binutils/gcc/gdb/qem [...] new df9ac5ef83 449: onsuccess: #2186: 7: Success after binutils/gcc/linux/g [...] new e488f3acb0 450: onsuccess: #2188: 7: Success after binutils/gcc/linux/g [...] new 6cf8178fb7 451: onsuccess: #2189: 7: Success after binutils/gcc/gdb: 11 [...] new eea5d12aa8 452: onsuccess: #2190: 7: Success after binutils/gcc/linux/g [...] new c1f5489dad 453: onsuccess: #2191: 7: Success after binutils/gcc/linux/g [...] new ad4f779ad1 454: onsuccess: #2192: 7: Success after binutils/linux/glibc [...] new 122ef80c2b 455: onsuccess: #2193: 7: Success after binutils/gcc/gdb: 13 [...] new 26bd6c9ac2 456: onsuccess: #1: 7: Success after binutils/gcc/linux/glib [...] new c7358e33ce 457: onsuccess: #2194: 7: Success after binutils/gcc/linux/g [...] new 0e8bde472a 458: onsuccess: #2: 7: Success after gcc/linux/glibc: 581 commits new ac6235ec94 459: onsuccess: #3: 7: Success after binutils/gcc/glibc/gdb/ [...] 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 (0e68fa438f) \ 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 1740 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2768 bytes 04-build_abe-binutils/console.log.xz | Bin 30504 -> 31012 bytes 05-build_abe-stage1/console.log.xz | Bin 88660 -> 88808 bytes 07-build_abe-linux/console.log.xz | Bin 9168 -> 9136 bytes 08-build_abe-glibc/console.log.xz | Bin 235844 -> 235468 bytes 09-build_abe-stage2/console.log.xz | Bin 225028 -> 225692 bytes 10-build_abe-gdb/console.log.xz | Bin 38628 -> 38780 bytes 11-build_abe-qemu/console.log.xz | Bin 31656 -> 31124 bytes 12-check_regression/console.log.xz | Bin 3868 -> 4476 bytes 13-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/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 44 ++++++++++++------------ 21 files changed, 63 insertions(+), 63 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[gcc] branch master updated (3d1d3ece9bc -> 94c9b1bb79f)

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 3d1d3ece9bc [PR105224] C++ modules and AAPCS/ARM EABI clash on inline k [...] new 94c9b1bb79f asan: adjust module name for global variables 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/asan.cc | 12 +++++++++++- gcc/testsuite/c-c++-common/asan/global-overflow-1.c | 2 +- 2 files changed, 12 insertions(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (91f84f3ea7 -> d9393fd5a6)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards 91f84f3ea7 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards da700b93b9 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] discards 7d91cdc513 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] discards 35f3f9b01b 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] discards 39fbcb505d 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] discards 2a3c7b5aa4 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] discards 8d972aed5b 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] discards c4fab9b818 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] discards 8a15fea837 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] discards 974a45815f 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] discards 1c0f971b49 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] discards 2df9886113 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits discards 7a12cc7519 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] discards bf972d6dca 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] discards d3ddb2245f 408: onsuccess: #2662: 1: Success after linux: 11 commits discards 9a232fcd6c 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards 166869255d 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards 4eec29cfcf 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards e80a4459bb 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards 766506dddb 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards be4bb5408e 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards 30089a18b3 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards 80be16c2ee 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards 31bc72e893 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards 966c19be5a 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards ff23c12391 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards 2917267ac4 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards fe4d18c745 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards 205f8c2079 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards 6716033bbb 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards 615e921cf1 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards 0c036a6c07 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards b67ae9839d 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 8d34d97e00 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards 1c0d59bd77 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards b1ad10ceb6 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards b7b2df4750 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 6d7e4ef183 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 143681b731 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 6c995bc975 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 372dcb6b9d 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 5fa9d008dd 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards df37681bc5 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards b8ac69755e 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 9013a1bd49 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards f2112d4bb2 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 0d8464a2ec 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 6ec9e631ab 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 36cf240a9c 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 02c1ffd864 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 79e95f0b67 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 426234ef57 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 46c96e2f15 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 328573083e 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards bb7e7e439e 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 856b4ea2cd 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 2b045c4145 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 058aba3cfe 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 20013d02ab 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 1d84bd2899 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards a28d276689 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards fd7bfaf46c 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 45a1388288 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 7d3fb62e2d 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 6d3d59c20f 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards d3042bf845 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 716e806c3e 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 2f4a5083c4 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 46ba08ba2d 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards b4b8325d9e 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards be40e5811f 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 09766ec37d 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 04ee183570 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards b650bc5f48 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards db8131f8db 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards ea415aa729 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards e8b80290c8 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 70afb6bf49 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards f6178d650b 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 9ce283c486 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards d90b04efc0 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 680ddef5af 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 8de157578f 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards c65387fa50 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards b6db5c5b09 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards d650fc1f1d 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards b20ecddada 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards ef3d973b5b 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 4490a1c0dc 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 5757bdfe2d 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards ea2ab843b6 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 31568ec480 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards bcf1763aa3 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 912d17d700 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards a0adbdc08b 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards f00ed4699a 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards e1db4b2bea 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards d7f9889c09 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards cfaf415d7d 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards a579f644bf 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 196421b199 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new b9e2b9d4ea 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new cfbd68f127 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new fa20d03c94 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new f2a103bb8c 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 336507aca6 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new c27ff240bb 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new e6bdd84595 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 4994bd79f9 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 60fbdb5d6a 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 60dfcad5b7 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 4b11f260a1 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 1dcf95ec62 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new f9067477b2 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 3334ab4b1c 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 64de7fd0c2 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 6e33869bfc 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new c2e8e36002 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new dcc0652a29 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new cfaa72e4ed 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 954bdfa55c 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 393be1347c 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 93b13c52c8 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 941e28bae8 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 703e545a89 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 9964649566 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new bdb7090beb 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new e7e61316f1 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 90c12ba3da 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 54fd19154a 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 503266f1c7 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 3817d71b09 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 35d846cecf 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 5660850f39 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 1e2629106f 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new dd51ed5746 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 763512c3ab 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new f8c3beff30 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new d5856351aa 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 20b131be91 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new b0ffe15e56 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 36387b1380 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 936b15a194 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 152c832cf2 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 8300fdd0d9 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 44fd02d617 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new 38e3ca5900 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 8ed7d78901 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 03f8d1e212 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 850fa35596 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 7cd413c9fa 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new afcbd9412b 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 5ebb63597e 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 01c42e0d54 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 683b94ea1b 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 2621c5f6b4 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 1849633438 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 4ba6995942 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 390f55dd78 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 696f0b491a 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 0a0b572678 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 77cd57896f 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 57f599e341 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new 37c7952159 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 0980a17a53 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new a784de5623 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new a3237481d3 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 7a34aff2fa 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new 77a07eda7f 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new c610c6cbab 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new f4aaf58d43 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new eab9133131 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new 07479fb00e 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new 06bba9b59f 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new 7714e1fbf1 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new 53bb1875e9 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new 7ec60414de 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new d25fae019b 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new f839ee4073 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new 9015a03360 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new b0db6dd9f9 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new 7c1d8a3eee 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new ffc9d743d2 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new 238cf5ea02 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new e6ecd3fb5a 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new 4e978b81d1 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new 1e5910a8ee 407: onsuccess: #2661: 1: Success after gcc: 7 commits new ab254c7ae1 408: onsuccess: #2662: 1: Success after linux: 11 commits new 0d043194dc 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] new 7616b46348 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] new b0ba5b81a7 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits new d101983982 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] new 0cb78d59d2 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] new ed735ba84c 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] new 9207bf2e10 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] new 1a88ae4a78 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] new 83faa3287b 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] new f69b4f9afc 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] new d348251507 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] new 408f4d978a 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] new 7d01797fe4 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] new b89846a51e 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new d9393fd5a6 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] 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 (91f84f3ea7) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1812 -> 1812 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 30964 -> 31100 bytes 04-build_abe-stage1/console.log.xz | Bin 70512 -> 71056 bytes 06-build_abe-linux/console.log.xz | Bin 9180 -> 9180 bytes 07-build_abe-glibc/console.log.xz | Bin 244340 -> 243964 bytes 08-build_abe-stage2/console.log.xz | Bin 201800 -> 202180 bytes 09-build_abe-gdb/console.log.xz | Bin 38544 -> 38644 bytes 10-build_abe-qemu/console.log.xz | Bin 31448 -> 31772 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3824 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2592 -> 2744 bytes 13-check_regression/console.log.xz | Bin 7940 -> 8204 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 7 -- 13-check_regression/mail-body.txt | 139 +++++-------------------------- 13-check_regression/results.compare | 54 ++++++------ 13-check_regression/results.compare2 | 139 ++++++++++++------------------- 13-check_regression/results.regressions | 45 ---------- 14-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 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 141 +++++--------------------------- mail/mail-subject.txt | 2 +- manifest.sh | 48 +++++------ results | 45 ---------- sumfiles/g++.log.xz | Bin 3392444 -> 3422708 bytes sumfiles/g++.sum | 11 ++- sumfiles/gcc.log.xz | Bin 3021676 -> 3020620 bytes sumfiles/gcc.sum | 48 ++++------- sumfiles/gfortran.log.xz | Bin 1041532 -> 1044040 bytes sumfiles/libatomic.log.xz | Bin 2312 -> 2312 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217404 -> 217388 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2680 -> 2684 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434620 -> 434196 bytes sumfiles/libstdc++.sum | 96 +++++++++------------- 44 files changed, 255 insertions(+), 607 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allnoconfig updated (bdff75097a -> dbb1586e8a)

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-lts-allnoconfig in repository toolchain/ci/base-artifacts. from bdff75097a 44: onsuccess: #504: boot: Success after binutils/llvm/linux [...] new dbb1586e8a 45: onsuccess: #1: boot: Success after binutils/llvm/qemu: 8 [...] 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 1788 -> 1952 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31148 -> 31368 bytes 04-build_kernel_llvm/console.log.xz | Bin 67196 -> 67272 bytes 05-build_abe-qemu/console.log.xz | Bin 31968 -> 31852 bytes 06-build_linux/console.log.xz | Bin 3340 -> 3352 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4368 -> 3960 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +++++++++++++------------- 16 files changed, 20 insertions(+), 20 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[gcc] branch master updated (8520132bc36 -> 3d1d3ece9bc)

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 8520132bc36 libstdc++: Constrain net::executor constructors new 3d1d3ece9bc [PR105224] C++ modules and AAPCS/ARM EABI clash on inline k [...] 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/testsuite/g++.dg/modules/virt-2_a.C | 3 +++ 1 file changed, 3 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-next-allmodconfig updated (1539022e7e -> ce1efda92b)

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-arm-next-allmodconfig in repository toolchain/ci/base-artifacts. from 1539022e7e 46: onsuccess: #594: 23428: Success after binutils/gcc/linux [...] new ce1efda92b 47: onsuccess: #1: 23433: Success after binutils/gcc/linux/q [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1772 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 30756 -> 31084 bytes 04-build_abe-stage1/console.log.xz | Bin 89452 -> 89012 bytes 05-build_abe-qemu/console.log.xz | Bin 32016 -> 31648 bytes 06-build_linux/console.log.xz | Bin 10384 -> 9604 bytes 08-check_regression/console.log.xz | Bin 4400 -> 4460 bytes 08-check_regression/mail-body.txt | 4 ++-- 09-update_baseline/console.log | 9 --------- 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 | 6 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 19 files changed, 29 insertions(+), 38 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[gcc] branch master updated (f30421fa72f -> 8520132bc36)

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 f30421fa72f libstdc++: Reorder dg-options before dg-do new ae390479340 libstdc++: Suppress warnings about use of deprecated std::a [...] new 363f0ef50bd libstdc++: Optimize net::ip::address_v4::to_string() new 36ecfb75e05 libstdc++: Fix conversion to/from net::ip::address_v4::bytes_type new 80e9bac232f libstdc++: Fix members of net::ip::network_v4 new 97111dccf97 libstdc++: Make net::ip::basic_endpoint comparisons constexpr new 8520132bc36 libstdc++: Constrain net::executor constructors 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: libstdc++-v3/include/experimental/executor | 9 +- libstdc++-v3/include/experimental/internet | 101 +++++++---- libstdc++-v3/include/ext/aligned_buffer.h | 3 + .../experimental/net/internet/address/v4/cons.cc | 33 ++-- .../net/internet/address/v4/creation.cc | 24 ++- .../net/internet/address/v4/members.cc | 14 ++ .../experimental/net/internet/endpoint/cons.cc | 66 ++++++++ .../experimental/net/internet/network/v4/cons.cc | 129 ++++++++++++++ .../net/internet/network/v4/members.cc | 186 +++++++++++++++++++++ 9 files changed, 516 insertions(+), 49 deletions(-) create mode 100644 libstdc++-v3/testsuite/experimental/net/internet/endpoint/cons.cc create mode 100644 libstdc++-v3/testsuite/experimental/net/internet/network/v4/cons.cc create mode 100644 libstdc++-v3/testsuite/experimental/net/internet/network/v4/members.cc -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[gcc] branch master updated (05a3fc910c3 -> f30421fa72f)

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 05a3fc910c3 i386: Update i386-builtin.def file comment description of B [...] new f30421fa72f libstdc++: Reorder dg-options before dg-do The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: libstdc++-v3/testsuite/std/format/arguments/lwg3810.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits February 2023