Tcwg-commits February 2023

tcwg-commits@lists.linaro.org

5 participants
3393 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-lts-allmodconfig updated (4264e403a2 -> dc9dbabcfe)

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-lts-allmodconfig in repository toolchain/ci/base-artifacts. from 4264e403a2 44: onsuccess: #506: 33: Success after binutils/gcc/linux/qe [...] new dc9dbabcfe 45: onsuccess: #507: 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 1760 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 30864 -> 31068 bytes 04-build_abe-stage1/console.log.xz | Bin 92552 -> 91412 bytes 05-build_abe-qemu/console.log.xz | Bin 31880 -> 31560 bytes 06-build_linux/console.log.xz | Bin 5116 -> 5596 bytes 08-check_regression/console.log.xz | Bin 4336 -> 4520 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.

1 year, 9 months

[glibc] branch master updated (d08ae9c3fb -> 23e2c3b25f)

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 glibc. from d08ae9c3fb hurd, htl: Add some x86_64-specific code new 23e2c3b25f htl: Remove ./sysdeps/htl/bits/types/struct___pthread_mutex.h The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: sysdeps/htl/bits/types/struct___pthread_mutex.h | 61 ------------------------- 1 file changed, 61 deletions(-) delete mode 100644 sysdeps/htl/bits/types/struct___pthread_mutex.h -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (525de04ba5 -> f4081000e5)

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 525de04ba5 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards f5863b532b 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 0030845b5a 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 5a078f8bbd 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards e1b5c70d18 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards e88b6a6bc0 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 3456a6b40a 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards adaa5b03a5 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards dba6e774a1 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 8677243f1a 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 22a081376b 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 0ef40c2d38 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards b0a2650c7e 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 56d5250fa1 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 25cb3e5820 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards ea35ecac1d 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 02c9e3b3f7 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards e3095b2c56 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards ce97c4c48f 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 967725787f 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 32b01a8f77 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 1a42ab91ec 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards c5767512ea 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 52acf6daa7 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards d68e28045f 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 43470b2000 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 0ecaf4507f 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 4889de4f76 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards bc768c0d7c 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 033aa678d9 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 4fb1cfc7e9 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 5c66a9c93d 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 1fca5c255f 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards e22c32ed86 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards e37e7ca1cf 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 98140d2ef1 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 94c04fc1d6 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards d562f8e938 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 1fe88a2f9b 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 7d7f5fd825 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 98ebc3d4b4 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 0e5e7c2098 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 4271df2bfb 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 242a898c5c 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 52a8b680db 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 591572cd3b 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 5303505a88 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 7e640fde4d 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 3c7aa4ed60 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards c5abc94ecb 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 4aa511b298 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 79c41b6c54 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 3e61241d55 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 50eff09c1c 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 857d44c34f 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards ab39160325 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 440f27a945 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards a21c6d5700 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 70ec56b3cc 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards f8b7671f0a 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards f2c066f1e5 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards bfa646e81b 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 7cd018ab8d 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards bd5249bb3f 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards cf4881b3d5 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 469d8eac8f 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards ef001cedad 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 814c885f99 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards a55e93b460 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 455c7fac61 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards c54e58ec01 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards e59540fd39 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 3452e090ac 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 2c09fa8181 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards e8e2b73816 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards df12553ce8 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 1fff223432 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards ed21f207cb 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 2e12fa79b8 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards c4b2f98aa1 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards b6a4ac595c 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards a98e0dc353 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 83ca896363 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards cc742927e5 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards f8d0f7e073 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 34a7ce2274 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards e079c9bbec 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 4979e373cf 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 1b0a2194d0 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 41e6988bdf 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards d5784f8702 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 18c845a27a 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 06585582ab 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 99de18c246 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 1fa69e8a0b 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 3dbff88de9 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 47f97dec12 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards b184744647 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards b2ab42b0d8 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards d60adcb848 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards bf4aa95da7 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new dfd6a527a3 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 899d6f0585 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 0b82ab6aeb 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new bb3a03b3c0 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 1ba163af1b 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 256bf33486 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new feb29ac76d 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 29f1943275 293: onsuccess: #2542: 1: Success after gcc: 5 commits new b2be406613 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 96763de39e 295: onsuccess: #2545: 1: Success after linux: 10 commits new a7324e7ac6 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 28aa6a585b 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 85d4fd1d89 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 6ec8d88887 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 88ef18368a 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 01c4fbc521 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new a065c57f0d 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new f9dc9db5e2 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new a10c399542 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 55dabc0343 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 1bbc5f29c3 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 8304d170c0 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new cb1e011d9c 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 9a18fd74a2 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 2799535572 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 7757cc2a2c 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 7817a34d75 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new d8041f9735 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new fbd8a0b7f4 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new a03e33b086 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new d41d0091cc 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 7562c0e23f 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 728d2f8de0 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new a1968100ed 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 530198ba5d 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 06b0d6bfcc 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 9b715eace0 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 349d7a3acd 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 42a3470d45 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new d0c28a25d3 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 425a4d04e5 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 9a014f0765 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new a52fa68b52 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new ec07c72d18 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 0e5b061be5 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new b79cf3806a 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new d493319e35 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 7c43f3148a 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 37298c38fc 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 2bc9beb745 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 5281c69cbd 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 90b0e76da9 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 14710234a2 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new a3889ede3a 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 01769e257f 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 30601e3f22 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new d6d80256d6 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 9e354836f6 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 5e97ab0356 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 5890144e72 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new f91caf36a5 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 82e24d5b99 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 85ecd91505 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 600bed0b6a 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 3792b73b1e 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 1b2c50e34b 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 75857dbf29 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new d0c9499def 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 2290c69d19 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new ebd9171b90 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 88cada7f7f 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 4c528e440e 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 43990049b7 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 60cb838655 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 17a30f87fb 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 321b631882 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 339573104a 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 9c7cae1269 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new fe3349b8d0 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new bcb9fe3675 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new dc921f123a 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new b7ffacaf11 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 77d8a41aa9 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 946c0b6990 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 343bd3ed9b 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 12aea3a0de 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 7980a34d4b 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 61d789fe8b 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 0a7e45c2bc 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 126f83dd02 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 0b121544cf 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 5f986987ff 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 156776ccf2 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new dc2a40aefd 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 8800e28b6c 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 3546a75711 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 9b2004e307 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 818a7b68d6 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new cf707acd3b 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 7f522df2a1 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new cf58f3797d 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new f4081000e5 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] 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 (525de04ba5) \ 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 1760 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31160 -> 31468 bytes 04-build_abe-stage1/console.log.xz | Bin 72792 -> 73116 bytes 06-build_abe-linux/console.log.xz | Bin 8664 -> 8660 bytes 07-build_abe-glibc/console.log.xz | Bin 244716 -> 245268 bytes 08-build_abe-stage2/console.log.xz | Bin 204000 -> 204696 bytes 09-build_abe-gdb/console.log.xz | Bin 38484 -> 38840 bytes 10-build_abe-qemu/console.log.xz | Bin 31368 -> 31980 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3908 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2644 -> 2724 bytes 13-check_regression/console.log.xz | Bin 6336 -> 6024 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 17 - 13-check_regression/mail-body.txt | 68 +- 13-check_regression/results.compare | 41 +- 13-check_regression/results.compare2 | 50 +- 13-check_regression/results.regressions | 51 - 14-update_baseline/console.log | 66 +- 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 | 70 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 51 - sumfiles/g++.log.xz | Bin 3395232 -> 3399904 bytes sumfiles/g++.sum | 34 +- sumfiles/gcc.log.xz | Bin 3017024 -> 3026312 bytes sumfiles/gcc.sum | 3464 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1035656 -> 1040708 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217520 -> 217508 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2660 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 431104 -> 435968 bytes sumfiles/libstdc++.sum | 52 +- 42 files changed, 1934 insertions(+), 2092 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-coremark/gnu_eabi-arm_eabi-master-Os updated (07f1bbbce1 -> b616fdfbbb)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_size-coremark/gnu_eabi-arm_eabi-master-Os in repository toolchain/ci/base-artifacts. from 07f1bbbce1 49: onsuccess: #9: 1: [TCWG CI] No change after binutils/gcc [...] new b616fdfbbb 50: onsuccess: #10: 1: [TCWG CI] No change after binutils/gc [...] 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 1812 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 31336 -> 31080 bytes 04-build_abe-stage1/console.log.xz | Bin 90628 -> 89980 bytes 06-build_abe-newlib/console.log.xz | Bin 14476 -> 14532 bytes 07-build_abe-stage2/console.log.xz | Bin 165876 -> 165516 bytes 08-benchmark/benchmark-build.log | 96 ++++++++++----------- 08-benchmark/benchmark.log | 94 ++++++++++---------- 08-benchmark/console.log.xz | Bin 3824 -> 3816 bytes 09-check_regression/console.log.xz | Bin 4916 -> 4932 bytes 09-check_regression/results-vs-first.log | 4 +- 09-check_regression/results-vs-prev.log | 4 +- dashboard/dashboard-generate.sh | 2 +- .../squad-vs-first/Mean/results-metadata.json | 12 +-- .../squad-vs-first/coremark/results-metadata.json | 12 +-- dashboard/squad-vs-first/dashboard-push-squad.sh | 10 +-- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/newlib_rev | 2 +- mail/jira-body.txt | 34 ++++---- mail/mail-body.txt | 34 ++++---- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++---- results_id | 2 +- 24 files changed, 171 insertions(+), 171 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/llvm-aarch64-master-Os updated (6db737c953 -> 5cae105b97)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/llvm-aarch64-master-Os in repository toolchain/ci/base-artifacts. from 6db737c953 47: onsuccess: #8: 1: [TCWG CI] No change after binutils/gcc [...] new 5cae105b97 48: onsuccess: #10: 1: [TCWG CI] No change after binutils/gc [...] 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 1960 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 32328 -> 31500 bytes 04-build_abe-stage1/console.log.xz | Bin 73704 -> 73512 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 7928 -> 8688 bytes 07-build_abe-glibc/console.log.xz | Bin 246488 -> 244580 bytes 08-build_abe-stage2/console.log.xz | Bin 182392 -> 178560 bytes 09-build_llvm-true-false-cflags-/console.log.xz | Bin 61096 -> 64180 bytes 10-benchmark/benchmark-build.log | 114 +- 10-benchmark/benchmark.log | 112 +- 10-benchmark/console.log.xz | Bin 3800 -> 3872 bytes 11-check_regression/console.log.xz | Bin 13160 -> 13176 bytes .../csv-results-vs-first-0/md5sum.csv | 1814 +- .../csv-results-vs-first-0/results.csv | 32076 +- .../csv-results-vs-first-0/size.csv | 369870 ++++++++--------- 11-check_regression/csv-results-vs-first-0/sve.csv | 24 +- .../csv-results-vs-first-1/md5sum.csv | 2245 +- .../csv-results-vs-first-1/perf.csv | 2568 +- .../csv-results-vs-first-1/results.csv | 377343 +++++++++-------- .../csv-results-vs-first-1/size.csv | 380171 +++++++++--------- 11-check_regression/csv-results-vs-first-1/sve.csv | 18 +- .../csv-results-vs-prev-0/md5sum.csv | 2327 +- 11-check_regression/csv-results-vs-prev-0/perf.csv | 2500 +- .../csv-results-vs-prev-0/results.csv | 319639 ++++++++------- 11-check_regression/csv-results-vs-prev-0/size.csv | 363875 +++++++++-------- 11-check_regression/csv-results-vs-prev-0/sve.csv | 20 +- .../csv-results-vs-prev-1/md5sum.csv | 2245 +- 11-check_regression/csv-results-vs-prev-1/perf.csv | 2568 +- .../csv-results-vs-prev-1/results.csv | 377343 +++++++++-------- 11-check_regression/csv-results-vs-prev-1/size.csv | 380171 +++++++++--------- 11-check_regression/csv-results-vs-prev-1/sve.csv | 18 +- 11-check_regression/results-vs-first-brief.csv | 48 +- 11-check_regression/results-vs-first-full.csv | 2611 +- 11-check_regression/results-vs-first-internal.csv | 170 +- 11-check_regression/results-vs-first.csv | 168 +- 11-check_regression/results-vs-first.log | 894 +- 11-check_regression/results-vs-prev-brief.csv | 48 +- 11-check_regression/results-vs-prev-compare.csv | 28 +- 11-check_regression/results-vs-prev-full.csv | 2651 +- 11-check_regression/results-vs-prev-internal.csv | 170 +- 11-check_regression/results-vs-prev.csv | 170 +- 11-check_regression/results-vs-prev.log | 994 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 18 +- .../400.perlbench/results-metrics.json | 2 +- .../squad-vs-first/401.bzip2/results-metadata.json | 18 +- .../squad-vs-first/401.bzip2/results-metrics.json | 2 +- .../squad-vs-first/403.gcc/results-metadata.json | 18 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../squad-vs-first/429.mcf/results-metadata.json | 18 +- .../squad-vs-first/429.mcf/results-metrics.json | 2 +- .../squad-vs-first/433.milc/results-metadata.json | 18 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 18 +- .../squad-vs-first/444.namd/results-metrics.json | 4 +- .../squad-vs-first/445.gobmk/results-metadata.json | 18 +- .../squad-vs-first/445.gobmk/results-metrics.json | 2 +- .../447.dealII/results-metadata.json | 18 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 18 +- .../453.povray/results-metadata.json | 18 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../squad-vs-first/456.hmmer/results-metadata.json | 18 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 18 +- .../squad-vs-first/458.sjeng/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 18 +- .../462.libquantum/results-metrics.json | 2 +- .../464.h264ref/results-metadata.json | 18 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 18 +- .../squad-vs-first/470.lbm/results-metrics.json | 2 +- .../471.omnetpp/results-metadata.json | 18 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 18 +- .../squad-vs-first/473.astar/results-metrics.json | 2 +- .../482.sphinx3/results-metadata.json | 18 +- .../482.sphinx3/results-metrics.json | 2 +- .../483.xalancbmk/results-metadata.json | 18 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 18 +- dashboard/squad-vs-first/Mean/results-metrics.json | 2 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 82 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 60 +- mail/mail-body.txt | 60 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results_id | 2 +- 94 files changed, 1327243 insertions(+), 1298430 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[glibc] branch master updated (be6d002ca2 -> d08ae9c3fb)

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 glibc. from be6d002ca2 hurd: Set up the basic tree for x86_64-gnu new bfb583e791 htl: Generalize i386 pt-machdep.h to x86 new 8420b3e832 Fix typos in comments new d08ae9c3fb hurd, htl: Add some x86_64-specific code 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: htl/pt-internal.h | 2 +- sysdeps/generic/pty-private.h | 2 +- sysdeps/i386/htl/Implies | 1 + sysdeps/mach/hurd/{i386 => x86_64}/static-start.S | 6 +++--- sysdeps/mach/hurd/{i386 => x86_64}/tlsdesc.sym | 5 ++++- sysdeps/{i386 => x86}/htl/pt-machdep.h | 2 +- sysdeps/x86_64/htl/Implies | 1 + sysdeps/{i386 => x86_64}/htl/machine-sp.h | 8 ++++---- 8 files changed, 16 insertions(+), 11 deletions(-) create mode 100644 sysdeps/i386/htl/Implies copy sysdeps/mach/hurd/{i386 => x86_64}/static-start.S (88%) copy sysdeps/mach/hurd/{i386 => x86_64}/tlsdesc.sym (72%) rename sysdeps/{i386 => x86}/htl/pt-machdep.h (93%) create mode 100644 sysdeps/x86_64/htl/Implies copy sysdeps/{i386 => x86_64}/htl/machine-sp.h (82%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[glibc] branch master updated (4fedebc911 -> be6d002ca2)

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 glibc. from 4fedebc911 mach: Look for mach_i386.defs on x86_64 too new be6d002ca2 hurd: Set up the basic tree for x86_64-gnu 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: sysdeps/mach/hurd/Implies | 1 + sysdeps/mach/hurd/i386/htl/Implies | 1 + sysdeps/mach/hurd/{i386 => x86}/htl/pt-setup.c | 4 ++-- sysdeps/mach/hurd/x86_64/Implies | 2 ++ sysdeps/mach/hurd/x86_64/htl/Implies | 3 +++ sysdeps/mach/{i386 => x86_64}/Implies | 0 6 files changed, 9 insertions(+), 2 deletions(-) rename sysdeps/mach/hurd/{i386 => x86}/htl/pt-setup.c (97%) create mode 100644 sysdeps/mach/hurd/x86_64/Implies create mode 100644 sysdeps/mach/hurd/x86_64/htl/Implies copy sysdeps/mach/{i386 => x86_64}/Implies (100%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[glibc] branch master updated (3d008a92a8 -> 4fedebc911)

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 glibc. from 3d008a92a8 htl: Fix semaphore reference new 4fedebc911 mach: Look for mach_i386.defs on x86_64 too 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: sysdeps/mach/configure | 6 +++--- sysdeps/mach/configure.ac | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[glibc] branch master updated (e42ec82219 -> 3d008a92a8)

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 glibc. from e42ec82219 Use __builtin_FILE instead of __FILE__ in assert in C++. new 8a86e7b6a6 hurd: Refactor readlinkat() new f4315054b4 hurd: Use mach_msg_type_number_t where appropriate new 62d6c33030 mach, hurd: Cast through uintptr_t new 48941024ba hurd: Fix xattr error value new 3d008a92a8 htl: Fix semaphore reference The 5 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: htl/cthreads-compat.c | 5 ++-- hurd/fopenport.c | 15 +++++++---- hurd/hurd/port.h | 2 +- hurd/hurdioctl.c | 2 +- hurd/hurdprio.c | 2 +- hurd/lookup-retry.c | 2 +- hurd/port-cleanup.c | 3 ++- hurd/vpprintf.c | 6 +++-- hurd/xattr.c | 6 ++--- mach/devstream.c | 9 ++++--- sysdeps/htl/sem-timedwait.c | 10 ++++---- sysdeps/mach/hurd/getcwd.c | 2 +- sysdeps/mach/hurd/readlinkat.c | 57 +++++++++++++++++++++++++----------------- sysdeps/mach/hurd/sendfile64.c | 2 +- 14 files changed, 72 insertions(+), 51 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (31580f8a4a -> 7a895be0f8)

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 31580f8a4a 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards d2a3501833 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 816c0a1853 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards d3d3a522b2 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 9b4efe2648 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards e0eb53e51d 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards edf00440f2 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 94e9fcea9e 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards bb93b0e255 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 84934f1745 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 7e57119117 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 710a3d3354 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards a0bd1d699c 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 14bb8c8833 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards e70ac8f759 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 6b33afe3a4 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards a81db0e926 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 9dee344351 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards ccae250b0a 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 40f39aee9e 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 9c5cf39d7f 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards f07bc324be 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 58d3bec070 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards f8569f70ed 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 80a4cc5d42 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 52d3cec15b 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 3a8545972e 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 47455750d7 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards cfa7060c12 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 165f5ea8dc 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 31c5966e32 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 3671d086e8 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards f0276ee534 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 1c77504c4c 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards bb404da8b9 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 59c605f8a3 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards a4dc09cae5 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 9381ea4671 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 384dface6c 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards d29b439b94 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards d154600b12 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 63da53dcdd 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 14ad5af409 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 51ccc60b17 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 74942d1f6d 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 7d58d931df 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 65834babc3 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards f35d9b8d72 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 0b7f076969 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 082d208c0a 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 721a09ec7a 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 7ee1837f90 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 345582d9c2 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards d1f3638550 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 0a932b520a 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards c6ce6ae42c 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards bac431bc78 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 6b85320fe8 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 4f11ef3cf5 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 9c3a5de508 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 7b9bdc3e20 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards aeeb0a2b6a 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 8be1cd72c0 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 9b70cc34df 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards def6929902 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 5b9576a404 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards cc58160ad2 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 2d0795c2bd 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards fd7caa0084 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 266b495a2d 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 5d19733f15 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 237f2656cf 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 6db582d983 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 0bacfb836e 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards c4357f2ed2 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 194ddba350 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 5fac55d7c0 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards f7da10850b 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 9028e63c45 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 355fea3f38 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 0b11c6af9b 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 85efb500f7 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 30ef48cfd2 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 4ef8be6641 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards abc3d28d34 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 02864561cc 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards e971ffc8ca 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 154bbf2a73 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 1e253daf79 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 4c5e69a95e 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards c6fc858d6a 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards f83d16a0d2 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 6c73a73cf5 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 9c17eb74b0 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards e6d4995242 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 8c17a7c653 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 0d24ee050d 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 06f089a07d 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards c197e7abc3 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 48f3c5f47c 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 7dc3eb6d7b 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 718d478cde 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 4b3d1ade1b 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new cbfb22146b 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 61212a68dc 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new a5b387aa32 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 2c42d26e7a 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new ba630b0cc4 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 175c4c315c 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 11752753ce 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 374b949d7e 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 5ad2b9f601 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 9bb606ef46 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 52ab4914e7 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new d618834847 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 0bee63f8e4 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 614f5914b8 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 1210658edc 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new c3d5879b7a 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new f5f4f7f7c5 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 6f6ec5be01 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 187cf237a7 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new cb4df6717c 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 1338f2dd2c 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new eed0d8f73c 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 425cac2810 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new f27d5523e9 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 4620013fe5 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 03967a8485 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new ffa4534dae 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new ef2ac39d8c 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 5050f53474 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 84857818a1 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new b7f739578b 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new d0c6a0a7b3 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 3cc197e27c 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new ad1e5646e8 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 1f5be54c2c 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new bd77d30b02 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new a128fd26fb 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 818335068b 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 426d8cce22 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 79d08b4d07 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new d33dbd2b76 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 0a1f4c2144 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new f6e6477837 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 006bead909 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new c8589352e2 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 1e68a39d78 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 6ee94b987c 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 97c70e7c67 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 1f141bcdba 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new fbb1efe8fd 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 20059e61b7 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 47e1fbc3de 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 4265a9c7b7 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new ea50967208 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new e5c8984419 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 2ebfab827e 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 50478702ea 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 902363c34e 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 14dd815920 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 1b4214e123 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 9d9cd3a35e 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new c6226648d0 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 068097d736 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new e623f2dcbf 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 39bc88570e 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new bcf44f60c8 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 5a78f4eba8 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new bcf0b3811d 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new b1d4b1868a 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 4df578cca4 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 328c944d05 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new aa1760d3d9 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new a81f791f20 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new ea1ba30b66 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new cef2cf9ca8 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new c9420a677a 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new bd89dc5a8b 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 3d9578e9b5 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 455eba624e 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 91c05f2d82 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 0c1490f4bc 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 7be09f720f 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new adb1986a71 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 988b0ec240 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 3755c8c37b 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new aa3f143a11 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 84a591e0c2 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 40af0bab10 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 2e684fe1d4 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 1f4f169c31 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 62ec704db0 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 8d1d7e3fbb 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 23b6789c06 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 963e42ce41 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new c43dd6a5d2 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 98e3d5df91 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new eecbdf7c2c 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 7176015a5b 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new ffe3343973 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new 7a895be0f8 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] 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 (31580f8a4a) \ 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 1800 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30932 -> 31388 bytes 04-build_abe-stage1/console.log.xz | Bin 91424 -> 91608 bytes 06-build_abe-linux/console.log.xz | Bin 8656 -> 8656 bytes 07-build_abe-glibc/console.log.xz | Bin 236892 -> 236972 bytes 08-build_abe-stage2/console.log.xz | Bin 227612 -> 228768 bytes 09-build_abe-gdb/console.log.xz | Bin 38168 -> 38664 bytes 10-build_abe-qemu/console.log.xz | Bin 31108 -> 31928 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2640 -> 2812 bytes 13-check_regression/console.log.xz | Bin 6108 -> 5968 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 60 +- 13-check_regression/results.compare | 29 +- 13-check_regression/results.compare2 | 19 +- 13-check_regression/results.regressions | 40 - 14-update_baseline/console.log | 66 +- 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 | 62 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 40 - sumfiles/g++.log.xz | Bin 2655284 -> 2641368 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 2220492 -> 2202220 bytes sumfiles/gcc.sum | 2594 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 895356 -> 891556 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216944 -> 216836 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 443648 -> 438260 bytes sumfiles/libstdc++.sum | 30 +- 42 files changed, 1425 insertions(+), 1600 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits February 2023