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-mainline-allnoconfig
in repository toolchain/ci/gcc.
from c1379a1c645 Fix problematic TLS sequences for the Solaris linker
adds 2d625a6d4bb Daily bump.
adds 49805533139 match.pd: Disallow side-effects in GENERIC for non-COND_EXP [...]
No new revisions were added by this update.
Summary of changes:
gcc/ChangeLog | 7 +++++++
gcc/DATESTAMP | 2 +-
gcc/match.pd | 3 ++-
gcc/testsuite/ChangeLog | 7 +++++++
gcc/testsuite/gcc.c-torture/execute/pr93744-1.c | 14 ++++++++++++++
gcc/testsuite/gcc.c-torture/execute/pr93744-2.c | 21 +++++++++++++++++++++
gcc/testsuite/gcc.c-torture/execute/pr93744-3.c | 21 +++++++++++++++++++++
7 files changed, 73 insertions(+), 2 deletions(-)
create mode 100644 gcc/testsuite/gcc.c-torture/execute/pr93744-1.c
create mode 100644 gcc/testsuite/gcc.c-torture/execute/pr93744-2.c
create mode 100644 gcc/testsuite/gcc.c-torture/execute/pr93744-3.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-mainline-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 3cd3231f 0: update: binutils-gcc-linux: boot
new e1c9faf2 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 (3cd3231f)
\
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 | 220 +-
02-prepare_abe/console.log | 428 +-
03-build_abe-binutils/console.log | 11524 ++++++++--------
04-build_abe-stage1/console.log | 13675 ++++++++++---------
05-build_linux/console.log | 694 +-
06-boot_linux/console.log | 4 +-
07-check_regression/console.log | 10 +-
08-update_baseline/console.log | 10 +-
console.log | 26565 ++++++++++++++++++------------------
jenkins/manifest.sh | 12 +-
10 files changed, 26586 insertions(+), 26556 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-master-aarch64-lts-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 7bc1f7c2 10: update: llvm-linux: 17560
new ff7081d7 10: update: llvm-linux: 17560
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 (7bc1f7c2)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-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 | 162 +-
02-build_llvm/console.log | 12642 ++++++++++++-------------
03-build_linux/console.log | 6384 +++++++------
05-check_regression/console.log | 2 +-
06-update_baseline/console.log | 12 +-
console.log | 19202 +++++++++++++++++++-------------------
jenkins/manifest.sh | 8 +-
7 files changed, 19204 insertions(+), 19208 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-master-arm-lts-defconfig
in repository toolchain/ci/base-artifacts.
discards e2ff9bfa 0: update: llvm-linux: boot
new 8501dc27 0: update: llvm-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 (e2ff9bfa)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-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 | 48 +-
02-build_llvm/console.log | 12692 ++++++++++++++++----------------
03-build_linux/console.log | 1772 +++--
04-boot_linux/console.log | 388 +-
05-check_regression/console.log | 2 +-
06-update_baseline/console.log | 2 +-
console.log | 14904 +++++++++++++++++++-------------------
jenkins/manifest.sh | 8 +-
8 files changed, 14906 insertions(+), 14910 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/gnu-release-aarch64-bootstrap_O1
in repository toolchain/ci/base-artifacts.
discards 77b506ee 0: update: gcc-7276dd4c7480dd952f0d4a9322ca04ca29f5126f: 1
new ca2c9fd2 0: update: gcc-498055331393d3c32fea5a6142c926b6a7700b8d: 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 (77b506ee)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu/gnu-release-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 | 204 +-
02-prepare_abe/console.log | 430 +-
03-build_abe-bootstrap_O1/console.log | 65390 ++++++++++++++++---------------
05-check_regression/console.log | 2 +-
06-update_baseline/console.log | 2 +-
console.log | 66026 ++++++++++++++++----------------
jenkins/manifest.sh | 8 +-
7 files changed, 66029 insertions(+), 66033 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.