Tcwg-commits February 2023

tcwg-commits@lists.linaro.org

5 participants
3393 discussions

[gcc] branch master updated (af46073dbe8 -> 8fda668e091)

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 af46073dbe8 Fix memory leak in if-conversion new 2e29e2fbeb8 libstdc++: Simplify three helper functions into one new 92c47b15d5a libstdc++: Fix simd build failure on clang new fa37ac2b59e libstdc++: Add missing constexpr on simd shift implementation new ffa39f7120f libstdc++: Fix -Wsign-compare issue new 8fda668e091 libstdc++: Test that integral simd reductions are precise The 5 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/bits/simd.h | 12 ++++++------ libstdc++-v3/include/experimental/bits/simd_builtin.h | 2 +- libstdc++-v3/include/experimental/bits/simd_detail.h | 3 ++- libstdc++-v3/include/experimental/bits/simd_x86.h | 8 ++++---- libstdc++-v3/testsuite/experimental/simd/tests/reductions.cc | 3 ++- 5 files changed, 15 insertions(+), 13 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 (7668d7c255 -> a12df02cb1)

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 7668d7c255 454: onsuccess: #2192: 7: Success after binutils/linux/glibc [...] discards 84b8ff9272 453: onsuccess: #2191: 7: Success after binutils/gcc/linux/g [...] discards eab9a9e848 452: onsuccess: #2190: 7: Success after binutils/gcc/linux/g [...] discards 56c669f6aa 451: onsuccess: #2189: 7: Success after binutils/gcc/gdb: 11 [...] discards a5e5ad5024 450: onsuccess: #2188: 7: Success after binutils/gcc/linux/g [...] discards 4a174e97c7 449: onsuccess: #2186: 7: Success after binutils/gcc/linux/g [...] discards 95c55c5283 448: onsuccess: #2185: 7: Success after binutils/gcc/gdb/qem [...] discards 2aae462543 447: onsuccess: #2184: 7: Success after binutils/gcc/linux/g [...] discards e379b0f1b9 446: onsuccess: #2183: 7: Success after binutils/gcc/linux/g [...] discards 54df82e995 445: onsuccess: #2182: 7: Success after binutils/gcc/glibc/g [...] discards d6d36d9603 444: onsuccess: #2181: 7: Success after binutils/gcc/glibc/g [...] discards 4efa8705df 443: onsuccess: #2180: 7: Success after binutils/gdb: 2 commits discards c9d807dc1a 442: onsuccess: #2179: 7: Success after binutils/gcc/linux/g [...] discards 95ea1c2c38 441: onsuccess: #2178: 7: Success after binutils/linux/gdb: [...] discards 4eb64743d3 440: onsuccess: #2177: 7: Success after binutils/gcc/gdb: 6 commits discards 00960ff6ae 439: onsuccess: #2176: 7: Success after linux: 11 commits discards 51ae3a9c0b 438: onsuccess: #2175: 7: Success after gcc: 7 commits discards 43a5a5b9d7 437: onsuccess: #2174: 7: Success after gcc/linux: 9 commits discards bd979b37b7 436: onsuccess: #2173: 7: Success after binutils/gcc/linux/g [...] discards 5498dba8d2 435: onsuccess: #2172: 7: Success after binutils/gcc/glibc/g [...] discards 0a5259b51d 434: onsuccess: #2171: 7: Success after gcc/glibc: 5 commits discards 23df04aff2 433: onsuccess: #2170: 7: Success after binutils/gcc/linux/g [...] discards 87dd2fdb8d 432: onsuccess: #2169: 7: Success after binutils/gcc/linux/g [...] discards 5be4cf8e60 431: onsuccess: #2168: 7: Success after binutils/gcc/gdb/qem [...] discards d07d1da152 430: onsuccess: #2167: 7: Success after binutils/gcc/gdb/qem [...] discards 9dcece820c 429: onsuccess: #2166: 7: Success after binutils/gcc/linux/g [...] discards 95fde6ff3f 428: onsuccess: #2165: 7: Success after binutils/gcc/glibc/g [...] discards b0a18e66b1 427: onsuccess: #2163: 7: Success after binutils/gdb: 4 commits discards 0dc1d505a1 426: onsuccess: #2162: 7: Success after binutils/gcc/gdb: 13 [...] discards c1cc14265e 425: onsuccess: #2161: 7: Success after binutils/gcc/linux/g [...] discards 2855f68778 424: onsuccess: #2160: 7: Success after binutils/gcc/glibc/g [...] discards 752045219f 423: onsuccess: #2159: 7: Success after binutils/gcc/gdb: 5 commits discards 20dadbde10 422: onsuccess: #2158: 7: Success after binutils/gcc/linux/g [...] discards 1583f461b7 421: onsuccess: #2157: 7: Success after binutils/gcc/linux/g [...] discards 2428a437dc 420: onsuccess: #2156: 7: Success after binutils/gcc/gdb: 27 [...] discards 7bc6edd1e5 419: onsuccess: #2155: 7: Success after binutils/gcc/gdb: 4 commits discards f767f66544 418: onsuccess: #2154: 7: Success after binutils/gcc/linux/g [...] discards cbad2c4f65 417: onsuccess: #2153: 7: Success after linux/glibc: 27 commits discards a651fa0460 416: onsuccess: #2152: 7: Success after gcc: 50 commits discards 57cee61b82 415: onsuccess: #2151: 7: Success after binutils/gcc/gdb: 93 [...] discards 77274cb0fd 414: onsuccess: #2150: 7: Success after binutils/gcc/linux/g [...] discards c92f3b36e2 413: onsuccess: #2149: 7: Success after binutils/gcc/linux/g [...] discards c357c00e60 412: onsuccess: #2148: 7: Success after binutils/gcc/gdb: 6 commits discards a944f3457b 411: onsuccess: #2147: 7: Success after binutils/gcc/gdb: 9 commits discards 30e349797e 410: onsuccess: #2146: 7: Success after binutils/gcc/linux/g [...] discards eb4f99019a 409: onsuccess: #2145: 7: Success after binutils/gcc/linux/g [...] discards 4edb1e7dbf 408: onsuccess: #2144: 7: Success after binutils/gcc/gdb/qem [...] discards c777febaf7 407: onsuccess: #2143: 7: Success after binutils/gcc/linux/g [...] discards f9bd83f84f 406: onsuccess: #2142: 7: Success after binutils/gcc/gdb: 14 [...] discards c49f9da9b2 405: onsuccess: #2141: 7: Success after binutils/gcc/linux/g [...] discards ffdfcab832 404: onsuccess: #2139: 7: Success after basepoints/gcc-13-57 [...] discards 769566fe1f 403: onsuccess: #2138: 7: Success after binutils/gcc/gdb: 4 commits discards dec8c179b7 402: onsuccess: #2137: 7: Success after binutils/gcc/gdb: 22 [...] discards 8d98859dd3 401: onsuccess: #2136: 7: Success after binutils/gcc/glibc/g [...] discards 79ca500863 400: onsuccess: #2135: 7: Success after binutils/gcc/linux/g [...] discards 3c99202cd8 399: onsuccess: #2134: 7: Success after binutils/gcc/linux/g [...] discards 8e15bd0da5 398: onsuccess: #2133: 7: Success after binutils/gcc/glibc/g [...] discards 535738aa22 397: onsuccess: #2132: 7: Success after gcc: 2 commits discards 9a3fc36456 396: onsuccess: #2131: 7: Success after binutils/gcc/linux/g [...] discards 9c69c51cf3 395: onsuccess: #2130: 7: Success after binutils/gcc/gdb/qem [...] discards 99480ac217 394: onsuccess: #2129: 7: Success after binutils/gcc/linux/g [...] discards 296d5e7723 393: onsuccess: #2128: 7: Success after gcc/qemu: 42 commits discards daad2ed4fb 392: onsuccess: #2127: 7: Success after glibc-2.37.9000-17-g [...] discards b94b16aec0 391: onsuccess: #2126: 7: Success after binutils/gcc/linux/g [...] discards aadb45e9e7 390: onsuccess: #2125: 7: Success after binutils/gcc/linux/g [...] discards ebd36aa374 389: onsuccess: #2124: 7: Success after binutils/gcc/gdb: 5 commits discards 1350bf60cf 388: onsuccess: #2123: 7: Success after binutils/gcc/gdb: 3 commits discards 5b75128054 387: onsuccess: #2122: 7: Success after gcc/linux/qemu: 117 commits discards 331cf16f54 386: onsuccess: #2121: 7: Success after binutils/gcc/glibc/g [...] discards ee1fa02d3f 385: onsuccess: #2120: 7: Success after binutils/gcc/gdb/qem [...] discards a923fdaf2e 384: onsuccess: #2119: 7: Success after binutils/gcc/linux/g [...] discards 5c534f11e5 383: onsuccess: #2118: 7: Success after binutils/gcc/glibc/g [...] discards 1b1786b57f 382: onsuccess: #2117: 7: Success after binutils/gcc/linux/g [...] discards 50608b2e89 381: onsuccess: #2116: 7: Success after binutils/gcc/linux/g [...] discards 1bd2666c1e 380: onsuccess: #2115: 7: Success after binutils/gcc/linux/g [...] discards bf2e0df13f 379: onsuccess: #2114: 7: Success after binutils/gcc/linux/g [...] discards aaed27b485 378: onsuccess: #2113: 7: Success after binutils/gcc/linux/g [...] discards 54200ada30 377: onsuccess: #2112: 7: Success after binutils/gcc/gdb: 16 [...] discards dc5cb7ff9b 376: onsuccess: #2111: 7: Success after binutils/gcc/linux/g [...] discards 449ebfdb8b 375: onsuccess: #2110: 7: Success after binutils/gcc/linux/g [...] discards d712ce3fb3 374: onsuccess: #2109: 7: Success after binutils/gcc/linux/g [...] discards c21c43a43b 373: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] discards a3cdce35ea 372: onsuccess: #2106: 7: Success after binutils/gcc/linux/g [...] discards b1a4819388 371: onsuccess: #2105: 7: Success after binutils/gcc/gdb/qem [...] discards f86fea2e5b 370: onsuccess: #2104: 7: Success after binutils/gcc/linux/g [...] discards 4330754f68 369: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] discards fbad837aaf 368: onsuccess: #2102: 7: Success after binutils/gcc/linux/g [...] discards 9bba4eb4c2 367: onsuccess: #2101: 7: Success after binutils/gcc/linux/g [...] discards 86496f4274 366: onsuccess: #2100: 7: Success after binutils/gcc/glibc/g [...] discards 41965fb87f 365: onsuccess: #2099: 7: Success after gcc/linux: 21 commits discards 9705d09ec2 364: onsuccess: #2098: 7: Success after binutils/gdb: 4 commits discards 7e15b4fa25 363: onsuccess: #2097: 7: Success after binutils/gcc/gdb: 25 [...] discards 3c5d9abba7 362: onsuccess: #2096: 7: Success after binutils/gcc/linux/g [...] discards 78774b75ed 361: onsuccess: #2095: 7: Success after gcc/linux: 15 commits discards 27c9f443b2 360: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] discards e512682494 359: onsuccess: #2093: 7: Success after binutils/gcc/linux/g [...] discards 7718e18e81 358: onsuccess: #2092: 7: Success after binutils/gcc/gdb: 10 [...] discards b90c7270c1 357: onsuccess: #2091: 7: Success after binutils/gcc/linux/g [...] discards dc9011a092 356: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] discards ced64d3d45 355: onsuccess: #2089: 7: Success after binutils/gcc/linux/g [...] discards b9bf3ecd9f 354: onsuccess: #2088: 7: Success after binutils/gcc/gdb: 7 commits new 8fcc3df059 354: onsuccess: #2088: 7: Success after binutils/gcc/gdb: 7 commits new 77c0dc27fb 355: onsuccess: #2089: 7: Success after binutils/gcc/linux/g [...] new 2816631969 356: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] new 5f7e13aef3 357: onsuccess: #2091: 7: Success after binutils/gcc/linux/g [...] new f3f91050fd 358: onsuccess: #2092: 7: Success after binutils/gcc/gdb: 10 [...] new fc44fc3534 359: onsuccess: #2093: 7: Success after binutils/gcc/linux/g [...] new 9995e71d3a 360: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] new ae65a5641f 361: onsuccess: #2095: 7: Success after gcc/linux: 15 commits new ec4ea9bc59 362: onsuccess: #2096: 7: Success after binutils/gcc/linux/g [...] new 20c0d2512a 363: onsuccess: #2097: 7: Success after binutils/gcc/gdb: 25 [...] new 0a0afea960 364: onsuccess: #2098: 7: Success after binutils/gdb: 4 commits new dbee8b8836 365: onsuccess: #2099: 7: Success after gcc/linux: 21 commits new 8935782765 366: onsuccess: #2100: 7: Success after binutils/gcc/glibc/g [...] new 5ef4e6f632 367: onsuccess: #2101: 7: Success after binutils/gcc/linux/g [...] new 5afe89a086 368: onsuccess: #2102: 7: Success after binutils/gcc/linux/g [...] new 447e1dbbdf 369: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] new 09fb8e103d 370: onsuccess: #2104: 7: Success after binutils/gcc/linux/g [...] new 7c0d5d34e3 371: onsuccess: #2105: 7: Success after binutils/gcc/gdb/qem [...] new 6731ade254 372: onsuccess: #2106: 7: Success after binutils/gcc/linux/g [...] new 4564c132d2 373: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] new 3ff5c51176 374: onsuccess: #2109: 7: Success after binutils/gcc/linux/g [...] new c810b8f7ea 375: onsuccess: #2110: 7: Success after binutils/gcc/linux/g [...] new ee14d9d336 376: onsuccess: #2111: 7: Success after binutils/gcc/linux/g [...] new ba98113620 377: onsuccess: #2112: 7: Success after binutils/gcc/gdb: 16 [...] new 40a365f7ba 378: onsuccess: #2113: 7: Success after binutils/gcc/linux/g [...] new 4a494e56d1 379: onsuccess: #2114: 7: Success after binutils/gcc/linux/g [...] new bd2dc618fa 380: onsuccess: #2115: 7: Success after binutils/gcc/linux/g [...] new 6abf9efc11 381: onsuccess: #2116: 7: Success after binutils/gcc/linux/g [...] new dab9dcc309 382: onsuccess: #2117: 7: Success after binutils/gcc/linux/g [...] new 182d1db775 383: onsuccess: #2118: 7: Success after binutils/gcc/glibc/g [...] new f22e2cc7b9 384: onsuccess: #2119: 7: Success after binutils/gcc/linux/g [...] new f45b0f4d6d 385: onsuccess: #2120: 7: Success after binutils/gcc/gdb/qem [...] new 0756b283f9 386: onsuccess: #2121: 7: Success after binutils/gcc/glibc/g [...] new 5fdf7bef37 387: onsuccess: #2122: 7: Success after gcc/linux/qemu: 117 commits new 40da30e06b 388: onsuccess: #2123: 7: Success after binutils/gcc/gdb: 3 commits new 85e3183e45 389: onsuccess: #2124: 7: Success after binutils/gcc/gdb: 5 commits new 723496fca0 390: onsuccess: #2125: 7: Success after binutils/gcc/linux/g [...] new 9e7ec3ba8e 391: onsuccess: #2126: 7: Success after binutils/gcc/linux/g [...] new 0c87099f2a 392: onsuccess: #2127: 7: Success after glibc-2.37.9000-17-g [...] new d9fdcad766 393: onsuccess: #2128: 7: Success after gcc/qemu: 42 commits new 8e5a5a9341 394: onsuccess: #2129: 7: Success after binutils/gcc/linux/g [...] new 504614877c 395: onsuccess: #2130: 7: Success after binutils/gcc/gdb/qem [...] new 5aeaabcab4 396: onsuccess: #2131: 7: Success after binutils/gcc/linux/g [...] new 914c061aea 397: onsuccess: #2132: 7: Success after gcc: 2 commits new 719264da23 398: onsuccess: #2133: 7: Success after binutils/gcc/glibc/g [...] new bb7e405c64 399: onsuccess: #2134: 7: Success after binutils/gcc/linux/g [...] new d49f660790 400: onsuccess: #2135: 7: Success after binutils/gcc/linux/g [...] new f628a78c9f 401: onsuccess: #2136: 7: Success after binutils/gcc/glibc/g [...] new 9a21d910d0 402: onsuccess: #2137: 7: Success after binutils/gcc/gdb: 22 [...] new 8961017820 403: onsuccess: #2138: 7: Success after binutils/gcc/gdb: 4 commits new 7f746348fc 404: onsuccess: #2139: 7: Success after basepoints/gcc-13-57 [...] new 9fad0f943c 405: onsuccess: #2141: 7: Success after binutils/gcc/linux/g [...] new e3514a7f62 406: onsuccess: #2142: 7: Success after binutils/gcc/gdb: 14 [...] new c160ef7913 407: onsuccess: #2143: 7: Success after binutils/gcc/linux/g [...] new 1ffff63a30 408: onsuccess: #2144: 7: Success after binutils/gcc/gdb/qem [...] new 0ad20556d8 409: onsuccess: #2145: 7: Success after binutils/gcc/linux/g [...] new adc665ec4f 410: onsuccess: #2146: 7: Success after binutils/gcc/linux/g [...] new f2e4eb03f0 411: onsuccess: #2147: 7: Success after binutils/gcc/gdb: 9 commits new f560408883 412: onsuccess: #2148: 7: Success after binutils/gcc/gdb: 6 commits new 43af5bbe09 413: onsuccess: #2149: 7: Success after binutils/gcc/linux/g [...] new 756ebe70f9 414: onsuccess: #2150: 7: Success after binutils/gcc/linux/g [...] new 7f5636ada3 415: onsuccess: #2151: 7: Success after binutils/gcc/gdb: 93 [...] new ff176f405a 416: onsuccess: #2152: 7: Success after gcc: 50 commits new ffee28ecc3 417: onsuccess: #2153: 7: Success after linux/glibc: 27 commits new 759b5661b3 418: onsuccess: #2154: 7: Success after binutils/gcc/linux/g [...] new 2e6e8988d4 419: onsuccess: #2155: 7: Success after binutils/gcc/gdb: 4 commits new 91efc809a8 420: onsuccess: #2156: 7: Success after binutils/gcc/gdb: 27 [...] new 4c1eecfd31 421: onsuccess: #2157: 7: Success after binutils/gcc/linux/g [...] new 5b44eee1fa 422: onsuccess: #2158: 7: Success after binutils/gcc/linux/g [...] new 423c1286de 423: onsuccess: #2159: 7: Success after binutils/gcc/gdb: 5 commits new eb83b4b1ed 424: onsuccess: #2160: 7: Success after binutils/gcc/glibc/g [...] new 0f25d9f08f 425: onsuccess: #2161: 7: Success after binutils/gcc/linux/g [...] new c1f86a6d20 426: onsuccess: #2162: 7: Success after binutils/gcc/gdb: 13 [...] new 4abf11d754 427: onsuccess: #2163: 7: Success after binutils/gdb: 4 commits new c9a4e02650 428: onsuccess: #2165: 7: Success after binutils/gcc/glibc/g [...] new 02e0421d47 429: onsuccess: #2166: 7: Success after binutils/gcc/linux/g [...] new 4bff6a42b7 430: onsuccess: #2167: 7: Success after binutils/gcc/gdb/qem [...] new ccccc24406 431: onsuccess: #2168: 7: Success after binutils/gcc/gdb/qem [...] new a12b6f1079 432: onsuccess: #2169: 7: Success after binutils/gcc/linux/g [...] new a2058dc334 433: onsuccess: #2170: 7: Success after binutils/gcc/linux/g [...] new a6525ce636 434: onsuccess: #2171: 7: Success after gcc/glibc: 5 commits new 2abece251b 435: onsuccess: #2172: 7: Success after binutils/gcc/glibc/g [...] new 4271f3fc24 436: onsuccess: #2173: 7: Success after binutils/gcc/linux/g [...] new 583e61c45f 437: onsuccess: #2174: 7: Success after gcc/linux: 9 commits new 42baa85366 438: onsuccess: #2175: 7: Success after gcc: 7 commits new 58a1b25c97 439: onsuccess: #2176: 7: Success after linux: 11 commits new eec60b0081 440: onsuccess: #2177: 7: Success after binutils/gcc/gdb: 6 commits new aa7b88cff2 441: onsuccess: #2178: 7: Success after binutils/linux/gdb: [...] new f24ea80077 442: onsuccess: #2179: 7: Success after binutils/gcc/linux/g [...] new 36bb603a4c 443: onsuccess: #2180: 7: Success after binutils/gdb: 2 commits new f44bf6bdf2 444: onsuccess: #2181: 7: Success after binutils/gcc/glibc/g [...] new 71e3876096 445: onsuccess: #2182: 7: Success after binutils/gcc/glibc/g [...] new da1fc3e155 446: onsuccess: #2183: 7: Success after binutils/gcc/linux/g [...] new 8c2e82b23f 447: onsuccess: #2184: 7: Success after binutils/gcc/linux/g [...] new 80f0a85914 448: onsuccess: #2185: 7: Success after binutils/gcc/gdb/qem [...] new 8a9f67d4aa 449: onsuccess: #2186: 7: Success after binutils/gcc/linux/g [...] new d50a084813 450: onsuccess: #2188: 7: Success after binutils/gcc/linux/g [...] new e8d3382b24 451: onsuccess: #2189: 7: Success after binutils/gcc/gdb: 11 [...] new 3ab1219259 452: onsuccess: #2190: 7: Success after binutils/gcc/linux/g [...] new 28776fd8d7 453: onsuccess: #2191: 7: Success after binutils/gcc/linux/g [...] new f34e5037d5 454: onsuccess: #2192: 7: Success after binutils/linux/glibc [...] new a12df02cb1 455: onsuccess: #2193: 7: Success after binutils/gcc/gdb: 13 [...] 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 (7668d7c255) \ 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 1768 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2780 bytes 04-build_abe-binutils/console.log.xz | Bin 30612 -> 30908 bytes 05-build_abe-stage1/console.log.xz | Bin 88752 -> 88724 bytes 07-build_abe-linux/console.log.xz | Bin 11876 -> 11868 bytes 08-build_abe-glibc/console.log.xz | Bin 236164 -> 235944 bytes 09-build_abe-stage2/console.log.xz | Bin 224664 -> 225624 bytes 10-build_abe-gdb/console.log.xz | Bin 38492 -> 38568 bytes 11-build_abe-qemu/console.log.xz | Bin 31048 -> 31388 bytes 12-check_regression/console.log.xz | Bin 4060 -> 3636 bytes 13-update_baseline/console.log | 36 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +++++++++++++++---------------- 19 files changed, 41 insertions(+), 41 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[binutils-gdb] branch master updated (0373a76af6b -> e98a23bfb30)

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 binutils-gdb. from 0373a76af6b gdb: LoongArch: Support reg aliases in info reg command new e98a23bfb30 Remove 'eval' from gdb_breakpoint 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: gdb/testsuite/lib/gdb.exp | 7 +------ 1 file changed, 1 insertion(+), 6 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-arm updated (66bc24f2ce -> 265804ee10)

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 66bc24f2ce 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] discards 6b9a21bef5 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards 8965826d93 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] discards 94c12ed64e 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] discards a18b1f520b 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] discards 8126651d08 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards e1c2c14ad5 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] discards 596cab1a5a 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] discards 34a736491d 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] discards ca01771be0 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards 4471d6a8d5 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] discards f5d4bf9dd2 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards c9074e6797 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards 733ed54456 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards 621440e714 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards 025dcc0e9c 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards ad7d905c9d 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards 43d33b4f94 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards 84e91941ae 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards f8a1577dbd 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards 53e9df4a8d 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards 2f86f74688 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards a8ffcbcddd 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards c23cdea5cf 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards 4dec7cb700 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards 5471883b84 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards c771ce75aa 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 21182c086b 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards 4c58471408 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 121cb6cf54 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 501c8cd5ce 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 90c68d88fc 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards 436566fa8c 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 4d1305d65d 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 77d22a0bf3 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 9cd3477e24 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 3bc5cc9e4c 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 00eed5debc 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 15f6fd852a 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 4c22f172e9 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards e73352055d 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards dbfa3c7a23 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 9806f4c56e 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards f162ec7e1a 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 05ecc8f655 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 360cb7b5f5 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 6370e725f7 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 62ff706443 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 15c34ef365 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 52a1b03f53 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards e823572e65 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards b0e06aca14 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 180dc22404 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 58294db893 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards e05ff788e2 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards bc26c76370 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 5f606b064b 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 2ab513ad13 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 49a333b92d 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 81116e3b66 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 38df95b138 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 4b2e786fd5 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 760b342b96 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 2428a51974 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 0e9f832076 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards f5d7ea533a 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 39804a4d1f 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards f576323590 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 3e4b298d3b 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 90f5dc3246 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 617f18a75c 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 30911dcc44 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 752d081105 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 4e78c87ae0 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 3c202e03ef 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards a745ffb7d3 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 3d430ac7ea 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 33cc53a78c 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards c732f35229 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards c303e127e4 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 3f59b3373e 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 669279f898 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 866d11de6e 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 384ebaa4fe 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards d08f526b36 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards a3c9f16474 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 1edb7b3e2b 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 4a99945359 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards d1f9c6aaf2 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 7414ab49ed 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 632b2651f0 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards ba15e8dc2d 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards e3d25a2ece 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards fc27cef76a 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 82f869be7a 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards eff52de47e 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 417c4622a2 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 824d6e94d6 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 24716fab3f 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards bad8bed109 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 9f6a94db38 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new b41003c774 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new d4e8ffeca0 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 141b2c9d1e 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 0e992d772b 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 26d0306a6b 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 1cda6f5c88 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new f816d2f3f5 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 4662f1476c 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 57219b7d28 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 6c710030e2 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 7320b92e7e 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 351de1eaf2 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new aae8e90a06 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 77a2e9a477 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 72f5d25046 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 7f8c499412 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new fdef62eef2 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 567b9ef41c 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 45331d7924 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 04d68fd2d7 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 1071c77dd5 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new cee424ba1e 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new e4c7fceb84 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 4500fc38ae 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new b452a8d1c8 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 0f51e53dc0 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 91ef8a6719 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new e3a2558ce7 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 684d15a220 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new aad311892d 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 99d237dbf1 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new af4bae1c41 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 8d0840108d 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 7a0d2f7201 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 9a34ec30bb 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 8847744443 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new f70d9fb946 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new d8300de04f 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 1b070fa299 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new a10985efcc 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 8a009160cb 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 48e64bf4a7 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 6eaf589eb5 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 706a1275f2 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 7af02b14a5 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new a7ca3fda21 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new c054fd0b92 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 5473ffd8ce 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 3c51c33ee3 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 906c35dbc1 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new af3b9bb18e 387: onsuccess: #2208: 1: Success after gcc: 2 commits new b0f34d2350 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 5b3a6de712 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 9c130ccd38 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new bb38fe6ca6 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 5465edfda0 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new b35c222151 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new c68aad6d9f 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new d4ed487eb1 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 4bc3cd1c42 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 60ade25e9f 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 93b6c889f1 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 713bc038f6 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 5946e892e0 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new c43adfd03a 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 1541b8139f 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 0ffb624fbf 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new f96ee7acbb 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 9172b354c6 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new d81532a233 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 1c35b72cd4 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new e454f8c302 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 5e34c0652d 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 692fd774f8 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 617ae82095 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 067258d309 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new 3799e9210b 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new 767a752677 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new dc31f8568a 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new cdeead40d5 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new a80a344ddd 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new 66a19c19b8 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new 3cd2574b63 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new aa57ca7c58 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new 96adb840b4 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new 83ccfba2b5 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new 0794a523fe 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new 90bbdfad0c 424: onsuccess: #2248: 1: Success after gcc: 6 commits new e37d77a1b7 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new 25becf49ca 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new 01f9440830 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] new 0c2a1cb3dd 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new 9168ede683 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] new bf52dd6536 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] new 138d358c67 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] new 8c7d33456e 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new e45de941ae 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] new 50561f45bc 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] new c2807bc13c 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] new be03207e18 436: onsuccess: #2260: 1: Success after gcc: 7 commits new f87a3c357e 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] new 265804ee10 438: onsuccess: #2263: 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 (66bc24f2ce) \ 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 1796 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31060 -> 30772 bytes 04-build_abe-stage1/console.log.xz | Bin 88948 -> 89040 bytes 06-build_abe-linux/console.log.xz | Bin 12980 -> 11844 bytes 07-build_abe-glibc/console.log.xz | Bin 235712 -> 235232 bytes 08-build_abe-stage2/console.log.xz | Bin 225112 -> 225364 bytes 09-build_abe-gdb/console.log.xz | Bin 38828 -> 38756 bytes 10-build_abe-qemu/console.log.xz | Bin 31256 -> 31660 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3792 -> 3796 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2716 -> 2704 bytes 13-check_regression/console.log.xz | Bin 14480 -> 6640 bytes 13-check_regression/results.compare | 65 +- 13-check_regression/results.compare2 | 2280 +-------------------------------- 14-update_baseline/console.log | 66 +- 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 | 44 +- sumfiles/g++.log.xz | Bin 2640344 -> 2629636 bytes sumfiles/g++.sum | 8 +- sumfiles/gcc.log.xz | Bin 2225264 -> 2218864 bytes sumfiles/gcc.sum | 11 +- sumfiles/gfortran.log.xz | Bin 898144 -> 888304 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2284 -> 2284 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217032 -> 216784 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2688 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 436636 -> 434704 bytes sumfiles/libstdc++.sum | 18 +- 39 files changed, 122 insertions(+), 2396 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_kernel/llvm-master-aarch64-lts-allyesconfig updated (4e112c1bd3 -> a51daf0c2a)

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-allyesconfig in repository toolchain/ci/base-artifacts. from 4e112c1bd3 65: onsuccess: #556: 21422: Success after binutils/llvm/qemu [...] new a51daf0c2a 66: onsuccess: #557: 21422: Success after binutils/llvm/linu [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1780 -> 1992 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 31260 -> 30892 bytes 04-build_kernel_llvm/console.log.xz | Bin 64360 -> 64636 bytes 05-build_abe-qemu/console.log.xz | Bin 32340 -> 31560 bytes 06-build_linux/console.log.xz | Bin 3696 -> 3720 bytes 08-check_regression/console.log.xz | Bin 3944 -> 4492 bytes 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 16 files changed, 24 insertions(+), 24 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-aarch64 updated (ed2d8dd461 -> 681ab298ea)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards ed2d8dd461 442: onsuccess: #2146: 7: Success after binutils/gcc/linux/g [...] discards da66f65751 441: onsuccess: #2145: 7: Success after binutils/gcc/linux/g [...] discards 2feef7300f 440: onsuccess: #2144: 7: Success after binutils/gcc/glibc/g [...] discards b2d30631bd 439: onsuccess: #2143: 7: Success after gcc: 7 commits discards a000ac57fe 438: onsuccess: #2142: 7: Success after binutils/linux/gdb: [...] discards cc7f785186 437: onsuccess: #2141: 7: Success after binutils/gcc/linux/g [...] discards 8adc3dcb1f 436: onsuccess: #2140: 7: Success after binutils/gcc/linux/g [...] discards 285ef2f26d 435: onsuccess: #2139: 7: Success after binutils/gcc/gdb/qem [...] discards fdba516e21 434: onsuccess: #2138: 7: Success after binutils/gcc/linux/g [...] discards 5014877b34 433: onsuccess: #2137: 7: Success after binutils/gcc/linux/g [...] discards 67f87658e3 432: onsuccess: #2136: 7: Success after binutils/gcc/glibc/g [...] discards 0731d8b802 431: onsuccess: #2135: 7: Success after binutils/gcc/glibc/g [...] discards b1c2615b09 430: onsuccess: #2134: 7: Success after binutils/gdb: 2 commits discards 599caf259d 429: onsuccess: #2133: 7: Success after binutils/gcc/linux/g [...] discards 3141c792e9 428: onsuccess: #2132: 7: Success after binutils/linux/gdb: [...] discards 32a79065a7 427: onsuccess: #2131: 7: Success after binutils/gcc/linux/g [...] discards a4e982a737 426: onsuccess: #2130: 7: Success after gcc: 7 commits discards fd403adb94 425: onsuccess: #2129: 7: Success after gcc/linux: 9 commits discards 0ed5d525da 424: onsuccess: #2128: 7: Success after binutils/gcc/linux/g [...] discards f5e7c053bf 423: onsuccess: #2127: 7: Success after binutils/gcc/glibc/g [...] discards e2c9dc47b0 422: onsuccess: #2126: 7: Success after gcc/glibc: 5 commits discards 36ab93c5b1 421: onsuccess: #2125: 7: Success after binutils/gcc/linux/g [...] discards e77707a69a 420: onsuccess: #2124: 7: Success after binutils/gcc/linux/g [...] discards bfe9c595b0 419: onsuccess: #2123: 7: Success after binutils/gcc/gdb/qem [...] discards c176660d33 418: onsuccess: #2122: 7: Success after binutils/gcc/gdb/qem [...] discards c60b1836ef 417: onsuccess: #2121: 7: Success after binutils/gcc/linux/g [...] discards da903b1d26 416: onsuccess: #2120: 7: Success after binutils/gcc/glibc/g [...] discards c42c6b4ed7 415: onsuccess: #2119: 7: Success after gcc: 37 commits discards abba361669 414: onsuccess: #2118: 7: Success after binutils: 5 commits discards 0ed6516d5c 413: onsuccess: #2116: 7: Success after binutils/gdb: 4 commits discards 768e458b8c 412: onsuccess: #2115: 7: Success after binutils/gcc/glibc/g [...] discards 4ad426b58d 411: onsuccess: #2114: 7: Success after binutils/gcc/linux/g [...] discards fa870d07c6 410: onsuccess: #2113: 7: Success after binutils/gcc/glibc/g [...] discards c250027db1 409: onsuccess: #2112: 7: Success after gcc: 3 commits discards e78cba8ccf 408: onsuccess: #2111: 7: Success after binutils/gcc/linux/g [...] discards 87a6c28bb2 407: onsuccess: #2110: 7: Success after binutils/gcc/glibc/g [...] discards b9d5360b69 406: onsuccess: #2109: 7: Success after binutils/gcc/gdb: 26 [...] discards fd9497619f 405: onsuccess: #2108: 7: Success after binutils/gcc/gdb: 3 commits discards 8c45fa6a75 404: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] discards fadef2e5a6 403: onsuccess: #2106: 7: Success after glibc: 12 commits discards d6d442f4ec 402: onsuccess: #2105: 7: Success after binutils/gcc/gdb: 58 [...] discards 93322049f3 401: onsuccess: #2104: 7: Success after binutils/gcc/gdb: 85 [...] discards bf58d812d8 400: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] discards e8b225d7c0 399: onsuccess: #2102: 7: Success after binutils/gcc/gdb: 9 commits discards c89dea30f1 398: onsuccess: #2101: 7: Success after binutils/gcc/gdb: 6 commits discards 76bd74836f 397: onsuccess: #2100: 7: Success after binutils/gcc/gdb: 9 commits discards 606872eb3e 396: onsuccess: #2099: 7: Success after binutils/gcc/linux/g [...] discards 0724e3314b 395: onsuccess: #2098: 7: Success after binutils/gcc/linux/g [...] discards 385d3e22d2 394: onsuccess: #2097: 7: Success after binutils/gcc/gdb/qem [...] discards ddca84b9ca 393: onsuccess: #2096: 7: Success after gcc/linux: 45 commits discards bee42d7522 392: onsuccess: #2095: 7: Success after binutils/gcc/linux/g [...] discards 05f797fbb1 391: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] discards b93018b31f 390: onsuccess: #2092: 7: Success after basepoints/gcc-13-57 [...] discards d13f943ac3 389: onsuccess: #2091: 7: Success after binutils/gcc/gdb: 12 [...] discards 2d056bf37f 388: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] discards b536bcf881 387: onsuccess: #2089: 7: Success after binutils/gcc/gdb/qem [...] discards 855ab189fa 386: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] discards cb327fd985 385: onsuccess: #2086: 7: Success after binutils/gcc/linux/g [...] discards ebbc202395 384: onsuccess: #2085: 7: Success after binutils/gcc/glibc/g [...] discards 143b00f018 383: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits discards fb95105181 382: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] discards a03f7b14df 381: onsuccess: #2082: 7: Success after binutils/gcc/gdb/qem [...] discards 299e57cc85 380: onsuccess: #2081: 7: Success after basepoints/gcc-13-57 [...] discards 2908277e92 379: onsuccess: #2080: 7: Success after binutils/gcc/linux/g [...] discards 33035e322f 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 commits discards 5f2551f745 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] discards 045844fbc9 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] discards 272d65f269 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] discards ac627188c3 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] discards b602db154a 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits discards d8d3c8c843 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits discards 1523f932b2 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] discards 1af6a3e8ab 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] discards b9a702ce19 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] discards 0278c02d98 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards 3e0d8b925c 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] discards 365c1fb9ca 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] discards d42cb3d30e 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] discards d5bc73ba3b 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards 181f9d9980 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] discards 3d980758ef 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] discards 9c9ac46a87 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards 6a32d52cea 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards fcd1096f32 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] discards 9d01f6db26 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] discards 7e5433de94 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards fcb570e735 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] discards 847dc48131 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] discards 6dae0408f7 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] discards c9279bce88 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] discards 2abb9aec23 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] discards d0ac201cc3 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] discards 37b7b7644c 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] discards 97e00b35ea 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] discards a2c1d05ef1 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits discards 5dd7ca20fd 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] discards d233a6c370 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] discards 903a50c226 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] discards 3902002310 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards cbff3c3896 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards ee05f16202 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits new 82a6124d77 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits new 129ed1245d 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new 3028fde6a8 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new 8c6bc29aae 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] new 529c05b694 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] new 22ff0064be 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] new b5c8efcfe1 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits new c834171f71 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] new b12cfe697e 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] new a06501302e 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] new 53f51a8000 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] new 14e16f620b 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] new ef17091884 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] new 3e1009c47f 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] new 2e1ba650c7 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] new cd10c93b13 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new de1fe06c2a 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] new 933ea07a19 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] new 4f8a829a21 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new 880c52d799 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new 32e2fef482 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] new 1d45790e9e 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] new 13fb96c3bf 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new 72986dc9f0 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] new d730b459e3 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] new fa62d35ff9 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] new e36a490090 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new 0ba7200f3d 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] new 15633e377b 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] new 91a9b2ae1b 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] new 5ef92cb0af 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits new 18fedd4a55 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits new 773fb28f22 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] new 50cd05a7ce 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] new b67bb46b00 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] new c14d2c775f 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] new 1c53d8e5e9 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 commits new 132b5bef79 379: onsuccess: #2080: 7: Success after binutils/gcc/linux/g [...] new 2ab826e84b 380: onsuccess: #2081: 7: Success after basepoints/gcc-13-57 [...] new e856176d82 381: onsuccess: #2082: 7: Success after binutils/gcc/gdb/qem [...] new 4066380637 382: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] new 9031002e43 383: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits new 170d012a8c 384: onsuccess: #2085: 7: Success after binutils/gcc/glibc/g [...] new 6118bc6ea6 385: onsuccess: #2086: 7: Success after binutils/gcc/linux/g [...] new d3fad3a8d8 386: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] new b7962086a5 387: onsuccess: #2089: 7: Success after binutils/gcc/gdb/qem [...] new 90793a3303 388: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] new 5a512c62cf 389: onsuccess: #2091: 7: Success after binutils/gcc/gdb: 12 [...] new 96212e8aef 390: onsuccess: #2092: 7: Success after basepoints/gcc-13-57 [...] new dff5ee80f6 391: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] new e4a19d39f4 392: onsuccess: #2095: 7: Success after binutils/gcc/linux/g [...] new 17bb549adb 393: onsuccess: #2096: 7: Success after gcc/linux: 45 commits new ede05088f0 394: onsuccess: #2097: 7: Success after binutils/gcc/gdb/qem [...] new 92a410b02b 395: onsuccess: #2098: 7: Success after binutils/gcc/linux/g [...] new 74a2fa790f 396: onsuccess: #2099: 7: Success after binutils/gcc/linux/g [...] new 5e844212a8 397: onsuccess: #2100: 7: Success after binutils/gcc/gdb: 9 commits new 35a117494a 398: onsuccess: #2101: 7: Success after binutils/gcc/gdb: 6 commits new 32e6943331 399: onsuccess: #2102: 7: Success after binutils/gcc/gdb: 9 commits new 16a0e245dd 400: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] new 341593ec4d 401: onsuccess: #2104: 7: Success after binutils/gcc/gdb: 85 [...] new dce24dbe89 402: onsuccess: #2105: 7: Success after binutils/gcc/gdb: 58 [...] new 09a3919cad 403: onsuccess: #2106: 7: Success after glibc: 12 commits new 19a9ee3bd0 404: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] new c9d580917e 405: onsuccess: #2108: 7: Success after binutils/gcc/gdb: 3 commits new ef0c804a0e 406: onsuccess: #2109: 7: Success after binutils/gcc/gdb: 26 [...] new 19c8ebcac5 407: onsuccess: #2110: 7: Success after binutils/gcc/glibc/g [...] new 4bdb1d9891 408: onsuccess: #2111: 7: Success after binutils/gcc/linux/g [...] new 59c4539467 409: onsuccess: #2112: 7: Success after gcc: 3 commits new 7fde5e0148 410: onsuccess: #2113: 7: Success after binutils/gcc/glibc/g [...] new a05c6bcad1 411: onsuccess: #2114: 7: Success after binutils/gcc/linux/g [...] new 69a8dbfd9e 412: onsuccess: #2115: 7: Success after binutils/gcc/glibc/g [...] new 1cbf391dd6 413: onsuccess: #2116: 7: Success after binutils/gdb: 4 commits new fbaa4d7842 414: onsuccess: #2118: 7: Success after binutils: 5 commits new a16db5d4a1 415: onsuccess: #2119: 7: Success after gcc: 37 commits new 583430e428 416: onsuccess: #2120: 7: Success after binutils/gcc/glibc/g [...] new fd257053b7 417: onsuccess: #2121: 7: Success after binutils/gcc/linux/g [...] new c20b8aa8b8 418: onsuccess: #2122: 7: Success after binutils/gcc/gdb/qem [...] new 4edcf6b94b 419: onsuccess: #2123: 7: Success after binutils/gcc/gdb/qem [...] new 85a5b406b3 420: onsuccess: #2124: 7: Success after binutils/gcc/linux/g [...] new ece863689c 421: onsuccess: #2125: 7: Success after binutils/gcc/linux/g [...] new 97abb6bf37 422: onsuccess: #2126: 7: Success after gcc/glibc: 5 commits new 4539fa37a2 423: onsuccess: #2127: 7: Success after binutils/gcc/glibc/g [...] new b65f7b962a 424: onsuccess: #2128: 7: Success after binutils/gcc/linux/g [...] new d1be20f6e0 425: onsuccess: #2129: 7: Success after gcc/linux: 9 commits new dbda5a29f0 426: onsuccess: #2130: 7: Success after gcc: 7 commits new 0ba4fbf35e 427: onsuccess: #2131: 7: Success after binutils/gcc/linux/g [...] new 4c0546374e 428: onsuccess: #2132: 7: Success after binutils/linux/gdb: [...] new 60edc27bb3 429: onsuccess: #2133: 7: Success after binutils/gcc/linux/g [...] new bf42213bd0 430: onsuccess: #2134: 7: Success after binutils/gdb: 2 commits new c537e491e2 431: onsuccess: #2135: 7: Success after binutils/gcc/glibc/g [...] new 22f8416d5f 432: onsuccess: #2136: 7: Success after binutils/gcc/glibc/g [...] new d44eba8026 433: onsuccess: #2137: 7: Success after binutils/gcc/linux/g [...] new 242c91008e 434: onsuccess: #2138: 7: Success after binutils/gcc/linux/g [...] new e9bcf5fe39 435: onsuccess: #2139: 7: Success after binutils/gcc/gdb/qem [...] new 4cdebe7cd4 436: onsuccess: #2140: 7: Success after binutils/gcc/linux/g [...] new b683b17adb 437: onsuccess: #2141: 7: Success after binutils/gcc/linux/g [...] new cc65b12cb4 438: onsuccess: #2142: 7: Success after binutils/linux/gdb: [...] new 420782a98c 439: onsuccess: #2143: 7: Success after gcc: 7 commits new ee5e19a36e 440: onsuccess: #2144: 7: Success after binutils/gcc/glibc/g [...] new 7b8d04faa7 441: onsuccess: #2145: 7: Success after binutils/gcc/linux/g [...] new a61beae33e 442: onsuccess: #2146: 7: Success after binutils/gcc/linux/g [...] new 681ab298ea 443: onsuccess: #2147: 7: Success after binutils/gcc/gdb: 12 [...] 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 (ed2d8dd461) \ 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 1708 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2764 bytes 04-build_abe-binutils/console.log.xz | Bin 31012 -> 31076 bytes 05-build_abe-stage1/console.log.xz | Bin 70696 -> 70608 bytes 07-build_abe-linux/console.log.xz | Bin 11896 -> 11844 bytes 08-build_abe-glibc/console.log.xz | Bin 244360 -> 244020 bytes 09-build_abe-stage2/console.log.xz | Bin 202124 -> 202368 bytes 10-build_abe-gdb/console.log.xz | Bin 38680 -> 38828 bytes 11-build_abe-qemu/console.log.xz | Bin 31308 -> 31464 bytes 12-check_regression/console.log.xz | Bin 4252 -> 3584 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +++++++++--------- 19 files changed, 55 insertions(+), 55 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[gcc] branch master updated (31cc5821223 -> af46073dbe8)

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 31cc5821223 tree-optimization/108888 - call if-conversion new af46073dbe8 Fix memory leak in if-conversion The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/tree-if-conv.cc | 9 +++++---- 1 file changed, 5 insertions(+), 4 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_kernel/llvm-master-aarch64-next-allmodconfig updated (173e9292d5 -> 5d6a0659c8)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-allmodconfig in repository toolchain/ci/base-artifacts. from 173e9292d5 79: onsuccess: #632: all: Success after binutils/llvm/qemu: [...] new 5d6a0659c8 80: force: #634: all: Success after linux: 728 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1768 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31280 -> 31464 bytes 04-build_kernel_llvm/console.log.xz | Bin 65952 -> 64828 bytes 05-build_abe-qemu/console.log.xz | Bin 32192 -> 32292 bytes 06-build_linux/console.log.xz | Bin 3196 -> 3040 bytes 08-check_regression/console.log.xz | Bin 3904 -> 2868 bytes 08-check_regression/mail-body.txt | 2 +- 09-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 24 +++++++++++------------- results | 2 +- 16 files changed, 20 insertions(+), 22 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[binutils-gdb] branch master updated (d273049e140 -> 0373a76af6b)

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 binutils-gdb. from d273049e140 bfd: xtensa: fix __stop_SECTION literal drop new 9d7c73af4bf gdb: LoongArch: Modify the result of the info reg command new 0373a76af6b gdb: LoongArch: Support reg aliases in info reg command 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: gdb/loongarch-tdep.c | 60 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 60 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[gcc] branch devel/omp/gcc-12 updated (55a18d47442 -> 3ad47717bf7)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch devel/omp/gcc-12 in repository gcc. from 55a18d47442 Fortran/OpenMP: Fix mapping of array descriptors and deferr [...] new 3ad47717bf7 libgomp: no need to attach USM pointers 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: libgomp/ChangeLog.omp | 5 +++++ libgomp/target.c | 5 +++++ libgomp/testsuite/libgomp.fortran/usm-3.f90 | 33 +++++++++++++++++++++++++++++ 3 files changed, 43 insertions(+) create mode 100644 libgomp/testsuite/libgomp.fortran/usm-3.f90 -- 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