Tcwg-commits January 2023

tcwg-commits@lists.linaro.org

5 participants
4127 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-mainline-allmodconfig updated (f745b01fa8 -> 58b6ca5a40)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-arm-mainline-allmodconfig in repository toolchain/ci/base-artifacts. from f745b01fa8 41: onsuccess: #452: boot: Success after binutils/gcc/linux: [...] new 58b6ca5a40 42: onsuccess: #453: boot: Success after binutils/gcc/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1988 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30004 -> 30360 bytes 04-build_abe-stage1/console.log.xz | Bin 86916 -> 87692 bytes 05-build_abe-qemu/console.log.xz | Bin 31128 -> 31416 bytes 06-build_linux/console.log.xz | Bin 3320 -> 3328 bytes 07-boot_linux/console.log.xz | Bin 480 -> 480 bytes 08-check_regression/console.log.xz | Bin 3716 -> 4160 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 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-arm updated (cb5b33915d -> 702c9305b9)

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_fast_check_gdb/master-arm in repository toolchain/ci/base-artifacts. from cb5b33915d 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] new 702c9305b9 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] 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 1756 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 53168 -> 52300 bytes 04-build_abe-gcc/console.log.xz | Bin 238380 -> 238932 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8828 -> 8624 bytes 07-build_abe-glibc/console.log.xz | Bin 235540 -> 236388 bytes 08-build_abe-gdb/console.log.xz | Bin 52216 -> 52372 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3864 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2524 -> 2660 bytes 11-check_regression/console.log.xz | Bin 5588 -> 6160 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 +++--- 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 | 36 +++++++++++++++++----------------- sumfiles/gdb.log.xz | Bin 14480 -> 14464 bytes sumfiles/gdb.sum | 34 ++++++++++++++++---------------- 25 files changed, 49 insertions(+), 49 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[binutils-gdb] branch master updated (1a8605a8c79 -> 7e0bd9ea7e2)

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 1a8605a8c79 gdbsupport: add gdb::string_view_hash new 7e0bd9ea7e2 gdbsupport: fix scoped_debug_start_end's move constructor 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: gdbsupport/common-debug.h | 21 ++++++++++++++++++++- 1 file changed, 20 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (0395640e05 -> 59826ef68c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/master-aarch64 in repository toolchain/ci/base-artifacts. discards 0395640e05 502: onsuccess: #2464: 1: Success after binutils/gcc: 4 commits discards dca45200d7 501: onsuccess: #2463: 1: Success after binutils/gcc: 8 commits discards 4419f0c201 500: onsuccess: #2462: 1: Success after binutils/gcc: 6 commits discards 52d371a848 499: onsuccess: #2461: 1: Success after binutils/gcc: 16 commits discards ed10fcb3f7 498: onsuccess: #2460: 1: Success after binutils/gcc: 7 commits discards 395db2b610 497: onsuccess: #2459: 1: Success after binutils/gcc: 6 commits discards f2c6e11267 496: onsuccess: #2458: 1: Success after binutils/gcc: 4 commits discards add16e294c 495: onsuccess: #2457: 1: Success after binutils/gcc: 19 commits discards 409d393f79 494: onsuccess: #2456: 1: Success after binutils/gcc: 23 commits discards 12b0ab21dc 493: onsuccess: #2455: 1: Success after binutils: 14 commits discards bbbfb9dccf 492: onsuccess: #2454: 1: Success after binutils/gcc: 2 commits discards 48150df12b 491: onsuccess: #2453: 1: Success after binutils/gcc: 8 commits discards 9965fbb59d 490: onsuccess: #2452: 1: Success after binutils/gcc: 7 commits discards 3cb86a4b08 489: onsuccess: #2451: 1: Success after binutils/gcc: 4 commits discards 217e6bb23d 488: onsuccess: #2450: 1: Success after binutils: 7 commits discards 50a51a237d 487: onsuccess: #2449: 1: Success after binutils/gcc: 7 commits discards 46382ec725 486: onsuccess: #2448: 1: Success after binutils/gcc: 3 commits discards daff230549 485: onsuccess: #2447: 1: Success after binutils/gcc: 3 commits discards 5fbd39999d 484: onsuccess: #2446: 1: Success after binutils/gcc: 3 commits discards 8160cd951f 483: onsuccess: #2445: 1: Success after binutils: 11 commits discards d961c38b8f 482: onsuccess: #2444: 1: Success after binutils/gcc: 2 commits discards 551ff5a336 481: onsuccess: #2443: 1: Success after gdb-13-branchpoint-2 [...] discards 525756c960 480: onsuccess: #2442: 1: Success after binutils/gcc: 6 commits discards f3fed1198f 479: onsuccess: #2441: 1: Success after binutils/gcc: 2 commits discards 4fa6260c5e 478: onsuccess: #2440: 1: Success after basepoints/gcc-13-49 [...] discards 7a8762005c 477: onsuccess: #2439: 1: Success after binutils/gcc: 2 commits discards ee14e3ac75 476: onsuccess: #2438: 1: Success after gcc: 17 commits discards 32e61ae087 475: onsuccess: #2437: 1: Success after gdb-13-branchpoint-2 [...] discards 8d1aa142eb 474: onsuccess: #2436: 1: Success after basepoints/gcc-13-49 [...] discards 02880df5e9 473: onsuccess: #2435: 1: Success after binutils/gcc: 3 commits discards 8121308817 472: onsuccess: #2434: 1: Success after binutils: 2 commits discards 26b67bad2f 471: onsuccess: #2433: 1: Success after gcc: 2 commits discards 1422f69cca 470: onsuccess: #2432: 1: Success after gcc: 2 commits discards 1aa575a1f8 469: onsuccess: #2431: 1: Success after binutils/gcc: 7 commits discards 2522dc7a7a 468: onsuccess: #2430: 1: Success after binutils/gcc: 11 commits discards 823432cce0 467: onsuccess: #2429: 1: Success after basepoints/gcc-13-48 [...] discards 80744b782b 466: onsuccess: #2428: 1: Success after binutils: 9 commits discards b034a6efc5 465: onsuccess: #2427: 1: Success after binutils/gcc: 3 commits discards dee7a2f3ae 464: onsuccess: #2426: 1: Success after basepoints/gcc-13-48 [...] discards a736e477a6 463: onsuccess: #2425: 1: Success after binutils: 2 commits discards 66dcc9af6f 462: onsuccess: #2424: 1: Success after gcc: 2 commits discards f346e1c84b 461: onsuccess: #2423: 1: Success after binutils: 2 commits discards 0a196f8b42 460: onsuccess: #2422: 1: Success after gdb-13-branchpoint-1 [...] discards 656bf23729 459: onsuccess: #2421: 1: Success after binutils/gcc: 11 commits discards 960ae8fffa 458: onsuccess: #2420: 1: Success after binutils/gcc: 9 commits discards f7159a9d15 457: onsuccess: #2419: 1: Success after binutils/gcc: 3 commits discards 8d4ae49a4c 456: onsuccess: #2418: 1: Success after binutils/gcc: 4 commits discards 5b73c5817d 455: onsuccess: #2417: 1: Success after binutils/gcc: 2 commits discards e9d60963d8 454: onsuccess: #2416: 1: Success after binutils/gcc: 6 commits discards f8f17a1b36 453: onsuccess: #2415: 1: Success after binutils/gcc: 27 commits discards 26d8bef460 452: onsuccess: #2414: 1: Success after binutils/gcc: 17 commits discards 3840d185b7 451: onsuccess: #2413: 1: Success after binutils/gcc: 31 commits discards b183941e15 450: onsuccess: #2412: 1: Success after binutils/gcc: 12 commits discards 413638ca9d 449: onsuccess: #2411: 1: Success after binutils/gcc: 11 commits discards 79aff4a881 448: onsuccess: #2410: 1: Success after binutils/gcc: 18 commits discards d2972d04c2 447: onsuccess: #2409: 1: Success after binutils/gcc: 9 commits discards 54e511d3e4 446: onsuccess: #2408: 1: Success after binutils/gcc: 5 commits discards 7266328aaf 445: onsuccess: #2407: 1: Success after binutils/gcc: 8 commits discards 43cf1b6c05 444: onsuccess: #2406: 1: Success after binutils/gcc: 18 commits discards a7cd12f24b 443: onsuccess: #2405: 1: Success after binutils/gcc: 36 commits discards f5847a8886 442: onsuccess: #2404: 1: Success after binutils/gcc: 5 commits discards cc266fa84a 441: onsuccess: #2403: 1: Success after gcc: 3 commits discards cfa2518c0e 440: onsuccess: #2402: 1: Success after binutils/gcc: 4 commits discards f15062a918 439: onsuccess: #2401: 1: Success after binutils/gcc: 4 commits discards 93c86871f4 438: onsuccess: #2400: 1: Success after binutils/gcc: 7 commits discards c1534fcc35 437: onsuccess: #2399: 1: Success after binutils/gcc: 26 commits discards f0e66f4eba 436: onsuccess: #2398: 1: Success after binutils/gcc: 20 commits discards 9c79f31cff 435: onsuccess: #2397: 1: Success after basepoints/gcc-13-47 [...] discards 1b57a58a3b 434: onsuccess: #2396: 1: Success after binutils/gcc: 2 commits discards 48d258dc04 433: onsuccess: #2395: 1: Success after binutils/gcc: 3 commits discards 78e0d65c10 432: onsuccess: #2394: 1: Success after binutils/gcc: 3 commits discards 500be5b0a4 431: onsuccess: #2393: 1: Success after binutils/gcc: 3 commits discards 29a73b63a9 430: onsuccess: #2392: 1: Success after basepoints/gcc-13-47 [...] discards 088b48af21 429: onsuccess: #2391: 1: Success after binutils: 3 commits discards 54359d2ba9 428: onsuccess: #2390: 1: Success after binutils/gcc: 8 commits discards df21d9f404 427: onsuccess: #2389: 1: Success after binutils/gcc: 11 commits discards 6e844c6473 426: onsuccess: #2388: 1: Success after binutils/gcc: 11 commits discards f562add3cf 425: onsuccess: #2387: 1: Success after binutils/gcc: 13 commits discards edb25569e6 424: onsuccess: #2386: 1: Success after binutils/gcc: 3 commits discards b469a08128 423: onsuccess: #2385: 1: Success after binutils/gcc: 14 commits discards f92d20b943 422: onsuccess: #2384: 1: Success after binutils/gcc: 12 commits discards c458f5c980 421: onsuccess: #2383: 1: Success after binutils/gcc: 7 commits discards 25a34ae088 420: onsuccess: #2382: 1: Success after gcc: 2 commits discards e900bc74c0 419: onsuccess: #2381: 1: Success after binutils/gcc: 7 commits discards 5b79c3d224 418: onsuccess: #2380: 1: Success after binutils/gcc: 14 commits discards 7ffde5a8d3 417: onsuccess: #2379: 1: Success after binutils/gcc: 13 commits discards b8dfc633e5 416: onsuccess: #2378: 1: Success after binutils/gcc: 4 commits discards 6b69c6399c 415: onsuccess: #2377: 1: Success after binutils/gcc: 15 commits discards d35c39681b 414: onsuccess: #2376: 1: Success after binutils/gcc: 55 commits discards b9109f175b 413: onsuccess: #2375: 1: Success after binutils/gcc: 7 commits discards 2e3381e1a9 412: onsuccess: #2374: 1: Success after binutils/gcc: 4 commits discards 08a5ffc3af 411: onsuccess: #2373: 1: Success after binutils/gcc: 6 commits discards 2e0ed642ee 410: onsuccess: #2372: 1: Success after binutils/gcc: 27 commits discards 0f60d0597b 409: onsuccess: #2371: 1: Success after binutils/gcc: 13 commits discards 15f6da5017 408: onsuccess: #2370: 1: Success after basepoints/gcc-13-46 [...] discards 0de4010b12 407: onsuccess: #2369: 1: Success after binutils/gcc: 2 commits discards 455a3ce2f5 406: onsuccess: #2368: 1: Success after binutils/gcc: 8 commits discards 3df1a2faab 405: onsuccess: #2367: 1: Success after basepoints/gcc-13-45 [...] discards 4e6302590c 404: onsuccess: #2366: 1: Success after basepoints/gcc-13-45 [...] discards 40079a86d9 403: onsuccess: #2365: 1: Success after binutils/gcc: 2 commits discards e60c480b50 402: onsuccess: #2364: 1: Success after binutils/gcc: 19 commits new 98ebb3ce93 402: onsuccess: #2364: 1: Success after binutils/gcc: 19 commits new f5378c0b70 403: onsuccess: #2365: 1: Success after binutils/gcc: 2 commits new 00a88edf30 404: onsuccess: #2366: 1: Success after basepoints/gcc-13-45 [...] new 8db2d198a8 405: onsuccess: #2367: 1: Success after basepoints/gcc-13-45 [...] new 1a0c22ed30 406: onsuccess: #2368: 1: Success after binutils/gcc: 8 commits new 0cf7cce1fe 407: onsuccess: #2369: 1: Success after binutils/gcc: 2 commits new a4257ed867 408: onsuccess: #2370: 1: Success after basepoints/gcc-13-46 [...] new ea3389d925 409: onsuccess: #2371: 1: Success after binutils/gcc: 13 commits new ae64d839e5 410: onsuccess: #2372: 1: Success after binutils/gcc: 27 commits new 46e2fee0cb 411: onsuccess: #2373: 1: Success after binutils/gcc: 6 commits new 52828f6ae1 412: onsuccess: #2374: 1: Success after binutils/gcc: 4 commits new c305125f21 413: onsuccess: #2375: 1: Success after binutils/gcc: 7 commits new 01c1119bee 414: onsuccess: #2376: 1: Success after binutils/gcc: 55 commits new 4d5c6c913f 415: onsuccess: #2377: 1: Success after binutils/gcc: 15 commits new 5db2cbe464 416: onsuccess: #2378: 1: Success after binutils/gcc: 4 commits new 0f56163cac 417: onsuccess: #2379: 1: Success after binutils/gcc: 13 commits new 5ba9bc6b33 418: onsuccess: #2380: 1: Success after binutils/gcc: 14 commits new 5ceeecd83e 419: onsuccess: #2381: 1: Success after binutils/gcc: 7 commits new 85fb43bcc5 420: onsuccess: #2382: 1: Success after gcc: 2 commits new 9b796e19b8 421: onsuccess: #2383: 1: Success after binutils/gcc: 7 commits new fa2b642f46 422: onsuccess: #2384: 1: Success after binutils/gcc: 12 commits new e2ba9acd33 423: onsuccess: #2385: 1: Success after binutils/gcc: 14 commits new b1ce2f1e7c 424: onsuccess: #2386: 1: Success after binutils/gcc: 3 commits new 06466c985e 425: onsuccess: #2387: 1: Success after binutils/gcc: 13 commits new 130f552431 426: onsuccess: #2388: 1: Success after binutils/gcc: 11 commits new a6459186c6 427: onsuccess: #2389: 1: Success after binutils/gcc: 11 commits new 7f08e73fec 428: onsuccess: #2390: 1: Success after binutils/gcc: 8 commits new f51df170b9 429: onsuccess: #2391: 1: Success after binutils: 3 commits new 3e054dc03c 430: onsuccess: #2392: 1: Success after basepoints/gcc-13-47 [...] new 6e0f9da320 431: onsuccess: #2393: 1: Success after binutils/gcc: 3 commits new 36c659ebec 432: onsuccess: #2394: 1: Success after binutils/gcc: 3 commits new 0f245b7091 433: onsuccess: #2395: 1: Success after binutils/gcc: 3 commits new 9fef19300f 434: onsuccess: #2396: 1: Success after binutils/gcc: 2 commits new e28d658f9d 435: onsuccess: #2397: 1: Success after basepoints/gcc-13-47 [...] new d428dd0499 436: onsuccess: #2398: 1: Success after binutils/gcc: 20 commits new 0756d0b827 437: onsuccess: #2399: 1: Success after binutils/gcc: 26 commits new 76b4064431 438: onsuccess: #2400: 1: Success after binutils/gcc: 7 commits new b5a3968e65 439: onsuccess: #2401: 1: Success after binutils/gcc: 4 commits new 7a294c19c1 440: onsuccess: #2402: 1: Success after binutils/gcc: 4 commits new dd2cb9f7fd 441: onsuccess: #2403: 1: Success after gcc: 3 commits new 91bb6c4117 442: onsuccess: #2404: 1: Success after binutils/gcc: 5 commits new 07920ad34c 443: onsuccess: #2405: 1: Success after binutils/gcc: 36 commits new 5a348ab524 444: onsuccess: #2406: 1: Success after binutils/gcc: 18 commits new 11799bb7b4 445: onsuccess: #2407: 1: Success after binutils/gcc: 8 commits new 876721ec2e 446: onsuccess: #2408: 1: Success after binutils/gcc: 5 commits new f425bbd3c7 447: onsuccess: #2409: 1: Success after binutils/gcc: 9 commits new ecbe7e9304 448: onsuccess: #2410: 1: Success after binutils/gcc: 18 commits new a1f67e2022 449: onsuccess: #2411: 1: Success after binutils/gcc: 11 commits new d872077b3a 450: onsuccess: #2412: 1: Success after binutils/gcc: 12 commits new 5e86ed2cee 451: onsuccess: #2413: 1: Success after binutils/gcc: 31 commits new fde0da9023 452: onsuccess: #2414: 1: Success after binutils/gcc: 17 commits new 9cf22a9117 453: onsuccess: #2415: 1: Success after binutils/gcc: 27 commits new 5d73cb1609 454: onsuccess: #2416: 1: Success after binutils/gcc: 6 commits new 74e95f8d4b 455: onsuccess: #2417: 1: Success after binutils/gcc: 2 commits new f257697224 456: onsuccess: #2418: 1: Success after binutils/gcc: 4 commits new 4ef0d00cfa 457: onsuccess: #2419: 1: Success after binutils/gcc: 3 commits new e47013b4b2 458: onsuccess: #2420: 1: Success after binutils/gcc: 9 commits new 2936fbb2bb 459: onsuccess: #2421: 1: Success after binutils/gcc: 11 commits new 0338e83231 460: onsuccess: #2422: 1: Success after gdb-13-branchpoint-1 [...] new 35dcdbb65d 461: onsuccess: #2423: 1: Success after binutils: 2 commits new 9a9519f6ab 462: onsuccess: #2424: 1: Success after gcc: 2 commits new 839f4c509b 463: onsuccess: #2425: 1: Success after binutils: 2 commits new 3a2fbcfcfe 464: onsuccess: #2426: 1: Success after basepoints/gcc-13-48 [...] new 4c4b6452a0 465: onsuccess: #2427: 1: Success after binutils/gcc: 3 commits new 1fd49243f8 466: onsuccess: #2428: 1: Success after binutils: 9 commits new 72e4f690af 467: onsuccess: #2429: 1: Success after basepoints/gcc-13-48 [...] new 6bb938c297 468: onsuccess: #2430: 1: Success after binutils/gcc: 11 commits new 34b90afbbb 469: onsuccess: #2431: 1: Success after binutils/gcc: 7 commits new 5a313f61b4 470: onsuccess: #2432: 1: Success after gcc: 2 commits new e9e89ae4ac 471: onsuccess: #2433: 1: Success after gcc: 2 commits new 22118cd155 472: onsuccess: #2434: 1: Success after binutils: 2 commits new 487d888764 473: onsuccess: #2435: 1: Success after binutils/gcc: 3 commits new e9bb8206d7 474: onsuccess: #2436: 1: Success after basepoints/gcc-13-49 [...] new 5a9ce60946 475: onsuccess: #2437: 1: Success after gdb-13-branchpoint-2 [...] new 62118db9e8 476: onsuccess: #2438: 1: Success after gcc: 17 commits new c8239475ce 477: onsuccess: #2439: 1: Success after binutils/gcc: 2 commits new 6e711f96f3 478: onsuccess: #2440: 1: Success after basepoints/gcc-13-49 [...] new 779ec9bcd8 479: onsuccess: #2441: 1: Success after binutils/gcc: 2 commits new c2c6924d5b 480: onsuccess: #2442: 1: Success after binutils/gcc: 6 commits new b5261e72ea 481: onsuccess: #2443: 1: Success after gdb-13-branchpoint-2 [...] new b876fbf4db 482: onsuccess: #2444: 1: Success after binutils/gcc: 2 commits new 9ffefa42b0 483: onsuccess: #2445: 1: Success after binutils: 11 commits new 003a7b6aa7 484: onsuccess: #2446: 1: Success after binutils/gcc: 3 commits new b78c544df0 485: onsuccess: #2447: 1: Success after binutils/gcc: 3 commits new 2be502dc77 486: onsuccess: #2448: 1: Success after binutils/gcc: 3 commits new d9b727d86e 487: onsuccess: #2449: 1: Success after binutils/gcc: 7 commits new 2bf7bb9a3f 488: onsuccess: #2450: 1: Success after binutils: 7 commits new bba545e12d 489: onsuccess: #2451: 1: Success after binutils/gcc: 4 commits new 92c5b5510f 490: onsuccess: #2452: 1: Success after binutils/gcc: 7 commits new d9c5e3e13d 491: onsuccess: #2453: 1: Success after binutils/gcc: 8 commits new 7b99e6322a 492: onsuccess: #2454: 1: Success after binutils/gcc: 2 commits new b35ded4bfb 493: onsuccess: #2455: 1: Success after binutils: 14 commits new 284d099838 494: onsuccess: #2456: 1: Success after binutils/gcc: 23 commits new 7233ace12e 495: onsuccess: #2457: 1: Success after binutils/gcc: 19 commits new 53bb4f2596 496: onsuccess: #2458: 1: Success after binutils/gcc: 4 commits new ca960e1342 497: onsuccess: #2459: 1: Success after binutils/gcc: 6 commits new 88d4fe6409 498: onsuccess: #2460: 1: Success after binutils/gcc: 7 commits new 9eadf9a255 499: onsuccess: #2461: 1: Success after binutils/gcc: 16 commits new 8c827fcb5e 500: onsuccess: #2462: 1: Success after binutils/gcc: 6 commits new 90bc7fafd8 501: onsuccess: #2463: 1: Success after binutils/gcc: 8 commits new 8fdde6497b 502: onsuccess: #2464: 1: Success after binutils/gcc: 4 commits new 59826ef68c 503: onsuccess: #2465: 1: Success after binutils/gcc: 33 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 (0395640e05) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-aarch64 [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1792 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2788 bytes 03-build_abe-binutils/console.log.xz | Bin 40404 -> 41708 bytes 04-build_abe-gcc/console.log.xz | Bin 215144 -> 217872 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3908 -> 3832 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2748 -> 2820 bytes 07-check_regression/console.log.xz | Bin 4696 -> 4832 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 19 +- 08-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/g++.log.xz | Bin 3630616 -> 3651460 bytes sumfiles/g++.sum | 106 +- sumfiles/gcc.log.xz | Bin 3149740 -> 3157248 bytes sumfiles/gcc.sum | 5090 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1043432 -> 1055344 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2188 -> 2192 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 219556 -> 220076 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2552 -> 2540 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 454428 -> 463960 bytes sumfiles/libstdc++.sum | 10 +- 31 files changed, 2684 insertions(+), 2693 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[gcc] branch master updated (12b0d35ec52 -> 9e6ac747ac5)

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 12b0d35ec52 c++: class-head parsing and CPP_TEMPLATE_ID access [PR108275] new 9e6ac747ac5 [Committed] PR rtl-optimization/108292: Revert "Improve ix8 [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/config/i386/i386-expand.cc | 46 +++++++++++++++++++--------------- gcc/testsuite/gcc.target/i386/cmov10.c | 21 ---------------- 2 files changed, 26 insertions(+), 41 deletions(-) delete mode 100644 gcc/testsuite/gcc.target/i386/cmov10.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

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

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 7935529517 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 7f78a91c10 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 5089c3e5aa 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 5fb6e2d380 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards f93ccfe71f 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards ce01d480fd 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 521e6530c6 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards f8c3017758 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 279a96c0c3 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 39294dcd99 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 4451e68749 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards a3d5368f2e 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 80ab1f4231 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards b563817e47 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 3b5a4c933e 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards d162b705c8 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 9fe7907eee 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 65d9a3c9f4 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards fe01318126 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 5d5ed9c77d 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 62a5303492 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards e24d767e7f 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards a8b0ce429e 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 06831c0192 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 30496df901 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 1fb589bdfb 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 4376b68f22 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 60e167c8c2 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 119e663d8c 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 777112d062 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards e29e0a1ab7 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 9773220a52 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 44c0de6816 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards b657d66f54 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 55b02584fa 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards ca663d3b7d 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 2bbdb4f0e4 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 33c10c36b6 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 381f7664b3 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 639b188d4f 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 0f2ad9cc7e 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 480b9fab4c 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 1c5e050065 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards e5831e980c 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards e9bf1dea7a 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 8243cb488b 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 034916c1ba 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 38237df0c6 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards c1a21389b0 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards f9a97df07b 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards a37d3445c3 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards fa00312752 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 7c32295ec5 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards cf7f4f55b9 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards 6af4729b49 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards 9ea29df695 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 4960d9b46d 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards e64d513b64 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards 28a87cff6f 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards f11becca58 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards 38f70b27c5 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards aa5923b34c 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 0197790001 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards c1138a8f6c 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards b5cf496402 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards f6f5a6ac13 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards 4f15790638 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 5a0bb834a9 235: onsuccess: #2483: 1: Success after linux: 108 commits discards 956bfbfd57 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards fe0fec27ef 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards 39943a75c9 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards e2140cb811 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards 7ceebd5c6b 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards 81f759cd8e 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards 9cea9611f9 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards 15ad0f6121 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards f3621a882b 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] discards d075aac176 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards d11b7e2e40 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] discards 4dff38ecda 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] discards 9c822f6ff0 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] discards b3797aa6a6 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards 2bf70ac805 220: onsuccess: #2465: 1: Success after linux: 572 commits discards 9e5f8af9b7 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards af6a7f97b1 218: onsuccess: #2461: 1: Success after linux: 916 commits discards fa7d3bc48e 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards 658acf24ab 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards b13bf90520 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards 3c9a760f30 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] discards 83cd2b4ecb 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] discards b635995219 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] discards df4cf3e795 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits discards deef36c3c1 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits discards 78d12e2aa7 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] discards 67b3cab79c 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] discards 450f89654f 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] discards 2757ab7faf 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] discards 4508e32b48 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] discards 0cfb89bbc2 204: onsuccess: #2435: 1: Success after linux: 3 commits discards dbd540791b 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards 3dc3508bbf 202: onsuccess: #2431: 1: Success after linux: 944 commits new 607e9f4398 202: onsuccess: #2431: 1: Success after linux: 944 commits new 9179eb0c0b 203: onsuccess: #2433: 1: Success after binutils: 27 commits new 958391771f 204: onsuccess: #2435: 1: Success after linux: 3 commits new 83ab182bb4 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] new 11740953e4 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] new ab58c57ad8 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] new 7a74a116eb 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] new 6133f97453 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] new 1c39d6cb1d 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits new d5a1264532 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits new 6b0c64f9b6 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] new 9228adbd21 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] new 6cb917d47a 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] new 902b2d419f 215: onsuccess: #2455: 1: Success after binutils: 3 commits new 72e8e6847e 216: onsuccess: #2457: 1: Success after linux: 1736 commits new 3fdfbe07e1 217: onsuccess: #2459: 1: Success after binutils: 3 commits new b4afc9c7df 218: onsuccess: #2461: 1: Success after linux: 916 commits new 148e9f6aba 219: onsuccess: #2463: 1: Success after binutils: 3 commits new cca2bd7eb1 220: onsuccess: #2465: 1: Success after linux: 572 commits new a0a99ab67d 221: onsuccess: #2467: 1: Success after binutils: 3 commits new 4b024ac862 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] new d75065900d 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] new 0e69ddfb02 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] new 19e33e2c72 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new 7e1af6da40 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] new 475b90a062 227: onsuccess: #2474: 1: Success after gcc: 2 commits new b0815c6d64 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new e5c387ae2a 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new 813f07675e 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new f11e05c887 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new 7f479f895a 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new 350476c8d3 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new 25a9d1f1a2 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new c7f3b0be66 235: onsuccess: #2483: 1: Success after linux: 108 commits new e65b7ae2bb 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 09772d920c 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new 4a598573f4 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new 0e48493ae6 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new d2c5e15454 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new afbfe927f9 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 6ee5e683b4 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new a5aec0a343 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new b4061ef638 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new 6bd7485bac 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 1da753d526 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new c4d41b8d76 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new 49ad8b79f4 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 17515df9be 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new 8efd5f5af9 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 71e824668d 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 647352e07d 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new 8cc6fccb0a 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new 0674e1973f 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 43a572314d 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new cb752f8fb6 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 22e6ee4392 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new a0cf08b627 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new c86a4f628e 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new f205d5b1f0 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 314caef53c 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 86f4d89e9d 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new c70cd4a421 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 274138298a 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 075a4fede7 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new f30a7d25c5 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 73cdd00ff8 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 64fb340e11 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 872ba7b97f 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 78c19b5ac1 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 1064794c6c 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 8e0b12ad3c 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 1b833394d2 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 0f020d8ae5 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 92b1110e61 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 21953674bb 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 762b77ea5f 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 482139094a 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 6356d105e2 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 3a7ef90e56 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new e586e9d48a 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 7858bcdec8 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 90e970ba85 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new feb8306314 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new efaa418b71 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 54a28e1c0e 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 38b4b6ef38 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 74e4745fd9 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 6a29911f52 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new b1ee865649 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new eef128e3b7 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new aae9ef6cfe 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 7102140706 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 080e2d1fc7 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new e2abb449e4 295: onsuccess: #2545: 1: Success after linux: 10 commits new 4219010bb9 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new cc04a7881d 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new bde767c42b 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new caac9cd72e 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 733c8aefb3 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 10519ccbb1 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 458b32f3ca 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new ed9d40c05a 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] 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 (7935529517) \ 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 1744 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 32040 -> 32468 bytes 04-build_abe-stage1/console.log.xz | Bin 73508 -> 73804 bytes 06-build_abe-linux/console.log.xz | Bin 8996 -> 8988 bytes 07-build_abe-glibc/console.log.xz | Bin 245716 -> 245488 bytes 08-build_abe-stage2/console.log.xz | Bin 205284 -> 204996 bytes 09-build_abe-gdb/console.log.xz | Bin 39512 -> 39916 bytes 10-build_abe-qemu/console.log.xz | Bin 31052 -> 31252 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2976 -> 3044 bytes 13-check_regression/console.log.xz | Bin 6256 -> 6836 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 8 +- 13-check_regression/mail-body.txt | 68 +- 13-check_regression/results.compare | 34 +- 13-check_regression/results.compare2 | 52 +- 13-check_regression/results.regressions | 34 +- 14-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 70 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 34 +- sumfiles/g++.log.xz | Bin 3407636 -> 3417616 bytes sumfiles/g++.sum | 40 +- sumfiles/gcc.log.xz | Bin 3026268 -> 3032196 bytes sumfiles/gcc.sum | 5164 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1039004 -> 1043028 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214648 -> 214604 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2700 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 430012 -> 435320 bytes sumfiles/libstdc++.sum | 8 +- 43 files changed, 2774 insertions(+), 2860 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (e9f116a428 -> 8c8b98accf)

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_gdb/master-arm in repository toolchain/ci/base-artifacts. discards e9f116a428 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] discards c67c81d928 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] discards 39ba4c3378 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] discards c4463e7464 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards 3e1623e592 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards 4101a035d9 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 5a0b864061 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards f1d64c1764 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits discards 16b9821168 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits discards f13f6cb623 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] discards f707ee2b3a 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits discards 80fcd42f32 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards ae03c9e6c0 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] discards 392cfad971 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards 898ca7560a 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards 09b529f500 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards c0eed13e99 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards d34d9d4093 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards f6b3ca5eff 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 500bf62188 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 8423cf423a 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 58fe9c4907 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards b99a0f47df 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards 1dac1e972b 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 096e1c2516 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards b666b44956 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards 675e0de874 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards 1a5da410b0 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 80d941ad6c 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards cc55955407 125: onsuccess: #614: 1: Success after linux: 12 commits discards 716fa3c47a 124: onsuccess: #612: 1: Success after binutils: 18 commits discards bb64b1ced0 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards 9b0d89c081 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards ab230e10cf 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards b121e603f4 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards 56fa15e372 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 6f3f3073c7 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 4bc4352ba8 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards 6739be0d82 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 41e0d84d0c 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards 3588dae320 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 436a490b06 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards 1f02fb3dcf 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards caf885490a 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards e172642df6 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards 3043ef1458 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 4dcc6fad6a 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards 1bdaad0de9 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 324b7f616c 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 8c4c7373e7 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 0ef6223e94 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards b8a7bf0377 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 7ff051b5b7 102: onsuccess: #586: 1: Success after binutils: 5 commits discards bddb186229 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards a995ece949 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards fdf2938d97 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards f4fe821951 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 48ec703e66 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards a488068809 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 1a56da9788 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 707db10b5a 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards ad842dba91 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards ca06fb3835 92: onsuccess: #575: 1: Success after linux: 34 commits discards fb097dac96 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 731a858fa2 90: onsuccess: #572: 1: Success after binutils: 15 commits discards f529d5544c 89: onsuccess: #570: 1: Success after linux: 11 commits discards beedc34dcc 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 1907c020a5 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 60a40896be 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 14537aeace 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards 0f0a91b800 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 5493a40a1f 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards 15cbdde84b 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards 471288c2e8 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards 31160b6c26 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards 8ac3153eee 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards 378a30a49a 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards 89c4a3e8eb 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards ee4ecbb319 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards ee0e7ba2c4 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards ce82e93213 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards 805468d5f7 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 74a13ed02c 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 57bc2799ab 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards ec7db68d86 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards dcc1d35a89 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards 7bb8fedf1e 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards 43cfe799fb 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards c210b4dc31 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 24ada70878 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards 4981b55623 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards b058e4ad47 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 22bf333200 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards ae628412a5 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 3a745f94f5 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards ae8f0da706 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards 771a7d5973 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards 48d8781b3a 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards 886bc195ab 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards ffe1e621e9 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 498d219552 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new 92500b132d 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new 26c25ce4e9 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new b08f81ae12 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new 413b475139 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new b41d7893a2 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new 23a558e9bb 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 3288a9f9e8 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new cf7bc426d3 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new b98f41c311 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new 427f3420ad 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 379920a336 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new fd364a33c7 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new 47d56dc210 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 0cbd0e617c 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 7548235548 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new 0141a5e8e3 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new 4b3e259a90 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 571f0c01d3 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new 79cbf07b77 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new de6a10ff79 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new f3883700b6 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new 6776268cf6 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new 7dd9dec543 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new bdc8c25359 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new 0139baec65 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new 70883d4e19 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 9cc19f142b 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new f5d8be07e6 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new 0e8d2b3536 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 1cee6b3a2f 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 5535112b09 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 4f45516279 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new ea5b7a9e4a 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 77050fcdbd 87: onsuccess: #567: 1: Success after binutils: 8 commits new 752ebc62b8 88: onsuccess: #569: 1: Success after glibc: 10 commits new d4962cb940 89: onsuccess: #570: 1: Success after linux: 11 commits new bfb82a6046 90: onsuccess: #572: 1: Success after binutils: 15 commits new 9162062ece 91: onsuccess: #574: 1: Success after glibc: 3 commits new 0f7347c865 92: onsuccess: #575: 1: Success after linux: 34 commits new d79774f0bb 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 76e82049c0 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new a29aafb5dc 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new 3a0a116dc2 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new dd2736765f 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 1579d3734b 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new dcfce89f9d 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 529e980e36 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 12d0c474a3 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 150435e76e 102: onsuccess: #586: 1: Success after binutils: 5 commits new 80c25146ca 103: onsuccess: #589: 1: Success after binutils: 3 commits new 8682b5136b 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 9c69e120bc 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new 42abbc7be0 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new a561777d5d 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new fb03ced75f 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 83bd763110 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new f0d9766d49 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new 22f0aa480d 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new 2756fd3e7b 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new 009e2a1351 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new 14625d92b8 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 9cd8f12882 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new 3998409bac 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 92030f643c 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new daa7bc9b5c 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new ce6c555217 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 57642c4cf0 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new b2cc5de979 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new d85ecd8774 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 1613531001 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new e18d8273ec 124: onsuccess: #612: 1: Success after binutils: 18 commits new b4cb7e1cf1 125: onsuccess: #614: 1: Success after linux: 12 commits new a2c253dc69 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new ce4714f13c 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new c500b2906b 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 0206894f11 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new a3117a2cb8 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new fdd6ba7a59 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new c08fb5f074 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new 21a58a322d 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new 77ecdc979a 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new a875bbf47a 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 9bb0cb8582 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new 1a96695727 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new 427474d5ff 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new affbb70920 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new 8a3798e3a0 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new 7d58885988 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new 697fe93a4f 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] new 424c0be6ef 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 367b98d245 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits new b182e02973 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new 8bcb898b24 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits new f08fbdcbd0 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits new afa3918cc0 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 596880d3c5 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 1efe29c70e 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 9508460f66 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 23ec1e4c8c 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] new 8a7594b821 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] new 36487debd1 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] new 8c8b98accf 155: onsuccess: #649: 1: 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 (e9f116a428) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] 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 1728 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 53412 -> 54152 bytes 04-build_abe-gcc/console.log.xz | Bin 240576 -> 241588 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8992 -> 8960 bytes 07-build_abe-glibc/console.log.xz | Bin 237316 -> 237616 bytes 08-build_abe-gdb/console.log.xz | Bin 52300 -> 51516 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3864 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2212 -> 2512 bytes 11-check_regression/console.log.xz | Bin 17104 -> 10864 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 134 +- 11-check_regression/mail-body.txt | 223 +- 11-check_regression/results.compare | 92 +- 11-check_regression/results.compare2 | 3941 ++------------------- 11-check_regression/results.regressions | 96 +- 12-update_baseline/console.log | 38 +- 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 | 225 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 96 +- sumfiles/gdb.log.xz | Bin 1803940 -> 1756232 bytes sumfiles/gdb.sum | 5633 +++++++++++++++---------------- 31 files changed, 3411 insertions(+), 7121 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[binutils-gdb] branch master updated (cabd67874a6 -> 1a8605a8c79)

