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_build/master-arm
in repository toolchain/ci/binutils-gdb.
from ecbff28a44 gdb: LoongArch: Handle the function return value
adds 1bcb0708f2 gdb/linux-nat: Check whether /proc/pid/mem is writable
adds dd09fe0d53 gdb/linux_nat: Write memory using ptrace if /proc/pid/mem is [...]
adds 9c6dd6885b gprofng: check for the makeinfo version
adds 3c0c7b4e1a Automatic date update in version.in
No new revisions were added by this update.
Summary of changes:
bfd/version.h | 2 +-
gdb/linux-nat.c | 116 ++++++++++++++++++++++++++++++++++++++++++---------
gprofng/configure | 64 +++++++++++++++++++++++++++-
gprofng/configure.ac | 22 ++++++++--
4 files changed, 179 insertions(+), 25 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_native_build/master-arm
in repository toolchain/ci/base-artifacts.
discards 6c182203 0: update: binutils-gcc-linux-glibc-gdb: 6
new 631480fe 0: update: binutils-gcc-linux-glibc-gdb: 6
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 (6c182203)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/master- [...]
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 1604 -> 1608 bytes
02-prepare_abe/console.log.xz | Bin 2732 -> 2732 bytes
04-build_abe-binutils/console.log.xz | Bin 50760 -> 50964 bytes
05-build_abe-gcc/console.log.xz | Bin 232292 -> 232648 bytes
06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes
07-build_abe-linux/console.log.xz | Bin 8816 -> 8836 bytes
08-build_abe-glibc/console.log.xz | Bin 231812 -> 232328 bytes
09-build_abe-gdb/console.log.xz | Bin 49820 -> 49684 bytes
10-check_regression/console.log.xz | Bin 420 -> 416 bytes
11-update_baseline/console.log | 16 ++++++++--------
jenkins/manifest.sh | 24 ++++++++++++------------
11 files changed, 20 insertions(+), 20 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_check_gcc/master-aarch64
in repository toolchain/ci/base-artifacts.
discards cc5a1efb 0: update: binutils-gcc-linux-glibc-gdb-qemu: 1
new 64f37c31 0: update: binutils-gcc-linux-glibc-gdb-qemu: 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 (cc5a1efb)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...]
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 1632 -> 1628 bytes
02-prepare_abe/console.log.xz | Bin 2744 -> 2744 bytes
03-build_abe-binutils/console.log.xz | Bin 30432 -> 30392 bytes
04-build_abe-stage1/console.log.xz | Bin 73028 -> 72884 bytes
06-build_abe-linux/console.log.xz | Bin 9324 -> 9520 bytes
07-build_abe-glibc/console.log.xz | Bin 239800 -> 239580 bytes
08-build_abe-stage2/console.log.xz | Bin 203016 -> 202104 bytes
09-build_abe-gdb/console.log.xz | Bin 37708 -> 37504 bytes
10-build_abe-qemu/console.log.xz | Bin 30948 -> 31528 bytes
11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3872 bytes
12-build_abe-check_gcc/console.log.xz | Bin 2724 -> 2584 bytes
13-check_regression/console.log.xz | Bin 4644 -> 2672 bytes
13-check_regression/results.compare | 51 -
13-check_regression/results.compare2 | 388 +--
14-update_baseline/console.log | 747 ++----
14-update_baseline/results.compare | 51 -
14-update_baseline/results.compare2 | 388 +--
jenkins/manifest.sh | 14 +-
sumfiles/g++.log.xz | Bin 3394552 -> 3395000 bytes
sumfiles/g++.sum | 102 +-
sumfiles/gcc.log.xz | Bin 2990120 -> 2984548 bytes
sumfiles/gcc.sum | 4780 +++++++++++++++++----------------
sumfiles/gfortran.log.xz | Bin 1026056 -> 1028332 bytes
sumfiles/gfortran.sum | 54 +-
sumfiles/libatomic.log.xz | Bin 2300 -> 2288 bytes
sumfiles/libatomic.sum | 2 +-
sumfiles/libgomp.log.xz | Bin 199768 -> 199736 bytes
sumfiles/libgomp.sum | 2 +-
sumfiles/libitm.log.xz | Bin 2656 -> 2660 bytes
sumfiles/libitm.sum | 2 +-
sumfiles/libstdc++.log.xz | Bin 425568 -> 423096 bytes
sumfiles/libstdc++.sum | 8 +-
32 files changed, 2746 insertions(+), 3843 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-mainline-defconfig
in repository toolchain/ci/base-artifacts.
discards c6be6d7c 0: update: binutils-gcc-linux-qemu: boot
new 319492b7 0: update: binutils-gcc-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 (c6be6d7c)
\
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.xz | Bin 1764 -> 1648 bytes
02-prepare_abe/console.log.xz | Bin 2764 -> 2744 bytes
03-build_abe-binutils/console.log.xz | Bin 30712 -> 30500 bytes
04-build_abe-stage1/console.log.xz | Bin 68244 -> 68404 bytes
05-build_abe-qemu/console.log.xz | Bin 30976 -> 30828 bytes
06-build_linux/console.log.xz | Bin 3464 -> 3304 bytes
07-boot_linux/console.log.xz | Bin 6232 -> 6240 bytes
08-check_regression/console.log.xz | Bin 412 -> 412 bytes
09-update_baseline/console.log | 2 +-
jenkins/manifest.sh | 18 +++++++++---------
10 files changed, 10 insertions(+), 10 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.