This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk/llvm-release-arm-spec2k6-Os
in repository toolchain/ci/base-artifacts.
discards 1c613d0 0: update: binutils-gcc-glibc-llvm: 0
new fb0d9f2 0: update: binutils-gcc-glibc-llvm: 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 (1c613d0)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk/llvm-release-arm-spe [...]
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 | 130 +-
02-prepare_abe/console.log | 408 +-
03-build_abe-binutils/console.log | 10668 +-
.../console.log | 17499 ++-
05-build_abe-linux/console.log | 294 +-
06-build_abe-glibc/console.log | 37563 ++---
.../console.log | 46292 +++---
08-build_llvm-true/console.log | 11728 +-
09-benchmark/benchmark-start.log | 2 +-
09-benchmark/benchmark.log | 20 +-
09-benchmark/console.log | 134 +-
10-check_regression/console.log | 5401 +-
10-check_regression/results.log | 4217 +
11-update_baseline/console.log | 5411 +-
11-update_baseline/results.log | 4217 +
console.log | 135454 +++++++++---------
jenkins/manifest.sh | 12 +-
results-0.csv | 1228 +
results-1.csv | 1232 +
results-full.csv | 2422 +-
results.csv | 170 +-
results_id | 2 +-
22 files changed, 140052 insertions(+), 144452 deletions(-)
create mode 100644 10-check_regression/results.log
create mode 100644 11-update_baseline/results.log
create mode 100644 results-0.csv
create mode 100644 results-1.csv
--
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/llvm-project.
from 8972a4776da ReleaseNotes: known issue: PR40547
adds 12f174e98c3 Merging r371969: ------------------------------------------ [...]
adds 0399d5a9682 Add external project LDC to release notes.
No new revisions were added by this update.
Summary of changes:
clang/include/clang/Basic/Builtins.def | 2 +-
clang/test/CodeGen/avr-builtins.c | 4 ++++
llvm/docs/ReleaseNotes.rst | 15 +++++++++++++++
3 files changed, 20 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-mainline-allyesconfig
in repository toolchain/ci/base-artifacts.
discards a119a62 0: update: llvm-linux: 17896
new 6c6790f 0: update: llvm-linux: 17925
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 (a119a62)
\
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 | 229 +-
02-build_llvm/console.log | 12062 +++++++++++++++++-----------------
03-build_linux/console.log | 790 +--
05-check_regression/console.log | 18 +-
06-update_baseline/console.log | 16 +-
console.log | 13127 +++++++++++++++++++-------------------
jenkins/manifest.sh | 14 +-
results | 2 +-
8 files changed, 13106 insertions(+), 13152 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-next-allmodconfig
in repository toolchain/ci/gcc.
from 131317ad53e Daily bump.
adds 63ed120e3ff Daily bump.
No new revisions were added by this update.
Summary of changes:
gcc/DATESTAMP | 2 +-
1 file changed, 1 insertion(+), 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/gnu-release-aarch64-next-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 697a7d9 4: update: linux-f84e1c16f08d7d1d6955f8f1c2e6cc0587d6d14c: 18915
discards f2a0874 3: reset: linux-b8b576a16f79efbdde49348147f491b176537d88: 18681
discards 4db6ff8 2: update: gcc-131317ad53ede34ecd05b8d233d4c58e7d0080b6: 18916
new 34e2602 2: update: binutils-gcc-linux: 18924
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 (697a7d9)
\
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:
01-reset_artifacts/console.log | 184 +-
02-prepare_abe/console.log | 185 +-
03-build_abe-binutils/console.log | 10834 +++++++--------
04-build_abe-stage1/console.log | 13656 +++++++++----------
05-build_linux/console.log | 646 +-
07-check_regression/console.log | 18 +-
08-update_baseline/console.log | 97 +-
console.log | 25748 +++++++++++++++++++-----------------
jenkins/manifest.sh | 16 +-
results | 2 +-
10 files changed, 26498 insertions(+), 24888 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 5ba6f60 0: update: llvm-linux: boot
new e670779 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 (5ba6f60)
\
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 | 79 +-
02-build_llvm/console.log | 12156 ++++++++++++++++----------------
03-build_linux/console.log | 1816 +++--
04-boot_linux/console.log | 430 +-
05-check_regression/console.log | 8 +-
06-update_baseline/console.log | 8 +-
console.log | 14497 +++++++++++++++++++-------------------
jenkins/manifest.sh | 10 +-
8 files changed, 14513 insertions(+), 14491 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 d4eb3f39303 [X86] Prevent assertion when calling a function that return [...]
new b11e016ecd9 [BPF] Permit all user instructed offset relocatiions
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/BPF/BPFAbstractMemberAccess.cpp | 6 ++
test/CodeGen/BPF/CORE/offset-reloc-end-load.ll | 82 ++++++++++++++++++++++++++
test/CodeGen/BPF/CORE/offset-reloc-end-ret.ll | 76 ++++++++++++++++++++++++
3 files changed, 164 insertions(+)
create mode 100644 test/CodeGen/BPF/CORE/offset-reloc-end-load.ll
create mode 100644 test/CodeGen/BPF/CORE/offset-reloc-end-ret.ll
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.