by git＠git.linaro.org

1 year, 10 months

[linux] branch master updated (41c03ba9beea -> 5e9af4b42660)

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 linux. from 41c03ba9beea Merge tag 'for_linus' of git://git.kernel.org/pub/scm/linu [...] new 9d8b5376cc28 fbdev: make offb driver tristate new 8d8cf163c8d8 fbdev: omapfb: use strscpy() to instead of strncpy() new 6b90032c7340 fbdev: atyfb: use strscpy() to instead of strncpy() new f685dd7a8025 fbdev: matroxfb: G200eW: Increase max memory from 1 MB to 16 MB new 634cf6ead939 fbdev: omapfb: avoid stack overflow warning new 5e9af4b42660 Merge tag 'fbdev-for-6.2-rc3' of git://git.kernel.org/pub/ [...] The 6 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: drivers/video/fbdev/Kconfig | 4 ++-- drivers/video/fbdev/aty/atyfb_base.c | 3 +-- drivers/video/fbdev/matrox/matroxfb_base.c | 4 ++-- drivers/video/fbdev/omap/omapfb_main.c | 5 ++--- drivers/video/fbdev/omap2/omapfb/dss/dsi.c | 28 ++++++++++++++++++---------- 5 files changed, 25 insertions(+), 19 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[gcc] branch master updated (9807c31af91 -> 12b0d35ec52)

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 9807c31af91 Fix atomic operations on PA-RISC 2.0 processors. new 12b0d35ec52 c++: class-head parsing and CPP_TEMPLATE_ID access [PR108275] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/cp/parser.cc | 23 +++++++++++++++++------ gcc/testsuite/g++.dg/parse/access14.C | 18 ++++++++++++++++++ 2 files changed, 35 insertions(+), 6 deletions(-) create mode 100644 gcc/testsuite/g++.dg/parse/access14.C -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits January 2023