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-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 1a9d7bc 0: update: llvm-linux: boot
new 5042ae3 0: update: llvm-linux: boot
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 (1a9d7bc)
\
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 | 134 +-
02-build_llvm/console.log | 11906 ++++++++++++++++++------------------
03-build_linux/console.log | 708 +--
console.log | 12748 ++++++++++++++++++++-------------------
jenkins/manifest.sh | 8 +-
5 files changed, 12764 insertions(+), 12740 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 99f895334e4 [X86] EltsFromConsecutiveLoads - store Loads on a per-eleme [...]
new 14148404db0 [DAGCombine] visitINSERT_SUBVECTOR - use uint64_t subvector [...]
new d85c02f496e [X86] EltsFromConsecutiveLoads - LDBase is non-null. NFCI.
new f45090ffa8f [NFC][ARM] Convert lambdas to static helpers
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:
lib/CodeGen/SelectionDAG/DAGCombiner.cpp | 2 +-
lib/Target/ARM/ARMLowOverheadLoops.cpp | 130 +++++++++++++++++--------------
lib/Target/X86/X86ISelLowering.cpp | 10 +--
3 files changed, 78 insertions(+), 64 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-stable-allyesconfig
in repository toolchain/ci/llvm-project.
from 180a937d9a6 Merging r354633:
adds 635f8ffdbd7 Revert merge of r360861:
adds 19a71f6bdf2 Merging r360861, with an additional change to also add the [...]
No new revisions were added by this update.
Summary of changes:
libunwind/src/assembly.h | 4 +++-
1 file changed, 3 insertions(+), 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-release-arm-stable-allyesconfig
in repository toolchain/ci/base-artifacts.
discards f1a61d0 2: update: llvm-linux: 17398
new 7019e45 2: update: llvm-linux: 17398
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 (f1a61d0)
\
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:
01-reset_artifacts/console.log | 220 +-
02-build_llvm/console.log | 11528 ++++++++++++++---------------
03-build_linux/console.log | 3188 ++++----
05-check_regression/console.log | 6 +-
06-update_baseline/console.log | 20 +-
console.log | 14962 +++++++++++++++++++-------------------
jenkins/manifest.sh | 8 +-
7 files changed, 14968 insertions(+), 14964 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-aarch64-spec2k6-O2_LTO
in repository toolchain/ci/base-artifacts.
discards 18a632f 0: init: binutils-gcc-glibc: -5
new 218f3ef 0: update: gcc-dddb1553ce6bddfda82e5c2db5f909c3a8397afd: -5
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 (18a632f)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk/gnu-master-aarch64-s [...]
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 | 177 +-
02-prepare_abe/console.log | 424 +-
03-build_abe-binutils/console.log | 10796 ++--
04-build_abe-stage1/console.log | 15583 +++--
05-build_abe-linux/console.log | 196 +-
06-build_abe-glibc/console.log | 39798 +++++++------
07-build_abe-stage2/console.log | 40810 +++++++------
08-benchmark/benchmark-start.log | 2 +-
08-benchmark/benchmark.log | 21 +-
08-benchmark/console.log | 144 +-
09-check_regression/console.log | 18 +-
10-update_baseline/console.log | 10 +-
console.log | 107962 +++++++++++++++++------------------
jenkins/manifest.sh | 18 +-
14 files changed, 107247 insertions(+), 108712 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-master-arm-bootstrap_ubsan
in repository toolchain/ci/base-artifacts.
discards f91a75f 0: update: gcc-4eeba3bf0ba6e8afc34fc26bf592d240884bedfe: -5
new 1f00b9e 0: update: gcc-32b9937758c49d1a0da96f593f332f35886eff4a: -5
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 (f91a75f)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu/gnu-master-arm-boots [...]
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 | 76 +-
02-prepare_abe/console.log | 434 +-
03-build_abe-bootstrap_ubsan/console.log | 93326 ++++++++++++++--------------
console.log | 93836 ++++++++++++++---------------
jenkins/manifest.sh | 8 +-
5 files changed, 93840 insertions(+), 93840 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/base-artifacts.
from 28adf6e 0: update: binutils-gcc-glibc: -5
new 7de84d0 1: reset: binutils-7e56c51c7932cfdb178e9457011d09d53e98937b: -6
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 | 194 +-
02-prepare_abe/console.log | 254 +-
03-build_abe-binutils/console.log | 10094 ++--
04-build_abe-stage1/console.log | 19789 ++++---
05-build_abe-linux/console.log | 276 +-
06-build_abe-glibc/console.log | 38887 +++++++------
07-build_abe-stage2/console.log | 39170 +++++--------
08-benchmark/benchmark-start.log | 1 -
08-benchmark/benchmark.log | 51 -
08-benchmark/console.log | 255 -
09-check_regression/console.log | 18 +-
10-update_baseline/console.log | 22 +-
console.log | 108975 ++++++++++++++++-------------------
jenkins/manifest.sh | 14 +-
reset-baseline | 0
results | 2 -
16 files changed, 100757 insertions(+), 117245 deletions(-)
delete mode 100644 08-benchmark/benchmark-start.log
delete mode 100644 08-benchmark/benchmark.log
delete mode 100644 08-benchmark/console.log
create mode 100644 reset-baseline
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.