This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64
in repository toolchain/ci/glibc.
from 381b29616a aarch64: Disable A64FX memcpy/memmove BTI unconditionally
adds 91e92272ca i386: Port elf_machine_{load_address,dynamic} from x86-64
adds 5ad9d62c3b Linux: Avoid closing -1 on failure in __closefrom_fallback
new b26901b26e Fix sysdeps/x86/fpu/s_ffma.c for 32-bit FMA processor case
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:
sysdeps/i386/dl-machine.h | 25 +++++++++----------------
sysdeps/unix/sysv/linux/closefrom_fallback.c | 2 +-
sysdeps/x86/fpu/s_ffma.c | 8 ++++++--
3 files changed, 16 insertions(+), 19 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_gnu_cross_build/master-aarch64
in repository toolchain/ci/base-artifacts.
discards a096f9a2e 0: update: binutils-gcc-linux-glibc-gdb-qemu: 7
new c6ca6fecd 0: update: binutils-gcc-linux-glibc-gdb-qemu: 7
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 (a096f9a2e)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...]
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 1556 -> 1556 bytes
02-prepare_abe/console.log.xz | Bin 2772 -> 2776 bytes
04-build_abe-binutils/console.log.xz | Bin 44088 -> 43836 bytes
05-build_abe-stage1/console.log.xz | Bin 71360 -> 71564 bytes
06-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes
07-build_abe-linux/console.log.xz | Bin 8908 -> 9268 bytes
08-build_abe-glibc/console.log.xz | Bin 234792 -> 235104 bytes
09-build_abe-stage2/console.log.xz | Bin 189816 -> 190172 bytes
10-build_abe-gdb/console.log.xz | Bin 43868 -> 43240 bytes
11-build_abe-qemu/console.log.xz | Bin 30972 -> 30696 bytes
12-check_regression/console.log.xz | Bin 416 -> 416 bytes
13-update_baseline/console.log | 22 +++++++++++-----------
jenkins/manifest.sh | 30 +++++++++++++++---------------
13 files changed, 26 insertions(+), 26 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 23e3730c5 0: update: binutils-gcc: 1
new d238c3a0e 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 (23e3730c5)
\
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 1524 -> 1544 bytes
02-prepare_abe/console.log.xz | Bin 2752 -> 2752 bytes
03-build_abe-binutils/console.log.xz | Bin 51380 -> 52880 bytes
04-build_abe-gcc/console.log.xz | Bin 197988 -> 197708 bytes
05-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3840 bytes
06-build_abe-check_gcc/console.log.xz | Bin 2632 -> 2808 bytes
07-check_regression/console.log.xz | Bin 2720 -> 2644 bytes
07-check_regression/results.compare | 16 +-
07-check_regression/results.compare2 | 68 +-
08-update_baseline/console.log | 294 ++-
08-update_baseline/results.compare | 16 +-
08-update_baseline/results.compare2 | 68 +-
jenkins/manifest.sh | 12 +-
sumfiles/g++.log.xz | Bin 3375784 -> 3412068 bytes
sumfiles/g++.sum | 112 +-
sumfiles/gcc.log.xz | Bin 2913756 -> 2875660 bytes
sumfiles/gcc.sum | 4700 ++++++++++++++++-----------------
sumfiles/gfortran.log.xz | Bin 866612 -> 864944 bytes
sumfiles/gfortran.sum | 54 +-
sumfiles/libatomic.log.xz | Bin 2176 -> 2160 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 167904 -> 168124 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2528 -> 2532 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 422216 -> 422876 bytes
sumfiles/libstdc++.sum | 10 +-
27 files changed, 2699 insertions(+), 2677 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.