This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk/gnu-release-aarch64-spec2k6-Os_LTO
in repository toolchain/ci/base-artifacts.
discards 32eeb4243 gcc-df377fc48e3c95a674486243dfe08121ee67d1e0: 0
new 8c03df0f2 binutils-595d73421b2f56d343c8e0f32cef8c073f3dad70: 0
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 (32eeb4243)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk/gnu-release-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 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 | 6 +-
2-prepare_abe/console.log | 4 +-
3-build_abe-binutils/console.log | 3814 +++---
4-build_abe-stage1/console.log | 3908 +++---
5-build_abe-linux/console.log | 39 +-
6-build_abe-glibc/console.log | 1796 ++-
7-build_abe-stage2/console.log | 15093 ++++++++++++-----------
8-benchmark/console.log | 26 +-
console.log | 24416 ++++++++++++++++++-------------------
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
results_id | 2 +-
12 files changed, 24550 insertions(+), 24566 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 2ae44fa6148 2019-01-25 Steven G. Kargl <kargl(a)gcc.gnu.org>
new 837ddebd5ae /cp 2019-01-25 Paolo Carlini <paolo.carlini(a)oracle.com>
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/cp/ChangeLog | 7 +++++++
gcc/cp/call.c | 13 +++++++++++++
gcc/cp/decl2.c | 6 +++---
gcc/testsuite/ChangeLog | 6 ++++++
gcc/testsuite/g++.dg/cpp2a/destroying-delete2.C | 20 ++++++++++++++++++++
gcc/testsuite/g++.dg/cpp2a/destroying-delete3.C | 8 ++++++++
6 files changed, 57 insertions(+), 3 deletions(-)
create mode 100644 gcc/testsuite/g++.dg/cpp2a/destroying-delete2.C
create mode 100644 gcc/testsuite/g++.dg/cpp2a/destroying-delete3.C
--
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-arm-mainline-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 12f7ed529 linux-30bac164aca750892b93eef350439a0562a68647: all
new 7630a10a3 binutils-e10620d3b96a725c4752198cb3c7c00ea21b42b4: 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 (12f7ed529)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-arm-ma [...]
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 | 70 +-
2-prepare_abe/console.log | 26 +-
3-build_abe-binutils/console.log | 6225 ++++-----
4-build_abe-stage1/console.log | 12815 +++++++++---------
5-count_linux_objs/console.log | 7341 +++++------
6-check_regression/console.log | 2 +-
7-update_baseline/console.log | 4 +-
console.log | 26367 ++++++++++++++++++-------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 12 +-
trigger-bisect-on-failure | 6 +-
12 files changed, 26431 insertions(+), 26441 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-release-arm-mainline-allyesconfig
in repository toolchain/ci/base-artifacts.
discards be969dd58 linux-cffd425b90147296c627dfb13f7ea8f361d962b2: 17392
new 5cc1f9429 llvm-e25507d4378c85983ec4f55d9f2a606864752950: 17392
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 (be969dd58)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-release-arm- [...]
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-build_llvm/console.log | 10269 ++++++++++++++++++------------------
3-count_linux_objs/console.log | 736 ++-
4-check_regression/console.log | 2 +-
5-update_baseline/console.log | 4 +-
console.log | 11137 +++++++++++++++++++--------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 12 +-
trigger-bisect-on-failure | 6 +-
10 files changed, 11116 insertions(+), 11126 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-mainline-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 4ce5da5a3 llvm-3b9a82ff2c798aff3eb48ab1220447bfd2d013e0: all
new b95eb3057 linux-d73aba1115cf40630cc8b4b7aed049ed8117b458: 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 (4ce5da5a3)
\
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:
1-reset_artifacts/console.log | 14 +-
2-build_llvm/console.log | 9005 +++++++++++++++++++-------------------
3-count_linux_objs/console.log | 189 +-
console.log | 9246 ++++++++++++++++++++--------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 12 +-
trigger-bisect-on-failure | 6 +-
8 files changed, 9162 insertions(+), 9314 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_bmk/gnu-master-arm-spec2k6-Os
in repository toolchain/ci/gcc.
at 3e8e17778ee Fix Xiong's changelogs a bit
No new revisions were added by this update.
--
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_bmk/gnu-master-arm-spec2k6-Os
in repository toolchain/ci/base-artifacts.
discards 41636f458 binutils-e10620d3b96a725c4752198cb3c7c00ea21b42b4: 0
new 9826739d2 gcc-3e8e17778eebc4f739b368b71548f6437f95e2b0: 0
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 (41636f458)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk/gnu-master-arm-spec2 [...]
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 | 6 +-
2-prepare_abe/console.log | 4 +-
3-build_abe-binutils/console.log | 3453 +++--
4-build_abe-stage1/console.log | 4988 ++++----
5-build_abe-linux/console.log | 44 +-
6-build_abe-glibc/console.log | 2492 ++--
7-build_abe-stage2/console.log | 13960 +++++++++++----------
8-benchmark/console.log | 39 +-
console.log | 24916 ++++++++++++++++++-------------------
jenkins/build-name | 2 +-
jenkins/manifest.sh | 12 +-
results_id | 2 +-
12 files changed, 24907 insertions(+), 25011 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 release_80
in repository llvm.
from 9ff1abe5edc Merging r352034: ------------------------------------------ [...]
new 29eefd25394 Merging r352204: ------------------------------------------ [...]
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:
include/llvm/Support/JSON.h | 1 +
lib/Support/JSON.cpp | 6 ++++++
2 files changed, 7 insertions(+)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.