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-lts-allyesconfig
in repository toolchain/ci/binutils-gdb.
from bd6c5ec02d Automatic date update in version.in
adds 94e07b6911 Automatic date update in version.in
adds 5e59286034 Automatic date update in version.in
adds 5b43f78fb1 Automatic date update in version.in
adds 74ef67f9ba Automatic date update in version.in
adds 8d1187516e Adjust ld ctf test for 32-bit targets
adds c473aa1b9d M68K: avoid quadratic slowdlow in label alignment check
No new revisions were added by this update.
Summary of changes:
bfd/version.h | 2 +-
gas/config/tc-m68k.c | 43 +++++++---------------------------
gas/config/tc-m68k.h | 17 ++++++++++++++
ld/testsuite/ld-ctf/nonrepresentable.d | 2 +-
4 files changed, 28 insertions(+), 36 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-arm-lts-allyesconfig
in repository toolchain/ci/base-artifacts.
discards a00e4b794 0: update: binutils-gcc-linux-qemu: all
new e7e1b965f 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 (a00e4b794)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-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 -> 1680 bytes
02-prepare_abe/console.log.xz | Bin 2736 -> 2744 bytes
03-build_abe-binutils/console.log.xz | Bin 29792 -> 30292 bytes
04-build_abe-stage1/console.log.xz | Bin 85484 -> 85968 bytes
05-build_abe-qemu/console.log.xz | Bin 31756 -> 31928 bytes
06-build_linux/console.log.xz | Bin 3464 -> 3560 bytes
07-boot_linux/console.log.xz | Bin 496 -> 496 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.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/master-aarch64
in repository toolchain/ci/base-artifacts.
discards 93674640c 0: update: binutils-gcc: 1
new bb29bf175 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 (93674640c)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-aarch64 [...]
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 1564 -> 1484 bytes
02-prepare_abe/console.log.xz | Bin 2720 -> 2724 bytes
03-build_abe-binutils/console.log.xz | Bin 37808 -> 39284 bytes
04-build_abe-gcc/console.log.xz | Bin 207776 -> 208876 bytes
05-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3872 bytes
06-build_abe-check_gcc/console.log.xz | Bin 2548 -> 2676 bytes
07-check_regression/console.log.xz | Bin 2356 -> 3120 bytes
07-check_regression/extra-bisect-params | 1 +
07-check_regression/fails.sum | 7 +
07-check_regression/results.compare | 10 +-
07-check_regression/results.compare2 | 64 +-
07-check_regression/results.regressions | 27 +
08-update_baseline/console.log | 150 +-
08-update_baseline/extra-bisect-params | 1 +
08-update_baseline/fails.sum | 7 +
08-update_baseline/results.compare | 10 +-
08-update_baseline/results.compare2 | 64 +-
08-update_baseline/results.regressions | 27 +
jenkins/manifest.sh | 12 +-
sumfiles/g++.log.xz | Bin 3548036 -> 3518740 bytes
sumfiles/g++.sum | 36 +-
sumfiles/gcc.log.xz | Bin 3010708 -> 3047924 bytes
sumfiles/gcc.sum | 4866 +++++++++++++++----------------
sumfiles/gfortran.log.xz | Bin 1039668 -> 1023916 bytes
sumfiles/gfortran.sum | 4 +-
sumfiles/libatomic.log.xz | Bin 2180 -> 2192 bytes
sumfiles/libatomic.sum | 2 +-
sumfiles/libgomp.log.xz | Bin 202468 -> 202624 bytes
sumfiles/libgomp.sum | 2 +-
sumfiles/libitm.log.xz | Bin 2544 -> 2540 bytes
sumfiles/libitm.sum | 2 +-
sumfiles/libstdc++.log.xz | Bin 432584 -> 424184 bytes
sumfiles/libstdc++.sum | 2 +-
33 files changed, 2785 insertions(+), 2509 deletions(-)
create mode 100644 07-check_regression/extra-bisect-params
create mode 100644 07-check_regression/fails.sum
create mode 100644 07-check_regression/results.regressions
create mode 100644 08-update_baseline/extra-bisect-params
create mode 100644 08-update_baseline/fails.sum
create mode 100644 08-update_baseline/results.regressions
--
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_native_check_gcc/master-aarch64
in repository toolchain/ci/glibc.
from 71e2a681f1 linux: Fix posix_spawn return code if clone fails (BZ#29109)
adds 18bd9c3d3b ia64: Always define IA64_USE_NEW_STUB as a flag macro
adds a2a6bce7d7 Linux: Implement a useful version of _startup_fatal
No new revisions were added by this update.
Summary of changes:
sysdeps/unix/sysv/linux/i386/startup.h | 23 +++----------
sysdeps/unix/sysv/linux/ia64/brk.c | 5 ++-
.../unix/sysv/linux/ia64/startup.h | 17 +++-------
sysdeps/unix/sysv/linux/ia64/sysdep.h | 23 +++++++------
sysdeps/unix/sysv/linux/startup.h | 39 ++++++++++++++++++++++
5 files changed, 62 insertions(+), 45 deletions(-)
copy elf/tst-audit24amod1.c => sysdeps/unix/sysv/linux/ia64/startup.h (81%)
create mode 100644 sysdeps/unix/sysv/linux/startup.h
--
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_native_check_gcc/master-aarch64
in repository toolchain/ci/base-artifacts.
discards e9dd6a38c 0: update: binutils-gcc-linux-glibc-gdb: 1
new 60bbc580c 0: update: binutils-gcc-linux-glibc-gdb: 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 (e9dd6a38c)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...]
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 1576 -> 1668 bytes
02-prepare_abe/console.log.xz | Bin 2724 -> 2712 bytes
03-build_abe-binutils/console.log.xz | Bin 39296 -> 38344 bytes
04-build_abe-gcc/console.log.xz | Bin 209676 -> 207636 bytes
05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes
06-build_abe-linux/console.log.xz | Bin 9524 -> 8848 bytes
07-build_abe-glibc/console.log.xz | Bin 240384 -> 237984 bytes
08-build_abe-gdb/console.log.xz | Bin 39148 -> 37768 bytes
09-build_abe-dejagnu/console.log.xz | Bin 3952 -> 3840 bytes
10-build_abe-check_gcc/console.log.xz | Bin 2464 -> 2732 bytes
11-check_regression/console.log.xz | Bin 2812 -> 2548 bytes
11-check_regression/results.compare | 31 +-
11-check_regression/results.compare2 | 49 +-
12-update_baseline/console.log | 402 ++-
12-update_baseline/results.compare | 31 +-
12-update_baseline/results.compare2 | 49 +-
jenkins/manifest.sh | 26 +-
sumfiles/g++.log.xz | Bin 3648808 -> 3667020 bytes
sumfiles/g++.sum | 122 +-
sumfiles/gcc.log.xz | Bin 3194968 -> 3166452 bytes
sumfiles/gcc.sum | 4618 ++++++++++++++++-----------------
sumfiles/gfortran.log.xz | Bin 1063944 -> 1058524 bytes
sumfiles/gfortran.sum | 44 +-
sumfiles/libatomic.log.xz | Bin 2272 -> 2272 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 215208 -> 214324 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 435884 -> 434568 bytes
sumfiles/libstdc++.sum | 12 +-
31 files changed, 2692 insertions(+), 2718 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-mainline-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 714d80fa2 0: update: binutils-llvm-linux-qemu: all
new 61497ff54 0: update: binutils-llvm-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 (714d80fa2)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-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 1560 -> 1672 bytes
02-prepare_abe/console.log.xz | Bin 2744 -> 2736 bytes
03-build_abe-binutils/console.log.xz | Bin 30400 -> 30684 bytes
04-build_llvm/console.log.xz | Bin 61036 -> 61324 bytes
05-build_abe-qemu/console.log.xz | Bin 31824 -> 32080 bytes
06-build_linux/console.log.xz | Bin 3384 -> 3564 bytes
07-boot_linux/console.log.xz | Bin 496 -> 496 bytes
08-check_regression/console.log.xz | Bin 412 -> 412 bytes
09-update_baseline/console.log | 2 +-
jenkins/manifest.sh | 22 +++++++++++-----------
10 files changed, 12 insertions(+), 12 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-arm-mainline-allmodconfig
in repository toolchain/ci/binutils-gdb.
from bd6c5ec02d Automatic date update in version.in
adds 94e07b6911 Automatic date update in version.in
adds 5e59286034 Automatic date update in version.in
adds 5b43f78fb1 Automatic date update in version.in
adds 74ef67f9ba Automatic date update in version.in
adds 8d1187516e Adjust ld ctf test for 32-bit targets
adds c473aa1b9d M68K: avoid quadratic slowdlow in label alignment check
No new revisions were added by this update.
Summary of changes:
bfd/version.h | 2 +-
gas/config/tc-m68k.c | 43 +++++++---------------------------
gas/config/tc-m68k.h | 17 ++++++++++++++
ld/testsuite/ld-ctf/nonrepresentable.d | 2 +-
4 files changed, 28 insertions(+), 36 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-arm-mainline-allmodconfig
in repository toolchain/ci/base-artifacts.
discards f66c5fd92 0: update: binutils-gcc-linux-qemu: all
new ecbdd1422 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 (f66c5fd92)
\
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 1560 -> 1564 bytes
02-prepare_abe/console.log.xz | Bin 2728 -> 2736 bytes
03-build_abe-binutils/console.log.xz | Bin 30004 -> 30432 bytes
04-build_abe-stage1/console.log.xz | Bin 85496 -> 85712 bytes
05-build_abe-qemu/console.log.xz | Bin 31572 -> 31920 bytes
06-build_linux/console.log.xz | Bin 3220 -> 3216 bytes
07-boot_linux/console.log.xz | Bin 496 -> 496 bytes
08-check_regression/console.log.xz | Bin 412 -> 420 bytes
09-update_baseline/console.log | 2 +-
jenkins/manifest.sh | 22 +++++++++++-----------
10 files changed, 12 insertions(+), 12 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 da8b2af19 0: update: binutils-4dcb932e645bdb0e63cecffb626d0805d9a19c27: 1
new 2788f3bb4 0: update: binutils-77399b529808626f764bcc347be0d6e8b6b167ce: 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 (da8b2af19)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (27 [...]
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 -> 1520 bytes
02-prepare_abe/console.log.xz | Bin 2720 -> 2724 bytes
03-build_abe-binutils/console.log.xz | Bin 50796 -> 50776 bytes
04-build_abe-gcc/console.log.xz | Bin 232452 -> 231296 bytes
05-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3832 bytes
06-build_abe-check_gcc/console.log.xz | Bin 2548 -> 2540 bytes
07-check_regression/console.log.xz | Bin 3384 -> 3232 bytes
07-check_regression/extra-bisect-params | 1 -
07-check_regression/fails.sum | 7 -
07-check_regression/results.compare | 25 +-
07-check_regression/results.compare2 | 52 +-
07-check_regression/results.regressions | 27 -
08-update_baseline/console.log | 302 +--
08-update_baseline/extra-bisect-params | 1 -
08-update_baseline/fails.sum | 7 -
08-update_baseline/results.compare | 25 +-
08-update_baseline/results.compare2 | 52 +-
08-update_baseline/results.regressions | 27 -
jenkins/manifest.sh | 8 +-
sumfiles/g++.log.xz | Bin 2759540 -> 2778956 bytes
sumfiles/g++.sum | 122 +-
sumfiles/gcc.log.xz | Bin 2374688 -> 2336636 bytes
sumfiles/gcc.sum | 4174 +++++++++++++++----------------
sumfiles/gfortran.log.xz | Bin 891196 -> 896944 bytes
sumfiles/gfortran.sum | 40 +-
sumfiles/libatomic.log.xz | Bin 2168 -> 2172 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 200264 -> 200120 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2532 -> 2532 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 456108 -> 462204 bytes
sumfiles/libstdc++.sum | 10 +-
33 files changed, 2413 insertions(+), 2493 deletions(-)
delete mode 100644 07-check_regression/extra-bisect-params
delete mode 100644 07-check_regression/fails.sum
delete mode 100644 07-check_regression/results.regressions
delete mode 100644 08-update_baseline/extra-bisect-params
delete mode 100644 08-update_baseline/fails.sum
delete mode 100644 08-update_baseline/results.regressions
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.