Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-norov-allmodconfig updated (d85b419197 -> 51041dd801)

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-arm-norov-allmodconfig in repository toolchain/ci/base-artifacts. from d85b419197 22: onsuccess: #69: 23157: Success after binutils/llvm/qemu: [...] new 51041dd801 23: onsuccess: #70: 23157: Success after binutils/llvm/qemu: [...] 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 -> 1916 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30280 -> 31456 bytes 04-build_kernel_llvm/console.log.xz | Bin 65176 -> 65360 bytes 05-build_abe-qemu/console.log.xz | Bin 31664 -> 31628 bytes 06-build_linux/console.log.xz | Bin 5184 -> 5436 bytes 08-check_regression/console.log.xz | Bin 4072 -> 4180 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_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 | 28 ++++++++++++++-------------- 15 files changed, 21 insertions(+), 21 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled_lto_lean updated (031896d8a3 -> 1a06e45f0c)

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_profiled_lto_lean in repository toolchain/ci/base-artifacts. from 031896d8a3 76: onsuccess: #459: 2: Success after binutils/gcc: 34 commits new 1a06e45f0c 77: onsuccess: #460: 2: Success after binutils/gcc: 27 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1716 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2700 bytes 04-build_abe-binutils/console.log.xz | Bin 50848 -> 50936 bytes .../console.log.xz | Bin 945236 -> 946072 bytes 06-check_regression/console.log.xz | Bin 3144 -> 3136 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 | 20 ++++++++++---------- 12 files changed, 16 insertions(+), 16 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[glibc] branch master updated (b4174c28d2 -> 0cc0033ef1)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository glibc. from b4174c28d2 Fix resource/bug-ulimit1 test new 0cc0033ef1 stdlib/strfrom: Add copysign to fix NAN issue on riscv (BZ #29501) 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: stdlib/strfrom-skeleton.c | 3 ++- .../fix-float-double-convert-nan.h} | 19 +++++++++--------- .../rvd/fix-float-double-convert-nan.h} | 23 +++++++++++++--------- 3 files changed, 25 insertions(+), 20 deletions(-) copy sysdeps/{unix/sysv/linux/loongarch/sigcontextinfo.h => generic/fix-float-doub [...] copy sysdeps/{unix/sysv/linux/loongarch/sigcontextinfo.h => riscv/rvd/fix-float-do [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[gcc] branch master updated (988dd22ec66 -> 4fe34cdcc80)

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 988dd22ec66 libstdc++: Fix allocator propagation in regex algorithms [P [...] new 4fe34cdcc80 c: tree: target: C2x (...) function prototypes and va_start [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/c-family/c-common.cc | 11 +- gcc/c-family/c.opt | 4 +- gcc/c/c-decl.cc | 13 +- gcc/c/c-parser.cc | 22 +-- gcc/c/c-tree.h | 2 + gcc/c/c-typeck.cc | 20 ++- gcc/config/aarch64/aarch64.cc | 3 +- gcc/config/alpha/alpha.cc | 5 +- gcc/config/arc/arc.cc | 3 +- gcc/config/arm/arm.cc | 3 +- gcc/config/csky/csky.cc | 3 +- gcc/config/epiphany/epiphany.cc | 8 +- gcc/config/fr30/fr30.cc | 23 +-- gcc/config/frv/frv.cc | 3 +- gcc/config/ft32/ft32.cc | 6 +- gcc/config/i386/i386.cc | 3 +- gcc/config/ia64/ia64.cc | 5 +- gcc/config/loongarch/loongarch.cc | 3 +- gcc/config/m32r/m32r.cc | 12 +- gcc/config/mcore/mcore.cc | 5 +- gcc/config/mips/mips.cc | 3 +- gcc/config/mmix/mmix.cc | 3 +- gcc/config/nds32/nds32.cc | 9 +- gcc/config/nios2/nios2.cc | 3 +- gcc/config/riscv/riscv.cc | 3 +- gcc/config/rs6000/rs6000-call.cc | 7 +- gcc/config/sh/sh.cc | 9 +- gcc/config/visium/visium.cc | 3 +- gcc/config/vms/vms-c.cc | 3 - gcc/doc/invoke.texi | 10 +- gcc/doc/tm.texi | 4 +- gcc/fortran/trans-types.cc | 4 +- gcc/function.cc | 6 + gcc/ginclude/stdarg.h | 4 + gcc/lto/lto-common.cc | 1 + gcc/objc/objc-next-runtime-abi-01.cc | 2 +- gcc/target.def | 4 +- gcc/testsuite/gcc.dg/Wold-style-definition-2.c | 2 +- gcc/testsuite/gcc.dg/c11-stdarg-1.c | 7 + gcc/testsuite/gcc.dg/c11-stdarg-2.c | 7 + gcc/testsuite/gcc.dg/c11-stdarg-3.c | 8 + gcc/testsuite/gcc.dg/c2x-nullptr-1.c | 1 + gcc/testsuite/gcc.dg/c2x-stdarg-1.c | 22 +++ gcc/testsuite/gcc.dg/c2x-stdarg-2.c | 22 +++ gcc/testsuite/gcc.dg/c2x-stdarg-3.c | 16 ++ gcc/testsuite/gcc.dg/c2x-stdarg-4.c | 164 +++++++++++++++++++++ gcc/testsuite/gcc.dg/diagnostic-token-ranges.c | 4 +- gcc/testsuite/gcc.dg/format/sentinel-1.c | 2 +- gcc/testsuite/gcc.dg/gnu2x-stdarg-1.c | 8 + gcc/testsuite/gcc.dg/torture/c2x-stdarg-split-1a.c | 37 +++++ gcc/testsuite/gcc.dg/torture/c2x-stdarg-split-1b.c | 147 ++++++++++++++++++ gcc/tree-core.h | 3 +- gcc/tree-streamer-in.cc | 1 + gcc/tree-streamer-out.cc | 1 + gcc/tree.cc | 31 +++- gcc/tree.h | 8 +- 56 files changed, 621 insertions(+), 105 deletions(-) create mode 100644 gcc/testsuite/gcc.dg/c11-stdarg-1.c create mode 100644 gcc/testsuite/gcc.dg/c11-stdarg-2.c create mode 100644 gcc/testsuite/gcc.dg/c11-stdarg-3.c create mode 100644 gcc/testsuite/gcc.dg/c2x-stdarg-1.c create mode 100644 gcc/testsuite/gcc.dg/c2x-stdarg-2.c create mode 100644 gcc/testsuite/gcc.dg/c2x-stdarg-3.c create mode 100644 gcc/testsuite/gcc.dg/c2x-stdarg-4.c create mode 100644 gcc/testsuite/gcc.dg/gnu2x-stdarg-1.c create mode 100644 gcc/testsuite/gcc.dg/torture/c2x-stdarg-split-1a.c create mode 100644 gcc/testsuite/gcc.dg/torture/c2x-stdarg-split-1b.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (703b3d30ed -> de6fdfc460)

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 703b3d30ed 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/g [...] discards 7e14d10133 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] discards f411d7f960 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards f19f803d7b 178: onsuccess: #1631: 7: Success after binutils/gcc/linux/g [...] discards 78a2f8d7db 177: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards 428abe8029 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc/g [...] discards 28cfd543ea 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc/g [...] discards 8b7d97f5b6 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: 15 [...] discards fc44e336d3 173: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 16cfcfcee3 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qemu [...] discards c5ff9cc3e2 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 12 [...] discards 5fdba01561 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/g [...] discards 893b90ef81 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/g [...] discards 9fe189e4ad 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/g [...] discards 0f7c55a5b8 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 28 [...] discards e96898d04c 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits discards d4011aef12 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/g [...] discards b03ac617fd 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/g [...] discards 3983a95dd8 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 12 [...] discards 3d9662e362 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 commits discards 18e6985c05 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/g [...] discards 80de96ce08 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 69d8949b4c 159: onsuccess: #1612: 7: Success after gcc: 4 commits discards 8990bd3123 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/g [...] discards a42df398f5 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits discards d9e81cfe60 156: onsuccess: #1609: 7: Success after gcc: 2 commits discards 57de70ce7a 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] discards 483a3c1d1e 154: onsuccess: #1607: 1: Success after gcc: 2 commits discards 265857fe7b 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] discards ba61bfabe2 152: force: #1605: 7: Success after gcc: 9 commits discards 815a350530 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] discards 464b5fbe24 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] discards c2f5771dce 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] discards 29b20bd278 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] discards 229ebbde2c 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] discards fad433639d 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] discards e68eb64983 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] discards 89bdee6fdd 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards 3046fa982c 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] discards 4a20251cc4 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards e2518cb9bf 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards 73fa856ed4 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards 69ef4e4f97 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards 9439eb38b0 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards f063646df7 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards 69142cc1b3 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards d443ce2375 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards b21556fe2d 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards 7c6a240d1e 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards 7a13501bb8 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards dcfddc3712 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards 387b5f0667 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards 284cb8b750 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards 815752844f 128: onsuccess: #1579: 7: Success after linux: 12 commits discards 5898ecfcb1 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards 1538fddad3 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards d9d44f87cd 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards 664b29a63c 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards c3c5dde874 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards 15444b419e 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards 1d646fdadc 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards c148025f96 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards 25044024e2 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards 533945e5eb 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards 5bdc889018 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards d6f032c666 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards 3041bd29e3 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards 4805f5a172 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards a1fc717372 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards a7b8aab77a 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards 02e23aa501 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards bf2a7e6fe3 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 35ceb7aff0 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 074b869f8d 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards 4f7fbdc9f8 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards 4e9b5ad07e 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards 185736e72f 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards f8c7eecc93 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards e7df191140 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 7d76e4e202 102: force: #1551: 1: Failure after gcc: 306 commits discards bf3e554fa3 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 7ed4deaff0 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards 69b9579826 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 1d2d18515d 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards ab80e6e340 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 0f808e8ba8 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 39c5ac6919 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 3637b779d0 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 4aef443dd4 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 868eeb2b23 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards b564530475 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards 9fa13a10f0 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 22b552fb4c 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 3a148cbc1f 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards ea7e8c8b12 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards b995937ab9 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 851466c535 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 7868b57c38 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 99b4d85729 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards cbf6df9987 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 9138ae8783 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f5e8c84308 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 44c34ec53a 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new ae3c6c683e 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 6e7556250e 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 99804fc682 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new ba61013f07 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new a951338673 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 1a257eb304 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 3f8fd3461c 89: onsuccess: 7: Success after gcc/glibc: 8 commits new 2226467ea8 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 80df83eee6 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 9d3c7ab69f 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 1fd2c1d853 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new aff0435a1a 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 91d2d9bf57 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new caaaa4dd10 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 4305791f54 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new e82eb42369 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 942f99ccfd 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 2d542e9ae9 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new 892fe9b850 101: onsuccess: #1547: 7: Success after binutils: 82 commits new d28f8e20b4 102: force: #1551: 1: Failure after gcc: 306 commits new 6d50c20b53 103: onsuccess: #1552: 1: Success after gcc: 5 commits new ff9d7c75f5 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new 160647f5a9 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new 6e4d1b2a03 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 839b1d88a4 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new 2734534b69 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new a2a1da17f0 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 1befc4f0a1 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 2f421d6ac3 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new 17fdbbbf00 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new a72ce66c0e 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new dfa347bf05 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new a172418056 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new 74354fcb3d 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new 4d442b75b6 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new 466f0940d6 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new 4035892055 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new b440733880 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new 0b2dc41d5e 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new 87db0aca81 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new f9cde2525c 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new 2de49161d9 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new 4bfb5f680d 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new cd9e0256ae 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new c180783488 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new bbba2ec9f5 128: onsuccess: #1579: 7: Success after linux: 12 commits new 6b02e8920b 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new 8244f35ab1 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new d597a0588a 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new d940526186 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new 8798dda3d5 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new 0a9df52c29 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new a34472abf7 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new 5e94736b9f 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new 29807a9346 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 6ac180f569 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new d92b52e23e 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new 289f4e73f4 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new 5f43879e6c 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new 65bd8740a8 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new eda1fcbc70 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] new abd2406f54 144: onsuccess: #1595: 7: Success after glibc: 2 commits new 902587c5ae 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] new 370d4ec0b2 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] new ea00179fe6 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] new 94641d1a45 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] new 5b1fd968bf 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] new c571c5c6cd 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] new 8a7be0b1da 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] new de47596c18 152: force: #1605: 7: Success after gcc: 9 commits new 16a589f0bc 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] new dbef2ef054 154: onsuccess: #1607: 1: Success after gcc: 2 commits new 6de85b8c63 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...] new d87032aff3 156: onsuccess: #1609: 7: Success after gcc: 2 commits new 7897c81c5d 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits new 0c373f4bdb 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/g [...] new 23ddf76d06 159: onsuccess: #1612: 7: Success after gcc: 4 commits new ea63975359 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 52edff61fd 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/g [...] new 772b22686b 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 commits new 146ec33247 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 12 [...] new 2fb64b0c52 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/g [...] new 13da254433 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/g [...] new 2cd6815f82 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits new 56428c297b 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 28 [...] new 282d075670 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/g [...] new 81c03037fc 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/g [...] new 3c97d8501d 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/g [...] new e7103bf2de 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 12 [...] new b1bdf2c722 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qemu [...] new 61262cbf23 173: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 26ed6fa443 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: 15 [...] new 0618d7ed04 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc/g [...] new c90979ecbe 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc/g [...] new 0fee689b68 177: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 1df6025dcd 178: onsuccess: #1631: 7: Success after binutils/gcc/linux/g [...] new a1be47d725 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new eb257ce023 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] new b3dff1171e 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/g [...] new de6fdfc460 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/g [...] 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 (703b3d30ed) \ 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 1664 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2756 bytes 04-build_abe-binutils/console.log.xz | Bin 30376 -> 31056 bytes 05-build_abe-stage1/console.log.xz | Bin 73192 -> 72992 bytes 07-build_abe-linux/console.log.xz | Bin 8828 -> 9580 bytes 08-build_abe-glibc/console.log.xz | Bin 239544 -> 239776 bytes 09-build_abe-stage2/console.log.xz | Bin 203784 -> 205356 bytes 10-build_abe-gdb/console.log.xz | Bin 37632 -> 38268 bytes 11-build_abe-qemu/console.log.xz | Bin 32200 -> 32224 bytes 12-check_regression/console.log.xz | Bin 5408 -> 5348 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 48 ++++++++++++------------- 22 files changed, 67 insertions(+), 67 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[newlib] branch master updated (eaa51ea45 -> 389f071f4)

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 newlib. from eaa51ea45 Cygwin: add missing .com entry in new-features.xml new b9e97f58a Cygwin: exceptions: print 48 bit addresses new c0776fa7b Cygwin: add memory_layout.h new 2f9b8ff00 Cygwin: decouple cygheap from Cygwin DLL new 60675f1a7 Cygwin: decouple shared mem regions from Cygwin DLL new 0508e11f8 Cygwin: memory_layout.h: fix comments new 49df152de Cygwin: memory_layout.h: define absolute MMAP_STORAGE_HIGH va [...] new ebbff10ae Cygwin: drop objcopy .gnu_debuglink juggle new a3f1eff38 Cygwin: /proc/<PID>/maps: output cygheap info new 943433b00 Cygwin: Enable dynamicbase on the Cygwin DLL by default new 389f071f4 Cygwin: document ASLR support The 10 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: winsup/cygwin/Makefile.am | 25 ++++------- winsup/cygwin/create_posix_thread.cc | 4 -- winsup/cygwin/cygwin.sc.in | 27 ------------ winsup/cygwin/dcrt0.cc | 3 -- winsup/cygwin/exceptions.cc | 8 ++-- winsup/cygwin/fhandler/process.cc | 2 + winsup/cygwin/local_includes/cygheap.h | 1 - winsup/cygwin/local_includes/memory_layout.h | 63 ++++++++++++++++++++++++++++ winsup/cygwin/local_includes/mmap_alloc.h | 6 +-- winsup/cygwin/mm/cygheap.cc | 62 ++++++++++++++++----------- winsup/cygwin/mm/heap.cc | 18 +------- winsup/cygwin/mm/shared.cc | 55 ++++-------------------- winsup/cygwin/release/3.4.0 | 2 + winsup/cygwin/wincap.cc | 25 +++++------ winsup/doc/new-features.xml | 4 ++ 15 files changed, 144 insertions(+), 161 deletions(-) create mode 100644 winsup/cygwin/local_includes/memory_layout.h -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[gcc] branch master updated (95decac3ce8 -> 988dd22ec66)

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 95decac3ce8 vect: Reject non-byte offsets for gather/scatters [PR107346] new 988dd22ec66 libstdc++: Fix allocator propagation in regex algorithms [P [...] 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/bits/regex_executor.h | 17 ++--- libstdc++-v3/include/bits/regex_executor.tcc | 3 +- .../28_regex/algorithms/regex_match/107376.cc | 76 ++++++++++++++++++++++ 3 files changed, 87 insertions(+), 9 deletions(-) create mode 100644 libstdc++-v3/testsuite/28_regex/algorithms/regex_match/107376.cc -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[gcc] branch master updated (031a400e49d -> 95decac3ce8)

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 031a400e49d tree-optimization/107407 - wrong code with DSE new 95decac3ce8 vect: Reject non-byte offsets for gather/scatters [PR107346] 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/tree-vect-data-refs.cc | 5 +++++ 1 file changed, 5 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (806f2ff9a8 -> 7d17afac69)

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 806f2ff9a8 249: onsuccess: #2186: 1: Success after binutils/gcc: 7 commits discards cd51e912a9 248: onsuccess: #2185: 1: Success after binutils/gcc: 7 commits discards 80bda5ef10 247: onsuccess: #2184: 1: Success after binutils/gcc: 7 commits discards dfdfda0d66 246: onsuccess: #2183: 1: Success after binutils/gcc: 8 commits discards a3d70e0a0d 245: onsuccess: #2182: 1: Success after binutils/gcc: 6 commits discards ccc0b99f10 244: onsuccess: #2181: 1: Success after binutils/gcc: 7 commits discards 5d72477a05 243: onsuccess: #2180: 1: Success after binutils/gcc: 4 commits discards 2dc01f42b3 242: onsuccess: #2179: 1: Success after binutils/gcc: 16 commits discards 91071fc3c9 241: onsuccess: #2178: 1: Success after binutils/gcc: 7 commits discards eda882f411 240: onsuccess: #2177: 1: Success after binutils/gcc: 6 commits discards 6ceb97be4b 239: onsuccess: #2176: 1: Success after binutils/gcc: 8 commits discards fa41b4db79 238: onsuccess: #2175: 1: Success after binutils/gcc: 14 commits discards e82434a7d6 237: onsuccess: #2174: 1: Success after binutils/gcc: 8 commits discards e9ea200396 236: onsuccess: #2173: 1: Success after binutils/gcc: 9 commits discards d3824eab8e 235: onsuccess: #2172: 1: Success after binutils/gcc: 16 commits discards 87891f6421 234: onsuccess: #2171: 1: Success after binutils/gcc: 11 commits discards 51fd7bf069 233: onsuccess: #2170: 1: Success after gcc: 5 commits discards 8360c0af2a 232: onsuccess: #2169: 1: Success after binutils: 4 commits discards da1079c0f0 231: onsuccess: #2168: 1: Success after gcc: 2 commits discards 3b9650ea5a 230: onsuccess: #2167: 1: Success after binutils/gcc: 2 commits discards 26ef24e964 229: onsuccess: #2166: 1: Success after basepoints/gcc-13-34 [...] discards acfc577841 228: onsuccess: #2165: 1: Success after basepoints/gcc-13-34 [...] discards 45d82ccae5 227: onsuccess: #2164: 1: Success after binutils/gcc: 2 commits discards 8dc2b5855e 226: onsuccess: #2163: 1: Success after binutils/gcc: 5 commits discards 20bfb62b74 225: onsuccess: #2162: 1: Success after binutils/gcc: 7 commits discards 755fdcb0b0 224: onsuccess: #2161: 1: Success after binutils/gcc: 19 commits discards 5e31d13ee1 223: onsuccess: #2160: 1: Success after binutils/gcc: 7 commits discards a3ede8f09a 222: onsuccess: #2159: 1: Success after binutils/gcc: 7 commits discards 47fb4620e4 221: onsuccess: #2158: 1: Success after binutils/gcc: 15 commits discards 4f86ffcdae 220: onsuccess: #2157: 1: Success after binutils/gcc: 18 commits discards aa143251d5 219: onsuccess: #2156: 1: Success after binutils/gcc: 7 commits discards 9ecef86500 218: onsuccess: #2155: 1: Success after binutils/gcc: 9 commits discards 437638865d 217: onsuccess: #2154: 1: Success after binutils/gcc: 19 commits discards e2ed26de92 216: onsuccess: #2153: 1: Success after binutils/gcc: 18 commits discards 1a8c3353c1 215: onsuccess: #2152: 1: Success after binutils/gcc: 2 commits discards b6fbe8a845 214: onsuccess: #2151: 1: Success after binutils/gcc: 2 commits discards 332ccec418 213: onsuccess: #2150: 1: Success after binutils/gcc: 29 commits discards 5ecd94788c 212: onsuccess: #2149: 1: Success after binutils/gcc: 10 commits discards f5f7140d08 211: onsuccess: #2148: 1: Success after gcc: 3 commits discards d7dcc69d6f 210: onsuccess: #2147: 1: Success after binutils/gcc: 11 commits discards f0f3db4a64 209: onsuccess: #2146: 1: Success after binutils/gcc: 17 commits discards 67bd29db84 208: onsuccess: #2145: 1: Success after binutils/gcc: 14 commits discards 414f41da98 207: onsuccess: #2144: 1: Success after gcc: 3 commits discards 1daa4b0a4f 206: onsuccess: #2143: 1: Success after gdb-12-branchpoint-2 [...] discards 0a6ab02b48 205: onsuccess: #2142: 1: Success after binutils/gcc: 4 commits discards 1238d8dc53 204: onsuccess: #2141: 1: Success after binutils/gcc: 4 commits discards 0e660509bc 203: onsuccess: #2140: 1: Success after binutils/gcc: 4 commits discards d08cc2426c 202: onsuccess: #2139: 1: Success after gdb-12-branchpoint-2 [...] discards ac85806217 201: onsuccess: #2138: 1: Success after binutils/gcc: 7 commits discards 1a184503cf 200: onsuccess: #2137: 1: Success after binutils/gcc: 15 commits discards 7d2689a869 199: onsuccess: #2136: 1: Success after binutils/gcc: 31 commits discards a851a7b463 198: onsuccess: #2134: 1: Success after binutils/gcc: 7 commits discards d41d677e97 197: onsuccess: #2133: 1: Success after gcc: 12 commits discards d527178485 196: onsuccess: #2132: 1: Success after binutils/gcc: 7 commits discards da02b0d6c3 195: onsuccess: #2131: 1: Success after gcc: 2 commits discards ffefd67d12 194: onsuccess: #2130: 1: Success after binutils/gcc: 7 commits discards da479a8505 193: onsuccess: #2129: 1: Success after binutils/gcc: 20 commits discards 8734776219 192: onsuccess: #2128: 1: Success after binutils/gcc: 11 commits discards 5ac8609ba0 191: onsuccess: #2127: 1: Success after binutils/gcc: 3 commits discards 7fa745b4cf 190: onsuccess: #2126: 1: Success after binutils/gcc: 8 commits discards 485e86226f 189: onsuccess: #2125: 1: Success after binutils/gcc: 23 commits discards 9ecfdb3fac 188: onsuccess: #2124: 1: Success after binutils/gcc: 26 commits discards ba905a626f 187: onsuccess: #2123: 1: Success after binutils/gcc: 4 commits discards 92c3b0b951 186: onsuccess: #2122: 1: Success after binutils/gcc: 8 commits discards 18931b83be 185: onsuccess: #2121: 1: Success after binutils/gcc: 18 commits discards e939e5e06b 184: onsuccess: #2120: 1: Success after binutils/gcc: 22 commits discards dc73b4dbaf 183: onsuccess: #2119: 1: Success after binutils/gcc: 3 commits discards a9dd8d4e8b 182: onsuccess: #2118: 1: Success after gdb-12-branchpoint-2 [...] discards 6f53c657a3 181: onsuccess: #2117: 1: Success after gcc: 3 commits discards 3bda82494b 180: onsuccess: #2116: 1: Success after basepoints/gcc-13-31 [...] discards c6942f8ba0 179: onsuccess: #2115: 1: Success after binutils/gcc: 2 commits discards 1e21633024 178: onsuccess: #2114: 1: Success after gdb-12-branchpoint-2 [...] discards 1d8f9e373c 177: onsuccess: #2113: 1: Success after gdb-12-branchpoint-2 [...] discards 1eeeed72c2 176: onsuccess: #2112: 1: Success after gcc: 2 commits discards 7e85681b06 175: onsuccess: #2111: 1: Success after binutils/gcc: 4 commits discards c1279d8cab 174: onsuccess: #2110: 1: Success after binutils/gcc: 16 commits discards 5d1e27fbf7 173: onsuccess: #2109: 1: Success after gcc: 17 commits discards 195094c139 172: onsuccess: #2108: 1: Success after binutils/gcc: 3 commits discards a1d199eb78 171: onsuccess: #2107: 1: Success after binutils/gcc: 7 commits discards 9921c8caa7 170: onsuccess: #2106: 1: Success after binutils/gcc: 8 commits discards ffe3f45229 169: onsuccess: #2105: 1: Success after binutils/gcc: 32 commits discards f2ee071b35 168: onsuccess: #2104: 1: Success after binutils/gcc: 7 commits discards 4dd26d71ba 167: onsuccess: #2103: 1: Success after binutils/gcc: 7 commits discards e822b8fd1d 166: onsuccess: #2102: 1: Success after gcc: 11 commits discards 1efe22fa08 165: onsuccess: #2101: 1: Success after binutils/gcc: 8 commits discards c7af97538a 164: onsuccess: #2100: 1: Success after binutils/gcc: 15 commits discards 7413a9538a 163: onsuccess: #2098: 1: Success after binutils/gcc: 18 commits discards ad5bf57e5f 162: onsuccess: #2097: 1: Success after binutils/gcc: 16 commits discards d1815f67d6 161: onsuccess: #2096: 1: Success after gcc: 2 commits discards b734079659 160: onsuccess: #2095: 1: Success after binutils/gcc: 4 commits discards 94199eea08 159: onsuccess: #2094: 1: Success after binutils/gcc: 23 commits discards 3db179e8ce 158: onsuccess: #2093: 1: Success after binutils/gcc: 9 commits discards fa9305f8e8 157: onsuccess: #2092: 1: Success after binutils/gcc: 3 commits discards 00a1b73118 156: onsuccess: #2091: 1: Success after binutils/gcc: 2 commits discards 137adfc86f 155: onsuccess: #2090: 1: Success after binutils/gcc: 22 commits discards 505293355e 154: onsuccess: #2089: 1: Success after gcc: 4 commits discards 2212a2b998 153: onsuccess: #2088: 1: Success after basepoints/gcc-13-30 [...] discards fb2031a7e0 152: onsuccess: #2087: 1: Success after gdb-12-branchpoint-2 [...] discards 01957db4bb 151: onsuccess: #2086: 1: Success after gcc: 2 commits discards c87e9aa566 150: onsuccess: #2085: 1: Success after gcc: 2 commits discards 082c8d4ac8 149: onsuccess: #2084: 1: Success after gcc: 16 commits new 14de39093a 149: onsuccess: #2084: 1: Success after gcc: 16 commits new 0ce90a7016 150: onsuccess: #2085: 1: Success after gcc: 2 commits new dc8cfabf26 151: onsuccess: #2086: 1: Success after gcc: 2 commits new 4b1b37517b 152: onsuccess: #2087: 1: Success after gdb-12-branchpoint-2 [...] new 0fb838e9dd 153: onsuccess: #2088: 1: Success after basepoints/gcc-13-30 [...] new 6e05460818 154: onsuccess: #2089: 1: Success after gcc: 4 commits new 75101a58ec 155: onsuccess: #2090: 1: Success after binutils/gcc: 22 commits new 3b9501fcb9 156: onsuccess: #2091: 1: Success after binutils/gcc: 2 commits new 315e5e2430 157: onsuccess: #2092: 1: Success after binutils/gcc: 3 commits new f9d77ec9f5 158: onsuccess: #2093: 1: Success after binutils/gcc: 9 commits new c3af3ef7a3 159: onsuccess: #2094: 1: Success after binutils/gcc: 23 commits new 3351ba261e 160: onsuccess: #2095: 1: Success after binutils/gcc: 4 commits new fcdf73f7f9 161: onsuccess: #2096: 1: Success after gcc: 2 commits new d49346589a 162: onsuccess: #2097: 1: Success after binutils/gcc: 16 commits new c14d6803b3 163: onsuccess: #2098: 1: Success after binutils/gcc: 18 commits new 9c6d5b635a 164: onsuccess: #2100: 1: Success after binutils/gcc: 15 commits new 4715554d8c 165: onsuccess: #2101: 1: Success after binutils/gcc: 8 commits new 6da7fa2ce0 166: onsuccess: #2102: 1: Success after gcc: 11 commits new 4fd4358e7f 167: onsuccess: #2103: 1: Success after binutils/gcc: 7 commits new 8d009ee482 168: onsuccess: #2104: 1: Success after binutils/gcc: 7 commits new 08929efb7d 169: onsuccess: #2105: 1: Success after binutils/gcc: 32 commits new 5617e6ac2e 170: onsuccess: #2106: 1: Success after binutils/gcc: 8 commits new 6a4fccb925 171: onsuccess: #2107: 1: Success after binutils/gcc: 7 commits new be4975cd26 172: onsuccess: #2108: 1: Success after binutils/gcc: 3 commits new 844198af29 173: onsuccess: #2109: 1: Success after gcc: 17 commits new b50fbec378 174: onsuccess: #2110: 1: Success after binutils/gcc: 16 commits new ea6552aba3 175: onsuccess: #2111: 1: Success after binutils/gcc: 4 commits new 908d8a9ff6 176: onsuccess: #2112: 1: Success after gcc: 2 commits new aeeeff95d0 177: onsuccess: #2113: 1: Success after gdb-12-branchpoint-2 [...] new 557ca933da 178: onsuccess: #2114: 1: Success after gdb-12-branchpoint-2 [...] new bbb920cc53 179: onsuccess: #2115: 1: Success after binutils/gcc: 2 commits new cdd5d04f3f 180: onsuccess: #2116: 1: Success after basepoints/gcc-13-31 [...] new 07b8f69857 181: onsuccess: #2117: 1: Success after gcc: 3 commits new 0f5bf6eb7a 182: onsuccess: #2118: 1: Success after gdb-12-branchpoint-2 [...] new 56f44b509b 183: onsuccess: #2119: 1: Success after binutils/gcc: 3 commits new 7a0e3a76f3 184: onsuccess: #2120: 1: Success after binutils/gcc: 22 commits new 6b43ec59f5 185: onsuccess: #2121: 1: Success after binutils/gcc: 18 commits new 93d86086bf 186: onsuccess: #2122: 1: Success after binutils/gcc: 8 commits new 9b9492ce1e 187: onsuccess: #2123: 1: Success after binutils/gcc: 4 commits new d069d45345 188: onsuccess: #2124: 1: Success after binutils/gcc: 26 commits new 5ebf06e28c 189: onsuccess: #2125: 1: Success after binutils/gcc: 23 commits new 094e70a60e 190: onsuccess: #2126: 1: Success after binutils/gcc: 8 commits new 7493d43553 191: onsuccess: #2127: 1: Success after binutils/gcc: 3 commits new 266ae28c16 192: onsuccess: #2128: 1: Success after binutils/gcc: 11 commits new a2422a9259 193: onsuccess: #2129: 1: Success after binutils/gcc: 20 commits new 77b12ef8ad 194: onsuccess: #2130: 1: Success after binutils/gcc: 7 commits new a81d6465e2 195: onsuccess: #2131: 1: Success after gcc: 2 commits new ff403afbd9 196: onsuccess: #2132: 1: Success after binutils/gcc: 7 commits new 05b6d2f6a2 197: onsuccess: #2133: 1: Success after gcc: 12 commits new a2c5b2d493 198: onsuccess: #2134: 1: Success after binutils/gcc: 7 commits new 1f80143eb5 199: onsuccess: #2136: 1: Success after binutils/gcc: 31 commits new 0378a4258f 200: onsuccess: #2137: 1: Success after binutils/gcc: 15 commits new 625a873132 201: onsuccess: #2138: 1: Success after binutils/gcc: 7 commits new 0cafd23af9 202: onsuccess: #2139: 1: Success after gdb-12-branchpoint-2 [...] new e07dc70f16 203: onsuccess: #2140: 1: Success after binutils/gcc: 4 commits new 8f2e8086c2 204: onsuccess: #2141: 1: Success after binutils/gcc: 4 commits new a9c729b3cc 205: onsuccess: #2142: 1: Success after binutils/gcc: 4 commits new a131ca459e 206: onsuccess: #2143: 1: Success after gdb-12-branchpoint-2 [...] new 57b15da383 207: onsuccess: #2144: 1: Success after gcc: 3 commits new 8520fb8b1a 208: onsuccess: #2145: 1: Success after binutils/gcc: 14 commits new ccb4b2b136 209: onsuccess: #2146: 1: Success after binutils/gcc: 17 commits new 8214dad54d 210: onsuccess: #2147: 1: Success after binutils/gcc: 11 commits new 804ef94d9b 211: onsuccess: #2148: 1: Success after gcc: 3 commits new d7aad31fae 212: onsuccess: #2149: 1: Success after binutils/gcc: 10 commits new af188fbdb1 213: onsuccess: #2150: 1: Success after binutils/gcc: 29 commits new 72dc5c7cff 214: onsuccess: #2151: 1: Success after binutils/gcc: 2 commits new 54c6e4b5af 215: onsuccess: #2152: 1: Success after binutils/gcc: 2 commits new aa35be6542 216: onsuccess: #2153: 1: Success after binutils/gcc: 18 commits new 86f687890c 217: onsuccess: #2154: 1: Success after binutils/gcc: 19 commits new 56e755f428 218: onsuccess: #2155: 1: Success after binutils/gcc: 9 commits new 1a4a638f23 219: onsuccess: #2156: 1: Success after binutils/gcc: 7 commits new c134d6ea4b 220: onsuccess: #2157: 1: Success after binutils/gcc: 18 commits new f1678fab3f 221: onsuccess: #2158: 1: Success after binutils/gcc: 15 commits new 250d864c41 222: onsuccess: #2159: 1: Success after binutils/gcc: 7 commits new 7641981e30 223: onsuccess: #2160: 1: Success after binutils/gcc: 7 commits new 9c451dfe14 224: onsuccess: #2161: 1: Success after binutils/gcc: 19 commits new 7c365531be 225: onsuccess: #2162: 1: Success after binutils/gcc: 7 commits new 5fd5457013 226: onsuccess: #2163: 1: Success after binutils/gcc: 5 commits new 630581bd2f 227: onsuccess: #2164: 1: Success after binutils/gcc: 2 commits new 0c45c19cf6 228: onsuccess: #2165: 1: Success after basepoints/gcc-13-34 [...] new e9fc6dd81b 229: onsuccess: #2166: 1: Success after basepoints/gcc-13-34 [...] new 32c97e846b 230: onsuccess: #2167: 1: Success after binutils/gcc: 2 commits new f79dac9ea5 231: onsuccess: #2168: 1: Success after gcc: 2 commits new d5a00e6d36 232: onsuccess: #2169: 1: Success after binutils: 4 commits new 6036188c77 233: onsuccess: #2170: 1: Success after gcc: 5 commits new 79457e2695 234: onsuccess: #2171: 1: Success after binutils/gcc: 11 commits new bc2fca6834 235: onsuccess: #2172: 1: Success after binutils/gcc: 16 commits new 38df700b79 236: onsuccess: #2173: 1: Success after binutils/gcc: 9 commits new bce1243ae1 237: onsuccess: #2174: 1: Success after binutils/gcc: 8 commits new 792cd5431f 238: onsuccess: #2175: 1: Success after binutils/gcc: 14 commits new a31feca608 239: onsuccess: #2176: 1: Success after binutils/gcc: 8 commits new 453cdc4f1f 240: onsuccess: #2177: 1: Success after binutils/gcc: 6 commits new 69395a733e 241: onsuccess: #2178: 1: Success after binutils/gcc: 7 commits new 9e733d730d 242: onsuccess: #2179: 1: Success after binutils/gcc: 16 commits new abe0fdebfd 243: onsuccess: #2180: 1: Success after binutils/gcc: 4 commits new 9b4cdaa3e7 244: onsuccess: #2181: 1: Success after binutils/gcc: 7 commits new d04035caf3 245: onsuccess: #2182: 1: Success after binutils/gcc: 6 commits new 810db2aab3 246: onsuccess: #2183: 1: Success after binutils/gcc: 8 commits new 79bb341d35 247: onsuccess: #2184: 1: Success after binutils/gcc: 7 commits new 0e7bd49d5d 248: onsuccess: #2185: 1: Success after binutils/gcc: 7 commits new fa9e45057e 249: onsuccess: #2186: 1: Success after binutils/gcc: 7 commits new 7d17afac69 250: onsuccess: #2187: 1: Success after binutils/gcc: 10 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (806f2ff9a8) \ 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 1688 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 37824 -> 38404 bytes 04-build_abe-gcc/console.log.xz | Bin 213460 -> 213412 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3852 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2736 -> 2988 bytes 07-check_regression/console.log.xz | Bin 5876 -> 6608 bytes 07-check_regression/extra-bisect-params | 1 - 07-check_regression/fails.sum | 7 - 07-check_regression/mail-body.txt | 48 +- 07-check_regression/results.compare | 35 +- 07-check_regression/results.compare2 | 462 ++- 07-check_regression/results.regressions | 41 - 08-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 | 50 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 41 - sumfiles/g++.log.xz | Bin 3585004 -> 3573088 bytes sumfiles/g++.sum | 208 +- sumfiles/gcc.log.xz | Bin 3136460 -> 3108928 bytes sumfiles/gcc.sum | 4805 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1050692 -> 1047832 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2192 -> 2184 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 209228 -> 209688 bytes sumfiles/libgomp.sum | 228 +- sumfiles/libitm.log.xz | Bin 2540 -> 2540 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 455352 -> 450048 bytes sumfiles/libstdc++.sum | 12 +- 36 files changed, 3084 insertions(+), 2972 deletions(-) delete mode 100644 07-check_regression/extra-bisect-params delete mode 100644 07-check_regression/fails.sum delete mode 100644 07-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[binutils-gdb] branch master updated (615d4f41337 -> 3190ebcbbf8)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from 615d4f41337 RISC-V: Fix build failure for -Werror=maybe-uninitialized new 3190ebcbbf8 RISC-V/gas: fix build with certain gcc versions 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: gas/config/tc-riscv.c | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits October 2022