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/binutils-gdb.
from fba9460f7c PR27202, readelf -wL doesn't work on ".loc 0"
adds 80656a8e4b gdb: fix manor -> manner typo in some comments
adds 4180173142 gdb/doc: use 'standard error stream' instead of 'stderr' in [...]
adds 74ea3b51c3 gdb: fix build when libbacktrace and execinfo backtrace are [...]
No new revisions were added by this update.
Summary of changes:
gdb/bt-utils.c | 4 +++-
gdb/bt-utils.h | 2 +-
gdb/doc/gdb.texinfo | 12 ++++++------
gdb/language.h | 2 +-
4 files changed, 11 insertions(+), 9 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 763f0b7b0 0: update: binutils-gcc-linux-glibc-gdb-qemu: 7
new 79d872a14 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 (763f0b7b0)
\
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 1560 -> 1548 bytes
02-prepare_abe/console.log.xz | Bin 2772 -> 2768 bytes
04-build_abe-binutils/console.log.xz | Bin 45324 -> 45208 bytes
05-build_abe-stage1/console.log.xz | Bin 71560 -> 71744 bytes
06-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes
07-build_abe-linux/console.log.xz | Bin 9264 -> 9192 bytes
08-build_abe-glibc/console.log.xz | Bin 236716 -> 235844 bytes
09-build_abe-stage2/console.log.xz | Bin 189504 -> 190056 bytes
10-build_abe-gdb/console.log.xz | Bin 44720 -> 45068 bytes
11-build_abe-qemu/console.log.xz | Bin 30868 -> 30644 bytes
12-check_regression/console.log.xz | Bin 416 -> 416 bytes
13-update_baseline/console.log | 16 ++++++++--------
jenkins/manifest.sh | 18 +++++++++---------
13 files changed, 17 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_bootstrap/master-arm-bootstrap_lto
in repository toolchain/ci/base-artifacts.
discards ee9d8e297 0: update: binutils-gcc: 2
new 718c3a09a 0: update: binutils-gcc: 2
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 (ee9d8e297)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...]
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 1500 -> 1544 bytes
02-prepare_abe/console.log.xz | Bin 2748 -> 2752 bytes
04-build_abe-binutils/console.log.xz | Bin 64844 -> 66452 bytes
05-build_abe-bootstrap_lto/console.log.xz | Bin 473312 -> 471360 bytes
06-check_regression/console.log.xz | Bin 416 -> 416 bytes
07-update_baseline/console.log | 2 +-
jenkins/manifest.sh | 12 ++++++------
7 files changed, 7 insertions(+), 7 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/binutils-gdb.
from fba9460f7c PR27202, readelf -wL doesn't work on ".loc 0"
adds 80656a8e4b gdb: fix manor -> manner typo in some comments
adds 4180173142 gdb/doc: use 'standard error stream' instead of 'stderr' in [...]
adds 74ea3b51c3 gdb: fix build when libbacktrace and execinfo backtrace are [...]
No new revisions were added by this update.
Summary of changes:
gdb/bt-utils.c | 4 +++-
gdb/bt-utils.h | 2 +-
gdb/doc/gdb.texinfo | 12 ++++++------
gdb/language.h | 2 +-
4 files changed, 11 insertions(+), 9 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 e38456878 0: update: binutils-gcc: 1
new c279a55b0 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 (e38456878)
\
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 1536 -> 1520 bytes
02-prepare_abe/console.log.xz | Bin 2748 -> 2728 bytes
03-build_abe-binutils/console.log.xz | Bin 53232 -> 52688 bytes
04-build_abe-gcc/console.log.xz | Bin 198472 -> 198336 bytes
05-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3836 bytes
06-build_abe-check_gcc/console.log.xz | Bin 2552 -> 2740 bytes
07-check_regression/console.log.xz | Bin 2636 -> 3288 bytes
07-check_regression/results.compare | 51 +-
07-check_regression/results.compare2 | 84 +-
08-update_baseline/console.log | 433 ++--
08-update_baseline/results.compare | 51 +-
08-update_baseline/results.compare2 | 84 +-
jenkins/manifest.sh | 12 +-
sumfiles/g++.log.xz | Bin 3382932 -> 3388712 bytes
sumfiles/g++.sum | 130 +-
sumfiles/gcc.log.xz | Bin 2875948 -> 2900668 bytes
sumfiles/gcc.sum | 4196 +++++++++++++++++----------------
sumfiles/gfortran.log.xz | Bin 867772 -> 862872 bytes
sumfiles/gfortran.sum | 40 +-
sumfiles/libatomic.log.xz | Bin 2172 -> 2172 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 168064 -> 168420 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2528 -> 2536 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 426408 -> 419496 bytes
sumfiles/libstdc++.sum | 12 +-
27 files changed, 2706 insertions(+), 2413 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.