Tcwg-commits January 2023

tcwg-commits@lists.linaro.org

5 participants
4127 discussions

[binutils-gdb] branch users/mjw/try-sim-sparc updated (8ab3c866397 -> 69680559cb7)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch users/mjw/try-sim-sparc in repository binutils-gdb. discards 8ab3c866397 sim: common, microblaze: handle signal.h defining REC_PC. new 69680559cb7 sim: common, microblaze: handle signal.h defining REC_PC. 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 (8ab3c866397) \ N -- N -- N refs/heads/users/mjw/try-sim-sparc (69680559cb7) 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 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: sim/common/sim-signal.c | 6 ++++++ 1 file changed, 6 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[binutils-gdb] branch users/mjw/try-sim-sparc updated (8bc2389d17d -> 8ab3c866397)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch users/mjw/try-sim-sparc in repository binutils-gdb. discards 8bc2389d17d sim: microblaze: interp.c don't include signal.h new 8ab3c866397 sim: common, microblaze: handle signal.h defining REC_PC. 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 (8bc2389d17d) \ N -- N -- N refs/heads/users/mjw/try-sim-sparc (8ab3c866397) 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 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: sim/common/sim-events.c | 6 ++++++ 1 file changed, 6 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (a6656870fc -> ad7835c275)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm in repository toolchain/ci/base-artifacts. discards a6656870fc 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 00e65f419c 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards b80b3a6130 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 70985dfe72 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards e7231f543c 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 7bdc209988 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 45e56e4b84 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 61b3b6dfd2 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 49178cba03 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 67ad9883d9 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards baa924a4f5 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 751e379956 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards ad36b9b5bc 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 6600f99d4e 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards bb76af3378 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards d1f4c63635 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 09c657a7bb 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards fed540622f 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 5a11e8fee1 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 1a6e9cb55f 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards ad4b37b9dd 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 8ea654fb4b 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 11cd0e6b45 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards da5fbeddbf 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 6dd9c49d5b 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards e446d8aed0 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 0e3d441b70 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards c6989e0f6c 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 894d2fb8ca 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 938a565bdf 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 7ac3370bda 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 6f0f166f46 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards d6867d365a 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 40917e0318 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 570921c09b 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards daeb5c0b3b 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 233a22bf5d 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 1272dbda12 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 58c53f24a6 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards d14a93528b 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards d824c8bb52 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 2e3489df85 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 7821f64f0b 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards fdfa42ac91 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 15996cfeba 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 2d67449214 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 24b58ee717 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 089992126f 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 0a06bed8b1 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 4cbf65a782 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards c236c368f7 301: onsuccess: #2118: 1: Success after linux: 16 commits discards f8f2e7b407 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 385b015ac8 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards d576532be2 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 2d644268b5 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 5732d2e906 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 56c7be7d66 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 4e9cbd4d71 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 37cb920791 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 6387470029 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 9ca5290bf7 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards e6722cda96 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 9c9be62036 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 742df23e52 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards cae69f9054 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards e3b8bd6add 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards c2b0f8f5e8 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 67fa0e6602 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards cc148f7b0a 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 16f1a6524a 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 0e1ffd4366 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 31b0513b1c 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 005ac44862 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 66616696cd 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards b388bee479 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 5203b19c92 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 263746b716 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards a0680f041c 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 0932afa440 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 67a6458b71 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 5da0c52bef 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 82cba8e35a 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards a604acf403 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards fdb9432e6b 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards d0a7222a5b 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 6f03f45a7f 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 7221a67df8 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 0ed48fe69b 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards da61cb65d5 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 95e96a9691 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 820716b2bb 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 07d6530378 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 8f1fcb40a0 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards e3506dff60 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards debd05ea18 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 1a0ea0e73f 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 22c7c12d29 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 806d9cbc28 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 3ae8c3b5a7 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards a26037e2b7 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 315d85dbbe 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new fab40790ee 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 3ff58db684 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new d0903bbd75 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 3fcaa36307 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new b0d548a39b 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 850d74d92f 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 4c180629d0 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 679745a2bf 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new eecadeebc4 259: onsuccess: #2075: 1: Success after glibc: 2 commits new bb5cdaaaef 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 9efadeff31 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 5bf86f2546 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 9e37e65eb8 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new e96572125e 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 98b4e70356 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 6e3f341e2e 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new ba0dcd4bdf 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 7284ca1105 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 59897e98cf 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 005d3facca 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 80594229a6 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 55e23c282c 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new fa4c1bc6d7 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 93041fb90e 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new a7d170c22f 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new beacf3d495 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new e9a741f895 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 4cf9499ed8 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new e565441b0d 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 12cbaa4883 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 988f69423b 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 17c788964b 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 75a845b69c 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new c1d559c88a 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new d9240b274f 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new e50509397f 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 2b9eb5d16f 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 89aba5ff87 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 745ec88705 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 040031211b 290: onsuccess: #2106: 1: Success after gcc: 2 commits new c9e888e244 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 192ee8b633 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 8e75379819 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new f5d9e98a26 294: onsuccess: #2110: 1: Success after gcc: 17 commits new ebca23a63e 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 2d10320220 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 423cc136cc 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new ccdb6659e4 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 2350f9244e 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 450e6638aa 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 0a5e29b306 301: onsuccess: #2118: 1: Success after linux: 16 commits new bcab69df1d 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 32cd6c671b 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 05b8e07158 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 3b95545132 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new a40edd813b 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 2cf30786a8 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 01f22e56c3 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new b467c49fe4 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 00d5f649e3 310: onsuccess: #2129: 1: Success after binutils: 4 commits new a1a04df0af 311: onsuccess: #2130: 1: Success after gcc: 4 commits new daed8d1463 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 9630acfad3 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new a6b6c32b97 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 4becb8a471 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new d223030b16 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 02edc3aaef 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new e15271bf63 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new cc5b4d086d 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 6d0d9b19ec 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 58739e9067 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 00bfb8203c 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new ad39ef1463 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new eb6c47b95a 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new defcda6d53 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 2a2112c9d3 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 9b41a732c8 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 5fed159209 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 8e0ae871d6 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 353c376d2c 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 06144580d1 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 79973bd3ce 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new c819e5011d 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new b9eede0ad4 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new a10bb00197 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 29256a1ada 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new b67c46ee59 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 34f2507d56 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 0b0d48d0c1 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 7905a69452 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 49eb57d928 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 4fbb25c4a2 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 2f6c095734 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 87aa472244 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 76e617472c 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new d943b2d137 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 084c8bea55 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 0fe7265970 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new ce94c84015 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new ae6c03a58c 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 9fa920fbc1 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new ad7835c275 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (a6656870fc) \ 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 1780 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2804 bytes 03-build_abe-binutils/console.log.xz | Bin 31544 -> 31820 bytes 04-build_abe-stage1/console.log.xz | Bin 91604 -> 92048 bytes 06-build_abe-linux/console.log.xz | Bin 8660 -> 8992 bytes 07-build_abe-glibc/console.log.xz | Bin 236720 -> 240168 bytes 08-build_abe-stage2/console.log.xz | Bin 229124 -> 229016 bytes 09-build_abe-gdb/console.log.xz | Bin 39044 -> 39204 bytes 10-build_abe-qemu/console.log.xz | Bin 32004 -> 32160 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2620 -> 2748 bytes 13-check_regression/console.log.xz | Bin 5992 -> 6452 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 26 + 13-check_regression/results.compare | 21 +- 13-check_regression/results.compare2 | 82 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 26 + sumfiles/g++.log.xz | Bin 2670956 -> 2692288 bytes sumfiles/g++.sum | 36 +- sumfiles/gcc.log.xz | Bin 2242860 -> 2241952 bytes sumfiles/gcc.sum | 2204 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 891476 -> 896920 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213996 -> 213988 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434860 -> 445344 bytes sumfiles/libstdc++.sum | 20 +- 43 files changed, 1346 insertions(+), 1254 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch master updated (d80e5a7b30e -> 523e8716a45)

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 d80e5a7b30e libstdc++: Implement std::chrono::current_zone() for AIX [P [...] new b1c839be835 libstdc++: Deliver names of C functions in <stacktrace> new 523e8716a45 libstdc++: enable <stacktrace> on windows 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: libstdc++-v3/acinclude.m4 | 2 ++ libstdc++-v3/config.h.in | 3 +++ libstdc++-v3/configure | 13 +++++++++++++ libstdc++-v3/include/std/stacktrace | 2 ++ libstdc++-v3/src/libbacktrace/Makefile.am | 1 + libstdc++-v3/src/libbacktrace/Makefile.in | 4 ++++ 6 files changed, 25 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-stable-allnoconfig updated (286f701726 -> bbad99a007)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-stable-allnoconfig in repository toolchain/ci/base-artifacts. from 286f701726 38: onsuccess: #488: boot: Success after binutils/llvm/linux [...] new bbad99a007 39: onsuccess: #489: boot: Success after binutils/llvm/linux [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1808 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2804 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 32492 -> 32020 bytes 04-build_kernel_llvm/console.log.xz | Bin 66428 -> 66096 bytes 05-build_abe-qemu/console.log.xz | Bin 31840 -> 32744 bytes 06-build_linux/console.log.xz | Bin 3420 -> 3364 bytes 08-check_regression/console.log.xz | Bin 4448 -> 4400 bytes 08-check_regression/mail-body.txt | 2 +- 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- results | 2 +- 19 files changed, 30 insertions(+), 30 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[binutils-gdb] branch users/mjw/try-sim-sparc created (now 8bc2389d17d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch users/mjw/try-sim-sparc in repository binutils-gdb. at 8bc2389d17d sim: microblaze: interp.c don't include signal.h This branch includes the following new commits: new 8bc2389d17d sim: microblaze: interp.c don't include signal.h The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch master updated (c47dcb95666 -> d80e5a7b30e)

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 c47dcb95666 libstdc++: Disable unwanted code for --with-libstdcxx-zoneinfo=no new d80e5a7b30e libstdc++: Implement std::chrono::current_zone() for AIX [P [...] 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/src/c++20/tzdb.cc | 23 +++++++++++++++++++++-- 1 file changed, 21 insertions(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_ubsan updated (13f4b00e4c -> d63e899ff1)

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_ubsan in repository toolchain/ci/base-artifacts. from 13f4b00e4c 50: onsuccess: #170: 2: Success after binutils/gcc: 7 commits new d63e899ff1 51: onsuccess: #171: 2: Success after binutils/gcc: 8 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 1732 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2752 bytes 04-build_abe-binutils/console.log.xz | Bin 50888 -> 51680 bytes 05-build_abe-bootstrap_ubsan/console.log.xz | Bin 526408 -> 525896 bytes 06-check_regression/console.log.xz | Bin 2764 -> 2848 bytes 07-update_baseline/console.log | 9 +++++++++ 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, 24 insertions(+), 15 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/release-arm updated (cbdfe9eb5b -> fda78c46c8)

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/release-arm in repository toolchain/ci/base-artifacts. from cbdfe9eb5b 51: onsuccess: #215: 1: Success after gcc/glibc: 8 commits new fda78c46c8 52: onsuccess: #216: 1: Success after gcc/linux/glibc: 16739 [...] 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 1736 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 50732 -> 51908 bytes 04-build_abe-gcc/console.log.xz | Bin 228452 -> 229320 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8688 -> 8648 bytes 07-build_abe-glibc/console.log.xz | Bin 232488 -> 232992 bytes 08-build_abe-gdb/console.log.xz | Bin 45592 -> 46504 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3828 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3100 -> 2412 bytes 11-check_regression/console.log.xz | Bin 5816 -> 5804 bytes 11-check_regression/mail-body.txt | 27 - 11-check_regression/results.compare | 31 +- 11-check_regression/results.compare2 | 63 +- 12-update_baseline/console.log | 9 + dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- sumfiles/g++.log.xz | Bin 2846308 -> 2838296 bytes sumfiles/g++.sum | 120 +- sumfiles/gcc.log.xz | Bin 2452536 -> 2476660 bytes sumfiles/gcc.sum | 4811 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 938416 -> 941768 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 212684 -> 212784 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 458032 -> 457168 bytes sumfiles/libstdc++.sum | 10 +- 37 files changed, 2557 insertions(+), 2651 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-defconfig updated (9f4fb38b11 -> 6cd765c279)

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-arm-next-defconfig in repository toolchain/ci/base-artifacts. from 9f4fb38b11 37: onsuccess: #458: boot: Success after binutils/llvm/linux [...] new 6cd765c279 38: onsuccess: #459: boot: Success after binutils/llvm/linux [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1772 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31800 -> 31532 bytes 04-build_kernel_llvm/console.log.xz | Bin 64312 -> 64324 bytes 05-build_abe-qemu/console.log.xz | Bin 31536 -> 31980 bytes 06-build_linux/console.log.xz | Bin 3140 -> 3616 bytes 07-boot_linux/console.log.xz | Bin 5640 -> 5648 bytes 08-check_regression/console.log.xz | Bin 4356 -> 4360 bytes 08-check_regression/mail-body.txt | 4 ++-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 6 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- results | 2 +- 19 files changed, 28 insertions(+), 28 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits January 2023