Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[gcc] branch master updated (b8473c9a2b8 -> df4c584c567)

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 b8473c9a2b8 libtdc++: Regenerate Makefile.in after freestanding header changes new df4c584c567 range-op: Keep nonzero mask up to date with truncating casts. 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/range-op.cc | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 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 (65d065bbad9 -> 5c341c056b0)

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 65d065bbad9 openmp: Add begin declare target support new e9c986d63ea install.texi: gcn - update llvm reqirements, gcn/nvptx - ne [...] new 5c341c056b0 OpenMP: Update invoke.texi and fix fortran/parse.cc for -fo [...] 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: gcc/ChangeLog.omp | 17 +++++++++++++ gcc/doc/install.texi | 31 ++++++++++++++++++++---- gcc/doc/invoke.texi | 12 ++++++--- gcc/fortran/ChangeLog.omp | 8 ++++++ gcc/fortran/parse.cc | 6 ++--- gcc/testsuite/ChangeLog.omp | 7 ++++++ gcc/testsuite/gfortran.dg/gomp/openmp-simd-7.f90 | 23 ++++++++++++++++++ 7 files changed, 92 insertions(+), 12 deletions(-) create mode 100644 gcc/testsuite/gfortran.dg/gomp/openmp-simd-7.f90 -- 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_ubsan updated (36103864d2 -> 7f90eba081)

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_ubsan in repository toolchain/ci/base-artifacts. from 36103864d2 53: onsuccess: #479: 2: Success after binutils/gcc: 48 commits new 7f90eba081 54: onsuccess: #480: 2: Success after binutils/gcc: 39 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 1700 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2772 bytes 04-build_abe-binutils/console.log.xz | Bin 37876 -> 40020 bytes 05-build_abe-bootstrap_ubsan/console.log.xz | Bin 355500 -> 356252 bytes 06-check_regression/console.log.xz | Bin 3196 -> 3080 bytes 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 +++++++++--------- 12 files changed, 15 insertions(+), 15 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/llvm-master-aarch64-norov-allnoconfig updated (de5d6d3e72 -> a915ebd7d5)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-norov-allnoconfig in repository toolchain/ci/base-artifacts. from de5d6d3e72 13: onsuccess: #50: boot: Success after binutils/llvm/linux/ [...] new a915ebd7d5 14: onsuccess: #51: boot: Success after binutils/llvm/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1692 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 30084 -> 30728 bytes 04-build_kernel_llvm/console.log.xz | Bin 64232 -> 64648 bytes 05-build_abe-qemu/console.log.xz | Bin 31928 -> 32756 bytes 06-build_linux/console.log.xz | Bin 3444 -> 4316 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4436 -> 4160 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (a2a1313a03 -> 38d436116f)

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-aarch64 in repository toolchain/ci/base-artifacts. discards a2a1313a03 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/g [...] discards 11a6125132 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/g [...] discards f38faca449 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/g [...] discards 008c54b54e 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 28 [...] discards 3bc7b774b4 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits discards 5fdc077c86 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/g [...] discards 7d83b82a68 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/g [...] discards 92c0fe546a 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 12 [...] discards 6e0197132b 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 commits discards 2774fc9151 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/g [...] discards 5acadfa56b 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 3614c41b99 159: onsuccess: #1612: 7: Success after gcc: 4 commits discards 56a0a53c86 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/g [...] discards 19e4f80c27 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits discards 9e2de572be 156: onsuccess: #1609: 7: Success after gcc: 2 commits discards d5bb18d8b9 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] discards 007268fa4e 154: onsuccess: #1607: 1: Success after gcc: 2 commits discards 5ca36ee727 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] discards 8ee9db2036 152: force: #1605: 7: Success after gcc: 9 commits discards bf6deda76b 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] discards de86fe811e 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] discards eef08b4e4b 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] discards 0a164c3bc5 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] discards 111da188de 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] discards ec4bb242bd 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] discards 5d6333aec7 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] discards b6ffa37e9d 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards 2394eb1399 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] discards f31b77d010 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards add8483111 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards 002b9771d5 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards 41c15249c0 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards d94774e1e4 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards 23cd4b8e64 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards a750a03c47 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards 4648529a4f 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards 79930f903e 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards bac69c9dad 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards d5b64a7664 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards e4f37c52d9 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards 32e0d61415 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards 06b98aa4bb 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards ff4115b5dd 128: onsuccess: #1579: 7: Success after linux: 12 commits discards 286775f14b 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards 77e7f5f12e 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards 11fd65e558 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards 352072e67b 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards c3e6d93c17 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards b1af4fadc1 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards 7bafcca2ca 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards 05222cf55e 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards 49e4bce492 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards e4a2c9b48c 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards b3c6c7b438 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards 44b6e80d87 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards 36221dea80 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards 6e2dbcaa68 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards fb3270b329 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards f1131804c0 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards 3cf45a75f3 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards 202b191580 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 31d3bb1b8d 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards b5676a4583 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards da3719eb9f 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards 837dcfce9c 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards 2ee18c0a29 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards 0fe91276ad 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards 64801f36ff 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 08bb2778ac 102: force: #1551: 1: Failure after gcc: 306 commits discards 3867450bc7 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards cb9cbc35cd 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards f5d94bbd67 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards e86fc9b7d9 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards 0dc7d22b0f 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 30068bd4e5 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 58da619d56 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 92b4fa7a97 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 230ee1caf3 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards a076a0dcb1 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 24ba696be4 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards b136f24a28 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards ac3d367fbd 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards c2700628bd 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 83776dd2e3 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 327dcd96fd 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 3434a75048 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 15f5286ca5 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 4e58b4b46d 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 9bca26f87d 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards baa148214f 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards caa5e8963a 80: onsuccess: 7: Successful build after linux: 44 commits discards cd76bc2344 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 5e04bc52ec 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards f19d4c4be0 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 2590c9b579 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards ad4b647715 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards e9b50cf262 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 651d546c76 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 4d3e3bda77 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 18b943e4d3 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 6dd2c52df5 70: onsuccess: 7: Successful build after gcc: 4 commits new ad553734ea 70: onsuccess: 7: Successful build after gcc: 4 commits new cbb287aaaa 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 6f1573a4c7 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 480bac9fa4 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new d684d6c7f8 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 775c4c2e4d 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 9611bf2ca8 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 269636284e 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 080d238cbb 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new 6aa678f091 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 5c07850c74 80: onsuccess: 7: Successful build after linux: 44 commits new 8fc1dc827d 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f8b61c435a 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 7955446e61 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new fd9eb6fc4d 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 0df5f05a01 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 72c65a0c52 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 9aa9a4de93 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 85864d3a96 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 4027349060 89: onsuccess: 7: Success after gcc/glibc: 8 commits new d37cd44464 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 449f7e1022 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 1b8d7abeaf 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new a2099cff70 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 468fbc0b11 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 8cc754be7f 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new d1290b9a79 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 06e3dff6dd 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 6c60aaf789 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new c3fb846c0c 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 60bdaa1374 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new 1a22bd28e4 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 90aee79033 102: force: #1551: 1: Failure after gcc: 306 commits new 317c97ca5b 103: onsuccess: #1552: 1: Success after gcc: 5 commits new ace75fd29d 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new 5149289f62 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new e5f2bbba25 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 34e4757ab9 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new 9231de05da 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new efe5fe67c3 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 70160f6d83 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 0a00ee0e3c 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new b7147aa9dc 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new aadcaf1677 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new f20770c2e5 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new 1fa450f809 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new 6ba07731c4 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new fc405b00b0 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new 34a3fac97a 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new 3a76786ef8 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new 3d4e57dfe1 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new 1d71088206 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new 4860a7992c 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new 6493da86e5 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new f1fa3bd786 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new cd4db46d70 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new 606098471f 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new d569064792 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new 52f69af9c5 128: onsuccess: #1579: 7: Success after linux: 12 commits new 00384fa1a0 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new c009f6f3f8 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new d0f3add6db 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new 46c1fa185d 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new 905d1f8be5 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new 3e269eccce 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new 9e61d18be5 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new 6ade05ee4b 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new b231867ed6 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 171dc3205d 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new 819d39b940 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new 6040cc1ea3 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new 6c11121da0 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new 2c2c92e2d4 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new 9af71c06bf 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] new 3c50793bf2 144: onsuccess: #1595: 7: Success after glibc: 2 commits new c41bbb98e7 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] new f2c9b92bb7 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] new d5b21334a4 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] new b483efc873 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] new 20697ec3a0 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] new 27394594cd 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] new 9c16f4da59 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] new e5b5454395 152: force: #1605: 7: Success after gcc: 9 commits new 078ca218ea 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] new 04eb7e0e09 154: onsuccess: #1607: 1: Success after gcc: 2 commits new 43cf8e4f1b 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] new d4c700a92e 156: onsuccess: #1609: 7: Success after gcc: 2 commits new 14493d04fc 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits new 94084bfbec 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/g [...] new 4418b19970 159: onsuccess: #1612: 7: Success after gcc: 4 commits new e437cdf3fe 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new aac055c7b3 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/g [...] new b8243948d1 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 commits new cfb1deee53 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 12 [...] new b35b9d78f8 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/g [...] new 119cbcfc77 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/g [...] new 6abf648455 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits new 6b1f1e72e0 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 28 [...] new e10f589502 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/g [...] new 1c747c3c6b 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/g [...] new c670aa1010 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/g [...] new 38d436116f 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 12 [...] 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 (a2a1313a03) \ 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 1728 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 30376 -> 30448 bytes 05-build_abe-stage1/console.log.xz | Bin 72596 -> 71968 bytes 06-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 07-build_abe-linux/console.log.xz | Bin 9212 -> 9212 bytes 08-build_abe-glibc/console.log.xz | Bin 240184 -> 240280 bytes 09-build_abe-stage2/console.log.xz | Bin 203248 -> 203300 bytes 10-build_abe-gdb/console.log.xz | Bin 37380 -> 37628 bytes 11-build_abe-qemu/console.log.xz | Bin 32300 -> 32532 bytes 12-check_regression/console.log.xz | Bin 4008 -> 3688 bytes 13-update_baseline/console.log | 38 +++++++++++++++++------------------ 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 | 32 ++++++++++++++--------------- 20 files changed, 42 insertions(+), 42 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/master-aarch64 updated (9f9d862b1e -> 34ac577888)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/master-aarch64 in repository toolchain/ci/base-artifacts. discards 9f9d862b1e 164: onsuccess: #2100: 1: Success after binutils/gcc: 15 commits discards bab9c8aa8c 163: onsuccess: #2098: 1: Success after binutils/gcc: 18 commits discards 87b62a866b 162: onsuccess: #2097: 1: Success after binutils/gcc: 16 commits discards ec62ae053e 161: onsuccess: #2096: 1: Success after gcc: 2 commits discards 1beadf917b 160: onsuccess: #2095: 1: Success after binutils/gcc: 4 commits discards fcac483f33 159: onsuccess: #2094: 1: Success after binutils/gcc: 23 commits discards 91f1da0704 158: onsuccess: #2093: 1: Success after binutils/gcc: 9 commits discards b3658dfebf 157: onsuccess: #2092: 1: Success after binutils/gcc: 3 commits discards e835ad9fe5 156: onsuccess: #2091: 1: Success after binutils/gcc: 2 commits discards b7311ad921 155: onsuccess: #2090: 1: Success after binutils/gcc: 22 commits discards 74246d03cb 154: onsuccess: #2089: 1: Success after gcc: 4 commits discards d159c9d871 153: onsuccess: #2088: 1: Success after basepoints/gcc-13-30 [...] discards c6e4265ec0 152: onsuccess: #2087: 1: Success after gdb-12-branchpoint-2 [...] discards 6889b8386c 151: onsuccess: #2086: 1: Success after gcc: 2 commits discards 35b8cdbc2d 150: onsuccess: #2085: 1: Success after gcc: 2 commits discards b90954b8a8 149: onsuccess: #2084: 1: Success after gcc: 16 commits discards c004a7de82 148: onsuccess: #2082: 1: Success after gdb-12-branchpoint-2 [...] discards c0994344f5 147: onsuccess: #2080: 1: Success after binutils/gcc: 13 commits discards e3d13c4173 146: onsuccess: #2079: 1: Success after binutils/gcc: 14 commits discards 1761a844f0 145: onsuccess: #2078: 1: Success after binutils/gcc: 10 commits discards 6cc09e0c9c 144: onsuccess: #2077: 1: Success after binutils/gcc: 15 commits discards 66bd5b78c7 143: onsuccess: #2076: 1: Success after binutils/gcc: 14 commits discards a97799f117 142: onsuccess: #2075: 1: Success after binutils/gcc: 71 commits discards 2f9642cd54 141: onsuccess: #2073: 1: Success after binutils: 3 commits discards c669f8d32b 140: onsuccess: #2070: 1: Success after binutils: 4 commits discards 810f05a3e5 139: onsuccess: #2067: 1: Success after binutils: 2 commits discards 40635d2413 138: onsuccess: #2064: 1: Success after binutils: 4 commits discards 01c463d5cf 137: onsuccess: #2061: 1: Success after binutils: 2 commits discards 768ea86366 136: onsuccess: #2056: 1: Success after binutils: 4 commits discards cf0a874675 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits discards 16438f224f 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits discards 13d7152f16 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits discards 1c23d9a2e2 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits discards dfc048cee8 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] discards 5e5f7f19d2 130: onsuccess: #2049: 1: Success after gcc: 9 commits discards 47e2f023a1 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] discards c2d7bdc5f0 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] discards 73c991ae2f 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] discards 00a2399c39 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] discards 948b4c94b6 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits discards 4c26e83829 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits discards 5d97eda856 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits discards 395811a521 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits discards 365287d8ae 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits discards 0bb19e1df8 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits discards 86bc943805 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits discards 1830caa7e0 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits discards cc549ec4ac 117: onsuccess: #2034: 1: Success after binutils: 2 commits discards 9262756cf6 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits discards f3d0175a17 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits discards 07045f4373 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits discards a77a83b278 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits discards 025ce26b8d 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits discards b98896c10d 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits discards 23dd5a69dd 110: onsuccess: #2027: 1: Success after gcc: 5 commits discards 9400c985c1 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits discards 999ac4575f 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits discards c56d9d73d5 107: onsuccess: #2024: 1: Success after gcc: 3 commits discards 75e9567c40 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits discards e3aea1ad17 105: onsuccess: #2022: 1: Success after gcc: 4 commits discards 1473621430 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits discards 18f5fc0f2a 103: onsuccess: #2020: 1: Success after gcc: 2 commits discards 1191b056d3 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] discards 1bb0a9467f 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits discards e681cb53d0 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits discards 7c9a4507ea 99: onsuccess: #1974: 1: Success after gcc: 14 commits discards 8fe4a8a31e 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits discards 684d090b98 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits discards de201c6458 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] discards 38a4bd83ce 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] discards c786d1adbe 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits discards b610bef3e0 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] discards 46de97d081 92: onsuccess: #1965: 1: Success after gcc: 2 commits discards aa790ae89c 91: onsuccess: 1: Success after gcc: Daily bump. discards fea3484198 90: onsuccess: 1: Success after binutils/gcc: 6 commits discards eb85de3524 89: onsuccess: 1: Success after binutils/gcc: 9 commits discards 58107ed790 88: onsuccess: 1: Success after binutils/gcc: 16 commits discards b4b4bcf63b 87: onsuccess: 1: Success after binutils/gcc: 4 commits discards 4e3064eb74 86: onsuccess: 1: Success after binutils/gcc: 13 commits discards b68e006aed 85: onsuccess: 1: Success after binutils/gcc: 9 commits discards 717134be65 84: onsuccess: 1: Success after binutils/gcc: 9 commits discards ff96234447 83: onsuccess: 1: Success after gcc: 8 commits discards e058decd5d 82: onsuccess: 1: Success after binutils/gcc: 10 commits discards 0e902ab961 81: onsuccess: 1: Success after binutils/gcc: 27 commits discards 5419792e24 80: onsuccess: 1: Success after binutils/gcc: 14 commits discards e2211e68b3 79: onsuccess: 1: Successful build after gcc: Daily bump. discards 3ebcba8664 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards f1ad2ddb06 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards 35b0837f0a 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards 25e5f1d044 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 7a6f464be8 74: onsuccess: 1: Successful build after binutils: Automatic [...] discards f8045b7b50 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards 97de0b7a47 72: onsuccess: 1: Successful build after gcc: 2 commits discards faf630b504 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 075d35dc69 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] discards 38baaacebc 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 465d084225 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 1300be2e86 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 3a880c08e3 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 69960d3b02 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 7013f12bbe 64: onsuccess: 1: Successful build after gcc: 5 commits new dbb1dcd0ed 64: onsuccess: 1: Successful build after gcc: 5 commits new 9d85fcde3e 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 13cff4c344 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 694fc9bbc5 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 7e0da96f89 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits new dd4d5373a0 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 4bdffea7de 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] new 2972ea3a11 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 4ac127125c 72: onsuccess: 1: Successful build after gcc: 2 commits new c18191bf5f 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] new 21ea50e9bc 74: onsuccess: 1: Successful build after binutils: Automatic [...] new 10ce1dc20c 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits new 925f30e16c 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 50a61a2051 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 5de9f11274 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits new c4400b489d 79: onsuccess: 1: Successful build after gcc: Daily bump. new 79824fa681 80: onsuccess: 1: Success after binutils/gcc: 14 commits new 8f2cfb2e4f 81: onsuccess: 1: Success after binutils/gcc: 27 commits new bf21dafb05 82: onsuccess: 1: Success after binutils/gcc: 10 commits new eeacc0e497 83: onsuccess: 1: Success after gcc: 8 commits new 98415c6703 84: onsuccess: 1: Success after binutils/gcc: 9 commits new 5a035fa8bc 85: onsuccess: 1: Success after binutils/gcc: 9 commits new 0603acc63e 86: onsuccess: 1: Success after binutils/gcc: 13 commits new 837ab378a7 87: onsuccess: 1: Success after binutils/gcc: 4 commits new c3cac1aa25 88: onsuccess: 1: Success after binutils/gcc: 16 commits new 04e42ea363 89: onsuccess: 1: Success after binutils/gcc: 9 commits new 6186b6f493 90: onsuccess: 1: Success after binutils/gcc: 6 commits new 5c63c5acfc 91: onsuccess: 1: Success after gcc: Daily bump. new d4082fe722 92: onsuccess: #1965: 1: Success after gcc: 2 commits new 1706814092 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] new 727081825b 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits new 8d109ff506 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] new 24209bfb77 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] new 71d4b82aab 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits new c2bfb402f2 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits new e0e5d1dd8d 99: onsuccess: #1974: 1: Success after gcc: 14 commits new 16952a06cf 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits new bbd6080399 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits new 0f967877c5 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] new d3f2639781 103: onsuccess: #2020: 1: Success after gcc: 2 commits new 164cdeff55 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits new b64ee7d960 105: onsuccess: #2022: 1: Success after gcc: 4 commits new b3089437cd 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits new d9204e81fd 107: onsuccess: #2024: 1: Success after gcc: 3 commits new cf67d91d81 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits new a5a6d81ee4 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits new e2efc13ea2 110: onsuccess: #2027: 1: Success after gcc: 5 commits new 60c1d0006f 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits new df91fdd098 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits new 7d7d1ac084 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits new d4f591dddd 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits new 0c31317dbd 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits new 4aaa55f0f7 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits new 4a93e22412 117: onsuccess: #2034: 1: Success after binutils: 2 commits new 469599af63 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits new e8af285cf6 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits new ab1b38c267 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits new b9f4d2fd1b 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits new 2fdf629760 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits new bbbe0b594e 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits new 75ed8320e7 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits new 5b6a4fde57 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits new 457b7177be 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] new dc8b706a3e 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] new de603bd90f 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] new 5c36f081c4 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] new 8acbf6a10f 130: onsuccess: #2049: 1: Success after gcc: 9 commits new 5ec1c38274 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] new e73ba76ef1 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits new c4a8c70a21 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits new 6cba0a2218 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits new efd0c8219b 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits new 8bc998f399 136: onsuccess: #2056: 1: Success after binutils: 4 commits new d15fd73006 137: onsuccess: #2061: 1: Success after binutils: 2 commits new 38f50dee74 138: onsuccess: #2064: 1: Success after binutils: 4 commits new 96a5c27b49 139: onsuccess: #2067: 1: Success after binutils: 2 commits new dff7379577 140: onsuccess: #2070: 1: Success after binutils: 4 commits new 065bce809e 141: onsuccess: #2073: 1: Success after binutils: 3 commits new 924c337339 142: onsuccess: #2075: 1: Success after binutils/gcc: 71 commits new 0733b27d0b 143: onsuccess: #2076: 1: Success after binutils/gcc: 14 commits new e9762d3b57 144: onsuccess: #2077: 1: Success after binutils/gcc: 15 commits new d7044cb813 145: onsuccess: #2078: 1: Success after binutils/gcc: 10 commits new 1e795de614 146: onsuccess: #2079: 1: Success after binutils/gcc: 14 commits new 17d305d2e4 147: onsuccess: #2080: 1: Success after binutils/gcc: 13 commits new 921554711c 148: onsuccess: #2082: 1: Success after gdb-12-branchpoint-2 [...] new a7a40ebd06 149: onsuccess: #2084: 1: Success after gcc: 16 commits new 59f1cd486e 150: onsuccess: #2085: 1: Success after gcc: 2 commits new 2fd168092a 151: onsuccess: #2086: 1: Success after gcc: 2 commits new d6d128820d 152: onsuccess: #2087: 1: Success after gdb-12-branchpoint-2 [...] new aabd3311e0 153: onsuccess: #2088: 1: Success after basepoints/gcc-13-30 [...] new 49303f9c54 154: onsuccess: #2089: 1: Success after gcc: 4 commits new 11a9b34138 155: onsuccess: #2090: 1: Success after binutils/gcc: 22 commits new 83efede4d2 156: onsuccess: #2091: 1: Success after binutils/gcc: 2 commits new a07cf35c03 157: onsuccess: #2092: 1: Success after binutils/gcc: 3 commits new 352a85746c 158: onsuccess: #2093: 1: Success after binutils/gcc: 9 commits new f76718688e 159: onsuccess: #2094: 1: Success after binutils/gcc: 23 commits new 03315bcc77 160: onsuccess: #2095: 1: Success after binutils/gcc: 4 commits new 08e53ef38f 161: onsuccess: #2096: 1: Success after gcc: 2 commits new 8beebf340b 162: onsuccess: #2097: 1: Success after binutils/gcc: 16 commits new 889d46e95c 163: onsuccess: #2098: 1: Success after binutils/gcc: 18 commits new 91ce08872d 164: onsuccess: #2100: 1: Success after binutils/gcc: 15 commits new 34ac577888 165: onsuccess: #2101: 1: Success after binutils/gcc: 8 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 (9f9d862b1e) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-aarch64 [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1676 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 38452 -> 37856 bytes 04-build_abe-gcc/console.log.xz | Bin 215920 -> 213616 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3880 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2572 -> 2644 bytes 07-check_regression/console.log.xz | Bin 5636 -> 5464 bytes 07-check_regression/extra-bisect-params | 1 + 07-check_regression/fails.sum | 7 + 07-check_regression/mail-body.txt | 41 + 07-check_regression/results.compare | 40 +- 07-check_regression/results.compare2 | 230 +- 07-check_regression/results.regressions | 41 + 08-update_baseline/console.log | 46 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 43 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 41 + sumfiles/g++.log.xz | Bin 3585032 -> 3570952 bytes sumfiles/g++.sum | 130 +- sumfiles/gcc.log.xz | Bin 3098044 -> 3119032 bytes sumfiles/gcc.sum | 5058 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1042456 -> 1045944 bytes sumfiles/gfortran.sum | 46 +- sumfiles/libatomic.log.xz | Bin 2192 -> 2196 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 207680 -> 207464 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2548 -> 2544 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 448096 -> 445748 bytes sumfiles/libstdc++.sum | 12 +- 36 files changed, 2918 insertions(+), 2872 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_lto updated (be3db933c1 -> df18aa89e8)

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_lto in repository toolchain/ci/base-artifacts. from be3db933c1 55: onsuccess: #464: 2: Success after binutils/gcc: 45 commits new df18aa89e8 56: onsuccess: #465: 2: Success after binutils/gcc: 43 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 1668 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 50676 -> 50768 bytes 05-build_abe-bootstrap_lto/console.log.xz | Bin 474128 -> 475000 bytes 06-check_regression/console.log.xz | Bin 3196 -> 3084 bytes 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 +++++++++--------- 12 files changed, 15 insertions(+), 15 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (0afa9dfb8fb -> b8473c9a2b8)

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 0afa9dfb8fb c: support the attribute starting with '_' new b8473c9a2b8 libtdc++: Regenerate Makefile.in after freestanding header changes The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: libstdc++-v3/include/Makefile.in | 101 +++++++++++++++++++-------------------- 1 file changed, 49 insertions(+), 52 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch releases/gcc-12 updated (b947611dd47 -> 98508b96c53)

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-12 in repository gcc. from b947611dd47 Daily bump. new 98508b96c53 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/DATESTAMP | 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

[gcc] branch releases/gcc-11 updated (f8ddc6c5d50 -> 40f47c797bd)

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 f8ddc6c5d50 Daily bump. new 40f47c797bd 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/DATESTAMP | 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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits October 2022