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 (a78fdc2779 -> e067a17678)

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 a78fdc2779 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 9fc67ae714 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards c85150bab9 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards e837997d44 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards c77ed5ed66 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 46ca20c662 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards b2fe92119e 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards eb22e09a83 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards e885583d21 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards c7ab8548a7 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards e8d0be12e0 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 7608a1d004 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards f2df72bd2e 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 5cacffb072 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 131b83f796 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 4c2cbbf23d 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 12b79d166b 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 2135747166 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards bf329343a5 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 81dd6dff03 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 37955c6600 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 66c663f030 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards d9fcff59cd 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards d326b76ea9 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 0b915a565c 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 8e995ebb61 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 87f60b70f0 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 3f535a97df 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 5f18e676e2 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards a7b1cc359e 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards a361f583cb 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 20b808b535 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 089d565311 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards f6d88d51b3 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 3c995f405d 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 03d4dd90b8 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 72b918eeae 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 780efc81f4 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards aeb2426ba9 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 9cc64889ab 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 900fb96af9 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards dd4a1e44ff 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 03f9ec0467 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards a949989213 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 1fcdc06a07 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards ead5b6f03a 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 0bd960e9da 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards b8231a1cd2 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 515725e48c 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 1f20adadd5 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards d388e7c3d9 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards f60215649f 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 994f54d718 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 38af4e331d 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 3ba493e228 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards fdd4987c1f 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 3a319324c9 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 6aab94eb6c 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 9f504b3cd6 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 0941a0ae2f 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards b1b0d1c79b 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 7c6b21cb01 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 8666e05e00 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 4665bfdb8e 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 87fd651598 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 295f22741b 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 2c03874212 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards a48fddef6e 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 8b7c82fee3 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 9d751b01d0 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards bfd680518b 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 25858eb1b8 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 65cfff9750 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards d7a118d26f 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards c8b9dc4e91 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 70b77fe9c5 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards a9dea981d4 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 61b0673e6c 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 86d0084a07 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards a4fb1439ce 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 6fa0f61465 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards ff90939881 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 5cfe9e2868 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 17c3fb494c 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 08ad27dbb8 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 0537485319 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards a484e064e5 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards fc29498221 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 015ee3360f 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards 140a740592 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards ef8a9f4c96 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards 22e072f833 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards e479610ebd 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards c1ef2dc833 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards c38712aeb7 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards db0b9a4245 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards 30ae7a215f 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards 127cefd6d1 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards cb870631c9 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards 13b830cc45 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 88daec143e 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new cd2d47d62f 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 4fb77e4b17 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 2a4ab42eb1 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new 6a3f8a3c96 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new a2165b8c4b 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new edc10ba149 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 321245f26f 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new 629848f954 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new bf9f85ba57 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 66deabb8a1 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new 1e938928f2 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new d0973bc0fe 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 6d77698a13 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new d2b22a8282 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new a0114da385 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 2b46b17712 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new 74e40576cf 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new fe5e48774a 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new b4a359fd84 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new c870dbb621 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 4128980862 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 6074726271 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new c05362b5be 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 2d78560643 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 42c3f361ad 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new ca689420bd 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new a56967db4f 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new a4236e87a6 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new f21924df2b 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 2fbaf50af9 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new d00eadbbc9 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 03105dcaac 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 618a960609 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 8d041b899d 273: onsuccess: #2521: 1: Success after gcc: 2 commits new c104cda994 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 14389c075f 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 8dcbba79d7 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 0a6a9a6f38 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 4d2508102c 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 3056b2eb2d 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 711d910bf2 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 4d58d7270e 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new ccd1972997 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new cab67e1677 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 61724dad94 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new ccef26bd00 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new fe14651be2 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new d9093e012d 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 4f93c17efd 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new d8e9de866d 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new d9b71e52b6 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 7057d771b3 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 321b48a5c3 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 64bf85ff27 293: onsuccess: #2542: 1: Success after gcc: 5 commits new be35c134ef 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new f6683a54ed 295: onsuccess: #2545: 1: Success after linux: 10 commits new b482b8980b 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new c42ce0550e 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 5a03cb2014 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 7a69583781 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 17dc975172 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new e0d263627b 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new a619aa15b9 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 75d8c0315b 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new aa64e0a409 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 36b11d2458 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 3cdc7ce62a 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 3912f6cde6 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 66f977be5b 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new c4a187d81d 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 1d0555e80c 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 80737b7dae 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 89b0f8a79d 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new f2ecedaf54 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new f38d44a35c 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new cab6b360b6 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new a45b616206 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new df3b79432c 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new bb5af54d79 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 5f52faa1eb 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 8117dba758 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 21e362bfba 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 924809f2f0 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new ce5e5fc2df 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new c7585a1fd5 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 125fde25f1 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 8b73b57dc0 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 08f8cc6b40 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 82365fec23 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 341ab9327c 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 03dfa7aae2 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 3547276780 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new dc06c25a2e 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new eee7a66736 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 36416e6959 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new a2441d6d39 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 081163c053 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new f775e25905 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 2086307b1c 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new bf6a3628f0 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 10becbe593 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new e067a17678 341: onsuccess: #2591: 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 (a78fdc2779) \ 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 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 32468 -> 32272 bytes 04-build_abe-stage1/console.log.xz | Bin 73192 -> 74828 bytes 06-build_abe-linux/console.log.xz | Bin 8352 -> 9104 bytes 07-build_abe-glibc/console.log.xz | Bin 244628 -> 245740 bytes 08-build_abe-stage2/console.log.xz | Bin 204604 -> 206332 bytes 09-build_abe-gdb/console.log.xz | Bin 39616 -> 39148 bytes 10-build_abe-qemu/console.log.xz | Bin 32500 -> 31996 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3892 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2812 -> 3016 bytes 13-check_regression/console.log.xz | Bin 7876 -> 7592 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 37 +- 13-check_regression/mail-body.txt | 107 +- 13-check_regression/results.compare | 61 +- 13-check_regression/results.compare2 | 228 +- 13-check_regression/results.regressions | 61 +- 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 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 109 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 61 +- sumfiles/g++.log.xz | Bin 3408532 -> 3417696 bytes sumfiles/g++.sum | 32 +- sumfiles/gcc.log.xz | Bin 3047880 -> 3035272 bytes sumfiles/gcc.sum | 4516 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1043016 -> 1041084 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214684 -> 214732 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2692 -> 2704 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 433284 -> 431136 bytes sumfiles/libstdc++.sum | 8 +- 44 files changed, 2678 insertions(+), 2683 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-lts-defconfig updated (1ebe8d142b -> 3cbef013b2)

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-lts-defconfig in repository toolchain/ci/base-artifacts. from 1ebe8d142b 39: onsuccess: #454: boot: Success after linux: 307 commits new 3cbef013b2 40: onsuccess: #455: boot: Success after binutils: 115 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 1736 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 32800 -> 32420 bytes 04-build_kernel_llvm/console.log.xz | Bin 65504 -> 65432 bytes 05-build_abe-qemu/console.log.xz | Bin 31564 -> 31628 bytes 06-build_linux/console.log.xz | Bin 3380 -> 3532 bytes 07-boot_linux/console.log.xz | Bin 5824 -> 5832 bytes 08-check_regression/console.log.xz | Bin 2904 -> 2928 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +++++++------- 14 files changed, 12 insertions(+), 12 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/master-aarch64 updated (e20de6afcf -> 6dc45516d7)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards e20de6afcf 180: onsuccess: #606: 6: Success after binutils/gcc/linux/gd [...] discards fe3280fe35 179: onsuccess: #605: 6: Success after binutils/gcc/linux/gl [...] discards 480213e9e4 178: onsuccess: #604: 6: Success after binutils/gcc/linux/gl [...] discards 42972cf596 177: onsuccess: #603: 6: Success after binutils/gcc/linux/gl [...] discards 63082f368d 176: onsuccess: #601: 6: Success after binutils/gcc/linux/gd [...] discards c03746504b 175: onsuccess: #600: 6: Success after binutils/gcc/linux/gl [...] discards 5e2e95a5b5 174: onsuccess: #599: 6: Success after binutils/gcc/linux/gl [...] discards bd810b6732 173: onsuccess: #598: 6: Success after binutils/gcc/linux/gl [...] discards 3c1b985ef7 172: onsuccess: #597: 6: Success after binutils/gcc/glibc/gd [...] discards c34c25d232 171: onsuccess: #596: 5: Success after gdb: 21 commits discards 003cb9958c 170: force: #595: 5: Failure after gdb-13-branchpoint-245-gd [...] discards 5fd44b208c 169: force: #594: 6: Success after gdb: 2 commits discards 9b29b91b39 168: onsuccess: #593: 6: Success after linux: 10 commits discards 96ecdb4360 167: onsuccess: #592: 6: Success after glibc-2.36.9000-416-g [...] discards 906324f10b 166: onsuccess: #590: 6: Success after gcc: 23 commits discards 99c34e2a0e 165: onsuccess: #589: 6: Success after binutils: 24 commits discards 0d17eb61fc 164: onsuccess: #587: 6: Success after binutils/gcc/linux/gl [...] discards 6a150369fb 163: onsuccess: #586: 6: Success after binutils/gcc/linux/gd [...] discards b476b20644 162: onsuccess: #585: 6: Success after binutils/gcc/linux/gd [...] discards d19ddb25e2 161: onsuccess: #584: 6: Success after binutils/gcc/linux/gl [...] discards 2c75c28c6e 160: onsuccess: #583: 6: Success after binutils/gcc/gdb: 11 commits discards 4a6204ba70 159: onsuccess: #582: 6: Success after binutils/gcc/gdb: 26 commits discards ad28c93369 158: onsuccess: #581: 6: Success after binutils/gcc/gdb: 25 commits discards c9ec1ba4a7 157: onsuccess: #580: 6: Success after binutils/gcc/linux/gd [...] discards 5b50166795 156: onsuccess: #579: 6: Success after binutils/gcc/gdb: 47 commits discards 00a1a0b2cf 155: onsuccess: #578: 6: Success after binutils/gcc/linux/gd [...] discards b9b9c0351a 154: onsuccess: #577: 6: Success after binutils/gcc/linux/gl [...] discards a4ff40eacc 153: onsuccess: #576: 6: Success after binutils/gcc/linux/gl [...] discards 5e433784f2 152: onsuccess: #575: 6: Success after binutils/gcc/linux/gl [...] discards 97d9488d24 151: onsuccess: #574: 6: Success after binutils/gcc/linux/gl [...] discards fb26203fba 150: onsuccess: #573: 6: Success after binutils/gcc/glibc/gd [...] discards dfadddb5c8 149: onsuccess: #572: 6: Success after binutils/gcc/linux/gd [...] discards eb9640c030 148: onsuccess: #571: 6: Success after binutils/gcc/linux/gd [...] discards c2d6a31598 147: onsuccess: #570: 6: Success after binutils/gcc/linux/gl [...] discards 4559b7480f 146: onsuccess: #569: 6: Success after binutils/gcc/linux/gd [...] discards 44e294121c 145: onsuccess: #568: 6: Success after binutils/gcc/linux/gl [...] discards 83f884663a 144: onsuccess: #567: 4: Success after gcc: 12 commits discards 06f184dc8b 143: force: #566: 4: Failure after basepoints/gcc-13-4618-g1 [...] discards de2fdfb183 142: force: #565: 6: Success after gcc: 8 commits discards f579cf68ae 141: onsuccess: #564: 6: Success after linux: 3224 commits discards 396994e31f 140: onsuccess: #563: 6: Success after glibc: 2 commits discards 46d8de9600 139: onsuccess: #561: 6: Success after binutils: 23 commits discards 332f4cb949 138: onsuccess: #559: 6: Success after binutils/gcc/linux/gd [...] discards a7a8b426ec 137: onsuccess: #558: 6: Success after binutils/gcc/linux/gl [...] discards 0971add06b 136: onsuccess: #557: 6: Success after binutils/gcc/linux/gl [...] discards d08117a79a 135: onsuccess: #556: 6: Success after binutils/gcc/linux/gl [...] discards e80d966ca3 134: onsuccess: #555: 6: Success after binutils/gcc/linux/gl [...] discards 8673e2f166 133: onsuccess: #554: 6: Success after binutils/gcc/linux/gd [...] discards 36330d7100 132: onsuccess: #553: 4: Success after basepoints/gcc-13-449 [...] discards 012da2d921 131: force: #552: 4: Failure after basepoints/gcc-13-4492-g4 [...] discards c16280fa8a 130: force: #551: 6: Success after gcc: 10 commits discards 5387541cc1 129: onsuccess: #548: 6: Success after binutils: 8 commits discards 11968a7b02 128: onsuccess: #546: 6: Success after binutils/gcc/linux/gd [...] discards b90b676b03 127: onsuccess: #545: 6: Success after binutils/gcc/linux/gl [...] discards 425c6eadc4 126: onsuccess: #544: 6: Success after binutils/gcc/linux/gd [...] discards 21fbe8a348 125: onsuccess: #543: 6: Success after binutils/gcc/linux/gd [...] discards 3167e0f8ea 124: onsuccess: #542: 6: Success after binutils/gcc/linux/gl [...] discards 9dc78bd41e 123: onsuccess: #541: 6: Success after binutils/gcc/linux/gl [...] discards 2cc8adbe52 122: onsuccess: #540: 6: Success after binutils/gcc/linux/gl [...] discards 9d616a843b 121: onsuccess: #539: 6: Success after binutils/gcc/linux/gd [...] discards 7bc389d312 120: onsuccess: #538: 6: Success after binutils/gcc/linux/gd [...] discards 5a810915b2 119: onsuccess: #537: 6: Success after binutils/gcc/linux/gd [...] discards 92c94373ce 118: onsuccess: #536: 6: Success after binutils/gcc/linux/gd [...] discards 785a55fc01 117: onsuccess: #535: 6: Success after binutils/gcc/gdb: 72 commits discards cff3fee048 116: onsuccess: #534: 6: Success after binutils/gcc/glibc/gd [...] discards 06ab7e0710 115: onsuccess: #533: 6: Success after binutils/gcc/linux/gd [...] discards c711ee0675 114: onsuccess: #532: 6: Success after binutils/gcc/linux/gd [...] discards e0921b72b3 113: onsuccess: #531: 6: Success after binutils/gcc/linux/gd [...] discards 79078b5355 112: onsuccess: #530: 6: Success after binutils/gcc/linux/gl [...] discards 2eb36c62d0 111: onsuccess: #529: 6: Success after binutils/gcc/linux/gd [...] discards cc7a89654b 110: onsuccess: #528: 6: Success after binutils/gcc/gdb: 13 commits discards 78bfdb04fd 109: onsuccess: #527: 6: Success after binutils/gcc/linux/gd [...] discards d0a49e69b6 108: onsuccess: #526: 6: Success after binutils/gcc/linux/gl [...] discards 9b06080fdf 107: onsuccess: #525: 1: Success after binutils/gcc: 11 commits discards c27d8e0301 106: onsuccess: #524: 1: Success after gcc: 11 commits discards 7cf73ae268 105: force: #523: 1: Failure after basepoints/gcc-13-3918-gb [...] discards ffcaf61b24 104: force: #522: 6: Success after gcc: 24 commits discards 25b62647c9 103: onsuccess: #520: 6: Success after binutils: 10 commits discards cf9ce23a0c 102: onsuccess: #518: 6: Success after binutils/gcc/linux/gl [...] discards a4e3efa995 101: onsuccess: #517: 6: Success after binutils/gcc/linux/gl [...] discards 8c84551720 100: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] discards c1dd3671a3 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gli [...] discards 466ddd2744 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gdb [...] discards f12f9afbc5 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gdb [...] discards c941807b0f 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gli [...] discards 1764f2a2c1 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gli [...] discards 7986137103 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gli [...] discards 174c9b626e 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gli [...] discards 2180cea4b0 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gli [...] discards bf5547a6e6 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gli [...] discards 572f796669 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gdb [...] discards 9b6f16ff56 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gli [...] discards 41afa5fd45 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gli [...] discards 99c14c7d16 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gli [...] discards cd7d72d390 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gli [...] discards 294dabd26f 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gli [...] discards c8c9b9ac43 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gdb [...] discards 11658b594e 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gdb [...] discards ddeef32f00 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gdb [...] discards f33a980a56 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gli [...] discards 9740b80c9f 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gdb [...] new 56b0c2f324 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gdb [...] new 8b62f03a19 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gli [...] new 12f3bd8474 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gdb [...] new 49900a84e9 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gdb [...] new 85a44aaf0a 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gdb [...] new e071770418 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gli [...] new 661893b0ec 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gli [...] new c6be6412d5 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gli [...] new 748416bea0 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gli [...] new 146b27568a 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gli [...] new 8583e94291 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gdb [...] new b29392fdc6 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gli [...] new 94d2ad11b7 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gli [...] new 7beffb2dff 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gli [...] new 57def8f2a9 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gli [...] new 05d80a98a9 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gli [...] new 4ee42bc964 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gli [...] new 608729b376 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gdb [...] new e74bddc4ef 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gdb [...] new 8c347ad831 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gli [...] new d982e5a6c9 100: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] new 3dcdf7c9df 101: onsuccess: #517: 6: Success after binutils/gcc/linux/gl [...] new 9865fe5826 102: onsuccess: #518: 6: Success after binutils/gcc/linux/gl [...] new a4e10bf370 103: onsuccess: #520: 6: Success after binutils: 10 commits new 896184a60b 104: force: #522: 6: Success after gcc: 24 commits new b3dde86bee 105: force: #523: 1: Failure after basepoints/gcc-13-3918-gb [...] new 2cb19848ae 106: onsuccess: #524: 1: Success after gcc: 11 commits new e589247592 107: onsuccess: #525: 1: Success after binutils/gcc: 11 commits new 46db2e9c4f 108: onsuccess: #526: 6: Success after binutils/gcc/linux/gl [...] new c742db75e9 109: onsuccess: #527: 6: Success after binutils/gcc/linux/gd [...] new af9cb5eb98 110: onsuccess: #528: 6: Success after binutils/gcc/gdb: 13 commits new 92afb05052 111: onsuccess: #529: 6: Success after binutils/gcc/linux/gd [...] new 61f57f6942 112: onsuccess: #530: 6: Success after binutils/gcc/linux/gl [...] new 7555db65e3 113: onsuccess: #531: 6: Success after binutils/gcc/linux/gd [...] new 099a09fa51 114: onsuccess: #532: 6: Success after binutils/gcc/linux/gd [...] new 2aa6d00569 115: onsuccess: #533: 6: Success after binutils/gcc/linux/gd [...] new 76d7253397 116: onsuccess: #534: 6: Success after binutils/gcc/glibc/gd [...] new daf51b9aef 117: onsuccess: #535: 6: Success after binutils/gcc/gdb: 72 commits new 85955ee1e9 118: onsuccess: #536: 6: Success after binutils/gcc/linux/gd [...] new 4925cba05e 119: onsuccess: #537: 6: Success after binutils/gcc/linux/gd [...] new 9168da8d1c 120: onsuccess: #538: 6: Success after binutils/gcc/linux/gd [...] new 99c25dd6f6 121: onsuccess: #539: 6: Success after binutils/gcc/linux/gd [...] new 73b836f1d0 122: onsuccess: #540: 6: Success after binutils/gcc/linux/gl [...] new a2fc6e5bee 123: onsuccess: #541: 6: Success after binutils/gcc/linux/gl [...] new 0c186577c8 124: onsuccess: #542: 6: Success after binutils/gcc/linux/gl [...] new f710204945 125: onsuccess: #543: 6: Success after binutils/gcc/linux/gd [...] new 6940bc5848 126: onsuccess: #544: 6: Success after binutils/gcc/linux/gd [...] new 583e90a9a2 127: onsuccess: #545: 6: Success after binutils/gcc/linux/gl [...] new a8f635a529 128: onsuccess: #546: 6: Success after binutils/gcc/linux/gd [...] new 1bda745d43 129: onsuccess: #548: 6: Success after binutils: 8 commits new 817f91a14b 130: force: #551: 6: Success after gcc: 10 commits new c9091ad461 131: force: #552: 4: Failure after basepoints/gcc-13-4492-g4 [...] new f51a17eec0 132: onsuccess: #553: 4: Success after basepoints/gcc-13-449 [...] new ede8a0140e 133: onsuccess: #554: 6: Success after binutils/gcc/linux/gd [...] new 1b7cb71bce 134: onsuccess: #555: 6: Success after binutils/gcc/linux/gl [...] new b8a9b4b88e 135: onsuccess: #556: 6: Success after binutils/gcc/linux/gl [...] new 75898df07a 136: onsuccess: #557: 6: Success after binutils/gcc/linux/gl [...] new 461ee7130d 137: onsuccess: #558: 6: Success after binutils/gcc/linux/gl [...] new 34a37375c7 138: onsuccess: #559: 6: Success after binutils/gcc/linux/gd [...] new ba4f5b1804 139: onsuccess: #561: 6: Success after binutils: 23 commits new 9bcbb311a5 140: onsuccess: #563: 6: Success after glibc: 2 commits new 7e8e028696 141: onsuccess: #564: 6: Success after linux: 3224 commits new d5d773e82a 142: force: #565: 6: Success after gcc: 8 commits new 6db7782953 143: force: #566: 4: Failure after basepoints/gcc-13-4618-g1 [...] new 708b603795 144: onsuccess: #567: 4: Success after gcc: 12 commits new 948e461bb0 145: onsuccess: #568: 6: Success after binutils/gcc/linux/gl [...] new 9dded18c0a 146: onsuccess: #569: 6: Success after binutils/gcc/linux/gd [...] new 9d7b2d2ed6 147: onsuccess: #570: 6: Success after binutils/gcc/linux/gl [...] new aa4e4fbf98 148: onsuccess: #571: 6: Success after binutils/gcc/linux/gd [...] new b2fbfc9765 149: onsuccess: #572: 6: Success after binutils/gcc/linux/gd [...] new 6591f2f45e 150: onsuccess: #573: 6: Success after binutils/gcc/glibc/gd [...] new 5556a5d551 151: onsuccess: #574: 6: Success after binutils/gcc/linux/gl [...] new e2d7ed6d62 152: onsuccess: #575: 6: Success after binutils/gcc/linux/gl [...] new de814b9a8c 153: onsuccess: #576: 6: Success after binutils/gcc/linux/gl [...] new ca8b22f689 154: onsuccess: #577: 6: Success after binutils/gcc/linux/gl [...] new 1c9bc053b0 155: onsuccess: #578: 6: Success after binutils/gcc/linux/gd [...] new 1041f535a3 156: onsuccess: #579: 6: Success after binutils/gcc/gdb: 47 commits new 80d19e0d26 157: onsuccess: #580: 6: Success after binutils/gcc/linux/gd [...] new 4660990eea 158: onsuccess: #581: 6: Success after binutils/gcc/gdb: 25 commits new a4f9ddbe2a 159: onsuccess: #582: 6: Success after binutils/gcc/gdb: 26 commits new 3993f051cb 160: onsuccess: #583: 6: Success after binutils/gcc/gdb: 11 commits new 09a13c9757 161: onsuccess: #584: 6: Success after binutils/gcc/linux/gl [...] new dfd736b080 162: onsuccess: #585: 6: Success after binutils/gcc/linux/gd [...] new 4ce6fa4c92 163: onsuccess: #586: 6: Success after binutils/gcc/linux/gd [...] new dde5bfe51c 164: onsuccess: #587: 6: Success after binutils/gcc/linux/gl [...] new 1b58965d99 165: onsuccess: #589: 6: Success after binutils: 24 commits new a63938575b 166: onsuccess: #590: 6: Success after gcc: 23 commits new 0b11562f7f 167: onsuccess: #592: 6: Success after glibc-2.36.9000-416-g [...] new db1a64ac2b 168: onsuccess: #593: 6: Success after linux: 10 commits new 25891f4f9d 169: force: #594: 6: Success after gdb: 2 commits new e33e756c51 170: force: #595: 5: Failure after gdb-13-branchpoint-245-gd [...] new b318924dd6 171: onsuccess: #596: 5: Success after gdb: 21 commits new a394771d00 172: onsuccess: #597: 6: Success after binutils/gcc/glibc/gd [...] new 90671248d7 173: onsuccess: #598: 6: Success after binutils/gcc/linux/gl [...] new 81b3319eb4 174: onsuccess: #599: 6: Success after binutils/gcc/linux/gl [...] new 56a462f6fc 175: onsuccess: #600: 6: Success after binutils/gcc/linux/gl [...] new 3053dc0350 176: onsuccess: #601: 6: Success after binutils/gcc/linux/gd [...] new 895e4368a2 177: onsuccess: #603: 6: Success after binutils/gcc/linux/gl [...] new 7b960e8e4c 178: onsuccess: #604: 6: Success after binutils/gcc/linux/gl [...] new 035e7fd8a6 179: onsuccess: #605: 6: Success after binutils/gcc/linux/gl [...] new 35c573fa82 180: onsuccess: #606: 6: Success after binutils/gcc/linux/gd [...] new 6dc45516d7 181: onsuccess: #607: 6: Success after binutils/gcc/linux/gl [...] 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 (e20de6afcf) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/master- [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1740 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2752 bytes 04-build_abe-binutils/console.log.xz | Bin 39236 -> 40028 bytes 05-build_abe-gcc/console.log.xz | Bin 214196 -> 216772 bytes 06-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 07-build_abe-linux/console.log.xz | Bin 8260 -> 9180 bytes 08-build_abe-glibc/console.log.xz | Bin 244856 -> 247036 bytes 09-build_abe-gdb/console.log.xz | Bin 39108 -> 39644 bytes 10-check_regression/console.log.xz | Bin 4032 -> 4308 bytes 11-update_baseline/console.log | 60 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +++++++++++----------- 20 files changed, 58 insertions(+), 58 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_O3 updated (5c5e6b1e06 -> d1bc4419bd)

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_O3 in repository toolchain/ci/base-artifacts. discards 5c5e6b1e06 162: onsuccess: #595: 2: Success after binutils/gcc: 36 commits discards c8a5185054 161: onsuccess: #594: 2: Success after binutils/gcc: 135 commits discards 115f99404b 160: onsuccess: #593: 2: Success after binutils/gcc: 40 commits discards 4c67360603 159: onsuccess: #592: 2: Success after binutils/gcc: 131 commits discards 2b312191d8 158: onsuccess: #588: 2: Success after binutils/gcc: 6 commits discards 94c118b290 157: onsuccess: #587: 2: Success after binutils/gcc: 16 commits discards f002c373f3 156: onsuccess: #586: 2: Success after binutils/gcc: 55 commits discards 096942cb8c 155: onsuccess: #585: 2: Success after binutils/gcc: 36 commits discards b86c3dbe28 154: onsuccess: #584: 2: Success after binutils/gcc: 36 commits discards ec7c77bc2f 153: onsuccess: #583: 2: Success after binutils/gcc: 45 commits discards c7c7186e83 152: onsuccess: #582: 2: Success after binutils/gcc: 25 commits discards 932ac75519 151: onsuccess: #581: 2: Success after binutils/gcc: 12 commits discards bb3c7caa2e 150: onsuccess: #580: 2: Success after binutils/gcc: 19 commits discards 2ed9f6957d 149: onsuccess: #579: 2: Success after binutils/gcc: 20 commits discards da4ebb4fcc 148: onsuccess: #578: 2: Success after binutils/gcc: 7 commits discards e66e10d1c2 147: onsuccess: #577: 2: Success after binutils/gcc: 22 commits discards fde8b259b9 146: onsuccess: #576: 2: Success after binutils/gcc: 16 commits discards e5ed263d33 145: onsuccess: #575: 2: Success after binutils/gcc: 6 commits discards 2754f29773 144: onsuccess: #574: 2: Success after binutils/gcc: 26 commits discards 29daa7e8d1 143: onsuccess: #573: 2: Success after binutils/gcc: 35 commits discards cd3e0af18b 142: onsuccess: #572: 2: Success after binutils/gcc: 74 commits discards 9daff9a81b 141: onsuccess: #571: 2: Success after binutils/gcc: 43 commits discards 41d3fb579c 140: onsuccess: #570: 2: Success after binutils/gcc: 56 commits discards c40d0f8135 139: onsuccess: #569: 2: Success after binutils/gcc: 42 commits discards ae6235b8ab 138: onsuccess: #568: 2: Success after binutils/gcc: 22 commits discards 0c4e9ca64e 137: onsuccess: #567: 2: Success after binutils/gcc: 10 commits discards 7ce8bc6e73 136: onsuccess: #566: 2: Success after binutils/gcc: 37 commits discards 3acdd5ba02 135: onsuccess: #565: 2: Success after binutils/gcc: 40 commits discards 03892b3782 134: onsuccess: #564: 1: Success after binutils/gcc: 30 commits discards 2ee2ea1282 133: onsuccess: #563: 1: Success after binutils/gcc: 108 commits discards 86fc088469 132: onsuccess: #562: 1: Success after baseline build: no ne [...] discards 1a724229e5 131: force: #561: 1: Failure after gdb-12-branchpoint-3046-g [...] discards 6119a9878a 130: force: #560: 2: Success after binutils: 21 commits discards 07acfe4bb0 129: onsuccess: #556: 2: Success after binutils/gcc: 23 commits discards 2b3abe22f4 128: onsuccess: #555: 2: Success after binutils/gcc: 4 commits discards 883b257678 127: onsuccess: #554: 2: Success after binutils/gcc: 20 commits discards 48f742d4cc 126: onsuccess: #553: 2: Success after binutils/gcc: 36 commits discards f4ab2cd26d 125: onsuccess: #552: 2: Success after binutils/gcc: 25 commits discards 9c7d1a47ec 124: onsuccess: #551: 2: Success after binutils/gcc: 41 commits discards e70421ca9f 123: onsuccess: #550: 2: Success after binutils/gcc: 40 commits discards 100dd9c3a9 122: onsuccess: #549: 2: Success after binutils/gcc: 20 commits discards 769b5a0a54 121: onsuccess: #548: 2: Success after binutils/gcc: 9 commits discards 2bcd808162 120: onsuccess: #547: 2: Success after binutils/gcc: 17 commits discards 8bf4caee3c 119: onsuccess: #546: 2: Success after binutils/gcc: 47 commits discards 2758372148 118: onsuccess: #545: 2: Success after binutils/gcc: 48 commits discards d16bbd82e8 117: onsuccess: #544: 2: Success after binutils/gcc: 31 commits discards e003a59437 116: onsuccess: #543: 2: Success after binutils/gcc: 73 commits discards 80ff038275 115: onsuccess: #542: 1: Success after binutils/gcc: 58 commits discards 4b49ec8d93 114: onsuccess: #541: 1: Success after binutils/gcc: 8 commits discards a15650f45b 113: onsuccess: #540: 1: Success after binutils/gcc: 11 commits discards 9ed55b5995 112: onsuccess: #539: 1: Success after binutils/gcc: 31 commits discards e87b39cffe 111: onsuccess: #538: 1: Success after binutils/gcc: 39 commits discards dcc8badd81 110: onsuccess: #537: 1: Success after binutils/gcc: 51 commits discards bcaedfbfb8 109: onsuccess: #536: 1: Success after gcc: 2 commits discards ec426ed0c6 108: force: #535: 1: Failure after basepoints/gcc-13-4227-g0 [...] discards 7d51298e31 107: force: #534: 2: Success after gcc: 26 commits discards fee62bbb79 106: onsuccess: #532: 2: Success after binutils: 12 commits discards 1936818e3b 105: onsuccess: #530: 2: Success after binutils/gcc: 32 commits discards 5ca49bb286 104: onsuccess: #529: 2: Success after binutils/gcc: 11 commits discards 2de21e707f 103: onsuccess: #528: 2: Success after binutils/gcc: 40 commits discards 8a56a54806 102: onsuccess: #527: 2: Success after binutils/gcc: 32 commits discards 24ba340079 101: onsuccess: #526: 2: Success after binutils/gcc: 52 commits discards cd7f5e2786 100: onsuccess: #525: 2: Success after binutils/gcc: 128 commits discards 5a10dbf6f2 99: onsuccess: #523: 2: Success after binutils/gcc: 84 commits discards 7e17211017 98: onsuccess: #522: 1: Success after gcc: 11 commits discards d29657d734 97: force: #521: 1: Failure after basepoints/gcc-13-3918-gba [...] discards f00428ffd1 96: force: #520: 2: Success after gcc: 24 commits discards 282cbae31b 95: onsuccess: #518: 2: Success after binutils: 10 commits discards 42520e4a21 94: onsuccess: #516: 2: Success after binutils/gcc: 58 commits discards 760423b82a 93: onsuccess: #515: 2: Success after binutils/gcc: 47 commits discards 0f6afe789b 92: onsuccess: #514: 2: Success after binutils/gcc: 58 commits discards 1e54978677 91: onsuccess: #513: 2: Success after binutils/gcc: 71 commits discards 55855414f4 90: onsuccess: #512: 2: Success after binutils/gcc: 50 commits discards 56dc3e1d26 89: onsuccess: #511: 2: Success after binutils/gcc: 20 commits discards 3065f761c9 88: onsuccess: #510: 2: Success after binutils/gcc: 55 commits discards d2ba22d05b 87: onsuccess: #509: 2: Success after binutils/gcc: 58 commits discards 91b7a58fc7 86: onsuccess: #508: 2: Success after binutils/gcc: 29 commits discards c735c9e30d 85: onsuccess: #507: 2: Success after binutils/gcc: 27 commits discards 82b1541e35 84: onsuccess: #506: 2: Success after binutils/gcc: 37 commits discards 697756eee4 83: onsuccess: #505: 2: Success after binutils/gcc: 15 commits discards d083c1325d 82: onsuccess: #504: 2: Success after binutils/gcc: 6 commits discards 0c1839e8d3 81: onsuccess: #503: 2: Success after binutils/gcc: 38 commits discards cb15ca2aa1 80: onsuccess: #502: 2: Success after binutils/gcc: 31 commits discards 9ff0a7e1fb 79: onsuccess: #501: 2: Success after binutils/gcc: 28 commits discards eaf276c211 78: onsuccess: #500: 2: Success after binutils/gcc: 37 commits discards f9f250df57 77: onsuccess: #499: 2: Success after binutils/gcc: 48 commits discards 99dbf6bb55 76: onsuccess: #498: 2: Success after binutils/gcc: 16 commits discards a685f8b0b5 75: onsuccess: #497: 2: Success after binutils/gcc: 5 commits discards 0d3bdb5896 74: onsuccess: #496: 2: Success after binutils/gcc: 15 commits discards 268dcd6efe 73: onsuccess: #495: 2: Success after binutils/gcc: 50 commits discards fcdc438942 72: onsuccess: #494: 2: Success after binutils/gcc: 54 commits discards fe927342ff 71: onsuccess: #493: 2: Success after binutils/gcc: 50 commits discards 987c713aa1 70: onsuccess: #492: 2: Success after binutils/gcc: 42 commits discards eb2435aac6 69: onsuccess: #491: 2: Success after binutils/gcc: 19 commits discards 539158d23e 68: onsuccess: #490: 2: Success after binutils/gcc: 8 commits discards b085e4e30b 67: onsuccess: #489: 2: Success after binutils/gcc: 23 commits discards 842f92342c 66: onsuccess: #488: 2: Success after binutils/gcc: 51 commits discards ef7cefa577 65: onsuccess: #487: 2: Success after binutils/gcc: 35 commits discards c98a5d551a 64: onsuccess: #486: 1: Success after binutils/gcc: 48 commits discards ccf0833b6f 63: onsuccess: #485: 1: Success after binutils/gcc: 55 commits discards 6776340df5 62: onsuccess: #484: 1: Success after binutils/gcc: 31 commits new dfd12835d2 62: onsuccess: #484: 1: Success after binutils/gcc: 31 commits new 823dc940c3 63: onsuccess: #485: 1: Success after binutils/gcc: 55 commits new 0d35ab00c4 64: onsuccess: #486: 1: Success after binutils/gcc: 48 commits new 2068dc3f2d 65: onsuccess: #487: 2: Success after binutils/gcc: 35 commits new 231dce3d09 66: onsuccess: #488: 2: Success after binutils/gcc: 51 commits new 0b1162fe0b 67: onsuccess: #489: 2: Success after binutils/gcc: 23 commits new c9e610e058 68: onsuccess: #490: 2: Success after binutils/gcc: 8 commits new 1459fa463b 69: onsuccess: #491: 2: Success after binutils/gcc: 19 commits new c71bb6815c 70: onsuccess: #492: 2: Success after binutils/gcc: 42 commits new eb52ed742c 71: onsuccess: #493: 2: Success after binutils/gcc: 50 commits new 49b712cd9a 72: onsuccess: #494: 2: Success after binutils/gcc: 54 commits new 1b61f6c6e8 73: onsuccess: #495: 2: Success after binutils/gcc: 50 commits new d2e2792391 74: onsuccess: #496: 2: Success after binutils/gcc: 15 commits new 11afd40381 75: onsuccess: #497: 2: Success after binutils/gcc: 5 commits new f9b721a556 76: onsuccess: #498: 2: Success after binutils/gcc: 16 commits new 91133de146 77: onsuccess: #499: 2: Success after binutils/gcc: 48 commits new 8c2cf5ba55 78: onsuccess: #500: 2: Success after binutils/gcc: 37 commits new f6c7250e95 79: onsuccess: #501: 2: Success after binutils/gcc: 28 commits new 5d3038fa6d 80: onsuccess: #502: 2: Success after binutils/gcc: 31 commits new 4be1c546a7 81: onsuccess: #503: 2: Success after binutils/gcc: 38 commits new 854d8df4a8 82: onsuccess: #504: 2: Success after binutils/gcc: 6 commits new 283a8dd9f8 83: onsuccess: #505: 2: Success after binutils/gcc: 15 commits new 7b5724febf 84: onsuccess: #506: 2: Success after binutils/gcc: 37 commits new db8c67152a 85: onsuccess: #507: 2: Success after binutils/gcc: 27 commits new 3441508680 86: onsuccess: #508: 2: Success after binutils/gcc: 29 commits new 8737d5a343 87: onsuccess: #509: 2: Success after binutils/gcc: 58 commits new 923f06fefa 88: onsuccess: #510: 2: Success after binutils/gcc: 55 commits new a791be1763 89: onsuccess: #511: 2: Success after binutils/gcc: 20 commits new 26c50ed6bf 90: onsuccess: #512: 2: Success after binutils/gcc: 50 commits new 5b42ffe178 91: onsuccess: #513: 2: Success after binutils/gcc: 71 commits new 472f7cbab9 92: onsuccess: #514: 2: Success after binutils/gcc: 58 commits new a1c9b4f29f 93: onsuccess: #515: 2: Success after binutils/gcc: 47 commits new ea40eaa5b4 94: onsuccess: #516: 2: Success after binutils/gcc: 58 commits new e7d8e7dd26 95: onsuccess: #518: 2: Success after binutils: 10 commits new 2f891dc99b 96: force: #520: 2: Success after gcc: 24 commits new b050926c7d 97: force: #521: 1: Failure after basepoints/gcc-13-3918-gba [...] new 868ec2af39 98: onsuccess: #522: 1: Success after gcc: 11 commits new e833c7e771 99: onsuccess: #523: 2: Success after binutils/gcc: 84 commits new 9065ac1a0f 100: onsuccess: #525: 2: Success after binutils/gcc: 128 commits new 64c1628700 101: onsuccess: #526: 2: Success after binutils/gcc: 52 commits new adaddb1035 102: onsuccess: #527: 2: Success after binutils/gcc: 32 commits new 65a19cf736 103: onsuccess: #528: 2: Success after binutils/gcc: 40 commits new b1cb6e0d93 104: onsuccess: #529: 2: Success after binutils/gcc: 11 commits new 8765f62273 105: onsuccess: #530: 2: Success after binutils/gcc: 32 commits new b1e697df0b 106: onsuccess: #532: 2: Success after binutils: 12 commits new fbcb7ff9dc 107: force: #534: 2: Success after gcc: 26 commits new b290b2bd75 108: force: #535: 1: Failure after basepoints/gcc-13-4227-g0 [...] new bcbd8e03d9 109: onsuccess: #536: 1: Success after gcc: 2 commits new 851115c611 110: onsuccess: #537: 1: Success after binutils/gcc: 51 commits new d2a17207c9 111: onsuccess: #538: 1: Success after binutils/gcc: 39 commits new 970a2c7d73 112: onsuccess: #539: 1: Success after binutils/gcc: 31 commits new ed9e6e40b6 113: onsuccess: #540: 1: Success after binutils/gcc: 11 commits new 9f50433baa 114: onsuccess: #541: 1: Success after binutils/gcc: 8 commits new 9654f1ce54 115: onsuccess: #542: 1: Success after binutils/gcc: 58 commits new 0a5f89f00d 116: onsuccess: #543: 2: Success after binutils/gcc: 73 commits new b2456fa822 117: onsuccess: #544: 2: Success after binutils/gcc: 31 commits new 7062918734 118: onsuccess: #545: 2: Success after binutils/gcc: 48 commits new fb5894cfbe 119: onsuccess: #546: 2: Success after binutils/gcc: 47 commits new 7de47d0088 120: onsuccess: #547: 2: Success after binutils/gcc: 17 commits new 8680656f3c 121: onsuccess: #548: 2: Success after binutils/gcc: 9 commits new 7e873918cf 122: onsuccess: #549: 2: Success after binutils/gcc: 20 commits new cf47a2a2d4 123: onsuccess: #550: 2: Success after binutils/gcc: 40 commits new 7747f21d2e 124: onsuccess: #551: 2: Success after binutils/gcc: 41 commits new 49d88d39f3 125: onsuccess: #552: 2: Success after binutils/gcc: 25 commits new 0b08aec9b0 126: onsuccess: #553: 2: Success after binutils/gcc: 36 commits new f352b635b0 127: onsuccess: #554: 2: Success after binutils/gcc: 20 commits new c6c9eec3d5 128: onsuccess: #555: 2: Success after binutils/gcc: 4 commits new 481fa038bc 129: onsuccess: #556: 2: Success after binutils/gcc: 23 commits new 1251536a86 130: force: #560: 2: Success after binutils: 21 commits new 9d0be8d7f5 131: force: #561: 1: Failure after gdb-12-branchpoint-3046-g [...] new eaa36bad12 132: onsuccess: #562: 1: Success after baseline build: no ne [...] new a200452f70 133: onsuccess: #563: 1: Success after binutils/gcc: 108 commits new 201a6821de 134: onsuccess: #564: 1: Success after binutils/gcc: 30 commits new 33291cba91 135: onsuccess: #565: 2: Success after binutils/gcc: 40 commits new 7014aed80a 136: onsuccess: #566: 2: Success after binutils/gcc: 37 commits new 994b3b9523 137: onsuccess: #567: 2: Success after binutils/gcc: 10 commits new 81eab47318 138: onsuccess: #568: 2: Success after binutils/gcc: 22 commits new 8dd705abc0 139: onsuccess: #569: 2: Success after binutils/gcc: 42 commits new a2119050ff 140: onsuccess: #570: 2: Success after binutils/gcc: 56 commits new b2ac069727 141: onsuccess: #571: 2: Success after binutils/gcc: 43 commits new c5135efe47 142: onsuccess: #572: 2: Success after binutils/gcc: 74 commits new 49eb46dcb7 143: onsuccess: #573: 2: Success after binutils/gcc: 35 commits new cac543fde8 144: onsuccess: #574: 2: Success after binutils/gcc: 26 commits new 4c5393bf0d 145: onsuccess: #575: 2: Success after binutils/gcc: 6 commits new e2232779e5 146: onsuccess: #576: 2: Success after binutils/gcc: 16 commits new af450a9efd 147: onsuccess: #577: 2: Success after binutils/gcc: 22 commits new 2b97f3a819 148: onsuccess: #578: 2: Success after binutils/gcc: 7 commits new e2e7c0c5a8 149: onsuccess: #579: 2: Success after binutils/gcc: 20 commits new e9dd17b2dd 150: onsuccess: #580: 2: Success after binutils/gcc: 19 commits new f82792ff10 151: onsuccess: #581: 2: Success after binutils/gcc: 12 commits new ed8645f3b0 152: onsuccess: #582: 2: Success after binutils/gcc: 25 commits new 54f70c75f9 153: onsuccess: #583: 2: Success after binutils/gcc: 45 commits new 144e8fcc01 154: onsuccess: #584: 2: Success after binutils/gcc: 36 commits new ea56dc6903 155: onsuccess: #585: 2: Success after binutils/gcc: 36 commits new a9f121bbca 156: onsuccess: #586: 2: Success after binutils/gcc: 55 commits new a56d848954 157: onsuccess: #587: 2: Success after binutils/gcc: 16 commits new be4f02e1cf 158: onsuccess: #588: 2: Success after binutils/gcc: 6 commits new d197b365d3 159: onsuccess: #592: 2: Success after binutils/gcc: 131 commits new 7c5d312321 160: onsuccess: #593: 2: Success after binutils/gcc: 40 commits new adb2b37bf5 161: onsuccess: #594: 2: Success after binutils/gcc: 135 commits new b9252f3565 162: onsuccess: #595: 2: Success after binutils/gcc: 36 commits new d1bc4419bd 163: onsuccess: #596: 2: Success after binutils/gcc: 65 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 (5c5e6b1e06) \ 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 1740 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2756 bytes 04-build_abe-binutils/console.log.xz | Bin 52520 -> 52424 bytes 05-build_abe-bootstrap_O3/console.log.xz | Bin 468696 -> 469612 bytes 06-check_regression/console.log.xz | Bin 3028 -> 3024 bytes 07-update_baseline/console.log | 58 +++++++++++++++---------------- 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, 45 insertions(+), 45 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[binutils-gdb] branch gdb-13-branch updated (2ec9694617b -> 83d3152401c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch gdb-13-branch in repository binutils-gdb. from 2ec9694617b Automatic date update in version.in new 6107546876d Avoid submitting empty tasks in parallel_for_each new 947b698401f Move hash_entry and eq_entry into cooked_index::do_finalize new 83d3152401c Fix parameter-less template regression in new DWARF reader The 3 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/dwarf2/cooked-index.c | 161 +++++++++++++++++---- gdb/dwarf2/cooked-index.h | 15 +- gdb/dwarf2/read.c | 3 +- .../{gdb.dwarf2/index.cc => gdb.cp/paramless.cc} | 33 ++++- gdb/testsuite/gdb.cp/{bool.exp => paramless.exp} | 24 +-- gdb/unittests/parallel-for-selftests.c | 39 +++++ gdbsupport/parallel-for.h | 30 ++++ 7 files changed, 253 insertions(+), 52 deletions(-) copy gdb/testsuite/{gdb.dwarf2/index.cc => gdb.cp/paramless.cc} (63%) copy gdb/testsuite/gdb.cp/{bool.exp => paramless.exp} (65%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch master updated (3a121c06f3c -> d74d84c623e)

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 3a121c06f3c PR-108404 M2RTS_Halt fails with a segv new d74d84c623e libstdc++: Fix configuration of default zoneinfo dir on 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: libstdc++-v3/acinclude.m4 | 8 ++++---- libstdc++-v3/configure | 8 ++++---- 2 files changed, 8 insertions(+), 8 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

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

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/release-arm in repository toolchain/ci/base-artifacts. from fda78c46c8 52: onsuccess: #216: 1: Success after gcc/linux/glibc: 16739 [...] new 20c65f37ea 53: onsuccess: #217: 1: Success after gcc: 5 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 1740 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 51908 -> 50852 bytes 04-build_abe-gcc/console.log.xz | Bin 229320 -> 228424 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8648 -> 8680 bytes 07-build_abe-glibc/console.log.xz | Bin 232992 -> 233692 bytes 08-build_abe-gdb/console.log.xz | Bin 46504 -> 46080 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3844 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2412 -> 2420 bytes 11-check_regression/console.log.xz | Bin 5804 -> 4928 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 21 +- 12-update_baseline/console.log | 9 - dashboard/dashboard-generate.sh | 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 2838296 -> 2852176 bytes sumfiles/g++.sum | 120 +- sumfiles/gcc.log.xz | Bin 2476660 -> 2449692 bytes sumfiles/gcc.sum | 3994 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 941768 -> 946192 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 212784 -> 212404 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 457168 -> 459680 bytes sumfiles/libstdc++.sum | 10 +- 34 files changed, 2123 insertions(+), 2143 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[binutils-gdb] branch master updated (55e0daa3a3d -> ac37b79cc44)

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 55e0daa3a3d gas: arm: Change warning message to not reference specific [...] new 63078a04984 Avoid submitting empty tasks in parallel_for_each new 1a6191f1a61 Don't erase empty indices in DWARF reader new 5a89072f36d Move hash_entry and eq_entry into cooked_index::do_finalize new ac37b79cc44 Fix parameter-less template regression in new DWARF reader The 4 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/dwarf2/cooked-index.c | 161 +++++++++++++++++---- gdb/dwarf2/cooked-index.h | 15 +- gdb/dwarf2/read.c | 13 +- .../{gdb.dwarf2/index.cc => gdb.cp/paramless.cc} | 33 ++++- gdb/testsuite/gdb.cp/{bool.exp => paramless.exp} | 26 ++-- gdb/unittests/parallel-for-selftests.c | 39 +++++ gdbsupport/parallel-for.h | 30 ++++ 7 files changed, 254 insertions(+), 63 deletions(-) copy gdb/testsuite/{gdb.dwarf2/index.cc => gdb.cp/paramless.cc} (63%) copy gdb/testsuite/gdb.cp/{bool.exp => paramless.exp} (62%) -- 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-master-arm-mainline-allyesconfig updated (dd5d8afb30 -> 8a647ba071)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-mainline-allyesconfig in repository toolchain/ci/base-artifacts. from dd5d8afb30 42: onsuccess: #558: 33: Success after binutils/gcc/linux/qe [...] new 8a647ba071 43: onsuccess: #559: 33: Success after binutils/gcc/linux/qe [...] 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 1776 -> 1804 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2796 bytes 03-build_abe-binutils/console.log.xz | Bin 32428 -> 32024 bytes 04-build_abe-stage1/console.log.xz | Bin 92708 -> 92500 bytes 05-build_abe-qemu/console.log.xz | Bin 32252 -> 32064 bytes 06-build_linux/console.log.xz | Bin 4852 -> 4832 bytes 08-check_regression/console.log.xz | Bin 4400 -> 4328 bytes 09-update_baseline/console.log | 8 ++++---- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 28 insertions(+), 28 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-lts-allmodconfig updated (c71a756aaa -> a9d0425f36)

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-allmodconfig in repository toolchain/ci/base-artifacts. from c71a756aaa 38: onsuccess: #528: 33: Success after binutils/gcc/linux/qe [...] new a9d0425f36 39: onsuccess: #529: 33: Success after binutils/gcc/linux/qe [...] 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 1804 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 32648 -> 32040 bytes 04-build_abe-stage1/console.log.xz | Bin 74536 -> 74388 bytes 05-build_abe-qemu/console.log.xz | Bin 32300 -> 32168 bytes 06-build_linux/console.log.xz | Bin 5088 -> 5140 bytes 08-check_regression/console.log.xz | Bin 4516 -> 4428 bytes 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 16 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits January 2023