Tcwg-commits January 2023

tcwg-commits@lists.linaro.org

5 participants
4127 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/llvm-arm-master-O2_LTO created (now f0b73e5f8a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/llvm-arm-master-O2_LTO in repository toolchain/ci/base-artifacts. at f0b73e5f8a 50: onsuccess: #1: 1: [TCWG CI] No change after binutils/gcc [...] This branch includes the following new commits: new f0b73e5f8a 50: onsuccess: #1: 1: [TCWG CI] No change after binutils/gcc [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[gcc] branch master updated (4e0b504f26f -> 5b918b20d18)

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 4e0b504f26f tree-optimization/106293 - missed DSE with virtual LC PHI new 5b918b20d18 [PATCH, Modula2] PR-108142 Many empty directories created i [...] 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/m2/Make-lang.in | 148 +++++++++++++++++++++++----------------------- gcc/m2/Make-maintainer.in | 122 +++++++++++++++++++++++++++++++------- gcc/m2/config-lang.in | 29 --------- 3 files changed, 174 insertions(+), 125 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (af1a875236 -> e0170e96cd)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards af1a875236 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 51c1f81b15 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards c13e19695f 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 8e8b06080c 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 47647e4ed8 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 8c58a92436 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards bbf4b68801 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 809c5e9a07 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 752911b509 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards a7c11c6ed5 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards a50aa760fe 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards bf0af3d6b0 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 1ff8daea1c 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards a8e1e45d13 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 9ea88e469a 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 9e71720586 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 2e9d20684f 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards d158e8df34 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards aafa0f4f6a 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 744cd33508 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 00d82a2e4d 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 125d98785e 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 0338c434c0 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 5b550a5bcd 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 861d201a23 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 80073e4a4e 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards f80d6b7429 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards d4771978ec 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 6ad903976a 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 951f64b4ae 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 24753cbed6 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards d7c56cdd81 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 476cfbf07b 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards dc3fb2ab78 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 33f831a4a4 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 6e7b326a94 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 1039c686a0 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 15bb63134e 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 3c0ad7c9f4 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 771c3d50a9 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 0caeda47c2 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards afd2c9b6e5 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards fa7a72d0a6 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards be32bbc2f0 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 3b6e2cceb3 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 8165f83e61 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 6c57fcb648 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards d7ad8a1d9e 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards c38632b436 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 149744ca23 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 3257957ebc 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 43e5211921 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 335e3e3faa 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 77594aadc3 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 2eb364b450 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 492095e398 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 3c0f2ce79d 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 0198cd97c3 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 8dcb92dbd7 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards c065fa83e3 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards d136dfb54d 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 68f9b5bf12 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 48c2ad6147 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards b741f98923 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards 915cbdb54b 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards 2fe835a4ba 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 281882c045 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards 5cbff4b11d 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 18261da0bf 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards 2418777f6c 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards 06dcd50f5c 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards dee92e82a9 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 17044d4e23 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards a7ab120ea1 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards d81240649a 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards 82a0bd94ac 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards e23dbec789 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards f4bfc91994 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 5b880aa051 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards c5d3a46c10 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards 5b1b7bb053 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards eb4d57e3c2 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards 163e80c9aa 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 5128482de5 235: onsuccess: #2483: 1: Success after linux: 108 commits discards 7ee9e14722 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards f5b5635605 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards 7880cd5e5d 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards 6bec1e1b0e 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards f05d9367da 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards 56c680b7fe 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards 841b7c5572 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards 73fe2b20b5 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards 19b3dc2795 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] discards fb0794df88 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards ee2f5b33be 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] discards 2462803077 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] discards adada62d3b 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] discards 359eb85615 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards eaf0c5c683 220: onsuccess: #2465: 1: Success after linux: 572 commits discards 30d3ef79dc 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards 766de876df 218: onsuccess: #2461: 1: Success after linux: 916 commits new 543abcacfc 218: onsuccess: #2461: 1: Success after linux: 916 commits new 9c2a53fb4c 219: onsuccess: #2463: 1: Success after binutils: 3 commits new 15aff42065 220: onsuccess: #2465: 1: Success after linux: 572 commits new c6e30b27a7 221: onsuccess: #2467: 1: Success after binutils: 3 commits new 198297d958 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] new edf3a54c1a 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] new 574fabe8ff 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] new a3a8b04e89 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new 88f3304b3a 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] new 981f7ffb79 227: onsuccess: #2474: 1: Success after gcc: 2 commits new c010cffeb7 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new 013d1665d3 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new 8530f1bede 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new 9ed88d0db7 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new c2400cb40c 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new 394216dfc6 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new 823e6aa001 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new a873cd6fbe 235: onsuccess: #2483: 1: Success after linux: 108 commits new 0868bb2058 236: onsuccess: #2484: 1: Success after gcc: 2 commits new d54166c5ed 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new e4a56a294b 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new a1bb928fd1 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new 34883abeef 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 66b4ce9860 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 737409c507 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new bf2cd98de2 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new 9e7eddc48c 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new 02eec532fa 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 3be15f4539 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new 471a753fd9 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new a7696a9c2d 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 7d20209c8c 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new bdb0342264 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 6751edf019 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 0ea0d5abd6 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new 7c59ec406e 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new dbf09d9881 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 0a51f879c1 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new da0e3a7468 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new ad09c106f5 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new ac4e80df9e 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new d47afe1c42 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new d6cfa955f7 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 4f8c885529 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new f7a00b4afc 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new b34f3ec0d7 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 9fcf230e68 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 7d9f8d100d 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 30d5c56797 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 597d8ed7ad 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new baabea02c5 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 8040199828 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 4a96d31f94 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 4d6020e621 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new c67128322b 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new bdfd59cc5c 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 08be78bf88 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 3ceb6ade38 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 6b4b6910b1 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 7b2467367d 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 6086cac353 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new e7c5123089 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new d6d4b47395 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new d219b0879a 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new ede1afc48d 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 62e56ff525 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 83b5b3716a 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new be40b987cd 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 45ceb11048 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new c5a18cf55f 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 60740a212c 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 75d2ea6ffa 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new ecfe85eb6c 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 85d57fb2fc 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 2ebb9797f4 292: onsuccess: #2541: 1: Success after binutils: 13 commits new ba8e867e16 293: onsuccess: #2542: 1: Success after gcc: 5 commits new ea8df6d29f 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 22ee4087cf 295: onsuccess: #2545: 1: Success after linux: 10 commits new 1f190ce0f7 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new abcbd798bd 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 50fa715081 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new ef357d2679 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new fb3d86d8b9 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 17295f7178 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new beac10c6c1 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 1c772e68e6 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 75ff9650ad 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 144e6ad8e4 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 983bb3f09d 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new bda2f77fd3 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new cc3d319658 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new fd45233ee7 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 51bc1df023 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new ae1ae8ed80 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 81303f4e12 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 2118ac187b 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 305ade2d1c 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 103a470705 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 1242e43237 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 42d4b97ebd 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new f7720aa5f1 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new e0170e96cd 319: onsuccess: #2569: 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 (af1a875236) \ 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 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 32128 -> 32224 bytes 04-build_abe-stage1/console.log.xz | Bin 72984 -> 73156 bytes 06-build_abe-linux/console.log.xz | Bin 8752 -> 8620 bytes 07-build_abe-glibc/console.log.xz | Bin 244460 -> 244228 bytes 08-build_abe-stage2/console.log.xz | Bin 204184 -> 204192 bytes 09-build_abe-gdb/console.log.xz | Bin 39684 -> 39628 bytes 10-build_abe-qemu/console.log.xz | Bin 31504 -> 31540 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2628 -> 2912 bytes 13-check_regression/console.log.xz | Bin 6036 -> 7156 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 26 +- 13-check_regression/mail-body.txt | 127 +- 13-check_regression/results.compare | 64 +- 13-check_regression/results.compare2 | 81 +- 13-check_regression/results.regressions | 64 +- 14-update_baseline/console.log | 40 +- 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 | 129 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 64 +- sumfiles/g++.log.xz | Bin 3407620 -> 3420976 bytes sumfiles/g++.sum | 26 +- sumfiles/gcc.log.xz | Bin 3033448 -> 3039544 bytes sumfiles/gcc.sum | 3951 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1038640 -> 1039508 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214780 -> 214788 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2700 -> 2700 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 431500 -> 434264 bytes sumfiles/libstdc++.sum | 6 +- 43 files changed, 2272 insertions(+), 2368 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled_lto_lean updated (c12d8eb42d -> f34f6bda98)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled_lto_lean in repository toolchain/ci/base-artifacts. discards c12d8eb42d 137: onsuccess: #540: 2: Success after binutils/gcc: 6 commits discards ed337a07ad 136: onsuccess: #539: 2: Success after binutils/gcc: 82 commits discards 2bd4652ad8 135: onsuccess: #537: 2: Success after binutils/gcc: 34 commits discards 162f13d7a4 134: onsuccess: #536: 2: Success after binutils/gcc: 61 commits discards e5ca0ad62c 133: onsuccess: #535: 2: Success after binutils/gcc: 20 commits discards a7c2389f65 132: onsuccess: #534: 2: Success after binutils/gcc: 18 commits discards 50b09be8c6 131: onsuccess: #533: 2: Success after binutils/gcc: 29 commits discards b99ad219ec 130: onsuccess: #531: 2: Success after binutils/gcc: 20 commits discards f3d8693cf5 129: onsuccess: #530: 2: Success after binutils/gcc: 9 commits discards 2c36a58f10 128: onsuccess: #529: 2: Success after binutils/gcc: 29 commits discards e5c1757854 127: onsuccess: #528: 2: Success after binutils/gcc: 7 commits discards ee8d36155e 126: onsuccess: #527: 2: Success after binutils/gcc: 24 commits discards b23f9220c8 125: onsuccess: #526: 2: Success after binutils/gcc: 90 commits discards 51945a4cad 124: onsuccess: #522: 2: Success after binutils/gcc: 50 commits discards a138ebb1ce 123: onsuccess: #521: 2: Success after binutils/gcc: 66 commits discards 92218911be 122: onsuccess: #520: 2: Success after binutils/gcc: 17 commits discards 52cfae74e7 121: onsuccess: #519: 2: Success after binutils/gcc: 53 commits discards ef50fb1520 120: onsuccess: #518: 2: Success after binutils/gcc: 9 commits discards 83ef194fd7 119: onsuccess: #517: 2: Success after binutils/gcc: 14 commits discards c1a4df1c25 118: onsuccess: #516: 2: Success after binutils/gcc: 39 commits discards 08b664d439 117: onsuccess: #515: 2: Success after binutils/gcc: 34 commits discards 1bc06313ae 116: onsuccess: #514: 2: Success after binutils/gcc: 46 commits discards 14c49e08df 115: onsuccess: #513: 2: Success after binutils/gcc: 73 commits discards cf91b51941 114: onsuccess: #512: 2: Success after binutils/gcc: 47 commits discards 79963acd86 113: onsuccess: #511: 2: Success after binutils/gcc: 11 commits discards b668d6a80f 112: onsuccess: #510: 2: Success after binutils/gcc: 3 commits discards d1bb420445 111: onsuccess: #509: 2: Success after binutils/gcc: 36 commits discards d65a6fd3c8 110: onsuccess: #508: 2: Success after binutils/gcc: 31 commits discards 09378eab0c 109: onsuccess: #507: 2: Success after binutils/gcc: 27 commits discards 02668fc94d 108: onsuccess: #506: 2: Success after binutils/gcc: 47 commits discards 9735c2b838 107: onsuccess: #505: 2: Success after binutils/gcc: 32 commits discards 6124a87596 106: onsuccess: #504: 2: Success after binutils/gcc: 13 commits discards cd5cacae5a 105: onsuccess: #503: 2: Success after binutils/gcc: 8 commits discards 6b3a8e9984 104: onsuccess: #502: 2: Success after binutils/gcc: 31 commits discards d0d2195923 103: onsuccess: #501: 2: Success after binutils/gcc: 37 commits discards 68bfa38d77 102: onsuccess: #500: 2: Success after binutils/gcc: 27 commits discards a0dbddf30a 101: onsuccess: #499: 2: Success after binutils/gcc: 172 commits discards 8ef9c80328 100: onsuccess: #498: 1: Success after gcc: 85 commits discards 09d2843655 99: force: #497: 1: Failure after basepoints/gcc-13-4227-g09 [...] discards 58156f3a61 98: force: #496: 2: Success after gcc: 9 commits discards 4fbea1b584 97: onsuccess: #493: 2: Success after binutils: 49 commits discards 24ed8ca11a 96: onsuccess: #484: 2: Success after binutils: 14 commits discards 865dba717b 95: onsuccess: #482: 2: Success after binutils/gcc: 51 commits discards a69c03fb2c 94: onsuccess: #481: 2: Success after binutils/gcc: 367 commits discards 24aa773108 93: onsuccess: #477: 2: Success after binutils: 4 commits discards 04f0052d23 92: onsuccess: #475: 2: Success after binutils/gcc: 58 commits discards fe2ca083bc 91: onsuccess: #474: 2: Success after binutils/gcc: 50 commits discards fc38a82616 90: onsuccess: #473: 2: Success after binutils/gcc: 61 commits discards 6e889ee658 89: onsuccess: #472: 2: Success after binutils/gcc: 67 commits discards 0b5c4b2349 88: onsuccess: #471: 2: Success after binutils/gcc: 71 commits discards a2415c1442 87: onsuccess: #470: 2: Success after binutils/gcc: 13 commits discards 52c389b119 86: onsuccess: #469: 2: Success after binutils/gcc: 22 commits discards bf26e3229b 85: onsuccess: #468: 2: Success after binutils/gcc: 72 commits discards 259cdab674 84: onsuccess: #467: 2: Success after binutils/gcc: 42 commits discards 054de0b745 83: onsuccess: #466: 2: Success after binutils/gcc: 33 commits discards d8b26abc23 82: onsuccess: #465: 2: Success after binutils/gcc: 26 commits discards da3d840d9b 81: onsuccess: #464: 2: Success after binutils/gcc: 39 commits discards 39877eb476 80: onsuccess: #463: 2: Success after binutils/gcc: 3 commits discards 6835dca218 79: onsuccess: #462: 2: Success after binutils/gcc: 24 commits discards 0bc3df8fe7 78: onsuccess: #461: 2: Success after binutils/gcc: 37 commits discards f1276734a4 77: onsuccess: #460: 2: Success after binutils/gcc: 27 commits discards c6cffd6b50 76: onsuccess: #459: 2: Success after binutils/gcc: 34 commits discards 003d7e77c6 75: onsuccess: #458: 2: Success after binutils/gcc: 35 commits discards 6fc8eaa0f5 74: onsuccess: #457: 2: Success after binutils/gcc: 41 commits discards a5f670aa98 73: onsuccess: #456: 2: Success after binutils/gcc: 6 commits discards b01e9a37fa 72: onsuccess: #455: 2: Success after binutils/gcc: 6 commits discards d46964d943 71: onsuccess: #454: 2: Success after binutils/gcc: 39 commits discards d0687a0c84 70: onsuccess: #453: 2: Success after binutils/gcc: 47 commits discards 3ad67afd1a 69: onsuccess: #452: 2: Success after binutils/gcc: 47 commits discards 03c3c847e9 68: onsuccess: #451: 2: Success after binutils/gcc: 44 commits discards f7ca56c90e 67: onsuccess: #450: 2: Success after binutils/gcc: 45 commits discards ba2d860961 66: onsuccess: #449: 2: Success after binutils/gcc: 5 commits discards e27defd147 65: onsuccess: #448: 2: Success after binutils/gcc: 8 commits discards 6968df739e 64: onsuccess: #447: 2: Success after binutils/gcc: 124 commits discards 0ee24216ca 63: onsuccess: #446: 1: Success after gcc: 20 commits discards 28e636ee5b 62: force: #445: 1: Failure after basepoints/gcc-13-3219-g25 [...] discards e7facca1ae 61: force: #444: 2: Success after gcc: 11 commits discards f17f2c7571 60: onsuccess: #441: 2: Success after binutils: 29 commits discards 6188864960 59: onsuccess: #439: 2: Success after binutils/gcc: 50 commits discards 606c60d7f0 58: onsuccess: #438: 2: Success after binutils/gcc: 5 commits discards bf8c0af9ea 57: onsuccess: #437: 2: Success after binutils/gcc: 6 commits discards 7727f3940b 56: onsuccess: #436: 2: Success after binutils/gcc: 40 commits discards efc5e64056 55: onsuccess: #435: 2: Success after binutils/gcc: 54 commits discards 166c5b9a46 54: onsuccess: #434: 2: Success after binutils/gcc: 35 commits discards 51f325ece1 53: onsuccess: #433: 2: Success after binutils/gcc: 43 commits discards d2f1ed9147 52: onsuccess: #432: 2: Success after binutils/gcc: 39 commits discards 4bd5dba060 51: onsuccess: #431: 2: Success after binutils/gcc: 28 commits discards 6a1a29d2d7 50: onsuccess: #430: 2: Success after binutils/gcc: 178 commits discards 5f28381253 49: onsuccess: #429: 1: Success after gcc: 13 commits discards 9318f650d9 48: force: #428: 1: Failure after basepoints/gcc-13-2871-g1b [...] discards 06efba500b 47: force: #427: 2: Success after gcc: 29 commits discards 1147aa790b 46: onsuccess: #424: 2: Success after binutils: 11 commits discards cf3d953463 45: onsuccess: #422: 2: Success after binutils/gcc: 12 commits discards f94e718aa7 44: onsuccess: #421: 2: Success after binutils/gcc: 11 commits discards d779aeff4d 43: onsuccess: #420: 2: Success after binutils/gcc: 134 commits discards d9af542e34 42: onsuccess: #417: 2: Success after binutils/gcc: 40 commits discards d67128ed5c 41: onsuccess: #416: 2: Success after binutils/gcc: 9 commits discards 7159dbd3de 40: onsuccess: #415: 2: Success after binutils/gcc: 7 commits discards 5e59eaf24c 39: onsuccess: #414: 2: Success after binutils/gcc: 6 commits discards 7b9c22e937 38: onsuccess: #413: 2: Success after binutils/gcc: 25 commits discards 259dbd0648 37: onsuccess: #412: 2: Success after binutils/gcc: 18 commits new 58630d167e 37: onsuccess: #412: 2: Success after binutils/gcc: 18 commits new e56178c4ed 38: onsuccess: #413: 2: Success after binutils/gcc: 25 commits new d43c8e4449 39: onsuccess: #414: 2: Success after binutils/gcc: 6 commits new 3e0120e67f 40: onsuccess: #415: 2: Success after binutils/gcc: 7 commits new 3124ce91ee 41: onsuccess: #416: 2: Success after binutils/gcc: 9 commits new 19c58597f4 42: onsuccess: #417: 2: Success after binutils/gcc: 40 commits new 6e21ecea24 43: onsuccess: #420: 2: Success after binutils/gcc: 134 commits new 84245d5e2d 44: onsuccess: #421: 2: Success after binutils/gcc: 11 commits new 6ca1f549fc 45: onsuccess: #422: 2: Success after binutils/gcc: 12 commits new 14a0ca4e44 46: onsuccess: #424: 2: Success after binutils: 11 commits new 367b017a14 47: force: #427: 2: Success after gcc: 29 commits new 41e17b0253 48: force: #428: 1: Failure after basepoints/gcc-13-2871-g1b [...] new 0f00eb4856 49: onsuccess: #429: 1: Success after gcc: 13 commits new 3890ac54af 50: onsuccess: #430: 2: Success after binutils/gcc: 178 commits new 31e2dec358 51: onsuccess: #431: 2: Success after binutils/gcc: 28 commits new 6a4aeb1767 52: onsuccess: #432: 2: Success after binutils/gcc: 39 commits new 26bf1c6a8e 53: onsuccess: #433: 2: Success after binutils/gcc: 43 commits new e119d5fc38 54: onsuccess: #434: 2: Success after binutils/gcc: 35 commits new 4afca94c00 55: onsuccess: #435: 2: Success after binutils/gcc: 54 commits new b8d73e4030 56: onsuccess: #436: 2: Success after binutils/gcc: 40 commits new 308b245057 57: onsuccess: #437: 2: Success after binutils/gcc: 6 commits new ee82332da6 58: onsuccess: #438: 2: Success after binutils/gcc: 5 commits new f9b568c890 59: onsuccess: #439: 2: Success after binutils/gcc: 50 commits new ad398c87cf 60: onsuccess: #441: 2: Success after binutils: 29 commits new 6859da6e73 61: force: #444: 2: Success after gcc: 11 commits new 0f23308c19 62: force: #445: 1: Failure after basepoints/gcc-13-3219-g25 [...] new 5e7a60c70f 63: onsuccess: #446: 1: Success after gcc: 20 commits new 31b0ba4c31 64: onsuccess: #447: 2: Success after binutils/gcc: 124 commits new 811dda987d 65: onsuccess: #448: 2: Success after binutils/gcc: 8 commits new 8efe67329b 66: onsuccess: #449: 2: Success after binutils/gcc: 5 commits new ca0b76761e 67: onsuccess: #450: 2: Success after binutils/gcc: 45 commits new 305a36fd28 68: onsuccess: #451: 2: Success after binutils/gcc: 44 commits new bfd10c705e 69: onsuccess: #452: 2: Success after binutils/gcc: 47 commits new 0e790aeebd 70: onsuccess: #453: 2: Success after binutils/gcc: 47 commits new 871ad8f98c 71: onsuccess: #454: 2: Success after binutils/gcc: 39 commits new b3e38a66c9 72: onsuccess: #455: 2: Success after binutils/gcc: 6 commits new 9ee5899952 73: onsuccess: #456: 2: Success after binutils/gcc: 6 commits new 8992e7934f 74: onsuccess: #457: 2: Success after binutils/gcc: 41 commits new 033a157d0b 75: onsuccess: #458: 2: Success after binutils/gcc: 35 commits new 5cb865d9bd 76: onsuccess: #459: 2: Success after binutils/gcc: 34 commits new 56d0a6ecab 77: onsuccess: #460: 2: Success after binutils/gcc: 27 commits new d6a8e8982d 78: onsuccess: #461: 2: Success after binutils/gcc: 37 commits new 1eef56d14a 79: onsuccess: #462: 2: Success after binutils/gcc: 24 commits new 472ca03172 80: onsuccess: #463: 2: Success after binutils/gcc: 3 commits new 0aea01e59f 81: onsuccess: #464: 2: Success after binutils/gcc: 39 commits new 9664495fc9 82: onsuccess: #465: 2: Success after binutils/gcc: 26 commits new 8195501e6f 83: onsuccess: #466: 2: Success after binutils/gcc: 33 commits new c99cbaa47f 84: onsuccess: #467: 2: Success after binutils/gcc: 42 commits new 255fd1025b 85: onsuccess: #468: 2: Success after binutils/gcc: 72 commits new 007b430489 86: onsuccess: #469: 2: Success after binutils/gcc: 22 commits new 881d194e67 87: onsuccess: #470: 2: Success after binutils/gcc: 13 commits new 607de56091 88: onsuccess: #471: 2: Success after binutils/gcc: 71 commits new 7ed98153d4 89: onsuccess: #472: 2: Success after binutils/gcc: 67 commits new 51d2e90d41 90: onsuccess: #473: 2: Success after binutils/gcc: 61 commits new e06d6cb4be 91: onsuccess: #474: 2: Success after binutils/gcc: 50 commits new 77de4ed921 92: onsuccess: #475: 2: Success after binutils/gcc: 58 commits new cb04223af7 93: onsuccess: #477: 2: Success after binutils: 4 commits new 9e642562ce 94: onsuccess: #481: 2: Success after binutils/gcc: 367 commits new 3ff80e8677 95: onsuccess: #482: 2: Success after binutils/gcc: 51 commits new f62ea487cf 96: onsuccess: #484: 2: Success after binutils: 14 commits new 5cec5d8fb7 97: onsuccess: #493: 2: Success after binutils: 49 commits new 858eb6a01a 98: force: #496: 2: Success after gcc: 9 commits new 23e8475b4f 99: force: #497: 1: Failure after basepoints/gcc-13-4227-g09 [...] new ca3d8c71ee 100: onsuccess: #498: 1: Success after gcc: 85 commits new 6ab256b78d 101: onsuccess: #499: 2: Success after binutils/gcc: 172 commits new 2f13427658 102: onsuccess: #500: 2: Success after binutils/gcc: 27 commits new f57a013060 103: onsuccess: #501: 2: Success after binutils/gcc: 37 commits new 76798b366f 104: onsuccess: #502: 2: Success after binutils/gcc: 31 commits new 738666ee31 105: onsuccess: #503: 2: Success after binutils/gcc: 8 commits new c3ba84a870 106: onsuccess: #504: 2: Success after binutils/gcc: 13 commits new d262b5d1ce 107: onsuccess: #505: 2: Success after binutils/gcc: 32 commits new bcb750703a 108: onsuccess: #506: 2: Success after binutils/gcc: 47 commits new d2b1a4a166 109: onsuccess: #507: 2: Success after binutils/gcc: 27 commits new b9b509eefe 110: onsuccess: #508: 2: Success after binutils/gcc: 31 commits new 90fc758ce2 111: onsuccess: #509: 2: Success after binutils/gcc: 36 commits new cdf9d8890b 112: onsuccess: #510: 2: Success after binutils/gcc: 3 commits new e7bde05a8d 113: onsuccess: #511: 2: Success after binutils/gcc: 11 commits new 27b1206116 114: onsuccess: #512: 2: Success after binutils/gcc: 47 commits new 7cafdefef7 115: onsuccess: #513: 2: Success after binutils/gcc: 73 commits new abf69745ac 116: onsuccess: #514: 2: Success after binutils/gcc: 46 commits new 06161d2fb6 117: onsuccess: #515: 2: Success after binutils/gcc: 34 commits new 8b4b5cad25 118: onsuccess: #516: 2: Success after binutils/gcc: 39 commits new d140a53eb9 119: onsuccess: #517: 2: Success after binutils/gcc: 14 commits new 9c3b0e0f7a 120: onsuccess: #518: 2: Success after binutils/gcc: 9 commits new 1f68c30c75 121: onsuccess: #519: 2: Success after binutils/gcc: 53 commits new e5ef744afb 122: onsuccess: #520: 2: Success after binutils/gcc: 17 commits new 10506a027f 123: onsuccess: #521: 2: Success after binutils/gcc: 66 commits new e942011daf 124: onsuccess: #522: 2: Success after binutils/gcc: 50 commits new af425425f6 125: onsuccess: #526: 2: Success after binutils/gcc: 90 commits new fba9264597 126: onsuccess: #527: 2: Success after binutils/gcc: 24 commits new 19bd692f42 127: onsuccess: #528: 2: Success after binutils/gcc: 7 commits new 55457fab0c 128: onsuccess: #529: 2: Success after binutils/gcc: 29 commits new 0e97270eb5 129: onsuccess: #530: 2: Success after binutils/gcc: 9 commits new 3620b6cfc8 130: onsuccess: #531: 2: Success after binutils/gcc: 20 commits new 218c7c2fe7 131: onsuccess: #533: 2: Success after binutils/gcc: 29 commits new 6e964e421e 132: onsuccess: #534: 2: Success after binutils/gcc: 18 commits new 856a33f9ef 133: onsuccess: #535: 2: Success after binutils/gcc: 20 commits new 7ce6423f75 134: onsuccess: #536: 2: Success after binutils/gcc: 61 commits new 5784d51e52 135: onsuccess: #537: 2: Success after binutils/gcc: 34 commits new f442cc992c 136: onsuccess: #539: 2: Success after binutils/gcc: 82 commits new 0139b1a915 137: onsuccess: #540: 2: Success after binutils/gcc: 6 commits new f34f6bda98 138: onsuccess: #542: 2: Success after binutils/gcc: 35 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (c12d8eb42d) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1784 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2760 bytes 04-build_abe-binutils/console.log.xz | Bin 52576 -> 52972 bytes .../console.log.xz | Bin 960144 -> 953504 bytes 06-check_regression/console.log.xz | Bin 2768 -> 3032 bytes 07-update_baseline/console.log | 40 ++++++++++----------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +++++------ 13 files changed, 36 insertions(+), 36 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[newlib] branch master updated (3b7df69aa -> 31e5ce10d)

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 newlib. from 3b7df69aa Cygwin: ctty: Add comments for the special values: -1 and -2. new 9d6b00511 newlib: libc: define M-profile PACBTI-enablement macros new ebd922e77 newlib: libc: strcmp M-profile PACBTI-enablement new 558253689 newlib: libc: strlen M-profile PACBTI-enablement new db30cbee4 newlib: libc: memchr M-profile PACBTI-enablement new 60a50c284 newlib: libc: memcpy M-profile PACBTI-enablement new bddfd64ec newlib: libc: aeabi_memmove M-profile PACBTI-enablement new adc36ede1 newlib: libc: aeabi_memset M-profile PACBTI-enablement new 31e5ce10d newlib: libc: setjmp M-profile PACBTI-enablement The 8 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: newlib/libc/machine/arm/aeabi_memmove-thumb2.S | 17 +- newlib/libc/machine/arm/aeabi_memset-thumb2.S | 14 +- newlib/libc/machine/arm/arm_asm.h | 441 +++++++++++++++++++++++++ newlib/libc/machine/arm/memchr.S | 50 ++- newlib/libc/machine/arm/memcpy-armv7m.S | 33 +- newlib/libc/machine/arm/setjmp.S | 43 +++ newlib/libc/machine/arm/strcmp-arm-tiny.S | 8 +- newlib/libc/machine/arm/strcmp-armv7.S | 57 ++-- newlib/libc/machine/arm/strcmp-armv7m.S | 26 +- newlib/libc/machine/arm/strlen-armv7.S | 17 +- newlib/libc/machine/arm/strlen-thumb2-Os.S | 14 +- 11 files changed, 660 insertions(+), 60 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/release-arm updated (46b5235784 -> 37cc135322)

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_check/release-arm in repository toolchain/ci/base-artifacts. from 46b5235784 50: onsuccess: #213: 1: Success after gcc: 8 commits new 37cc135322 51: onsuccess: #214: 1: Success after binutils/gcc: 7 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1712 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 52360 -> 51208 bytes 04-build_abe-gcc/console.log.xz | Bin 228672 -> 228116 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3820 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2344 -> 2972 bytes 07-check_regression/console.log.xz | Bin 4956 -> 5304 bytes 07-check_regression/extra-bisect-params | 1 + 07-check_regression/fails.sum | 7 + 07-check_regression/mail-body.txt | 59 +- 07-check_regression/results.compare | 31 +- 07-check_regression/results.compare2 | 95 +- 07-check_regression/results.regressions | 27 + dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 61 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 27 + sumfiles/g++.log.xz | Bin 2758112 -> 2791652 bytes sumfiles/g++.sum | 132 +- sumfiles/gcc.log.xz | Bin 2331732 -> 2327864 bytes sumfiles/gcc.sum | 3772 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 903556 -> 904320 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2160 -> 2172 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 200084 -> 200268 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2548 -> 2536 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 456380 -> 459816 bytes sumfiles/libstdc++.sum | 10 +- 35 files changed, 2194 insertions(+), 2126 deletions(-) create mode 100644 07-check_regression/extra-bisect-params create mode 100644 07-check_regression/fails.sum create mode 100644 07-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[glibc] branch release/2.35/master updated (293211b6fd -> 82663d3c03)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch release/2.35/master in repository glibc. from 293211b6fd time: Use 64 bit time on tzfile new d9923235f0 elf/tst-tlsopt-powerpc fails when compiled with -mcpu=power1 [...] new 82663d3c03 time: Set daylight to 1 for matching DST/offset change (bug 29951) 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: NEWS | 2 ++ sysdeps/powerpc/mod-tlsopt-powerpc.c | 6 +++- time/tzfile.c | 41 +++++++++++---------- timezone/Makefile | 4 ++- timezone/testdata/XT6 | Bin 0 -> 625 bytes timezone/tst-bz29951.c | 68 +++++++++++++++++++++++++++++++++++ 6 files changed, 100 insertions(+), 21 deletions(-) create mode 100644 timezone/testdata/XT6 create mode 100644 timezone/tst-bz29951.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-lts-defconfig updated (e599f44ccf -> 24dd47067d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-lts-defconfig in repository toolchain/ci/base-artifacts. from e599f44ccf 38: onsuccess: #514: boot: Success after binutils/gcc/qemu: [...] new 24dd47067d 39: onsuccess: #515: boot: Success after binutils/gcc/qemu: [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1760 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 32764 -> 32796 bytes 04-build_abe-stage1/console.log.xz | Bin 74468 -> 73996 bytes 05-build_abe-qemu/console.log.xz | Bin 31568 -> 32264 bytes 06-build_linux/console.log.xz | Bin 3840 -> 3800 bytes 07-boot_linux/console.log.xz | Bin 6096 -> 6116 bytes 08-check_regression/console.log.xz | Bin 4004 -> 3996 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 16 files changed, 21 insertions(+), 21 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-allnoconfig updated (7784697c97 -> 70823ee15e)

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-allnoconfig in repository toolchain/ci/base-artifacts. from 7784697c97 33: onsuccess: #425: all: Success after binutils/llvm/linux/ [...] new 70823ee15e 34: onsuccess: #426: all: 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 1780 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2808 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 32316 -> 31660 bytes 04-build_kernel_llvm/console.log.xz | Bin 65068 -> 63444 bytes 05-build_abe-qemu/console.log.xz | Bin 31500 -> 31112 bytes 06-build_linux/console.log.xz | Bin 3132 -> 3108 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4444 -> 4324 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 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (a249403a4a -> 9266bb9237)

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 a249403a4a 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 2b4c468bbd 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 83fd6f2f1e 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 80f979de21 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 9338e15de5 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards f9878b8298 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards d9818ee6b2 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 6027ccd7f3 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards cae854a3f7 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards cf5cc45f64 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 49bcc5e5dc 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards b61fe7d567 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 60c576b8df 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards c9780de633 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards d36aaa4e0c 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 548af2a8e6 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 6f6ebab54e 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 09db7e8d5e 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 4cadf6fd24 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards cec10db4a9 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards a514862b01 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 6e5f08e41b 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards d3c50991c6 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 6bb28d23f3 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 91913d1e52 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards da2873c29d 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 44c5b9bcad 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards ce864aaf21 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 51be4a2409 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 5999acd65b 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 33880d1c00 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 1dae772ba9 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards a0dd2b552b 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 26ff1d8d63 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards c8875409af 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 25b0f3e9c1 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 10fee3c5cb 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 8266e90d24 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards b48ba59a0e 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 73c8cc25dd 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 43e79fa656 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards ad70d5f6cd 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 9b6c79a83b 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards d12d59b158 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards a6c94e563c 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 09207e18a9 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 4d5cc4902e 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 5c005fd03b 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 293c82ed2c 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 197ee46f10 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards c15fba167b 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 1805214376 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 7f81faf12e 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 48b7d621a7 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 84fa5401c1 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 1b4a4ec46c 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 4c25e3697d 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 1f55ae1446 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards f6d56fcab3 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards bd45e7d167 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 2e01c97d29 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 9a5b5badf6 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 4f100bc9f6 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 2d7d957c57 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 50429ba6b4 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 7cb203519a 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 7010dc88ca 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards baab32f936 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards b2aa6ca667 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards d7c6c8b27a 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards b3e12a4e18 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 68612c0774 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 4974d40a31 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards a0fc97bf5a 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 4253ac0135 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards bc12d028a1 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards ccb446fe21 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 80bc6b6cfd 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 8b6e9429d2 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 2ad6d1ba03 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 389d16c991 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards f1b60865ef 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 71c418b74c 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 1a214778ba 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 853252b25e 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards d685195b9e 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards b9375d3ca1 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 202b910a85 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 9d4e9cd722 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 7c25e5a70c 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 32c3a758cb 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards a5b1e70b55 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 8a3895c88f 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards eb5eb1ff7c 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards f55e2fbfe0 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards 0d7a2fd7ec 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards 97c17db283 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards 2a6c9dfaff 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards f646824914 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards a267944624 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards e0b2b65174 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new 977bebcebb 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new 23793002ee 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new a71e7ecb2e 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new abd685a435 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 881459eace 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new 84863c0ca2 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new 453748c11c 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new b0372c8893 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new eec4882010 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new dcacea044c 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 8f1db6120b 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new a1e92deae3 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new d93f3e93e6 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new cfa292190b 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 4f09fec9e9 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 177e30f788 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new a0e9141722 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 73a6e0e2f9 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 72fb18f872 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 85b8b33497 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new bdbe6bd119 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 77cbb60cfb 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new d09e12fe12 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 6a0d4f0b8f 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 3e04b4886f 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 4d3e7ca6ab 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 74800c6304 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new c6ee954d07 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 0774e468c1 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new de596fa09d 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 49d8f549e4 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new a3eb0375ca 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 9843a25626 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new fe9b3d8920 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 379f311e8b 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new c466d6b5de 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new cf20b01f53 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new aeb44f8c0b 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 61a5c60339 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 5d8962cc6d 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new f1c80ac746 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new f366a18668 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new b355fa1d39 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 139bdeddae 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new f16fc3a7af 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new bcdc712f67 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new a7f6cb800e 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 90a8de08cf 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 27e02f3659 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 541912f36c 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new bf58b78d10 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 9d5d56ccc7 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 5b3f930434 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 778009044b 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 23dd1bfc24 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 1c029b60bf 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 2e96daeefc 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 6340e5b359 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 4f5da5d4e7 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new ba7761119c 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 57e1e4fe9d 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 85600fee9e 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 8b198673a7 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 1f5304bb82 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new dbd26104af 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 9cf5943abb 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 903cc3ded2 301: onsuccess: #2118: 1: Success after linux: 16 commits new 43fcde4877 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 08eff115e7 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 7e967ea171 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 293f77eca9 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 7ddaaba8db 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 881dee4049 307: onsuccess: #2124: 1: Success after gcc: 2 commits new d8e8dc4ad6 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 85d2ce6cde 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 15858c7411 310: onsuccess: #2129: 1: Success after binutils: 4 commits new be35bd6b0e 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 7700c58c46 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new b2eede7b4e 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 0774ffe7a9 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 1791e53f4e 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 1e8154bc13 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 3353050a65 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 6f301045de 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 95a93b6acf 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new b6cd850423 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 2e0592fd8b 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 7bb6e334db 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 00b602ffbc 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 0d2ce2868f 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 621f9eddaa 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 006a32574c 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 34b646d3e3 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 62b49de642 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 89209e7f07 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 5436fa58e5 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 58a5b2b2da 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 4fb2ac06d5 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 73dd4a3d4b 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 23f59eba11 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new c1c56b9012 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 9266bb9237 336: onsuccess: #2156: 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 (a249403a4a) \ 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 1772 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 31804 -> 32196 bytes 04-build_abe-stage1/console.log.xz | Bin 91452 -> 92460 bytes 06-build_abe-linux/console.log.xz | Bin 8768 -> 8628 bytes 07-build_abe-glibc/console.log.xz | Bin 236120 -> 238432 bytes 08-build_abe-stage2/console.log.xz | Bin 227872 -> 231468 bytes 09-build_abe-gdb/console.log.xz | Bin 39364 -> 39764 bytes 10-build_abe-qemu/console.log.xz | Bin 31556 -> 31708 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3916 -> 3900 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2484 -> 2744 bytes 13-check_regression/console.log.xz | Bin 5200 -> 6376 bytes 13-check_regression/results.compare | 12 +- 13-check_regression/results.compare2 | 32 +- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- sumfiles/g++.log.xz | Bin 2668456 -> 2665288 bytes sumfiles/g++.sum | 12 +- sumfiles/gcc.log.xz | Bin 2268824 -> 2267784 bytes sumfiles/gcc.sum | 2406 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 894336 -> 895804 bytes sumfiles/gfortran.sum | 12 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214204 -> 214024 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 444864 -> 439012 bytes sumfiles/libstdc++.sum | 2 +- 38 files changed, 1311 insertions(+), 1293 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits January 2023