This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_cross/gnu-release-aarch64-build_cross
in repository toolchain/ci/base-artifacts.
discards 125fec18c 0: update: binutils-gcc-glibc-qemu: 6
new a64729f9b 0: update: binutils-gcc-glibc-qemu: 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 (125fec18c)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_cross/gnu-release-aarch6 [...]
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 | 172 +-
02-prepare_abe/console.log | 390 +-
04-build_abe-binutils/console.log | 11741 ++--
05-build_abe-stage1/console.log | 13946 +++--
06-build_abe-linux/console.log | 294 +-
07-build_abe-glibc/console.log | 40213 ++++++-------
08-build_abe-stage2/console.log | 39155 +++++++------
09-build_abe-qemu/console.log | 2465 +-
10-check_regression/console.log | 4 +-
11-update_baseline/console.log | 4 +-
console.log | 108410 +++++++++++++++++------------------
jenkins/manifest.sh | 12 +-
12 files changed, 108367 insertions(+), 108439 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-lts-defconfig
in repository toolchain/ci/gcc.
from cbc9dab25fb libstdc++: Make pmr::synchronized_pool_resource work withou [...]
adds 600ef5614b2 add --with-tune configure flag
adds e56eee08489 add --with-{cpu,arch,tune}-{32,64} as alias flags for --wit [...]
adds 83ded159c96 Daily bump.
No new revisions were added by this update.
Summary of changes:
gcc/ChangeLog | 40 ++++++++++++++++++++++++++++++++++++++++
gcc/DATESTAMP | 2 +-
gcc/config.gcc | 23 ++++++++++++++++++++---
gcc/doc/install.texi | 2 +-
gcc/testsuite/ChangeLog | 26 ++++++++++++++++++++++++++
libstdc++-v3/ChangeLog | 27 +++++++++++++++++++++++++++
6 files changed, 115 insertions(+), 5 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-lts-defconfig
in repository toolchain/ci/base-artifacts.
discards e6272bdc5 0: update: binutils-gcc-linux: boot
new 8af61389a 0: update: binutils-gcc-linux: 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 (e6272bdc5)
\
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 | 119 +-
02-prepare_abe/console.log | 74 +-
03-build_abe-binutils/console.log | 11410 ++++++-------
04-build_abe-stage1/console.log | 13311 ++++++++-------
05-build_linux/console.log | 812 +-
06-boot_linux/console.log | 404 +-
07-check_regression/console.log | 4 +-
07-check_regression/results.regressions | 2 +-
08-update_baseline/console.log | 2 +-
08-update_baseline/results.regressions | 2 +-
console.log | 26136 +++++++++++++++---------------
jenkins/manifest.sh | 14 +-
12 files changed, 26107 insertions(+), 26183 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-master-arm-lts-defconfig
in repository toolchain/ci/base-artifacts.
discards 7fb5a41be 0: update: binutils-gcc-linux: boot
new 3c818da99 0: update: binutils-gcc-linux: 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 (7fb5a41be)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-arm-lt [...]
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 | 129 +-
02-prepare_abe/console.log | 396 +-
03-build_abe-binutils/console.log | 11501 +++++-----
04-build_abe-stage1/console.log | 20397 +++++++++---------
05-build_linux/console.log | 820 +-
06-boot_linux/console.log | 470 +-
07-check_regression/console.log | 12 +-
07-check_regression/results.regressions | 2 +-
08-update_baseline/console.log | 12 +-
08-update_baseline/results.regressions | 2 +-
console.log | 33737 +++++++++++++++---------------
jenkins/manifest.sh | 18 +-
12 files changed, 33789 insertions(+), 33707 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 579d235ddcf lto: Fix typo in comment of gcc/lto/lto-symtab.c
new 1be4878116a Fix middle-end/85811: Introduce tree_expr_maybe_non_p et al.
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:
gcc/builtins.c | 26 ++--
gcc/fold-const.c | 262 ++++++++++++++++++++++++++++++++-
gcc/fold-const.h | 7 +
gcc/match.pd | 20 ++-
gcc/testsuite/gcc.dg/fold-isfinite-1.c | 21 +++
gcc/testsuite/gcc.dg/fold-isfinite-2.c | 21 +++
gcc/testsuite/gcc.dg/fold-isinf-1.c | 21 +++
gcc/testsuite/gcc.dg/fold-isinf-2.c | 21 +++
gcc/testsuite/gcc.dg/fold-isnan-1.c | 21 +++
gcc/testsuite/gcc.dg/fold-isnan-2.c | 21 +++
gcc/testsuite/gcc.dg/pr85811.c | 15 ++
11 files changed, 443 insertions(+), 13 deletions(-)
create mode 100644 gcc/testsuite/gcc.dg/fold-isfinite-1.c
create mode 100644 gcc/testsuite/gcc.dg/fold-isfinite-2.c
create mode 100644 gcc/testsuite/gcc.dg/fold-isinf-1.c
create mode 100644 gcc/testsuite/gcc.dg/fold-isinf-2.c
create mode 100644 gcc/testsuite/gcc.dg/fold-isnan-1.c
create mode 100644 gcc/testsuite/gcc.dg/fold-isnan-2.c
create mode 100644 gcc/testsuite/gcc.dg/pr85811.c
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.