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 7e371c5e5 0: update: binutils-gcc-linux-qemu: all
new bf09164fc 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 (7e371c5e5)
\
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 1572 -> 1564 bytes
02-prepare_abe/console.log.xz | Bin 2784 -> 2764 bytes
03-build_abe-binutils/console.log.xz | Bin 41952 -> 42092 bytes
04-build_abe-stage1/console.log.xz | Bin 86684 -> 85784 bytes
05-build_abe-qemu/console.log.xz | Bin 30324 -> 31200 bytes
06-build_linux/console.log.xz | Bin 3668 -> 3448 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 | 18 +++++++++---------
results | 2 +-
11 files changed, 15 insertions(+), 15 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.
unknown user pushed a change to branch master
in repository gcc.
from f32f74c2e8c [nvptx] Add uniform_warp_check insn
new b649071d4b3 tree: move tree_vec_map_cache_hasher into header
new 8a378978620 c++: lambda in template default argument [PR103186]
The 2 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:
gcc/cp/pt.cc | 42 +++++++++++++++++-----
.../g++.dg/cpp0x/lambda/lambda-defarg10.C | 21 +++++++++++
gcc/tree.cc | 17 ---------
gcc/tree.h | 17 +++++++++
4 files changed, 71 insertions(+), 26 deletions(-)
create mode 100644 gcc/testsuite/g++.dg/cpp0x/lambda/lambda-defarg10.C
--
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-next-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 4752c949c 0: update: linux-58da0d84fdd2563939dafa48334e190fad1b536c: all
new 0f3f3ab94 0: update: linux-58da0d84fdd2563939dafa48334e190fad1b536c: 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 (4752c949c)
\
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 1748 -> 1592 bytes
02-prepare_abe/console.log.xz | Bin 2772 -> 2768 bytes
03-build_abe-binutils/console.log.xz | Bin 42968 -> 42004 bytes
04-build_abe-stage1/console.log.xz | Bin 69956 -> 69256 bytes
05-build_abe-qemu/console.log.xz | Bin 32252 -> 32148 bytes
06-build_linux/console.log.xz | Bin 3524 -> 3388 bytes
07-boot_linux/console.log.xz | Bin 576 -> 576 bytes
08-check_regression/console.log.xz | Bin 412 -> 412 bytes
09-update_baseline/console.log | 10 +++++-----
jenkins/manifest.sh | 4 ++--
10 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_gnu_native_check_gcc/master-aarch64
in repository toolchain/ci/base-artifacts.
discards f4164bdfa 0: update: binutils-gcc-linux-glibc-gdb: 1
new 6eef6423d 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 (f4164bdfa)
\
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 1552 -> 1556 bytes
02-prepare_abe/console.log.xz | Bin 2752 -> 2764 bytes
03-build_abe-binutils/console.log.xz | Bin 38424 -> 38416 bytes
04-build_abe-gcc/console.log.xz | Bin 206048 -> 208412 bytes
05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes
06-build_abe-linux/console.log.xz | Bin 8476 -> 8576 bytes
07-build_abe-glibc/console.log.xz | Bin 236072 -> 238644 bytes
08-build_abe-gdb/console.log.xz | Bin 37396 -> 37424 bytes
09-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3824 bytes
10-build_abe-check_gcc/console.log.xz | Bin 2480 -> 2552 bytes
11-check_regression/console.log.xz | Bin 3280 -> 3904 bytes
11-check_regression/fails.sum | 8 +-
11-check_regression/results.compare | 36 +-
11-check_regression/results.compare2 | 152 +-
11-check_regression/results.regressions | 36 +-
12-update_baseline/console.log | 618 ++--
12-update_baseline/fails.sum | 8 +-
12-update_baseline/results.compare | 36 +-
12-update_baseline/results.compare2 | 152 +-
12-update_baseline/results.regressions | 36 +-
jenkins/manifest.sh | 20 +-
sumfiles/g++.log.xz | Bin 3623440 -> 3648204 bytes
sumfiles/g++.sum | 196 +-
sumfiles/gcc.log.xz | Bin 3145648 -> 3159844 bytes
sumfiles/gcc.sum | 5159 ++++++++++++++++---------------
sumfiles/gfortran.log.xz | Bin 1055480 -> 1061548 bytes
sumfiles/gfortran.sum | 42 +-
sumfiles/libatomic.log.xz | Bin 2276 -> 2272 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 199192 -> 199948 bytes
sumfiles/libgomp.sum | 28 +-
sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 423800 -> 432268 bytes
sumfiles/libstdc++.sum | 10 +-
35 files changed, 3443 insertions(+), 3104 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.
unknown user pushed a change to branch release/2.34/master
in repository glibc.
from aa601d0244 x86: Use CHECK_FEATURE_PRESENT to check HLE [BZ #27398]
new e09e7b1492 support: Add support_socket_so_timestamp_time64
new e098446037 linux: Fix ancillary 64-bit time timestamp conversion (BZ #2 [...]
new 489d0b8b32 Linux: Only generate 64 bit timestamps for 64 bit time_t rec [...]
new 008003dc6e tst-socket-timestamp-compat.c: Check __TIMESIZE [BZ #28837]
The 4 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:
NEWS | 3 +
include/sys/socket.h | 10 +-
support/Makefile | 1 +
support/support.h | 4 +
.../support_socket_so_timestamp_time64.c | 43 +--
sysdeps/unix/sysv/linux/Makefile | 9 +
sysdeps/unix/sysv/linux/convert_scm_timestamps.c | 14 +-
sysdeps/unix/sysv/linux/recvmmsg.c | 36 ++-
sysdeps/unix/sysv/linux/recvmsg.c | 34 ++-
.../linux/tst-socket-timestamp-compat-time64.c | 1 +
.../unix/sysv/linux/tst-socket-timestamp-compat.c | 265 ++++++++++++++++
.../unix/sysv/linux/tst-socket-timestamp-time64.c | 1 +
sysdeps/unix/sysv/linux/tst-socket-timestamp.c | 336 +++++++++++++++++++++
13 files changed, 709 insertions(+), 48 deletions(-)
copy socket/sockaddr_un_set.c => support/support_socket_so_timestamp_time64.c (53%)
create mode 100644 sysdeps/unix/sysv/linux/tst-socket-timestamp-compat-time64.c
create mode 100644 sysdeps/unix/sysv/linux/tst-socket-timestamp-compat.c
create mode 100644 sysdeps/unix/sysv/linux/tst-socket-timestamp-time64.c
create mode 100644 sysdeps/unix/sysv/linux/tst-socket-timestamp.c
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.