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-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 6a07a1f0 0: update: llvm-linux: all
new 848b5310 0: update: llvm-linux: 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 (6a07a1f0)
\
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 | 177 +-
02-build_llvm/console.log | 12528 ++++++++++++++--------------
03-build_linux/console.log | 4296 +++++-----
04-boot_linux/console.log | 6 +-
05-check_regression/console.log | 2 +-
06-update_baseline/console.log | 2 +-
console.log | 17011 +++++++++++++++++++-------------------
jenkins/manifest.sh | 14 +-
8 files changed, 17029 insertions(+), 17007 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-aarch64-stable-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 80d6a69d 0: update: llvm-linux: boot
new 1ddf4afb 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 (80d6a69d)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-release-aarc [...]
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 | 14 +-
02-build_llvm/console.log | 11966 +++++++++++++++++------------------
03-build_linux/console.log | 782 +--
04-boot_linux/console.log | 4 +-
05-check_regression/console.log | 2 +-
06-update_baseline/console.log | 29 +
console.log | 12797 +++++++++++++++++++-------------------
jenkins/manifest.sh | 6 +-
8 files changed, 12829 insertions(+), 12771 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-defconfig
in repository toolchain/ci/base-artifacts.
discards 84d04dce 0: update: llvm-linux: boot
new 80fe6d23 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 (84d04dce)
\
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 | 130 +-
02-build_llvm/console.log | 11952 +++++++++++++++++-----------------
03-build_linux/console.log | 812 +--
04-boot_linux/console.log | 410 +-
05-check_regression/console.log | 2 +-
06-update_baseline/console.log | 29 +
console.log | 13335 +++++++++++++++++++-------------------
jenkins/manifest.sh | 6 +-
8 files changed, 13367 insertions(+), 13309 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-stable-allyesconfig
in repository toolchain/ci/base-artifacts.
discards d4b56305 0: update: llvm-linux: 17875
new 48ad58a0 0: update: llvm-linux: 17875
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 (d4b56305)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-arm-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 | 65 +-
02-build_llvm/console.log | 12500 +++++++++++++--------------
03-build_linux/console.log | 4918 +++++------
05-check_regression/console.log | 2 +-
06-update_baseline/console.log | 10 +-
console.log | 17495 +++++++++++++++++++-------------------
jenkins/manifest.sh | 10 +-
7 files changed, 17509 insertions(+), 17491 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-allnoconfig
in repository toolchain/ci/gcc.
from 92e43afb5f2 Daily bump.
adds c653c45fe91 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-lts-allnoconfig
in repository toolchain/ci/base-artifacts.
discards f33eccd6 0: update: binutils-gcc-linux: boot
new 3bef5d5d 0: update: binutils-gcc-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 (f33eccd6)
\
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 | 166 +-
02-prepare_abe/console.log | 438 +-
03-build_abe-binutils/console.log | 10921 +++++++--------
04-build_abe-stage1/console.log | 14158 +++++++++----------
05-build_linux/console.log | 668 +-
07-check_regression/console.log | 2 +-
08-update_baseline/console.log | 29 +
console.log | 26388 ++++++++++++++++++------------------
jenkins/manifest.sh | 10 +-
9 files changed, 26422 insertions(+), 26358 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 82e489d72dd Add a couple int128_t bit-field testcases.
new f1ae9407963 Fix PR92950: Wrong code emitted for movv1qi
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/ChangeLog | 6 ++++++
gcc/config/s390/vector.md | 12 +++++-------
gcc/testsuite/ChangeLog | 5 +++++
gcc/testsuite/gcc.target/s390/vector/pr92950.c | 24 ++++++++++++++++++++++++
4 files changed, 40 insertions(+), 7 deletions(-)
create mode 100644 gcc/testsuite/gcc.target/s390/vector/pr92950.c
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.