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/gcc.
from 1f8a09d2f3c Daily bump.
adds 2c3309e3d0f c++: TTP in member alias template [PR104107]
No new revisions were added by this update.
Summary of changes:
gcc/cp/pt.cc | 41 +++++++++++++++++++++-------
gcc/testsuite/g++.dg/cpp0x/alias-decl-ttp2.C | 25 +++++++++++++++++
gcc/testsuite/g++.dg/cpp1z/ttp2.C | 21 ++++++++++++++
3 files changed, 77 insertions(+), 10 deletions(-)
create mode 100644 gcc/testsuite/g++.dg/cpp0x/alias-decl-ttp2.C
create mode 100644 gcc/testsuite/g++.dg/cpp1z/ttp2.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_gnu_cross_build/master-aarch64
in repository toolchain/ci/base-artifacts.
discards e294a84b 0: update: binutils-gcc-linux-glibc-gdb-qemu: 7
new b74a9bca 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 (e294a84b)
\
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 -> 1556 bytes
02-prepare_abe/console.log.xz | Bin 2780 -> 2760 bytes
04-build_abe-binutils/console.log.xz | Bin 30212 -> 30548 bytes
05-build_abe-stage1/console.log.xz | Bin 71352 -> 71396 bytes
07-build_abe-linux/console.log.xz | Bin 8888 -> 9028 bytes
08-build_abe-glibc/console.log.xz | Bin 237148 -> 236304 bytes
09-build_abe-stage2/console.log.xz | Bin 198244 -> 197832 bytes
10-build_abe-gdb/console.log.xz | Bin 37092 -> 37272 bytes
11-build_abe-qemu/console.log.xz | Bin 30824 -> 31216 bytes
12-check_regression/console.log.xz | Bin 416 -> 416 bytes
13-update_baseline/console.log | 2 +-
jenkins/manifest.sh | 22 +++++++++++-----------
12 files changed, 12 insertions(+), 12 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/llvm-release-aarch64-mainline-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 4b3a7a02 0: update: binutils-llvm-linux-qemu: boot
new ec3e8377 0: update: binutils-llvm-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 (4b3a7a02)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-release-aarc [...]
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 1576 -> 1564 bytes
02-prepare_abe/console.log.xz | Bin 2780 -> 2768 bytes
03-build_abe-binutils/console.log.xz | Bin 43612 -> 30244 bytes
04-build_llvm/console.log.xz | Bin 58996 -> 60232 bytes
05-build_abe-qemu/console.log.xz | Bin 31392 -> 30788 bytes
06-build_linux/console.log.xz | Bin 3524 -> 3524 bytes
07-boot_linux/console.log.xz | Bin 504 -> 504 bytes
08-check_regression/console.log.xz | Bin 412 -> 412 bytes
09-update_baseline/console.log | 10 +++++-----
jenkins/manifest.sh | 20 ++++++++++----------
10 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.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/master-aarch64
in repository toolchain/ci/base-artifacts.
discards 6aca5a76 0: update: binutils-gcc: 1
new 0d0e660a 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 (6aca5a76)
\
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 1532 -> 1520 bytes
02-prepare_abe/console.log.xz | Bin 2752 -> 2760 bytes
03-build_abe-binutils/console.log.xz | Bin 37676 -> 38528 bytes
04-build_abe-gcc/console.log.xz | Bin 207584 -> 207816 bytes
05-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3872 bytes
06-build_abe-check_gcc/console.log.xz | Bin 2524 -> 2712 bytes
07-check_regression/console.log.xz | Bin 3088 -> 3400 bytes
07-check_regression/extra-bisect-params | 2 +-
07-check_regression/fails.sum | 9 +-
07-check_regression/results.compare | 32 +-
07-check_regression/results.compare2 | 89 +-
07-check_regression/results.regressions | 32 +-
08-update_baseline/console.log | 383 +--
08-update_baseline/extra-bisect-params | 2 +-
08-update_baseline/fails.sum | 9 +-
08-update_baseline/results.compare | 32 +-
08-update_baseline/results.compare2 | 89 +-
08-update_baseline/results.regressions | 32 +-
jenkins/manifest.sh | 12 +-
sumfiles/g++.log.xz | Bin 3510600 -> 3473688 bytes
sumfiles/g++.sum | 152 +-
sumfiles/gcc.log.xz | Bin 2989992 -> 3001836 bytes
sumfiles/gcc.sum | 3994 +++++++++++++++----------------
sumfiles/gfortran.log.xz | Bin 1028556 -> 1021644 bytes
sumfiles/gfortran.sum | 42 +-
sumfiles/libatomic.log.xz | Bin 2184 -> 2192 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 190688 -> 190812 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2544 -> 2548 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 424304 -> 430408 bytes
sumfiles/libstdc++.sum | 10 +-
33 files changed, 2548 insertions(+), 2399 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.