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-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 5c8c36fb08 linux-cd984a5be21549273a3f13b52a8b7b84097b32a7: 17392
new 881c5c39b6 llvm-365e164fcc48ad72deb962937f05efe648c91803: 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 (5c8c36fb08)
\
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 | 70 +-
2-build_llvm/console.log | 10254 ++++++++++++++++++-------------------
3-count_linux_objs/console.log | 442 +-
4-check_regression/console.log | 2 +-
5-update_baseline/console.log | 4 +-
console.log | 10772 ++++++++++++++++++++-------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
10 files changed, 10836 insertions(+), 10728 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-release-aarch64-spec2k6-Os_LTO
in repository toolchain/ci/gcc.
from 6142f179ac2 Daily bump.
adds ac10c36db17 2019-02-02 Thomas Koenig <tkoenig(a)gcc.gnu.org>
adds 4e135b8a968 2019-02-02 Thomas Koenig <tkoenig(a)gcc.gnu.org>
new b881d66b4e1 Daily bump.
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/DATESTAMP | 2 +-
gcc/fortran/ChangeLog | 17 +++++++++++
gcc/fortran/arith.c | 2 +-
gcc/fortran/gfortran.h | 3 ++
gcc/fortran/interface.c | 9 ++++++
gcc/fortran/intrinsic.c | 2 ++
gcc/testsuite/ChangeLog | 9 +++++-
gcc/testsuite/gfortran.dg/c_funptr_1.f90 | 38 ++++++++++++++++++++++++
gcc/testsuite/gfortran.dg/c_funptr_1_mod.f90 | 16 ++++++++++
gcc/testsuite/gfortran.dg/warn_conversion_10.f90 | 8 +++++
10 files changed, 103 insertions(+), 3 deletions(-)
create mode 100644 gcc/testsuite/gfortran.dg/c_funptr_1.f90
create mode 100644 gcc/testsuite/gfortran.dg/c_funptr_1_mod.f90
create mode 100644 gcc/testsuite/gfortran.dg/warn_conversion_10.f90
--
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-release-aarch64-spec2k6-Os_LTO
in repository toolchain/ci/base-artifacts.
discards 8eeaf6d3b2 glibc-d09b11cbe57c6434813ead18ff128012230bb614: 0
new 4ff23a76ae gcc-b881d66b4e1312f6232fd44e01be41f5c0f77cff: 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 (8eeaf6d3b2)
\
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:
01-reset_artifacts/console.log | 13 +-
03-build_abe-binutils/console.log | 3208 +++---
04-build_abe-stage1/console.log | 3486 +++----
05-build_abe-linux/console.log | 16 +-
06-build_abe-glibc/console.log | 1457 ++-
07-build_abe-stage2/console.log | 10929 ++++++++++-----------
08-benchmark/console.log | 28 +-
09-check_regression/console.log | 26 +-
10-update_baseline/console.log | 26 +-
console.log | 19019 ++++++++++++++++++------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 16 +-
results.csv | 223 +-
results_id | 2 +-
trigger-bisect-on-failure | 6 +-
16 files changed, 19181 insertions(+), 19278 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 clang.
from 889a989a08 Fix handling of usual deallocation functions in various conf [...]
new 57b4f8bee6 Correct test my *really really* overaligning a type.
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:
test/SemaCXX/extended-usual-deallocation-functions.cpp | 4 ++--
1 file changed, 2 insertions(+), 2 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-next-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 9036f03707 gcc-f1329be60594951fb30fe859c6f0a86587b36bbd: all
new 8326225717 linux-dc4c899977350728714d44b6e0d39673f6a97281: 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 (9036f03707)
\
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 | 14 +-
2-prepare_abe/console.log | 4 +-
3-build_abe-binutils/console.log | 3773 +++--
4-build_abe-stage1/console.log | 4635 ++++---
5-count_linux_objs/console.log | 18602 ++++++++++++-------------
console.log | 27290 ++++++++++++++++++-------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
10 files changed, 27145 insertions(+), 27193 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-stable-defconfig
in repository toolchain/ci/base-artifacts.
discards 7aee0b04c4 llvm-a50489754a60000887c13a04b85c772e867e807a: all
new 643fde69e6 llvm-b21ed3c57aaa100a8fce29527bf20221ea208e54: 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 (7aee0b04c4)
\
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 | 74 +-
2-build_llvm/console.log | 10258 +++++++++++++++++++-------------------
3-count_linux_objs/console.log | 149 +-
4-check_regression/console.log | 2 +-
5-update_baseline/console.log | 4 +-
console.log | 10487 +++++++++++++++++++--------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 8 +-
trigger-bisect-on-failure | 4 +-
10 files changed, 10400 insertions(+), 10590 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 llvm.
from 505cfd572ae [InstSimplify] Missed optimization in math expression: log1 [...]
new 31b117619fe [AMDGPU] Fix -Wunused-variable after rL352978
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:
lib/Target/AMDGPU/AMDGPULegalizerInfo.cpp | 1 -
1 file changed, 1 deletion(-)
--
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-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 556898bf70 llvm-a50489754a60000887c13a04b85c772e867e807a: all
new 3f93903f1b llvm-b21ed3c57aaa100a8fce29527bf20221ea208e54: 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 (556898bf70)
\
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:
2-build_llvm/console.log | 10267 +++++++++++++++++++-------------------
3-count_linux_objs/console.log | 148 +-
4-check_regression/console.log | 2 +-
5-update_baseline/console.log | 4 +-
console.log | 10489 +++++++++++++++++++--------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 8 +-
trigger-bisect-on-failure | 4 +-
9 files changed, 10346 insertions(+), 10580 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.