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-stable-defconfig
in repository toolchain/ci/base-artifacts.
from 493d08fe 0: update: linux-d6591ea2dd1a44b1c72c5a3e3b6555d7585acdae: boot
new 1e8248ea 1: reset: llvm-aadb635e04854220064b77cc10d0e6772f5492fd: 5525
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 | 190 +-
02-build_llvm/console.log | 12554 +++++++++++++++----------------
03-build_linux/console.log | 783 +-
04-boot_linux/console.log | 226 -
05-check_regression/console.log | 93 +-
05-check_regression/trigger-bisect | 3 +
06-update_baseline/console.log | 53 +-
console.log | 13899 +++++++++++++++++------------------
jenkins/manifest.sh | 10 +-
reset-baseline | 0
results | 6 +-
11 files changed, 13761 insertions(+), 14056 deletions(-)
delete mode 100644 04-boot_linux/console.log
create mode 100644 05-check_regression/trigger-bisect
create mode 100644 reset-baseline
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
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-release-aarch64-lts-allyesconfig
in repository toolchain/ci/base-artifacts.
discards f9f88cd1 10: update: llvm-linux: 16048
new 6721a152 10: update: llvm-linux: 16048
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 (f9f88cd1)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-release-aarc [...]
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 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 | 231 +-
02-build_llvm/console.log | 12614 ++++++++++++------------
03-build_linux/console.log | 6882 +++++++------
05-check_regression/console.log | 10 +-
06-update_baseline/console.log | 64 +-
console.log | 19801 +++++++++++++++++++-------------------
jenkins/manifest.sh | 8 +-
7 files changed, 19794 insertions(+), 19816 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
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-lts-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 2b5ee3a1 13: update: llvm-e83b7b99da2e0385c567cd3883cad66fb5ce271c: 16047
discards 0ea1e0f3 12: reset: llvm-aadb635e04854220064b77cc10d0e6772f5492fd: 16047
discards 9d39f638 11: update: linux-357668399cf70ccdc0ee8967bff3448d0f4f9ae1: 16048
new 89a0da62 11: update: llvm-linux: 16048
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 (2b5ee3a1)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-aarch [...]
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 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 | 220 +-
02-build_llvm/console.log | 12751 +++++++++++++------------
03-build_linux/console.log | 6039 +++++++-----
05-check_regression/console.log | 18 +-
06-update_baseline/console.log | 110 +-
console.log | 19138 ++++++++++++++++++++------------------
jenkins/manifest.sh | 11 +-
results | 2 +-
8 files changed, 20095 insertions(+), 18194 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu/gnu-release-arm-bootstrap_ubsan
in repository toolchain/ci/base-artifacts.
discards 4053c578 0: update: gcc-f1ee6f0fe443129448fc90c42aaafc869a9f636f: 1
new 8291a0f9 0: update: gcc-541431facd4b1fa22b14ad2e6bc7c033bb833fd4: 1
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 (4053c578)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu/gnu-release-arm-boot [...]
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 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 | 130 +-
02-prepare_abe/console.log | 406 +-
03-build_abe-bootstrap_ubsan/console.log | 92101 ++++++++++++++--------------
05-check_regression/console.log | 4 +-
06-update_baseline/console.log | 10 +-
console.log | 92651 +++++++++++++++--------------
jenkins/manifest.sh | 10 +-
7 files changed, 92663 insertions(+), 92649 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
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 d27b8e5f146 Remove dwarf_expr_baton
new aeefc73cb23 Print more information in arm_dump_tdep
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:
gdb/ChangeLog | 4 ++++
gdb/arm-tdep.c | 14 ++++++++++++++
2 files changed, 18 insertions(+)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch master
in repository gcc.
from 985873e5087 Combine the two H8 mode shortening peepholes into a single [...]
new bc7ac0a2da2 Commit correct version of last patch
new 1cd9bef89ef testsuite: Fix up gcc.target/powerpc/pr93122.c test
new 68bb7e3b9dc coroutines: Update to n4849 allocation/deallocation.
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
gcc/config/h8300/h8300.md | 2 +-
gcc/cp/ChangeLog | 7 +
gcc/cp/coroutines.cc | 248 ++++++++++++++-------
gcc/testsuite/ChangeLog | 16 ++
.../coroutines/coro-bad-alloc-00-bad-op-new.C | 12 +
.../coroutines/coro-bad-alloc-01-bad-op-del.C | 13 ++
.../coroutines/coro-bad-alloc-02-no-op-new-nt.C | 15 ++
gcc/testsuite/g++.dg/coroutines/coro1-allocators.h | 184 +++++++++++++++
.../torture/alloc-00-gro-on-alloc-fail.C | 98 +-------
.../coroutines/torture/alloc-01-overload-newdel.C | 81 +------
.../torture/alloc-02-fail-new-grooaf-check.C | 41 ++++
.../coroutines/torture/alloc-03-overload-new-1.C | 55 +++++
.../torture/alloc-04-overload-del-use-two-args.C | 60 +++++
gcc/testsuite/gcc.target/powerpc/pr93122.c | 2 +-
14 files changed, 592 insertions(+), 242 deletions(-)
create mode 100644 gcc/testsuite/g++.dg/coroutines/coro-bad-alloc-00-bad-op-new.C
create mode 100644 gcc/testsuite/g++.dg/coroutines/coro-bad-alloc-01-bad-op-del.C
create mode 100644 gcc/testsuite/g++.dg/coroutines/coro-bad-alloc-02-no-op-new-nt.C
create mode 100644 gcc/testsuite/g++.dg/coroutines/coro1-allocators.h
create mode 100644 gcc/testsuite/g++.dg/coroutines/torture/alloc-02-fail-new-grooa [...]
create mode 100644 gcc/testsuite/g++.dg/coroutines/torture/alloc-03-overload-new-1.C
create mode 100644 gcc/testsuite/g++.dg/coroutines/torture/alloc-04-overload-del-u [...]
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.