This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-mainline-allyesconfig
in repository toolchain/gcc.
from 1f957e932eb 2018-12-29 Steven G. Kargl <kargl(a)gcc.gnu.org>
adds 369f42ad110 2018-12-29 Dominique d'Humieres <dominiq(a)gcc.gnu.org>
adds e2b3337085b * Makefile.am (xcoff_%.c): Use an actual newline instead o [...]
adds 1e89324e901 Daily bump.
adds f06e155896b Use dg-additional-options instead of dg-options
No new revisions were added by this update.
Summary of changes:
gcc/DATESTAMP | 2 +-
gcc/testsuite/ChangeLog | 10 ++++++++++
gcc/testsuite/g++.dg/abi/key2.C | 2 +-
gcc/testsuite/gfortran.dg/ieee/ieee_10.f90 | 5 ++++-
libbacktrace/ChangeLog | 6 ++++++
libbacktrace/Makefile.am | 3 ++-
libbacktrace/Makefile.in | 3 ++-
7 files changed, 26 insertions(+), 5 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-master-aarch64-mainline-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 8ee5d75e4 linux-195303136f192d37b89e20a8d1d2670d0d825266: all
new 7d654c7b7 gcc-f06e155896bc05df0186f7c5f1a689bbdd15a960: 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 (8ee5d75e4)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-aarch6 [...]
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:
1-reset_artifacts/console.log | 72 +-
2-prepare_abe/console.log | 4 +-
3-build_abe-binutils/console.log | 3678 ++---
4-build_abe-stage1/console.log | 5023 +++---
5-count_linux_objs/console.log | 20918 ++++++++++++------------
console.log | 31453 +++++++++++++++++++------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
10 files changed, 30709 insertions(+), 30459 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-arm-mainline-defconfig
in repository toolchain/ci/base-artifacts.
discards 2087033d3 linux-195303136f192d37b89e20a8d1d2670d0d825266: all
new a15e42bfb llvm-8bc6a184a031941c4e93f0baa9298dd89133c7bb: 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 (2087033d3)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-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:
1-reset_artifacts/console.log | 60 +-
2-build_llvm/console.log | 9365 ++++++++++++++++++++--------------------
3-count_linux_objs/console.log | 195 +-
console.log | 9300 +++++++++++++++++++--------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 8 +-
trigger-bisect-on-failure | 6 +-
8 files changed, 9579 insertions(+), 9359 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-lts-defconfig
in repository toolchain/ci/base-artifacts.
discards 314ab2576 binutils-ab937fbf067895b519dc717e5dd6643b00e90524: all
new 462d083c1 gcc-60ed4c6993faa7226752f3dcc2cf59ea54e18d30: 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 (314ab2576)
\
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:
1-reset_artifacts/console.log | 56 +-
2-prepare_abe/console.log | 4 +-
3-build_abe-binutils/console.log | 3730 ++++++++--------
4-build_abe-stage1/console.log | 4874 ++++++++++-----------
5-count_linux_objs/console.log | 105 +-
console.log | 8807 +++++++++++++++++++-------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
10 files changed, 8741 insertions(+), 8855 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-arm-mainline-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 656fc2aca linux-195303136f192d37b89e20a8d1d2670d0d825266: all
new f42d5b24b llvm-8bc6a184a031941c4e93f0baa9298dd89133c7bb: 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 (656fc2aca)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-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:
1-reset_artifacts/console.log | 54 +-
2-build_llvm/console.log | 10208 +++++++++++++++++++-------------------
3-count_linux_objs/console.log | 137 +-
4-check_regression/console.log | 2 +-
5-update_baseline/console.log | 4 +-
console.log | 10405 +++++++++++++++++++--------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 8 +-
trigger-bisect-on-failure | 6 +-
10 files changed, 10407 insertions(+), 10421 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-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 6a6f6b8d9 linux-195303136f192d37b89e20a8d1d2670d0d825266: all
new 7a5db94c5 gcc-60ed4c6993faa7226752f3dcc2cf59ea54e18d30: 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 (6a6f6b8d9)
\
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:
1-reset_artifacts/console.log | 158 +-
2-prepare_abe/console.log | 22 +-
3-build_abe-binutils/console.log | 6399 ++++++++--------
4-build_abe-stage1/console.log | 8567 ++++++++++-----------
5-count_linux_objs/console.log | 150 +-
6-check_regression/console.log | 2 +-
7-update_baseline/console.log | 4 +-
console.log | 15256 ++++++++++++++++++-------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
12 files changed, 15189 insertions(+), 15389 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.