Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[gcc] branch master updated (646ce0056ed -> 9a8212db2dd)

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 646ce0056ed LoongArch: Fixed a typo in the comment information of the f [...] new 9a8212db2dd testsuite: Skip intrinsics test if arm The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/testsuite/gcc.target/aarch64/advsimd-intrinsics/vld1x2.c | 2 +- gcc/testsuite/gcc.target/aarch64/advsimd-intrinsics/vld1x3.c | 2 +- gcc/testsuite/gcc.target/aarch64/advsimd-intrinsics/vld1x4.c | 2 +- gcc/testsuite/gcc.target/aarch64/advsimd-intrinsics/vst1x2.c | 2 +- gcc/testsuite/gcc.target/aarch64/advsimd-intrinsics/vst1x3.c | 2 +- gcc/testsuite/gcc.target/aarch64/advsimd-intrinsics/vst1x4.c | 2 +- 6 files changed, 6 insertions(+), 6 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-mainline-allmodconfig updated (ded5dad7a4 -> 652c088ba4)

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-mainline-allmodconfig in repository toolchain/ci/base-artifacts. from ded5dad7a4 15: onsuccess: #554: 33: Success after binutils/gcc/linux/qe [...] new 652c088ba4 16: onsuccess: #555: 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 1700 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 30204 -> 30588 bytes 04-build_abe-stage1/console.log.xz | Bin 72540 -> 72564 bytes 05-build_abe-qemu/console.log.xz | Bin 31616 -> 31360 bytes 06-build_linux/console.log.xz | Bin 4780 -> 4716 bytes 08-check_regression/console.log.xz | Bin 4332 -> 4376 bytes 09-update_baseline/console.log | 9 +++++++++ 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, 33 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_gcc_check_bootstrap/master-aarch64-check_bootstrap updated (0aaa416037 -> f61524fd65)

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 0aaa416037 46: onsuccess: #576: 1: Success after binutils: 12 commits new f61524fd65 47: onsuccess: #579: 1: Success after binutils: 6 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 1644 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 37764 -> 38084 bytes 04-build_abe-bootstrap/console.log.xz | Bin 271928 -> 270516 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3836 bytes 06-build_abe-check_bootstrap/console.log.xz | Bin 2756 -> 2764 bytes 07-check_regression/console.log.xz | Bin 4552 -> 5388 bytes 07-check_regression/extra-bisect-params | 1 + 07-check_regression/fails.sum | 7 + 07-check_regression/mail-body.txt | 27 + 07-check_regression/results.compare | 26 +- 07-check_regression/results.compare2 | 40 +- 07-check_regression/results.regressions | 27 + dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- results | 27 + sumfiles/g++.log.xz | Bin 3667984 -> 3660216 bytes sumfiles/g++.sum | 132 +- sumfiles/gcc.log.xz | Bin 3246032 -> 3218276 bytes sumfiles/gcc.sum | 4568 +++++++++++++-------------- sumfiles/gfortran.log.xz | Bin 1076388 -> 1079076 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2348 -> 2348 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 213564 -> 213712 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2728 -> 2728 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 465248 -> 463716 bytes sumfiles/libstdc++.sum | 10 +- 34 files changed, 2565 insertions(+), 2419 deletions(-) create mode 100644 07-check_regression/extra-bisect-params create mode 100644 07-check_regression/fails.sum create mode 100644 07-check_regression/results.regressions -- 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-arm-bootstrap updated (caa85f8d44 -> 0cb7121136)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap in repository toolchain/ci/base-artifacts. discards caa85f8d44 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits discards b9a53bec7f 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits discards 5d33988490 140: onsuccess: #1545: 1: Success after gcc: 7 commits discards 9a426f3e9b 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits discards f9c40221be 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits discards c26af2b5b0 137: onsuccess: #1542: 1: Success after gcc: 4 commits discards cbf78b5d67 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] discards 09e57fbdb0 135: force: #1540: 2: Success after gcc: 23 commits discards 90e530c903 134: onsuccess: #1538: 2: Success after binutils: 2 commits discards ecbab5eff0 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits discards 1ccc794182 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits discards a904d7988a 131: onsuccess: #1534: 2: Success after gcc: 9 commits discards 6e9c538383 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] discards 81de547ab4 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits discards f1c3ec414d 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 3b478e1eba 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits discards e590c1f6d5 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits discards 454fd07dfe 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits discards 5aa98ea155 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits discards 2517b2ef83 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits discards e76e494afc 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits discards 1c4dbdba8f 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits discards 77e187a411 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits discards 5ad1616f76 119: onsuccess: #1520: 2: Success after binutils: 8 commits discards 4a26767bf2 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards a9b933bb31 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards c8bc4c7a46 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards e4c113faf3 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards 596dfa70f3 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards 4405d234cf 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards 27baa74d4f 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards 48e5415dd2 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards 20df2263a4 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards 4164408f30 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] discards bb92d130b1 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards 5d30c4c336 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] discards c6eab3c0f5 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards 1986b2f83a 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards 66d4809ae2 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards 80b4780774 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards 75a91b1c67 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards 20ce9853ce 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards c2fafc59d7 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards 2b52994ab8 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] discards cf79dfa567 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] discards 6f343de00e 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards ff251f9142 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards 4228ce2e40 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] discards 6a7746bddb 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] discards e1ff5feae1 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards ad673c7f96 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards d1c523d7a0 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards c276d1bf77 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards 4530a3c043 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards 9d939551c9 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards 76cdb585cd 87: onsuccess: 2: Success after gcc: 4 commits discards 4e56409de8 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards 50e894aec2 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards e9ff150338 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards 28914e5e39 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards c0ae6112bd 82: onsuccess: 1: Successful build after gcc: 3 commits discards 910708ec58 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards c713fbb9c4 80: force: 2: Successful build after gcc: 14 commits discards 88cbe4094f 79: onsuccess: 2: Successful build after binutils: 5 commits discards 2463d2819d 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards 376d5ec074 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 791ac139df 76: onsuccess: 2: Successful build after gcc: 12 commits discards f8e2e1ab6f 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards f63b1545b3 74: onsuccess: 2: Successful build after baseline build: no [...] discards 9810da6a68 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 97fc36f932 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards f893f7c65e 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 7f4c623004 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 5de4eca650 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards b42f3b1bc1 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 1bbb96d192 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards bb79d0c742 66: onsuccess: 2: Successful build after gcc: 9 commits discards 469096f44a 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 7e68b2cf05 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 3dc07b6ffd 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards f3f44d8b4a 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards c6e10a07df 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards e65695a983 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards 58c2b9a1e6 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 9b232bed0a 58: force: 2: Successful build after gcc: 6 commits discards 2913747bca 57: onsuccess: 2: Successful build after binutils: gdb: new [...] discards c40b1e7cfb 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 351a86fe65 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 78afd6072d 54: onsuccess: 2: Successful build after gcc: 5 commits discards 2adcde16fe 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards b3cb479b7c 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards e03daf6b0a 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 17634d9e1f 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards ee77df96e7 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards e7ad1c7c70 48: onsuccess: 2: Successful build after gcc: 4 commits discards 82ab555d5e 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 8b093920e1 46: onsuccess: 2: Successful build after baseline build: no [...] discards c9d79395d5 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards b8ea14bff0 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 36c3f2c6ef 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] discards 51d3d5ba71 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] new 302e28a5b8 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] new cadb70cf6e 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new f00ff4ee7f 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 55ed6134a7 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new fb37d43dff 46: onsuccess: 2: Successful build after baseline build: no [...] new 577ddee362 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 7e593de193 48: onsuccess: 2: Successful build after gcc: 4 commits new fe258e3a89 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 39ed0f5f2e 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 1eb059151a 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits new e69f343542 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 8744cf2bf2 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 2d099a13d5 54: onsuccess: 2: Successful build after gcc: 5 commits new 5519ddb9d3 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new a67f540f64 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 4aab83d857 57: onsuccess: 2: Successful build after binutils: gdb: new [...] new 3e6d6a7e5a 58: force: 2: Successful build after gcc: 6 commits new 3981306b32 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new ebfa0a38fe 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new 24f606794e 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new 7419bef8f0 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 540d48fc2c 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 249e1ec5c5 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new d9ef433e21 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new afa3ce72a2 66: onsuccess: 2: Successful build after gcc: 9 commits new dcccbafded 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new ce5942a1a9 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 002c63ba23 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new cb0814d755 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new e273578f99 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 9b00a6787d 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 563d460136 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 22ecc8a809 74: onsuccess: 2: Successful build after baseline build: no [...] new 21137a3601 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new c063b7829b 76: onsuccess: 2: Successful build after gcc: 12 commits new ba007ea134 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 1fae03c2e6 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new 478050e90e 79: onsuccess: 2: Successful build after binutils: 5 commits new 6b947c3db9 80: force: 2: Successful build after gcc: 14 commits new 79a3acd00c 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 77604bb0d7 82: onsuccess: 1: Successful build after gcc: 3 commits new ff816e1ee5 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new 43e7e15a35 84: onsuccess: 2: Success after binutils/gcc: 15 commits new 6dca411232 85: onsuccess: 2: Success after binutils/gcc: 25 commits new dc39a500b4 86: onsuccess: 2: Success after binutils/gcc: 10 commits new cfb0d6870b 87: onsuccess: 2: Success after gcc: 4 commits new e29f8f687e 88: onsuccess: 2: Success after binutils/gcc: 25 commits new bac41fecee 89: onsuccess: 2: Success after binutils/gcc: 4 commits new 36f4cb6870 90: onsuccess: 2: Success after binutils/gcc: 16 commits new b711a506bc 91: onsuccess: 2: Success after binutils/gcc: 7 commits new 6ed3ced888 92: onsuccess: 2: Success after binutils/gcc: 9 commits new 36ec130dea 93: onsuccess: 2: Success after binutils/gcc: 3 commits new 489bb05f69 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] new 6d7e5889e9 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] new 2caf1e20ab 96: onsuccess: #1452: 2: Success after gcc: 2 commits new 9015d512e4 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new 74a2c23ac7 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] new 89e95a347f 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] new 2cf4829bf7 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new 4d74ea7f09 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new babcd5680c 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new 613f0fb932 103: onsuccess: #1504: 2: Success after gcc: 2 commits new 5c47828b9c 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new ac5d964de1 105: onsuccess: #1506: 2: Success after gcc: 2 commits new bb5ca631eb 106: onsuccess: #1507: 2: Success after gcc: 2 commits new 8eebcccbdf 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] new 0c9e1b9402 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new 249a4c8412 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] new 555aac3a57 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new 2aacfb4393 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new eef838cbef 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new 4f9577d37f 113: onsuccess: #1514: 2: Success after gcc: 5 commits new b4c8a66011 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new d0dfab3a8c 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new a21ed59484 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new aea09ab6a1 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new 84840fdf13 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new b961e47184 119: onsuccess: #1520: 2: Success after binutils: 8 commits new 15eb84dc7c 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits new e8ada16555 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits new 8e7512683c 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits new 40767e1083 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits new 6ffd4f8f03 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits new 0e97f7b4ac 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits new 5ec1e8506b 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits new 93a530337c 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits new b752851b7d 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 2f44eb863e 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits new b560337a70 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] new a86c16777f 131: onsuccess: #1534: 2: Success after gcc: 9 commits new e4a719f540 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits new 92f5d3396d 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits new eadbd3758c 134: onsuccess: #1538: 2: Success after binutils: 2 commits new f80fe83d09 135: force: #1540: 2: Success after gcc: 23 commits new c567d0fe03 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] new 8825e6998e 137: onsuccess: #1542: 1: Success after gcc: 4 commits new 3409ee6069 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits new ea9734f4e8 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits new d7d21bb819 140: onsuccess: #1545: 1: Success after gcc: 7 commits new 7c01513734 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits new 18fede7dde 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits new 0cb7121136 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 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 (caa85f8d44) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1676 -> 1660 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 51476 -> 50792 bytes 05-build_abe-bootstrap/console.log.xz | Bin 112236 -> 110396 bytes 06-check_regression/console.log.xz | Bin 2968 -> 2620 bytes 07-update_baseline/console.log | 38 +++++++++++++++++----------------- 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, 34 insertions(+), 34 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (175a89d1239 -> 646ce0056ed)

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 175a89d1239 libgomp.texi: Status 'P' for 'assume', remove duplicated line new 646ce0056ed LoongArch: Fixed a typo in the comment information of the f [...] 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/loongarch/loongarch.cc | 2 +- 1 file changed, 1 insertion(+), 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_build/master-arm updated (20a542d926 -> 706a3b9bf5)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-arm in repository toolchain/ci/base-artifacts. discards 20a542d926 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] discards 55a0d4c971 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] discards 88616bf9e3 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards af04be1450 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] discards 6a28b2d3ae 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards a18fef1f0b 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards ca87a23805 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards 28a5fe0700 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 3bdb4a417c 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards 9b8eb2308a 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards 1185ecc66b 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards 2fc7c7d779 132: onsuccess: #1645: 7: Success after linux: 23 commits discards 369307c8fb 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards 9b3c4bda10 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards 215b586395 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 4f65a30c73 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards 95d1ec7fc0 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards 2cea3dc85d 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards b00c3d13f4 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards 4a75b6c456 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards 54e8b6c696 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards e756910492 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards b0b6e3d9ab 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards b6f201244b 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards 66c3aede14 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards 3472d0b2a0 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards 6c29e24afd 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 05e63ee7da 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards e5603d9ff6 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 0aaaf11f3a 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards 5c63ef7d75 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 86eda0d023 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards d4a444765d 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 71b16d1160 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards 88899bf5cb 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards 0cd29ad42b 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 3f24ea916f 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards b2928ca429 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 8ccc0c4a35 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 2e9b8cacb5 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 169d582310 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards adc120c8f6 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 77d75e448f 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards c141f4de49 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards f1a958c4af 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 70375b29eb 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards fda67c79bf 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards ee1b9c4c62 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards cbda7316a1 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards 79003f37b4 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 7aadbf4c4c 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards c50b8798f3 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 43c95f5c10 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 4ef6c2c973 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 1ae3cb8209 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards c344dfa1ca 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 05afb8fe78 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 7e8a792c9a 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards bd3d5af37f 85: onsuccess: 7: Success after gcc: 9 commits discards 881de9afb4 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards d30e4d9ce1 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 4cf6359ace 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 63297a48d2 81: onsuccess: 7: Successful build after gcc: 2 commits discards 769c5d578c 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards fe12bde327 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 24835da773 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 586c4155dd 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 201f8ceb80 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e939a4dc1c 75: onsuccess: 7: Successful build after linux: 44 commits discards 046093b7f9 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards f7e9b799fc 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e4168a7748 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards b882d9307f 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 12b2627c1f 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards da4c789f8a 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards dd1a9c9959 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 86bc4bd1ad 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 0294bdacd2 66: onsuccess: 7: Successful build after gcc: 3 commits discards 986b7dbedb 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards bbbdc47e95 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards a1901003e8 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards f419199664 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards f875046ce0 61: onsuccess: 4: Successful build after gcc: 15 commits discards 1acb1e140f 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards aba2ff99bc 59: force: 7: Successful build after gcc: 2 commits discards 96b384989b 58: onsuccess: 7: Successful build after glibc: 2 commits discards 61f57bdf3c 57: onsuccess: 7: Successful build after gcc: 7 commits discards 12dc68e99e 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 3b8dd323c7 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards d3156568d6 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards 51cd20d411 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 51f711936f 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards ac69f4f3ba 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards a2982c4b40 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 4195b1a6f7 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 2e70708acb 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards 730688dbd2 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards aacf3d8f0f 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards f3bb4252d3 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards b254f42652 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards 756aa56120 43: onsuccess: 7: Successful build after gcc: 2 commits new 4612432681 43: onsuccess: 7: Successful build after gcc: 2 commits new 3720c030cc 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new 86480a1229 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new cd4dc76167 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 06253b44a5 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 32f4468dc3 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new e26f657078 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 6c3c495df6 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new c2fd801ea7 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new c774e89a1e 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 04443a27d4 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new fe4824e479 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new 505596ff5d 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 80126c08f8 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 78b726b003 57: onsuccess: 7: Successful build after gcc: 7 commits new 635394efd0 58: onsuccess: 7: Successful build after glibc: 2 commits new f7e8a315bd 59: force: 7: Successful build after gcc: 2 commits new 2e3b415495 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new b3bf632914 61: onsuccess: 4: Successful build after gcc: 15 commits new d037d6a93c 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 4660dcedeb 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 5ece150710 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 16e8fc913a 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new d98a597e80 66: onsuccess: 7: Successful build after gcc: 3 commits new d3467863ae 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 016ce86aa9 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b66fc63c3f 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new df5d4c2b35 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 8e226614a8 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new ea817d9cba 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new e7b7ee7aae 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ced1fbe233 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 7e5acdf793 75: onsuccess: 7: Successful build after linux: 44 commits new bc3abf8b71 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 319f1cc24a 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new e82098bd9b 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 405a53c6e1 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 732ecb52a0 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new b8a89f11ae 81: onsuccess: 7: Successful build after gcc: 2 commits new e255e823ed 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 0a570e38bc 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 1834e3b494 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new a4e65f35cf 85: onsuccess: 7: Success after gcc: 9 commits new fe8d31c8dc 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 62f778b51a 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 494cc15b71 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new d3761af125 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new fd0bb7d290 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 051cac89aa 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 73882e2cce 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 1d3d1bea41 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new 78c33174c1 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new e3205ac2fe 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new 2e3cdb1fb4 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new 6a3d902e16 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new aa55840051 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new e784177dff 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new 6f6db37485 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new 89186916e8 101: onsuccess: #1609: 7: Success after binutils: 78 commits new bb697c27d8 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 06c20eeb1c 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 5cee2865a7 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new e92e9a403a 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new f0abc172a4 106: onsuccess: #1617: 7: Success after gcc: 2 commits new a8a639c001 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 6aded29aad 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new ec528c049b 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new d56e3a984c 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new 05af5ab30d 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 41277418d3 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 4f017530b7 113: onsuccess: #1624: 7: Success after gcc: 6 commits new cbda003620 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new 4cb54f79cc 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new b29e56981c 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new 0039553123 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new 7abb309dd9 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new f2ecadf38c 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new f2813e6692 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 203cb4b3be 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new 5bfe1dc0eb 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new 651807bd9e 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new 7f0bcc6c28 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new 12d9f7ac44 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new 675e5e56ca 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new a91ef63514 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 3edd843d2d 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new 8a161257c3 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new 30cb07c11e 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new 41731d95b5 131: onsuccess: #1644: 7: Success after gcc: 10 commits new 4812c1adc6 132: onsuccess: #1645: 7: Success after linux: 23 commits new 26ff935763 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new 92c5994ae6 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new faea983134 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new adb237db70 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 5119047554 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new 9555a6ca2a 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new 09d909f40a 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 745fab2ac9 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] new a89f2ab7ab 141: onsuccess: #1656: 7: Success after gcc: 7 commits new 9161342acd 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] new 4158eca481 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] new 706a3b9bf5 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (20a542d926) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] 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 1692 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2760 bytes 04-build_abe-binutils/console.log.xz | Bin 29800 -> 30700 bytes 05-build_abe-stage1/console.log.xz | Bin 90448 -> 91092 bytes 07-build_abe-linux/console.log.xz | Bin 9236 -> 9240 bytes 08-build_abe-glibc/console.log.xz | Bin 233424 -> 234272 bytes 09-build_abe-stage2/console.log.xz | Bin 223680 -> 224508 bytes 10-build_abe-gdb/console.log.xz | Bin 37080 -> 37876 bytes 11-build_abe-qemu/console.log.xz | Bin 31108 -> 31052 bytes 12-check_regression/console.log.xz | Bin 4432 -> 3576 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++--------- 19 files changed, 57 insertions(+), 57 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (fa4bc21bac7 -> 175a89d1239)

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 fa4bc21bac7 LoongArch: Libitm add LoongArch support. new 175a89d1239 libgomp.texi: Status 'P' for 'assume', remove duplicated line 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: libgomp/libgomp.texi | 3 +-- 1 file changed, 1 insertion(+), 2 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_profiled_lto updated (25944e8339 -> 27ca94e7d3)

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_profiled_lto in repository toolchain/ci/base-artifacts. from 25944e8339 47: onsuccess: #446: 2: Success after binutils/gcc: 54 commits new 27ca94e7d3 48: onsuccess: #448: 2: Success after binutils: 6 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 1692 -> 1600 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2700 bytes 04-build_abe-binutils/console.log.xz | Bin 37548 -> 37284 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 525956 -> 521684 bytes 06-check_regression/console.log.xz | Bin 3280 -> 2704 bytes 07-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 19 +++++++++---------- 12 files changed, 15 insertions(+), 16 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch devel/omp/gcc-12 updated (87caae2e83f -> b1caa1db9d3)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch devel/omp/gcc-12 in repository gcc. from 87caae2e83f amdgcn: Add builtin for vectorized DFmode fabs operation adds c9bb2be0f3d Daily bump. adds a0d5241beb2 Daily bump. adds be18783dea5 Daily bump. adds 7cb8784fbd3 Daily bump. adds 36c23b302c9 c-family: Drop nothrow from c_keywords adds 8dbde52fbcd Daily bump. new b1caa1db9d3 Merge branch 'releases/gcc-12' into devel/omp/gcc-12 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/DATESTAMP | 2 +- gcc/c-family/ChangeLog | 4 ++++ gcc/c-family/c-format.cc | 1 - 3 files changed, 5 insertions(+), 2 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-release-aarch64-next-allyesconfig updated (fa28a923f0 -> c4f17e7494)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-next-allyesconfig in repository toolchain/ci/base-artifacts. from fa28a923f0 14: onsuccess: #684: all: Success after binutils/gcc/linux/q [...] new c4f17e7494 15: onsuccess: #685: all: Success after binutils/gcc/linux/q [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1720 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30184 -> 30148 bytes 04-build_abe-stage1/console.log.xz | Bin 68612 -> 68696 bytes 05-build_abe-qemu/console.log.xz | Bin 31488 -> 31040 bytes 06-build_linux/console.log.xz | Bin 3068 -> 3584 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4280 -> 4100 bytes 08-check_regression/mail-body.txt | 6 ++++-- 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 | 8 +++++--- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 19 files changed, 33 insertions(+), 29 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 September 2022