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 19b9612448 Automatic date update in version.in
adds b3a01ce215 CTF: incorrect underlying type setting for enumeration types
No new revisions were added by this update.
Summary of changes:
gdb/ctfread.c | 15 +++++++++------
gdb/dwarf2/cu.c | 2 +-
gdb/dwarf2/read.c | 26 +-------------------------
gdb/dwarf2/read.h | 4 ----
gdb/objfiles.c | 26 ++++++++++++++++++++++++++
gdb/objfiles.h | 5 +++++
6 files changed, 42 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_gnu_cross_build/master-aarch64
in repository toolchain/ci/base-artifacts.
discards efbb442e 0: update: binutils-gcc-linux-glibc-gdb-qemu: 7
new 70255a0a 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 (efbb442e)
\
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 1548 -> 1544 bytes
02-prepare_abe/console.log.xz | Bin 2768 -> 2764 bytes
04-build_abe-binutils/console.log.xz | Bin 45152 -> 45152 bytes
05-build_abe-stage1/console.log.xz | Bin 73680 -> 71368 bytes
06-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes
07-build_abe-linux/console.log.xz | Bin 8624 -> 8784 bytes
08-build_abe-glibc/console.log.xz | Bin 235816 -> 235496 bytes
09-build_abe-stage2/console.log.xz | Bin 202628 -> 200812 bytes
10-build_abe-gdb/console.log.xz | Bin 44616 -> 44960 bytes
11-build_abe-qemu/console.log.xz | Bin 29980 -> 30108 bytes
12-check_regression/console.log.xz | Bin 416 -> 416 bytes
13-update_baseline/console.log | 16 ++++++++--------
jenkins/manifest.sh | 26 +++++++++++++-------------
13 files changed, 21 insertions(+), 21 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 19b9612448 Automatic date update in version.in
new b3a01ce215 CTF: incorrect underlying type setting for enumeration types
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:
gdb/ctfread.c | 15 +++++++++------
gdb/dwarf2/cu.c | 2 +-
gdb/dwarf2/read.c | 26 +-------------------------
gdb/dwarf2/read.h | 4 ----
gdb/objfiles.c | 26 ++++++++++++++++++++++++++
gdb/objfiles.h | 5 +++++
6 files changed, 42 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_gcc_check/master-aarch64
in repository toolchain/ci/base-artifacts.
discards 2b380b0d 0: update: binutils-gcc: 1
new 7ed8dac5 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 (2b380b0d)
\
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 -> 1528 bytes
02-prepare_abe/console.log.xz | Bin 2736 -> 2760 bytes
03-build_abe-binutils/console.log.xz | Bin 52192 -> 53352 bytes
04-build_abe-gcc/console.log.xz | Bin 211072 -> 208184 bytes
05-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3816 bytes
06-build_abe-check_gcc/console.log.xz | Bin 4660 -> 2480 bytes
07-check_regression/console.log.xz | Bin 11632 -> 2812 bytes
07-check_regression/extra-bisect-params | 1 -
07-check_regression/fails.sum | 7 -
07-check_regression/results.compare | 68 +-
07-check_regression/results.compare2 | 3760 +---------------------------
07-check_regression/results.regressions | 70 -
08-update_baseline/console.log | 4035 +------------------------------
08-update_baseline/extra-bisect-params | 1 -
08-update_baseline/fails.sum | 7 -
08-update_baseline/results.compare | 68 +-
08-update_baseline/results.compare2 | 3760 +---------------------------
08-update_baseline/results.regressions | 70 -
jenkins/manifest.sh | 12 +-
sumfiles/g++.log.xz | Bin 3395112 -> 3395844 bytes
sumfiles/g++.sum | 137 +-
sumfiles/gcc.log.xz | Bin 2907328 -> 2906440 bytes
sumfiles/gcc.sum | 3800 ++++++++++++++---------------
sumfiles/gfortran.log.xz | Bin 879804 -> 876272 bytes
sumfiles/gfortran.sum | 96 +-
sumfiles/libatomic.log.xz | Bin 2160 -> 2168 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 170884 -> 170888 bytes
sumfiles/libgomp.sum | 21 +-
sumfiles/libitm.log.xz | Bin 2524 -> 2520 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 422872 -> 425876 bytes
sumfiles/libstdc++.sum | 12 +-
33 files changed, 2265 insertions(+), 13670 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.
This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch maskray/relr
in repository glibc.
discards ee9687b1b5 elf: Support DT_RELR relative relocation format [BZ #27924]
new e62bfdb731 elf: Support DT_RELR relative relocation format [BZ #27924]
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 (ee9687b1b5)
\
N -- N -- N refs/heads/maskray/relr (e62bfdb731)
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:
elf/Makefile | 6 +++---
elf/{tst-relr-static.c => tst-relr-no-pie.c} | 0
2 files changed, 3 insertions(+), 3 deletions(-)
rename elf/{tst-relr-static.c => tst-relr-no-pie.c} (100%)
--
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 maskray/relr
in repository glibc.
discards a6218e105b elf: Support DT_RELR relative relocation format [BZ #27924]
new ee9687b1b5 elf: Support DT_RELR relative relocation format [BZ #27924]
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 (a6218e105b)
\
N -- N -- N refs/heads/maskray/relr (ee9687b1b5)
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:
elf/Makefile | 2 ++
elf/tst-relr-static.c | 1 +
2 files changed, 3 insertions(+)
create mode 100644 elf/tst-relr-static.c
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.