Tcwg-commits January 2023

tcwg-commits@lists.linaro.org

5 participants
4127 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (bfc519bc54 -> 31246be472)

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 bfc519bc54 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 77a25891a5 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 194aa29784 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards e967e5de44 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards dac9366cb9 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 1b45fc3863 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 51eccb1fb0 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards a435814e7d 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards be7702ad87 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 8f9335549b 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 51a99248c2 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards fd011b177d 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards ef0e2a3d3c 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards bba2bc6d8c 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards d0b4f959e0 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards b4367fa0cc 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards e599c4c45d 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 831a8fbaed 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 2a44ec4aae 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards bdcfe8afbb 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 225afc7c42 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 00cb549d60 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards e4da5449c7 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 5144170cda 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 1ebf32e0b1 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards e25dbb1f41 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 3880462b31 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 4253691e51 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards ef91d4d887 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards b77fc4eb9d 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 36cde0a10b 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 371034fa7b 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards acbfd80a64 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 154febeb0d 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards f059b9d5dd 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 3a0236386a 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards b662a1ffa7 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards cbc4ce7d8c 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 73f1cecdbb 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 6e251e4301 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 110a963fa4 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards cbce6c6240 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 1e56d60a10 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 38e451b7c3 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards e4da4a24f1 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 1da4fd7691 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 784b350fea 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 40dcaa4f60 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 0b52b29f1a 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards a12cd7059c 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards fb90074526 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards b7bbb77b73 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards cd596d658d 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards a68d5ed779 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards aa311b203f 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 3110548b6a 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 738097a81b 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 424eca0e35 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 5e8eead0dc 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards eca8272e4e 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 491fecad82 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards a76f179f09 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards 9d27f9bf2e 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 001ae886ce 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards f11218ba7e 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 0e55ace345 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 41a63afd49 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards a389f258fe 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards d1aa9ee7db 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 8ebb761f1e 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards a3b96e9e0e 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 323e00ca7a 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards 721d85db1c 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards 463a5c5928 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards 259f1254b2 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 06211f0725 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards 8d84093e26 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards e7fd791243 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards f6ce10f3f6 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards 8ea185bbc9 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards faad2e4245 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 7099bed67e 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards 3feaa893bd 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards b58f7247d4 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards a93172dce8 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards 6a4a224b26 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 024e924ebc 235: onsuccess: #2483: 1: Success after linux: 108 commits discards c0490097e0 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards a5e00c49b1 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards 5ba7979146 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards a10b555d0c 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards e09456187e 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards 42d1e5a49a 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards 14581e44a6 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards 94b92ca595 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards 176fa1c6ae 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] discards f9a31bc6c9 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards 388e7d18d2 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] discards 957ed5e284 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] discards ce5a7956ca 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] discards ceafd904a1 221: onsuccess: #2467: 1: Success after binutils: 3 commits new a113ada316 221: onsuccess: #2467: 1: Success after binutils: 3 commits new 4190bb362c 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] new 87d940a0d0 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] new d3ea036b9a 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] new 314962501b 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new ad5fcd0fd2 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] new 46d068e2ed 227: onsuccess: #2474: 1: Success after gcc: 2 commits new 4720fec0b0 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new d44f4b77e4 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new 6b1ce7b6c7 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new 13ed46a702 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new 3abd901072 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new ae531b2140 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new bdf0448e57 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 881ff76f6e 235: onsuccess: #2483: 1: Success after linux: 108 commits new 43b9575cbf 236: onsuccess: #2484: 1: Success after gcc: 2 commits new c2cc9aed95 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new 4afb4a6b19 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new 31287f5d83 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new 28d9cdbc88 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 8781944717 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 11941e12ae 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new 08011d4851 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new 58c439a67c 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new dbdf4aea75 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new dc79f376ed 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new c6a8f23984 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new cac4e3b5e0 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new c7f83ab2a7 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new 1c8616b363 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 9f59d010dc 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 46b90f6259 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new e1fc21bcd9 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new 855b9e5276 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 957877fe6a 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new f54b8f18a0 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new d6039d7c87 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new ed7cc583ac 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new 946df1da07 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 3bc1f224d1 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 24306fec00 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 8cb2028009 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 0a78a13ead 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 7011a127a3 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new ae64af45ef 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new bd36330a0d 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 9339433996 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 30ce984353 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new fc809d8da6 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 43521ff238 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 302da9091f 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 0958fab953 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 548967fd5a 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 7dc3b2684d 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new e07009944b 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 5a9891ed15 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new a6ac5127f3 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 181701f1e4 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 305dec7d49 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new b3164e921e 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 8edaee7e4d 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 2e32cb634a 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new b125d19d6f 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 1bb9d8f48f 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 7432986223 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 5c331abea2 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new da1190223c 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new b840f477c4 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 4349e62d40 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new dc857f37d1 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 2095545f00 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 12230ca5fb 292: onsuccess: #2541: 1: Success after binutils: 13 commits new fa701a9237 293: onsuccess: #2542: 1: Success after gcc: 5 commits new a2dac1d7e5 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 53d4f10281 295: onsuccess: #2545: 1: Success after linux: 10 commits new be98897b7f 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 3c98665b75 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 6ac8193f69 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new df10366359 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new f4a62e7618 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new e55f7c1f6f 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 5b44964faa 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 0d315f9eef 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 378016b59c 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 9500d2da2f 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 9d7c0f57fa 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 7d2b7c02a4 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new b33125b633 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 4bcd8e423b 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 73e27a3eea 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 89259e3e22 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 613fa0b47c 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 03c09b4079 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 3556b80707 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 4cadc90ea1 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 5070fb35de 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 4b0137c203 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 87d324d0a2 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new a4c23264c2 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new f7c109275f 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 8a3a191778 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 31246be472 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 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 (bfc519bc54) \ 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 1776 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31992 -> 31948 bytes 04-build_abe-stage1/console.log.xz | Bin 73264 -> 72964 bytes 06-build_abe-linux/console.log.xz | Bin 8584 -> 8596 bytes 07-build_abe-glibc/console.log.xz | Bin 244532 -> 244600 bytes 08-build_abe-stage2/console.log.xz | Bin 204480 -> 204688 bytes 09-build_abe-gdb/console.log.xz | Bin 39472 -> 39584 bytes 10-build_abe-qemu/console.log.xz | Bin 31780 -> 31900 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3896 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2624 -> 2764 bytes 13-check_regression/console.log.xz | Bin 6292 -> 5840 bytes 13-check_regression/fails.sum | 27 +- 13-check_regression/mail-body.txt | 83 +- 13-check_regression/results.compare | 35 +- 13-check_regression/results.compare2 | 60 +- 13-check_regression/results.regressions | 35 +- 14-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 | 85 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 35 +- sumfiles/g++.log.xz | Bin 3414232 -> 3435496 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 3036908 -> 3014568 bytes sumfiles/gcc.sum | 4712 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1043520 -> 1040752 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2284 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214760 -> 214652 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2696 -> 2704 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 428532 -> 423472 bytes sumfiles/libstdc++.sum | 2 +- 41 files changed, 2622 insertions(+), 2570 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (563c304b3f -> c00af04b4c)

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/master-aarch64 in repository toolchain/ci/base-artifacts. discards 563c304b3f 517: onsuccess: #2481: 1: Success after binutils/gcc: 93 commits discards 0a467c8088 516: onsuccess: #2480: 1: Success after binutils/gcc: 17 commits discards 7f5393fa64 515: onsuccess: #2479: 1: Success after gcc: 9 commits discards 8be2f9fa18 514: onsuccess: #2478: 1: Success after binutils: 3 commits discards 0eddee45ed 513: onsuccess: #2476: 1: Success after basepoints/gcc-13-50 [...] discards eb94108d3e 512: onsuccess: #2475: 1: Success after binutils/gcc: 3 commits discards f3611e6f61 511: onsuccess: #2474: 1: Success after binutils/gcc: 2 commits discards b40d8550ea 510: onsuccess: #2473: 1: Success after binutils/gcc: 4 commits discards aaca1a6d45 509: onsuccess: #2472: 1: Success after basepoints/gcc-13-50 [...] discards 3e4114bb4e 508: onsuccess: #2471: 1: Success after basepoints/gcc-13-50 [...] discards 825d5abaa5 507: onsuccess: #2470: 1: Success after binutils/gcc: 4 commits discards 474a203152 506: onsuccess: #2469: 1: Success after binutils/gcc: 21 commits discards 891cf1c934 505: onsuccess: #2467: 1: Success after basepoints/gcc-13-50 [...] discards 66b19c7ea2 504: onsuccess: #2466: 1: Success after binutils/gcc: 10 commits discards f3a3330014 503: onsuccess: #2465: 1: Success after binutils/gcc: 33 commits discards b87d4e07b5 502: onsuccess: #2464: 1: Success after binutils/gcc: 4 commits discards b5d0bd38f5 501: onsuccess: #2463: 1: Success after binutils/gcc: 8 commits discards 4b95b4b0f5 500: onsuccess: #2462: 1: Success after binutils/gcc: 6 commits discards 790df72008 499: onsuccess: #2461: 1: Success after binutils/gcc: 16 commits discards 65542fd4f9 498: onsuccess: #2460: 1: Success after binutils/gcc: 7 commits discards 542b987bbd 497: onsuccess: #2459: 1: Success after binutils/gcc: 6 commits discards de5fc63477 496: onsuccess: #2458: 1: Success after binutils/gcc: 4 commits discards 833161ee64 495: onsuccess: #2457: 1: Success after binutils/gcc: 19 commits discards 09f2a4e990 494: onsuccess: #2456: 1: Success after binutils/gcc: 23 commits discards fd6e193559 493: onsuccess: #2455: 1: Success after binutils: 14 commits discards c54a354aa8 492: onsuccess: #2454: 1: Success after binutils/gcc: 2 commits discards 6106eac131 491: onsuccess: #2453: 1: Success after binutils/gcc: 8 commits discards b7c4affb85 490: onsuccess: #2452: 1: Success after binutils/gcc: 7 commits discards b9772844f2 489: onsuccess: #2451: 1: Success after binutils/gcc: 4 commits discards 9bcd31a488 488: onsuccess: #2450: 1: Success after binutils: 7 commits discards 0d64fc3e0e 487: onsuccess: #2449: 1: Success after binutils/gcc: 7 commits discards 0706409754 486: onsuccess: #2448: 1: Success after binutils/gcc: 3 commits discards c9f3b1b21f 485: onsuccess: #2447: 1: Success after binutils/gcc: 3 commits discards 9bea344230 484: onsuccess: #2446: 1: Success after binutils/gcc: 3 commits discards 7948844486 483: onsuccess: #2445: 1: Success after binutils: 11 commits discards 872e894d3f 482: onsuccess: #2444: 1: Success after binutils/gcc: 2 commits discards 01cfb5f62d 481: onsuccess: #2443: 1: Success after gdb-13-branchpoint-2 [...] discards 1e575f725c 480: onsuccess: #2442: 1: Success after binutils/gcc: 6 commits discards 6bc37f37cf 479: onsuccess: #2441: 1: Success after binutils/gcc: 2 commits discards 49ed64d8a3 478: onsuccess: #2440: 1: Success after basepoints/gcc-13-49 [...] discards 11ac67c172 477: onsuccess: #2439: 1: Success after binutils/gcc: 2 commits discards 115ffa0177 476: onsuccess: #2438: 1: Success after gcc: 17 commits discards 830633b07f 475: onsuccess: #2437: 1: Success after gdb-13-branchpoint-2 [...] discards edd9a855fc 474: onsuccess: #2436: 1: Success after basepoints/gcc-13-49 [...] discards 59d76f5586 473: onsuccess: #2435: 1: Success after binutils/gcc: 3 commits discards a7dbe019ac 472: onsuccess: #2434: 1: Success after binutils: 2 commits discards e11f4cea8a 471: onsuccess: #2433: 1: Success after gcc: 2 commits discards 640b53b00e 470: onsuccess: #2432: 1: Success after gcc: 2 commits discards 827b367cb2 469: onsuccess: #2431: 1: Success after binutils/gcc: 7 commits discards 8c5d8ad26f 468: onsuccess: #2430: 1: Success after binutils/gcc: 11 commits discards 8bb0d7fbaf 467: onsuccess: #2429: 1: Success after basepoints/gcc-13-48 [...] discards a66ec8f715 466: onsuccess: #2428: 1: Success after binutils: 9 commits discards 6627ce37b4 465: onsuccess: #2427: 1: Success after binutils/gcc: 3 commits discards ecd34d947a 464: onsuccess: #2426: 1: Success after basepoints/gcc-13-48 [...] discards a682ee8377 463: onsuccess: #2425: 1: Success after binutils: 2 commits discards 5ba6556623 462: onsuccess: #2424: 1: Success after gcc: 2 commits discards 729115a3f5 461: onsuccess: #2423: 1: Success after binutils: 2 commits discards a879654c2e 460: onsuccess: #2422: 1: Success after gdb-13-branchpoint-1 [...] discards be893d9f68 459: onsuccess: #2421: 1: Success after binutils/gcc: 11 commits discards ba537ce373 458: onsuccess: #2420: 1: Success after binutils/gcc: 9 commits discards 80a8d9d87c 457: onsuccess: #2419: 1: Success after binutils/gcc: 3 commits discards 92a79eebb7 456: onsuccess: #2418: 1: Success after binutils/gcc: 4 commits discards 3cccf7f2de 455: onsuccess: #2417: 1: Success after binutils/gcc: 2 commits discards edb7d0cf94 454: onsuccess: #2416: 1: Success after binutils/gcc: 6 commits discards 6f7db0c2a2 453: onsuccess: #2415: 1: Success after binutils/gcc: 27 commits discards 5c64f67abe 452: onsuccess: #2414: 1: Success after binutils/gcc: 17 commits discards c2bc658473 451: onsuccess: #2413: 1: Success after binutils/gcc: 31 commits discards 34bc0cb5f2 450: onsuccess: #2412: 1: Success after binutils/gcc: 12 commits discards 1d1ef6f3d3 449: onsuccess: #2411: 1: Success after binutils/gcc: 11 commits discards 3c8783f83e 448: onsuccess: #2410: 1: Success after binutils/gcc: 18 commits discards 196f690a5b 447: onsuccess: #2409: 1: Success after binutils/gcc: 9 commits discards b54189a8f0 446: onsuccess: #2408: 1: Success after binutils/gcc: 5 commits discards 84c069db76 445: onsuccess: #2407: 1: Success after binutils/gcc: 8 commits discards b1607156fa 444: onsuccess: #2406: 1: Success after binutils/gcc: 18 commits discards 0d4cfa4d85 443: onsuccess: #2405: 1: Success after binutils/gcc: 36 commits discards e69407af35 442: onsuccess: #2404: 1: Success after binutils/gcc: 5 commits discards 3bda88ced9 441: onsuccess: #2403: 1: Success after gcc: 3 commits discards 823efcd9d8 440: onsuccess: #2402: 1: Success after binutils/gcc: 4 commits discards 203e0fe469 439: onsuccess: #2401: 1: Success after binutils/gcc: 4 commits discards 31798ab74b 438: onsuccess: #2400: 1: Success after binutils/gcc: 7 commits discards 6f9d760ebb 437: onsuccess: #2399: 1: Success after binutils/gcc: 26 commits discards c5d09309f1 436: onsuccess: #2398: 1: Success after binutils/gcc: 20 commits discards d335873b71 435: onsuccess: #2397: 1: Success after basepoints/gcc-13-47 [...] discards 93a5b37aae 434: onsuccess: #2396: 1: Success after binutils/gcc: 2 commits discards 3ba87c1061 433: onsuccess: #2395: 1: Success after binutils/gcc: 3 commits discards 5f4f971d98 432: onsuccess: #2394: 1: Success after binutils/gcc: 3 commits discards 3fbf71abe5 431: onsuccess: #2393: 1: Success after binutils/gcc: 3 commits discards d154d689c1 430: onsuccess: #2392: 1: Success after basepoints/gcc-13-47 [...] discards 3f8e83ac5e 429: onsuccess: #2391: 1: Success after binutils: 3 commits discards 14571be32d 428: onsuccess: #2390: 1: Success after binutils/gcc: 8 commits discards b699799259 427: onsuccess: #2389: 1: Success after binutils/gcc: 11 commits discards be4af87e9a 426: onsuccess: #2388: 1: Success after binutils/gcc: 11 commits discards 75b8fb6c11 425: onsuccess: #2387: 1: Success after binutils/gcc: 13 commits discards ca4433e4d6 424: onsuccess: #2386: 1: Success after binutils/gcc: 3 commits discards d0a54ff778 423: onsuccess: #2385: 1: Success after binutils/gcc: 14 commits discards 20f8614b58 422: onsuccess: #2384: 1: Success after binutils/gcc: 12 commits discards f0a1c505a6 421: onsuccess: #2383: 1: Success after binutils/gcc: 7 commits discards 3a9ce1f035 420: onsuccess: #2382: 1: Success after gcc: 2 commits discards 7d7ba4a9d9 419: onsuccess: #2381: 1: Success after binutils/gcc: 7 commits discards fdc66fa6cc 418: onsuccess: #2380: 1: Success after binutils/gcc: 14 commits discards b363b713f8 417: onsuccess: #2379: 1: Success after binutils/gcc: 13 commits new 31731df443 417: onsuccess: #2379: 1: Success after binutils/gcc: 13 commits new 6d5d266a46 418: onsuccess: #2380: 1: Success after binutils/gcc: 14 commits new 9c30375d65 419: onsuccess: #2381: 1: Success after binutils/gcc: 7 commits new b25d9dc139 420: onsuccess: #2382: 1: Success after gcc: 2 commits new 2b9eefd115 421: onsuccess: #2383: 1: Success after binutils/gcc: 7 commits new 6ba46bd2f6 422: onsuccess: #2384: 1: Success after binutils/gcc: 12 commits new 4c302bca44 423: onsuccess: #2385: 1: Success after binutils/gcc: 14 commits new 92fb458053 424: onsuccess: #2386: 1: Success after binutils/gcc: 3 commits new 63d600e837 425: onsuccess: #2387: 1: Success after binutils/gcc: 13 commits new 4db3d1dc4c 426: onsuccess: #2388: 1: Success after binutils/gcc: 11 commits new bce5f28575 427: onsuccess: #2389: 1: Success after binutils/gcc: 11 commits new a7f1821d19 428: onsuccess: #2390: 1: Success after binutils/gcc: 8 commits new c41bf7c501 429: onsuccess: #2391: 1: Success after binutils: 3 commits new 3a332c4365 430: onsuccess: #2392: 1: Success after basepoints/gcc-13-47 [...] new 6316835522 431: onsuccess: #2393: 1: Success after binutils/gcc: 3 commits new f3f5c6acf4 432: onsuccess: #2394: 1: Success after binutils/gcc: 3 commits new 9725f20c46 433: onsuccess: #2395: 1: Success after binutils/gcc: 3 commits new 7dcff27d03 434: onsuccess: #2396: 1: Success after binutils/gcc: 2 commits new 6890cb17a1 435: onsuccess: #2397: 1: Success after basepoints/gcc-13-47 [...] new 16a79ab7db 436: onsuccess: #2398: 1: Success after binutils/gcc: 20 commits new d98cc0194d 437: onsuccess: #2399: 1: Success after binutils/gcc: 26 commits new 0a875c208a 438: onsuccess: #2400: 1: Success after binutils/gcc: 7 commits new 564fbfe500 439: onsuccess: #2401: 1: Success after binutils/gcc: 4 commits new 443853bd99 440: onsuccess: #2402: 1: Success after binutils/gcc: 4 commits new fa2a0a34ae 441: onsuccess: #2403: 1: Success after gcc: 3 commits new cb39513226 442: onsuccess: #2404: 1: Success after binutils/gcc: 5 commits new 4f48ddef78 443: onsuccess: #2405: 1: Success after binutils/gcc: 36 commits new a2d904c050 444: onsuccess: #2406: 1: Success after binutils/gcc: 18 commits new 74e9748643 445: onsuccess: #2407: 1: Success after binutils/gcc: 8 commits new ff5dce05e2 446: onsuccess: #2408: 1: Success after binutils/gcc: 5 commits new 2a4f92d27c 447: onsuccess: #2409: 1: Success after binutils/gcc: 9 commits new ccbb47ccd8 448: onsuccess: #2410: 1: Success after binutils/gcc: 18 commits new fea25776fa 449: onsuccess: #2411: 1: Success after binutils/gcc: 11 commits new 7903899c06 450: onsuccess: #2412: 1: Success after binutils/gcc: 12 commits new a56295ce4d 451: onsuccess: #2413: 1: Success after binutils/gcc: 31 commits new 18bb3e2d39 452: onsuccess: #2414: 1: Success after binutils/gcc: 17 commits new 1be562c0aa 453: onsuccess: #2415: 1: Success after binutils/gcc: 27 commits new 352559cb15 454: onsuccess: #2416: 1: Success after binutils/gcc: 6 commits new 238132d27c 455: onsuccess: #2417: 1: Success after binutils/gcc: 2 commits new 19d11e57d1 456: onsuccess: #2418: 1: Success after binutils/gcc: 4 commits new 117029dbd3 457: onsuccess: #2419: 1: Success after binutils/gcc: 3 commits new 2e89081359 458: onsuccess: #2420: 1: Success after binutils/gcc: 9 commits new 40cbc7d4fb 459: onsuccess: #2421: 1: Success after binutils/gcc: 11 commits new cd6fadf1c4 460: onsuccess: #2422: 1: Success after gdb-13-branchpoint-1 [...] new 86ea8234a7 461: onsuccess: #2423: 1: Success after binutils: 2 commits new fd5861d466 462: onsuccess: #2424: 1: Success after gcc: 2 commits new b78bfedd80 463: onsuccess: #2425: 1: Success after binutils: 2 commits new cf004115d7 464: onsuccess: #2426: 1: Success after basepoints/gcc-13-48 [...] new ed42843b38 465: onsuccess: #2427: 1: Success after binutils/gcc: 3 commits new 5a746a3c66 466: onsuccess: #2428: 1: Success after binutils: 9 commits new affc7f5b63 467: onsuccess: #2429: 1: Success after basepoints/gcc-13-48 [...] new 6461993327 468: onsuccess: #2430: 1: Success after binutils/gcc: 11 commits new 9b58ca9442 469: onsuccess: #2431: 1: Success after binutils/gcc: 7 commits new c03ba71d1a 470: onsuccess: #2432: 1: Success after gcc: 2 commits new 22bb12409c 471: onsuccess: #2433: 1: Success after gcc: 2 commits new 8be118fed3 472: onsuccess: #2434: 1: Success after binutils: 2 commits new 718e71379e 473: onsuccess: #2435: 1: Success after binutils/gcc: 3 commits new 9ddd0c94cb 474: onsuccess: #2436: 1: Success after basepoints/gcc-13-49 [...] new af47485b4a 475: onsuccess: #2437: 1: Success after gdb-13-branchpoint-2 [...] new 9b77b204de 476: onsuccess: #2438: 1: Success after gcc: 17 commits new 2ba7f88135 477: onsuccess: #2439: 1: Success after binutils/gcc: 2 commits new 2538aeba50 478: onsuccess: #2440: 1: Success after basepoints/gcc-13-49 [...] new 2024e8c63f 479: onsuccess: #2441: 1: Success after binutils/gcc: 2 commits new 143135d181 480: onsuccess: #2442: 1: Success after binutils/gcc: 6 commits new 2b27b9b7ab 481: onsuccess: #2443: 1: Success after gdb-13-branchpoint-2 [...] new bd9f38e068 482: onsuccess: #2444: 1: Success after binutils/gcc: 2 commits new 23fd2e6e27 483: onsuccess: #2445: 1: Success after binutils: 11 commits new ff6aa0ce6e 484: onsuccess: #2446: 1: Success after binutils/gcc: 3 commits new bfb8413de0 485: onsuccess: #2447: 1: Success after binutils/gcc: 3 commits new f870f604a6 486: onsuccess: #2448: 1: Success after binutils/gcc: 3 commits new cc1869ce20 487: onsuccess: #2449: 1: Success after binutils/gcc: 7 commits new 107168a48f 488: onsuccess: #2450: 1: Success after binutils: 7 commits new 64205bd78f 489: onsuccess: #2451: 1: Success after binutils/gcc: 4 commits new 14d9e8f1a8 490: onsuccess: #2452: 1: Success after binutils/gcc: 7 commits new 59736ae0d1 491: onsuccess: #2453: 1: Success after binutils/gcc: 8 commits new ca8af138cf 492: onsuccess: #2454: 1: Success after binutils/gcc: 2 commits new f6626dd853 493: onsuccess: #2455: 1: Success after binutils: 14 commits new 7d326c1b6c 494: onsuccess: #2456: 1: Success after binutils/gcc: 23 commits new dd4aae50ca 495: onsuccess: #2457: 1: Success after binutils/gcc: 19 commits new 23cf41a554 496: onsuccess: #2458: 1: Success after binutils/gcc: 4 commits new 81fe2fbab9 497: onsuccess: #2459: 1: Success after binutils/gcc: 6 commits new 66d04885a0 498: onsuccess: #2460: 1: Success after binutils/gcc: 7 commits new c3f838bf1d 499: onsuccess: #2461: 1: Success after binutils/gcc: 16 commits new bd7d0c772c 500: onsuccess: #2462: 1: Success after binutils/gcc: 6 commits new dd0ddffe07 501: onsuccess: #2463: 1: Success after binutils/gcc: 8 commits new 366b3d3fa0 502: onsuccess: #2464: 1: Success after binutils/gcc: 4 commits new 275d37fa9a 503: onsuccess: #2465: 1: Success after binutils/gcc: 33 commits new 078fff891b 504: onsuccess: #2466: 1: Success after binutils/gcc: 10 commits new 16d74ac8e2 505: onsuccess: #2467: 1: Success after basepoints/gcc-13-50 [...] new c1ca6dec03 506: onsuccess: #2469: 1: Success after binutils/gcc: 21 commits new 0156c81001 507: onsuccess: #2470: 1: Success after binutils/gcc: 4 commits new 455cc82bb7 508: onsuccess: #2471: 1: Success after basepoints/gcc-13-50 [...] new 3b98406e5c 509: onsuccess: #2472: 1: Success after basepoints/gcc-13-50 [...] new 1f6b142697 510: onsuccess: #2473: 1: Success after binutils/gcc: 4 commits new 52a34c73ae 511: onsuccess: #2474: 1: Success after binutils/gcc: 2 commits new 4ebaa52aeb 512: onsuccess: #2475: 1: Success after binutils/gcc: 3 commits new eb3e1b3b0f 513: onsuccess: #2476: 1: Success after basepoints/gcc-13-50 [...] new 2bcd5dc50e 514: onsuccess: #2478: 1: Success after binutils: 3 commits new 2df4c01c15 515: onsuccess: #2479: 1: Success after gcc: 9 commits new aba2d8c22d 516: onsuccess: #2480: 1: Success after binutils/gcc: 17 commits new 49dcda6ef4 517: onsuccess: #2481: 1: Success after binutils/gcc: 93 commits new c00af04b4c 518: onsuccess: #2482: 1: Success after binutils/gcc: 19 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 (563c304b3f) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-aarch64 [...] 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 1744 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 39608 -> 39564 bytes 04-build_abe-gcc/console.log.xz | Bin 214464 -> 214056 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3828 bytes 06-build_abe-check_gcc/console.log.xz | Bin 3144 -> 2944 bytes 07-check_regression/console.log.xz | Bin 5128 -> 4864 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 29 +- 08-update_baseline/console.log | 46 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/g++.log.xz | Bin 3614576 -> 3646080 bytes sumfiles/g++.sum | 118 +- sumfiles/gcc.log.xz | Bin 3165588 -> 3160912 bytes sumfiles/gcc.sum | 4746 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1051212 -> 1051904 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2192 -> 2184 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 220152 -> 220444 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2544 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 460760 -> 446228 bytes sumfiles/libstdc++.sum | 10 +- 31 files changed, 2522 insertions(+), 2541 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch releases/gcc-12 updated (14e25006c8d -> bd4c310b06d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-12 in repository gcc. from 14e25006c8d Daily bump. new bd4c310b06d strlen: do not use cond_expr for boundaries The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/testsuite/gcc.dg/tree-ssa/pr108137.c | 8 ++++++++ gcc/tree-ssa-strlen.cc | 13 +++++++------ 2 files changed, 15 insertions(+), 6 deletions(-) create mode 100644 gcc/testsuite/gcc.dg/tree-ssa/pr108137.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (64e52e6482 -> 26906d9048)

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 64e52e6482 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards a340ef4375 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 9838d09c2a 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 88366e0bd4 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 1cea275183 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 12f05d3937 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 52d5ca79fe 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 9b952680b4 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 67f78dd3ee 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards da12eb2a96 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 814ece578b 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 070ae1337e 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 26120cf094 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 687a7fc5a5 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 877a8585df 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 3c4a831787 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards f60bdffc7c 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards d4bd0f8b82 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards e38fc2890a 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards e0581285d2 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards b5525afae1 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 2b3992cb4a 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 096cf9a679 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 74839e3821 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 054e4f4fe6 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 6a47a3cc55 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 4de16cba36 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 3e8acd3842 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 0abf07a7ac 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 2bf4d63ac0 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards beba477af4 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 258b0ad99b 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 94eb3f240a 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards c842547108 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards aa4e1b990f 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 6c6dcc3b94 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 842b907aec 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 54df098fc9 301: onsuccess: #2118: 1: Success after linux: 16 commits discards bd13abde5f 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 94ac56ccfd 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards c743e1913c 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards e801bdc2dc 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards ae8964fcd5 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 905eea02ea 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards eb6af7e2d1 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards f435c8a134 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards d13c7b535f 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards e227485925 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 953a9e0bda 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards bb948e8679 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 06296e3200 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards aace657f0b 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards d3a853dc2f 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards f0d8874c08 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 1532cf60cc 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 86f0d9e4a6 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards a3e7fd9629 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 0846d21e0d 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 10c89669d3 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 5bf492a834 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards f5d617337d 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 8fea2e2478 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 11eba28624 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards efe71d53a8 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 6ee1229d8d 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards f0742b46c4 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 52a3470d4f 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 2133097903 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 5a99732ffa 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 224727fa77 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards d7560234cf 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards e55fab4778 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 589f3b661f 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 5d91a0b622 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 351a142748 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards c31bad6528 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 3185ce54eb 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 8651caa5b1 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards c28eee23df 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards b00f7c8b37 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 443c6a8d34 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 48c14e0036 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards f6feca5120 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 8f959e2ef9 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards d0653f51cd 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 2d405308ac 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 7310117341 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 90b86be02f 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards d25d330523 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards e13a91a07e 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 1a699288a5 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards d7439f15db 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 0e4760c67b 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 9e506d4e27 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 510e97cf9c 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 313b8e5d11 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards fb2e9c5371 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards 5066d8428d 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards 16dd521cd3 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards f87658c675 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards ec1a731fa4 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 401f9a60eb 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 7b850707e5 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new 3f935a9a99 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new 89c6cd8de5 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new a7d5a7d68f 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new b8f80e0fc6 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new ec8676d2f2 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 6d24c2a1d9 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new e2c8b9557e 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 1ad5142c1b 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new a8addfbad6 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 509ff5d40e 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new c676bde5aa 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 0c0d9aed54 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 0c8210bcb7 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 49faa48700 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new e967bde8c7 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new c9c6c1dd99 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 2880342d8b 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 1689779a9b 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 1cf2880338 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new b22dfb25b7 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 08e1971dd6 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 8d46811724 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 2b8f20971e 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new b90115ed27 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new e36bcc6fdc 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 876b6b5c84 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new ae67119433 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new b83857a9b2 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 21063cb952 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 00058f56a4 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new f3492ac6f7 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 65eae2a006 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 142f60deb0 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new e35b6427af 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 1914fd28cc 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 56f33dd94b 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 48b6ab0ac0 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 7571d41bde 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 08b668ecd4 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 3f8bc17dc4 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 014c407752 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 75097f0856 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 2e8ce3a743 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 487aa56654 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 059015e216 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new d86d1a26c2 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new b708ff5329 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 9e9601db00 287: onsuccess: #2103: 1: Success after gcc: 9 commits new e95b6b74cb 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 1ab474f2c9 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new c475910e2f 290: onsuccess: #2106: 1: Success after gcc: 2 commits new e9d981e501 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 4a1f9bd93f 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new cbd87e181c 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 062bee2dcb 294: onsuccess: #2110: 1: Success after gcc: 17 commits new dbed0ac7e8 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 1c00da0f8a 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 7bd665a5ba 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 8cdb896001 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 3709d4d381 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 98f1f417a1 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 4030888c70 301: onsuccess: #2118: 1: Success after linux: 16 commits new b559547472 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new cde93bbeca 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 447226fef7 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 313059d4eb 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new a9c8529374 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 26838f1feb 307: onsuccess: #2124: 1: Success after gcc: 2 commits new e0c4979690 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new d9aded48cd 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 1794ca6a06 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 1d12e38e3a 311: onsuccess: #2130: 1: Success after gcc: 4 commits new e82449c06e 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 574e643219 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 5291dcb8b6 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new fc09516b32 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new a27bcc5607 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 32809d4eb0 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new e965718bd8 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 884bebd4ba 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 7187e18786 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 27f2258719 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new d3a40d924a 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 0e3b5d32ab 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 505c3a68a6 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 8a910efdaa 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new eb2c859e54 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 8af3e80cf5 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new a26ad4fd07 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 1d1655d11e 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new fb508161f8 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 99d83fba01 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 759ae3a30a 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new c16129e305 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new aab2f0fa4d 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new b08605598f 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new a28db6f5e4 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 7ab5907257 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new e92516a580 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 26906d9048 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 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 (64e52e6482) \ 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 1808 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2804 -> 2788 bytes 03-build_abe-binutils/console.log.xz | Bin 32252 -> 32420 bytes 04-build_abe-stage1/console.log.xz | Bin 93076 -> 92636 bytes 06-build_abe-linux/console.log.xz | Bin 8704 -> 8700 bytes 07-build_abe-glibc/console.log.xz | Bin 237964 -> 238272 bytes 08-build_abe-stage2/console.log.xz | Bin 231568 -> 231304 bytes 09-build_abe-gdb/console.log.xz | Bin 39648 -> 39692 bytes 10-build_abe-qemu/console.log.xz | Bin 31492 -> 31504 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3908 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2544 -> 2692 bytes 13-check_regression/console.log.xz | Bin 6304 -> 5592 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 30 +- 13-check_regression/results.compare2 | 20 +- 14-update_baseline/console.log | 78 +- 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 | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.xz | Bin 2689380 -> 2662812 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 2258412 -> 2271064 bytes sumfiles/gcc.sum | 2460 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 898892 -> 895108 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214088 -> 214136 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 440428 -> 429432 bytes sumfiles/libstdc++.sum | 2 +- 38 files changed, 1335 insertions(+), 1365 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-lts-allnoconfig updated (086c0505b1 -> 8bd6a14329)

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-release-aarch64-lts-allnoconfig in repository toolchain/ci/base-artifacts. from 086c0505b1 34: onsuccess: #440: boot: Success after binutils/gcc/qemu: [...] new 8bd6a14329 35: onsuccess: #441: 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 1788 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 31180 -> 31416 bytes 04-build_abe-stage1/console.log.xz | Bin 68632 -> 69488 bytes 05-build_abe-qemu/console.log.xz | Bin 32124 -> 32056 bytes 06-build_linux/console.log.xz | Bin 3360 -> 3336 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 3616 -> 3676 bytes 09-update_baseline/console.log | 8 ++++---- 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 ++++++++++++++-------------- 17 files changed, 25 insertions(+), 25 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-mainline-allyesconfig updated (883b1550f6 -> 0a3953b6a8)

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-release-arm-mainline-allyesconfig in repository toolchain/ci/base-artifacts. from 883b1550f6 38: onsuccess: #437: all: Success after binutils/gcc/linux/q [...] new 0a3953b6a8 39: onsuccess: #438: all: Success after binutils/gcc/linux/q [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1796 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 30656 -> 30408 bytes 04-build_abe-stage1/console.log.xz | Bin 87128 -> 86116 bytes 05-build_abe-qemu/console.log.xz | Bin 31636 -> 31056 bytes 06-build_linux/console.log.xz | Bin 3320 -> 3308 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4156 -> 4008 bytes 08-check_regression/mail-body.txt | 2 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 18 files changed, 26 insertions(+), 26 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch master updated (2ce074a7f85 -> 445a48a226f)

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 2ce074a7f85 IBM zSystems: Use NAND instruction to implement bit not new 445a48a226f tree-optimization/108353 - copyprop iteration order The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/testsuite/gcc.dg/tree-ssa/ssa-copyprop-3.c | 38 ++++++++++++++++++++++++++ gcc/tree-ssa-propagate.cc | 35 +++--------------------- 2 files changed, 42 insertions(+), 31 deletions(-) create mode 100644 gcc/testsuite/gcc.dg/tree-ssa/ssa-copyprop-3.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[binutils-gdb] branch master updated (f56532cc178 -> f1e19328594)

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 f56532cc178 gas/RISC-V: adjust assembler for opcode table re-ordering new f1e19328594 [gdb/testsuite] Fix gdb.threads/dlopen-libpthread.exp for u [...] 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/gdb.threads/dlopen-libpthread.exp | 30 ++++++++++++++++++++----- gdb/testsuite/lib/gdb.exp | 17 ++++++++++++++ 2 files changed, 41 insertions(+), 6 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/release-arm updated (9b84767a1a -> 47a720534a)

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/release-arm in repository toolchain/ci/base-artifacts. from 9b84767a1a 31: onsuccess: #152: 7: Success after gcc/linux/qemu: 332 commits new 47a720534a 32: onsuccess: #153: 7: Success after gcc/glibc/qemu: 128 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1732 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2784 bytes 04-build_abe-binutils/console.log.xz | Bin 30432 -> 30216 bytes 05-build_abe-stage1/console.log.xz | Bin 87844 -> 86680 bytes 07-build_abe-linux/console.log.xz | Bin 8704 -> 8684 bytes 08-build_abe-glibc/console.log.xz | Bin 230044 -> 229152 bytes 09-build_abe-stage2/console.log.xz | Bin 221012 -> 221016 bytes 10-build_abe-gdb/console.log.xz | Bin 36948 -> 36876 bytes 11-build_abe-qemu/console.log.xz | Bin 30932 -> 31520 bytes 12-check_regression/console.log.xz | Bin 4104 -> 4044 bytes dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 18 files changed, 23 insertions(+), 23 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch master updated (0986c351aa8 -> 2ce074a7f85)

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 0986c351aa8 fortran: Fix up function types for realloc and sincos{,f,l} [...] new 2ce074a7f85 IBM zSystems: Use NAND instruction to implement bit not 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/config/s390/s390.md | 8 ++++++++ gcc/testsuite/gcc.target/s390/not.c | 11 +++++++++++ 2 files changed, 19 insertions(+) create mode 100644 gcc/testsuite/gcc.target/s390/not.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits January 2023