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-arm-mainline-allyesconfig
in repository toolchain/ci/binutils-gdb.
from 0d5a11affe Automatic date update in version.in
adds 6060c2f337 Automatic date update in version.in
adds 27439f0eda Automatic date update in version.in
adds fcc561a54d Automatic date update in version.in
adds f0f39c9cfa Automatic date update in version.in
No new revisions were added by this update.
Summary of changes:
bfd/version.h | 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-arm-mainline-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 1cad0e6b2 0: update: binutils-gcc-linux-qemu: all
new 318ddfe17 0: update: binutils-gcc-linux-qemu: 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 (1cad0e6b2)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-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:
01-reset_artifacts/console.log.xz | Bin 1608 -> 1584 bytes
02-prepare_abe/console.log.xz | Bin 2780 -> 2800 bytes
03-build_abe-binutils/console.log.xz | Bin 41620 -> 42064 bytes
04-build_abe-stage1/console.log.xz | Bin 85652 -> 86384 bytes
05-build_abe-qemu/console.log.xz | Bin 30464 -> 30960 bytes
06-build_linux/console.log.xz | Bin 3504 -> 3816 bytes
07-boot_linux/console.log.xz | Bin 496 -> 496 bytes
08-check_regression/console.log.xz | Bin 532 -> 524 bytes
09-update_baseline/console.log | 67 ++---------------------------------
jenkins/manifest.sh | 22 ++++++------
10 files changed, 13 insertions(+), 76 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/base-artifacts.
discards 47baa18ba 0: update: binutils-gcc: 1
new 06f01bd26 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 (47baa18ba)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (06 [...]
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 1516 -> 1516 bytes
02-prepare_abe/console.log.xz | Bin 2756 -> 2748 bytes
03-build_abe-binutils/console.log.xz | Bin 64808 -> 63940 bytes
04-build_abe-gcc/console.log.xz | Bin 225512 -> 225284 bytes
05-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3804 bytes
06-build_abe-check_gcc/console.log.xz | Bin 2420 -> 2696 bytes
07-check_regression/console.log.xz | Bin 3272 -> 2904 bytes
07-check_regression/results.compare | 37 +-
07-check_regression/results.compare2 | 279 +--
08-update_baseline/console.log | 666 ++----
08-update_baseline/results.compare | 37 +-
08-update_baseline/results.compare2 | 279 +--
jenkins/manifest.sh | 8 +-
sumfiles/g++.log.xz | Bin 2646972 -> 2675716 bytes
sumfiles/g++.sum | 121 +-
sumfiles/gcc.log.xz | Bin 2231548 -> 2257052 bytes
sumfiles/gcc.sum | 3992 ++++++++++++++++-----------------
sumfiles/gfortran.log.xz | Bin 859244 -> 856344 bytes
sumfiles/gfortran.sum | 54 +-
sumfiles/libatomic.log.xz | Bin 2148 -> 2148 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 165888 -> 165728 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2528 -> 2528 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 448128 -> 453104 bytes
sumfiles/libstdc++.sum | 10 +-
27 files changed, 2461 insertions(+), 3048 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 d917742fe27 configure: Update --help output for --with-multilib-list
new f3d357bab35 Hoist edge calculations in precompute_relations.
new 00446916206 Remove dominator check in fold_using_range::range_of_phi.
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-range-fold.cc | 4 +---
gcc/gimple-range-path.cc | 12 ++++++------
2 files changed, 7 insertions(+), 9 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.