This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-arm-next-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 478f47716a 0: last-good: binutils-gcc-linux: all
new 5be369ebc2 0: last-good: binutils-gcc-linux: all
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 (478f47716a)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-arm-n [...]
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:
3-build_abe-binutils/console.log | 3164 ++++++++---------
4-build_abe-stage1/console.log | 3675 ++++++++++----------
5-count_linux_objs/console.log | 92 +-
console.log | 7013 +++++++++++++++++++-------------------
jenkins/manifest.sh | 12 +-
5 files changed, 6913 insertions(+), 7043 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/gnu-release-arm-mainline-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 67e4f658c6 0: last-good: binutils-gcc-linux: all
new 9315304416 0: last-good: binutils-gcc-linux: all
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 (67e4f658c6)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-arm-m [...]
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:
2-prepare_abe/console.log | 4 +-
3-build_abe-binutils/console.log | 3248 ++++++++---------
4-build_abe-stage1/console.log | 3933 ++++++++++----------
5-count_linux_objs/console.log | 60 +-
console.log | 7487 +++++++++++++++++++-------------------
jenkins/manifest.sh | 12 +-
6 files changed, 7325 insertions(+), 7419 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/gnu-release-aarch64-mainline-defconfig
in repository toolchain/ci/base-artifacts.
discards ad7b75ab98 0: last-good: binutils-gcc-linux: all
new e053a0a909 0: last-good: binutils-gcc-linux: all
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 (ad7b75ab98)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-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:
2-prepare_abe/console.log | 4 +-
3-build_abe-binutils/console.log | 4082 +++++++++--------
4-build_abe-stage1/console.log | 5160 +++++++++++----------
5-count_linux_objs/console.log | 74 +-
console.log | 9342 ++++++++++++++++++++------------------
jenkins/manifest.sh | 12 +-
6 files changed, 9915 insertions(+), 8759 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 gcc.
from 88af6fa9fec * g++.dg/asan/asan_oob_test.cc: Skip OOB_int on SPARC. * [...]
new 9a8c5dc032f compiler,runtime: use __builtin_dwarf_cfa for getcallersp
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/go/ChangeLog | 5 +++++
gcc/go/go-gcc.cc | 5 +++--
gcc/go/gofrontend/MERGE | 2 +-
gcc/go/gofrontend/expressions.cc | 24 ++++++++++++++----------
gcc/go/gofrontend/expressions.h | 2 +-
gcc/go/gofrontend/gogo.cc | 13 ++++++++-----
gcc/go/gofrontend/gogo.h | 4 ++--
libgo/runtime/runtime.h | 2 +-
8 files changed, 35 insertions(+), 22 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.