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-next-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 190c644ec 5: reset: linux-dfd42facf1e4ada021b939b4e19c935dcdd55566: 19146
discards 6bfffe1bb 4: update: binutils-llvm-qemu: 19170
discards 034c429e2 3: reset: llvm-35737df4dcd28534bd3090157c224c19b501278a: 19151
discards 2ef3c8afb 2: update: qemu-aeb0ae95b7f18c66158792641cb6ba0cde5789ab: 20213
new f8d6aff64 2: update: binutils-llvm-linux-qemu: 20248
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 (190c644ec)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-arm-n [...]
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.xz | Bin 1572 -> 1644 bytes
02-prepare_abe/console.log.xz | Bin 2756 -> 2796 bytes
03-build_abe-binutils/console.log.xz | Bin 29380 -> 31116 bytes
04-build_llvm/console.log.xz | Bin 60212 -> 60316 bytes
05-build_abe-qemu/console.log.xz | Bin 31440 -> 31704 bytes
06-build_linux/console.log.xz | Bin 40140 -> 6144 bytes
08-check_regression/console.log.xz | Bin 1248 -> 484 bytes
08-check_regression/jira-body.txt | 2 -
08-check_regression/mail-body.txt | 37 -----
08-check_regression/mail-subject.txt | 1 -
08-check_regression/results.regressions | 11 --
08-check_regression/trigger-bisect | 2 -
09-update_baseline/console.log | 247 +++++++++++++++++++++++++++-----
jenkins/manifest.sh | 23 +--
mail/jira-body.txt | 5 -
mail/mail-body.txt | 40 ------
mail/mail-subject.txt | 1 -
reset-baseline | 0
results | 13 +-
19 files changed, 227 insertions(+), 155 deletions(-)
delete mode 100644 08-check_regression/jira-body.txt
delete mode 100644 08-check_regression/mail-body.txt
delete mode 100644 08-check_regression/mail-subject.txt
delete mode 100644 08-check_regression/results.regressions
delete mode 100644 08-check_regression/trigger-bisect
delete mode 100644 mail/jira-body.txt
delete mode 100644 mail/mail-body.txt
delete mode 100644 mail/mail-subject.txt
delete mode 100644 reset-baseline
--
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-lts-defconfig
in repository toolchain/ci/base-artifacts.
discards 8986ca43b 0: update: binutils-llvm-linux-qemu: boot
new 78c99d321 0: update: binutils-llvm-linux-qemu: 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 (8986ca43b)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-arm-l [...]
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.xz | Bin 1548 -> 1560 bytes
02-prepare_abe/console.log.xz | Bin 2768 -> 2784 bytes
03-build_abe-binutils/console.log.xz | Bin 30296 -> 30552 bytes
04-build_llvm/console.log.xz | Bin 59296 -> 60252 bytes
05-build_abe-qemu/console.log.xz | Bin 30700 -> 30872 bytes
06-build_linux/console.log.xz | Bin 3600 -> 3608 bytes
07-boot_linux/console.log.xz | Bin 5952 -> 5972 bytes
08-check_regression/console.log.xz | Bin 412 -> 412 bytes
09-update_baseline/console.log | 10 +++++-----
jenkins/manifest.sh | 22 +++++++++++-----------
10 files changed, 16 insertions(+), 16 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 13caa028f9f Regenerate .pot files.
new 4c3792d4489 LRA, rs6000, Darwin: Amend lo_sum use for forced constants [...]
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/config/rs6000/rs6000.cc | 38 ++++++++++++++++++++++++++++++++++++--
gcc/lra-constraints.cc | 17 ++---------------
2 files changed, 38 insertions(+), 17 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_gcc_check/master-arm
in repository toolchain/ci/gcc.
from 274a4d29421 [PR104400] LRA: Modify exclude start hard register calculat [...]
adds b56ad95854f middle-end: Small __builtin_clear_padding improvements
adds 9355a8c3588 match.pd: Fix up (X & Y) CMP 0 -> X CMP2 ~Y simplifications [...]
new b02247346ea libstdc++: Fix test failures at -O0
new 9a56779dbc4 libstdc++: Fix FAIL: 20_util/temporary_buffer.cc for C++14
The 2 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/gimple-fold.cc | 10 +++++-----
gcc/gimplify.cc | 19 ++++++-------------
gcc/match.pd | 2 +-
gcc/testsuite/gcc.c-torture/compile/pr104499.c | 11 +++++++++++
gcc/tree.cc | 2 +-
.../20_util/monotonic_buffer_resource/allocate.cc | 3 +++
libstdc++-v3/testsuite/20_util/temporary_buffer.cc | 2 +-
.../20_util/unsynchronized_pool_resource/allocate.cc | 3 +++
.../testsuite/29_atomics/atomic/cons/user_pod.cc | 1 +
9 files changed, 32 insertions(+), 21 deletions(-)
create mode 100644 gcc/testsuite/gcc.c-torture/compile/pr104499.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_gcc_check/master-arm
in repository toolchain/ci/base-artifacts.
discards 188b8a6da 0: update: binutils-gcc: 1
new c904cc63d 0: update: binutils-gcc: 1
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 (188b8a6da)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (c9 [...]
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.xz | Bin 1488 -> 1520 bytes
02-prepare_abe/console.log.xz | Bin 2756 -> 2752 bytes
03-build_abe-binutils/console.log.xz | Bin 52504 -> 51344 bytes
04-build_abe-gcc/console.log.xz | Bin 229868 -> 228180 bytes
05-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3816 bytes
06-build_abe-check_gcc/console.log.xz | Bin 2636 -> 2484 bytes
07-check_regression/console.log.xz | Bin 2856 -> 2556 bytes
07-check_regression/results.compare | 16 +-
07-check_regression/results.compare2 | 74 +-
08-update_baseline/console.log | 298 +--
08-update_baseline/results.compare | 16 +-
08-update_baseline/results.compare2 | 74 +-
jenkins/manifest.sh | 12 +-
sumfiles/g++.log.xz | Bin 2721792 -> 2732140 bytes
sumfiles/g++.sum | 120 +-
sumfiles/gcc.log.xz | Bin 2334104 -> 2332344 bytes
sumfiles/gcc.sum | 4741 +++++++++++++++++----------------
sumfiles/gfortran.log.xz | Bin 887472 -> 882828 bytes
sumfiles/gfortran.sum | 44 +-
sumfiles/libatomic.log.xz | Bin 2172 -> 2172 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 188344 -> 188512 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2532 -> 2536 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 455960 -> 458304 bytes
sumfiles/libstdc++.sum | 10 +-
27 files changed, 2656 insertions(+), 2775 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.