Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[gcc] branch releases/gcc-11 updated (06e1f909776 -> f8ddc6c5d50)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-11 in repository gcc. from 06e1f909776 gcc/config/t-i386: add build dependencies on i386-builtin-t [...] new f8ddc6c5d50 Daily bump. 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/ChangeLog | 10 ++++++++++ gcc/DATESTAMP | 2 +- 2 files changed, 11 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 updated (ee3772a636 -> 691321a263)

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_binutils/master-aarch64 in repository toolchain/ci/base-artifacts. from ee3772a636 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] new 691321a263 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] 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 1692 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 38916 -> 37620 bytes 04-build_abe-gcc/console.log.xz | Bin 214368 -> 212360 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8420 -> 9092 bytes 07-build_abe-glibc/console.log.xz | Bin 241712 -> 238892 bytes 08-build_abe-gdb/console.log.xz | Bin 38192 -> 37676 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3840 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2568 -> 2140 bytes 11-check_regression/console.log.xz | Bin 5832 -> 6172 bytes 11-check_regression/results.compare | 8 +- 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/binutils.log.xz | Bin 58468 -> 58740 bytes sumfiles/binutils.sum | 60 ++--- sumfiles/gas.log.xz | Bin 81112 -> 81116 bytes sumfiles/gas.sum | 268 +++++++++++----------- sumfiles/ld.log.xz | Bin 121200 -> 121420 bytes sumfiles/ld.sum | 342 ++++++++++++++--------------- 29 files changed, 369 insertions(+), 369 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-allmodconfig updated (e14f0253c2 -> 423f7d7252)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-allmodconfig in repository toolchain/ci/base-artifacts. from e14f0253c2 16: onsuccess: #484: 33: Success after binutils/gcc/qemu: 22 [...] new 423f7d7252 17: onsuccess: #485: 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 1920 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30972 -> 30352 bytes 04-build_abe-stage1/console.log.xz | Bin 72748 -> 73276 bytes 05-build_abe-qemu/console.log.xz | Bin 31880 -> 31984 bytes 06-build_linux/console.log.xz | Bin 5064 -> 3676 bytes 08-check_regression/console.log.xz | Bin 3960 -> 4588 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 16 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_eabi_stm32/gnu_eabi-master-arm_eabi-coremark-O3 updated (3305aae99d -> 33abbaff13)

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_gnu_eabi_stm32/gnu_eabi-master-arm_eabi-coremark-O3 in repository toolchain/ci/base-artifacts. from 3305aae99d 2: onsuccess: #315: 1: [TCWG CI] No change after binutils: 1 [...] new 33abbaff13 3: onsuccess: #318: 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 1724 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30724 -> 30000 bytes 04-build_abe-stage1/console.log.xz | Bin 89744 -> 89436 bytes 06-build_abe-newlib/console.log.xz | Bin 16640 -> 16748 bytes 07-build_abe-stage2/console.log.xz | Bin 160888 -> 161080 bytes 08-benchmark/benchmark-build.log | 98 +++++++++++++------------ 08-benchmark/benchmark.log | 96 ++++++++++++------------ 08-benchmark/console.log.xz | Bin 3688 -> 3752 bytes 09-check_regression/console.log.xz | Bin 4004 -> 5056 bytes 09-check_regression/csv-results-0/results.csv | 2 +- 09-check_regression/csv-results-1/perf.csv | 2 +- 09-check_regression/csv-results-1/results.csv | 12 +-- 09-check_regression/results-brief.csv | 8 +- 09-check_regression/results-compare.csv | 2 +- 09-check_regression/results-full.csv | 12 +-- 09-check_regression/results-internal.csv | 12 +-- 09-check_regression/results.csv | 12 +-- 09-check_regression/results.log | 10 +-- 10-update_baseline/console.log | 8 +- dashboard/dashboard-generate.sh | 2 +- dashboard/squad/Mean/results-functional.json | 4 - dashboard/squad/Mean/results-metadata.json | 10 --- dashboard/squad/Mean/results-metrics.json | 3 - dashboard/squad/coremark/results-metadata.json | 12 +-- dashboard/squad/coremark/results-metrics.json | 2 +- dashboard/squad/dashboard-push-squad.sh | 13 +--- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/newlib_rev | 2 +- mail/jira-body.txt | 26 +++++-- mail/mail-body.txt | 26 +++++-- mail/mail-subject.txt | 2 +- manifest.sh | 30 ++++---- results_id | 2 +- 35 files changed, 211 insertions(+), 201 deletions(-) delete mode 100644 dashboard/squad/Mean/results-functional.json delete mode 100644 dashboard/squad/Mean/results-metadata.json delete mode 100644 dashboard/squad/Mean/results-metrics.json -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check_bootstrap/master-aarch64-check_bootstrap updated (fb939b5b25 -> 0060a3c9ac)

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_bootstrap/master-aarch64-check_bootstrap in repository toolchain/ci/base-artifacts. from fb939b5b25 52: onsuccess: #587: 1: Success after binutils/gcc: 31 commits new 0060a3c9ac 53: onsuccess: #588: 1: Success after binutils/gcc: 38 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1716 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 38828 -> 37744 bytes 04-build_abe-bootstrap/console.log.xz | Bin 271340 -> 270836 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3824 bytes 06-build_abe-check_bootstrap/console.log.xz | Bin 2876 -> 2676 bytes 07-check_regression/console.log.xz | Bin 5368 -> 6876 bytes 07-check_regression/mail-body.txt | 52 - 07-check_regression/results.compare | 30 +- 07-check_regression/results.compare2 | 302 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 54 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/g++.log.xz | Bin 3665756 -> 3668884 bytes sumfiles/g++.sum | 188 +- sumfiles/gcc.log.xz | Bin 3223760 -> 3231324 bytes sumfiles/gcc.sum | 5106 ++++++++++++++------------- sumfiles/gfortran.log.xz | Bin 1090360 -> 1093208 bytes sumfiles/gfortran.sum | 52 +- sumfiles/libatomic.log.xz | Bin 2352 -> 2348 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 213564 -> 213624 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2724 -> 2724 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 467728 -> 468084 bytes sumfiles/libstdc++.sum | 182 +- 31 files changed, 3135 insertions(+), 2885 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap updated (9ef65d5802 -> b39ec5b745)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap in repository toolchain/ci/base-artifacts. discards 9ef65d5802 160: onsuccess: #1587: 2: Success after binutils/gcc: 5 commits discards 64b12ba5d3 159: onsuccess: #1586: 2: Success after binutils/gcc: 18 commits discards 78cce47d6e 158: onsuccess: #1585: 2: Success after binutils/gcc: 12 commits discards 622ed4632e 157: onsuccess: #1584: 2: Success after binutils/gcc: 5 commits discards 76d7684e23 156: onsuccess: #1583: 2: Success after binutils/gcc: 2 commits discards 9ec770ee84 155: onsuccess: #1582: 2: Success after binutils/gcc: 15 commits discards ca35b6af09 154: onsuccess: #1581: 2: Success after binutils/gcc: 11 commits discards 27481daad4 153: onsuccess: #1580: 2: Success after binutils/gcc: 2 commits discards 9f5d4cf417 152: onsuccess: #1579: 2: Success after gcc: 2 commits discards 00545d5981 151: onsuccess: #1578: 2: Success after gcc: 2 commits discards 7b4dfb4326 150: onsuccess: #1577: 2: Success after gcc: 3 commits discards 9ba94670fb 149: onsuccess: #1576: 2: Success after binutils/gcc: 13 commits discards 2b7fbec8c2 148: onsuccess: #1575: 2: Success after binutils/gcc: 12 commits discards e2d6d99cf6 147: onsuccess: #1574: 2: Success after binutils/gcc: 16 commits discards dc97c338e9 146: onsuccess: #1573: 2: Success after binutils: 7 commits discards d4a2eeb9d9 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 commits discards ed08dd27ba 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits discards c1216bd316 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits discards 4385fc6168 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] discards f94f3d9e99 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits discards 053b046a4e 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits discards 3c32c1d65c 139: onsuccess: #1566: 1: Success after gcc: 5 commits discards 495380512c 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] discards 132e063435 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] discards 8ff6c14557 136: onsuccess: #1561: 2: Success after binutils: 3 commits discards 292b31efb1 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits discards da347290a4 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits discards f859a98952 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits discards e0681b5620 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits discards eab3adfe36 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits discards 0ba1847d9b 130: onsuccess: #1554: 2: Success after gcc: 9 commits discards 8e476dfca6 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] discards 52762a46cb 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards 17e0cac955 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] discards 87b3870c00 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] discards 0bc7996d97 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards 4afc33c133 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards 1891233a77 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards 3c3bf30983 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 56d1aab18d 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards c16c20000b 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards cc9f147b36 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards 335a806398 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards 13eddc13a6 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards cb3773833a 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards 223b3487c5 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards e84b67d9ca 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards 210b4bd621 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards c98f3bd6be 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards d17dd0e2a5 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards 0dd09a7a0c 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 55256540fe 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards 121fdfa4be 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards 9f7cd77aae 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards aefcfd907d 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards 6d25d7b06a 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards b60d28e7de 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards abc446bc10 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards 1fa7d83629 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards 2e6973e42f 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards f4812517b3 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards 2782a5b524 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards 50f5057f06 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 3342da6fca 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards 766e8604a4 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards 3a37453603 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards 7a377c250c 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards 3abd4608a9 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards fec4dc2182 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 704a1d38e0 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards b7d665193b 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards cdb1dff3ec 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards cd27654fb9 88: onsuccess: 1: Success after gcc: 20 commits discards 99e38e01c5 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards df56bacdc0 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards ae261bf16d 85: onsuccess: 2: Success after binutils: 4 commits discards 8466a86f98 84: onsuccess: 2: Success after gcc: 9 commits discards de2e928a32 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards 2737284332 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards ee60c0bd61 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards b182bcec55 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 88614c529f 79: onsuccess: 1: Successful build after gcc: 3 commits discards ff4fd965f4 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 84e1bf091a 77: force: 2: Successful build after gcc: 32 commits discards bda264e4d0 76: onsuccess: 2: Successful build after binutils: 10 commits discards adb31d0481 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 8347d562d2 74: onsuccess: 2: Successful build after gcc: 13 commits discards d85c0d3ce8 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 52367f23d3 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards a4675394b4 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 814959f35f 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 096adefaa7 69: onsuccess: 2: Successful build after baseline build: no [...] discards 542e48773c 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards c38059377e 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 39a32efee5 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards 2bd4b101a7 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards dd9d9e9e1b 64: onsuccess: 2: Successful build after gcc: 7 commits discards 3100064013 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 74479681c0 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 734df18357 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards 6ecbe915ac 60: onsuccess: 1: Successful build after gcc: 15 commits new a780dbe08d 60: onsuccess: 1: Successful build after gcc: 15 commits new 7ee3b73070 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 2f4a8798cf 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 99760cdeee 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 08b90f14e7 64: onsuccess: 2: Successful build after gcc: 7 commits new 4ec024d425 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new c2aca63199 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 33f0940679 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 0c5080a5b5 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 8f3252722e 69: onsuccess: 2: Successful build after baseline build: no [...] new ab2018f5f7 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new de436b529a 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new deb69db537 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 206dd60266 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 5f34789a05 74: onsuccess: 2: Successful build after gcc: 13 commits new 339deb8f6a 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new fc93f8baf3 76: onsuccess: 2: Successful build after binutils: 10 commits new bade906b55 77: force: 2: Successful build after gcc: 32 commits new 1db313506e 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new cbba5078e2 79: onsuccess: 1: Successful build after gcc: 3 commits new c7dbda42d1 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new c2ebe86c8f 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 755b346dda 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 30d17c26cd 83: onsuccess: 2: Success after binutils/gcc: 7 commits new 313aaf62f1 84: onsuccess: 2: Success after gcc: 9 commits new 3ba6943ebe 85: onsuccess: 2: Success after binutils: 4 commits new c127567ec0 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new 20e4876fe3 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new 0bff3b4d20 88: onsuccess: 1: Success after gcc: 20 commits new 1da94689f8 89: onsuccess: 2: Success after binutils/gcc: 39 commits new e4d45672b3 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 6ab5ab1b6d 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 8d84db5a1d 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 0b646d0198 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new 8cc2b68ae8 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new 7a6ceae3a7 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new 578bf83850 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new f2c473ccb8 97: onsuccess: #1481: 2: Success after gcc: 8 commits new e628c62085 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new a7b406e524 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new 2d7ceab059 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new af96260374 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new e2620d5ad9 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new 7ddadad8a9 103: onsuccess: #1524: 2: Success after gcc: 2 commits new 65675fe561 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 8c27061b14 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 17d525f64b 106: onsuccess: #1527: 2: Success after gcc: 2 commits new 037e8c7ae5 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new c31c9a6412 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new ac92518784 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new a6bca91bf9 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new c01b307834 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new 6e5dcf3cda 112: onsuccess: #1533: 2: Success after gcc: 5 commits new a111129558 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new 191f32d3f4 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new c5439f49ca 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new 161b4e1308 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 39a9b211a3 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new aa4233c7d8 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new 553e7823aa 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new 2c0ce44215 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new f85603aeec 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new d1a76256a3 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new a681f0db72 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new 42170132b4 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new 92b89c9828 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new 17e703fc11 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] new 4fb9722358 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] new 834894756d 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new 2f4dd96444 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] new b9420ffde0 130: onsuccess: #1554: 2: Success after gcc: 9 commits new 7a9ac471d3 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits new c248a0c42d 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits new 4eb2654c56 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits new 4277b4cb0e 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits new be2aacc8fe 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits new 099ba6cb6a 136: onsuccess: #1561: 2: Success after binutils: 3 commits new 9509087ea6 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] new 63134fba8f 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] new b2fd20397f 139: onsuccess: #1566: 1: Success after gcc: 5 commits new f0147d8d7c 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits new d664d43d30 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits new 4727fbc866 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] new d7f7173fc4 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits new 45b6965983 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits new b64c042203 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 commits new 9b62639a92 146: onsuccess: #1573: 2: Success after binutils: 7 commits new 45e17de87e 147: onsuccess: #1574: 2: Success after binutils/gcc: 16 commits new d934a6ea1b 148: onsuccess: #1575: 2: Success after binutils/gcc: 12 commits new 280927df86 149: onsuccess: #1576: 2: Success after binutils/gcc: 13 commits new 5020a1d857 150: onsuccess: #1577: 2: Success after gcc: 3 commits new 9b9ee2c442 151: onsuccess: #1578: 2: Success after gcc: 2 commits new 27d2c23fb4 152: onsuccess: #1579: 2: Success after gcc: 2 commits new 22cde29649 153: onsuccess: #1580: 2: Success after binutils/gcc: 2 commits new 97d893fbb1 154: onsuccess: #1581: 2: Success after binutils/gcc: 11 commits new b7ccbeb339 155: onsuccess: #1582: 2: Success after binutils/gcc: 15 commits new 8f5a87ed47 156: onsuccess: #1583: 2: Success after binutils/gcc: 2 commits new 90b655b610 157: onsuccess: #1584: 2: Success after binutils/gcc: 5 commits new d11d1d1be2 158: onsuccess: #1585: 2: Success after binutils/gcc: 12 commits new f27625280c 159: onsuccess: #1586: 2: Success after binutils/gcc: 18 commits new 16b1a16c52 160: onsuccess: #1587: 2: Success after binutils/gcc: 5 commits new b39ec5b745 161: onsuccess: #1588: 2: Success after binutils/gcc: 10 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 (9ef65d5802) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] 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 1688 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 38120 -> 38436 bytes 05-build_abe-bootstrap/console.log.xz | Bin 274384 -> 273184 bytes 06-check_regression/console.log.xz | Bin 2772 -> 2944 bytes 07-update_baseline/console.log | 36 +++++++++++++++++----------------- 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 ++++++++--------- 13 files changed, 33 insertions(+), 33 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[binutils-gdb] branch master updated (f4b581f2d1a -> e840e61cacd)

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 f4b581f2d1a [AArch64] Update FPSR/FPCR fields for FPU and SVE new e840e61cacd opcodes/riscv: style csr names as registers 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: opcodes/riscv-dis.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (448523c6b8 -> 66479997e8)

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 448523c6b8 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards d0240683ad 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards 1ed8327915 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards 4d7b8ccbe7 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards 02f6d1a1de 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards 992dca57e9 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards e7535d5f6a 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards d467848945 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards 6fc190c61b 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 9dead4f250 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 7890eac7ac 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards b36030f1cc 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards d9d5dc595c 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards dd9b57b70d 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards f1bb16938e 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 858c0fd280 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards fa02531254 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards a892add553 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards f1995ad5df 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards a2ebcec634 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 13a94d557f 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards b4507beb6c 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards cc3dc1ef7a 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 8f68d325bd 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 4e9200cf7c 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 3d847f5e4b 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards f686d503b0 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 8102069899 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards c2dd1cff4c 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 4fabfd359d 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards c48e2bf526 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards bcbac98e94 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 2fcdfe63fa 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards d36f149b23 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 60b2c2afca 128: onsuccess: #1723: 1: Success after linux: 12 commits discards bdfce0e94b 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 60bb9db1f2 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 1c69d0d515 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards de1749134e 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 65925a19e7 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 7212fed5ae 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards c195caf4f0 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards bdf41074de 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 2d454f75c8 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 91c0e514c3 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 9b9d032c49 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 13a95c827d 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 6fb1ac7666 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards d07bf19e3f 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards d2f351270d 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 372da95bc1 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 0fbd499e32 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 1f3d43f67a 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 6041ae469e 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 9f2b051e37 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards c9e8c38aff 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 91381dadb1 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 51b1725535 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 031e6eb0ca 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards c026702245 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards bc99d97d11 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards ab2ad20e78 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 8e3f8f8acf 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 48b3d93ff7 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards df6a0a652e 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards b3ae8a9b2b 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards c2562eddfa 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 1730904208 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 87761395f6 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 562c5b8fce 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards fe60781a45 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 992ce7e3e7 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 72551749f1 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 336401f9a8 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards e1eef48c90 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 86cbd6a9a2 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 4ea9090020 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 4d60bc3f92 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards f6792a08a2 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards ae00fa4204 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 0ee0d72923 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 9321d8493d 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards a25f985d26 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards a0e9b4c0a8 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards f7ece26da6 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 5926ea5527 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a5baac5fb9 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 7667a238fc 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5f9d22e3e9 74: onsuccess: 1: Successful build after linux: 44 commits discards c71f786923 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards bdf0798d67 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ca130957de 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 025c06a9b3 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 07720536bb 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards d843aeda52 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3932d7964f 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3ee6192608 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0aa8496de0 65: onsuccess: 1: Successful build after gcc: 4 commits discards 7309b681a4 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 020b1609dd 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a57a3312fa 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new c4843acb61 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new b9c338ace4 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 21892102e9 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 28d6ef4d06 65: onsuccess: 1: Successful build after gcc: 4 commits new 7a71c2a9a7 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 3da5311298 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 20945e937c 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new decd4c7ea2 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new a1c8cbcace 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new aa88400261 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new c03811fd26 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c168688c75 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 9cacf00b72 74: onsuccess: 1: Successful build after linux: 44 commits new dc50daccb5 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d8eab329b8 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 0153ace560 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 960e5b48fb 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4383b21aae 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 47ce9f51ef 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 6a7a75d8f4 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new e5b04453b0 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 0763df29c8 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 8c40974b18 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 7b4cdf4cde 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 376af32620 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new c8c6fea90c 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 7c1cddb0de 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new ae34d4fca4 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new afe8d42b52 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 2ea89c9bbb 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 185db167e6 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 6822d3b53e 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 42b73e9913 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 81f57ecc47 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new b46a289250 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 3f61daac5a 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 7e33e43f5c 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 7470d8d002 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new b593271de6 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 0d04182077 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 13c6bb8fd2 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 0aa37fd2e3 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new a4a722ab95 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 4eaad04c40 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new a0391ceb78 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 45226893fa 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new fd22ecc2b2 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new f9bfd3f2b9 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 268b273224 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 12f1d23765 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new f1acd2c39b 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 745a5a7cf0 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new dd8560f937 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new fe87a1c39c 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new e37bcad012 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 58962cb019 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 010362aadd 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 449f7e596e 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 89f150cd07 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new d7b7cce1f2 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 8f18d0c02c 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 5c4e235445 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 10f118bb83 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 5f7dc455f1 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 6ce96052e3 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new d282f94d09 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 6122f62122 128: onsuccess: #1723: 1: Success after linux: 12 commits new ea4501a145 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 3dcc71a52b 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new bae66ef2da 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 6d1eb774c2 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 7cec31b28e 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 0b7e1f6ebe 134: onsuccess: #1730: 1: Success after binutils: 2 commits new e24dfe7b9b 135: onsuccess: #1733: 1: Success after binutils: 5 commits new dbf96cf4e3 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 2ac24ed81e 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 6615f26bd0 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new bc830da483 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new a1981a5982 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 56925f0f38 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new fc1bdc5483 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new b0ed45a633 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new aa70d480e2 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 007252073d 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 93113c0e5a 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 4c35e68ce2 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new f3ff4bdcaf 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new 5a34220aab 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new 0207880df1 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 876a2b3f23 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new 3323f1378d 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new 9ea27d3939 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 2d6f01a79d 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 888f142d19 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new c224c99a4f 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 8d57bc457f 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 471876c565 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new 318312bc9a 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new dedc7336ec 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new 2d93499990 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new b8a570f22f 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new 66479997e8 163: onsuccess: #1764: 1: Success after gcc/linux: 141 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 (448523c6b8) \ 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 1736 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30104 -> 30156 bytes 04-build_abe-stage1/console.log.xz | Bin 90592 -> 90552 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 9956 -> 9168 bytes 07-build_abe-glibc/console.log.xz | Bin 234052 -> 234360 bytes 08-build_abe-stage2/console.log.xz | Bin 223476 -> 223052 bytes 09-build_abe-gdb/console.log.xz | Bin 37136 -> 37056 bytes 10-build_abe-qemu/console.log.xz | Bin 31632 -> 31888 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2420 -> 2708 bytes 13-check_regression/console.log.xz | Bin 6876 -> 6156 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 26 + 13-check_regression/results.compare | 33 +- 13-check_regression/results.compare2 | 63 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 48 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +- results | 26 + sumfiles/g++.log.xz | Bin 2669836 -> 2665848 bytes sumfiles/g++.sum | 144 +- sumfiles/gcc.log.xz | Bin 2193148 -> 2232360 bytes sumfiles/gcc.sum | 2435 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 880740 -> 887284 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201484 -> 201452 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 428120 -> 427368 bytes sumfiles/libstdc++.sum | 16 +- 42 files changed, 1563 insertions(+), 1397 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (7df3693f745 -> b6d5d72bd0b)

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 7df3693f745 Convert nonzero mask in irange to wide_int. new b6d5d72bd0b openmp: Add begin declare target support 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/c-family/c-omp.cc | 4 +- gcc/c/c-decl.cc | 24 +++++- gcc/c/c-lang.h | 7 +- gcc/c/c-parser.cc | 75 ++++++++++++----- gcc/cp/cp-tree.h | 9 ++- gcc/cp/decl2.cc | 41 +++++++--- gcc/cp/parser.cc | 93 ++++++++++++++++------ gcc/cp/semantics.cc | 12 ++- .../c-c++-common/gomp/begin-declare-target-1.c | 25 ++++++ .../c-c++-common/gomp/begin-declare-target-2.c | 18 +++++ .../c-c++-common/gomp/begin-declare-target-3.c | 19 +++++ .../c-c++-common/gomp/begin-declare-target-4.c | 2 + gcc/testsuite/c-c++-common/gomp/declare-target-4.c | 6 -- gcc/testsuite/c-c++-common/gomp/declare-target-6.c | 2 +- gcc/testsuite/c-c++-common/gomp/declare-target-7.c | 8 ++ gcc/testsuite/g++.dg/gomp/attrs-18.C | 41 ++++++++++ gcc/testsuite/g++.dg/gomp/attrs-9.C | 15 ++++ libgomp/libgomp.texi | 2 +- 18 files changed, 328 insertions(+), 75 deletions(-) create mode 100644 gcc/testsuite/c-c++-common/gomp/begin-declare-target-1.c create mode 100644 gcc/testsuite/c-c++-common/gomp/begin-declare-target-2.c create mode 100644 gcc/testsuite/c-c++-common/gomp/begin-declare-target-3.c create mode 100644 gcc/testsuite/c-c++-common/gomp/begin-declare-target-4.c create mode 100644 gcc/testsuite/c-c++-common/gomp/declare-target-7.c create mode 100644 gcc/testsuite/g++.dg/gomp/attrs-18.C -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[binutils-gdb] branch master updated (034235cebd7 -> f4b581f2d1a)

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 034235cebd7 Re: compress .gnu.debuglto_.debug_* sections if requested new 758dd750bc6 Support objcopy changing compression to or from zstd new f4b581f2d1a [AArch64] Update FPSR/FPCR fields for FPU and SVE The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: bfd/bfd-in2.h | 5 +- bfd/compress.c | 240 +++++++++++++++++++++---------------------- bfd/elf.c | 93 +++++++++-------- gdb/features/aarch64-fpu.c | 3 + gdb/features/aarch64-fpu.xml | 14 +++ gdb/features/aarch64-sve.c | 38 ++++++- 6 files changed, 222 insertions(+), 171 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits October 2022