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-arm
in repository toolchain/ci/gcc.
from 500d3f0a302 RISC-V: fixed testcase riscv/pr103302.c
adds e078de24eae testsuite: Avoid unwanted vecorization [PR95046]
No new revisions were added by this update.
Summary of changes:
gcc/testsuite/gfortran.dg/extract_recip_1.f | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
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-arm
in repository toolchain/ci/base-artifacts.
discards 5e2061291 0: update: binutils-gcc-linux-glibc-gdb-qemu: 7
new 7261f4222 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 (5e2061291)
\
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 1536 -> 1536 bytes
02-prepare_abe/console.log.xz | Bin 2780 -> 2772 bytes
04-build_abe-binutils/console.log.xz | Bin 30240 -> 30004 bytes
05-build_abe-stage1/console.log.xz | Bin 90428 -> 90384 bytes
07-build_abe-linux/console.log.xz | Bin 8592 -> 8600 bytes
08-build_abe-glibc/console.log.xz | Bin 230036 -> 231320 bytes
09-build_abe-stage2/console.log.xz | Bin 216564 -> 217904 bytes
10-build_abe-gdb/console.log.xz | Bin 37752 -> 37756 bytes
11-build_abe-qemu/console.log.xz | Bin 29956 -> 29988 bytes
12-check_regression/console.log.xz | Bin 416 -> 416 bytes
13-update_baseline/console.log | 2 +-
jenkins/manifest.sh | 14 +++++++-------
12 files changed, 8 insertions(+), 8 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-stable-allyesconfig
in repository toolchain/ci/base-artifacts.
discards c20a94483 2: update: binutils-llvm-linux-qemu: 20154
new 187d0fad2 2: update: binutils-llvm-linux-qemu: 20154
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 (c20a94483)
\
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.xz | Bin 1600 -> 1564 bytes
02-prepare_abe/console.log.xz | Bin 2776 -> 2768 bytes
03-build_abe-binutils/console.log.xz | Bin 31612 -> 30308 bytes
04-build_llvm/console.log.xz | Bin 59760 -> 59936 bytes
05-build_abe-qemu/console.log.xz | Bin 30096 -> 30732 bytes
06-build_linux/console.log.xz | Bin 3932 -> 3888 bytes
08-check_regression/console.log.xz | Bin 480 -> 480 bytes
09-update_baseline/console.log | 60 +++++++++++++++++------------------
jenkins/manifest.sh | 16 +++++-----
9 files changed, 38 insertions(+), 38 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_bootstrap/master-aarch64-bootstrap_ubsan
in repository toolchain/ci/binutils-gdb.
from d16ce6240e Automatic date update in version.in
adds 67093b6e1a Automatic date update in version.in
No new revisions were added by this update.
Summary of changes:
bfd/version.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
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_bootstrap/master-aarch64-bootstrap_ubsan
in repository toolchain/ci/base-artifacts.
discards c61f1670e 0: update: binutils-gcc: 2
new b14aeb37d 0: update: binutils-gcc: 2
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 (c61f1670e)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...]
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 1516 -> 1576 bytes
02-prepare_abe/console.log.xz | Bin 2752 -> 2772 bytes
04-build_abe-binutils/console.log.xz | Bin 37444 -> 39048 bytes
05-build_abe-bootstrap_ubsan/console.log.xz | Bin 319568 -> 318476 bytes
06-check_regression/console.log.xz | Bin 420 -> 416 bytes
07-update_baseline/console.log | 36 ----------------------------
jenkins/manifest.sh | 12 +++++-----
7 files changed, 6 insertions(+), 42 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 e078de24eae testsuite: Avoid unwanted vecorization [PR95046]
new 9407058a430 ix86: Don't use the 'm' constraint for x86_64_general_operand
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/config/i386/constraints.md | 10 +
gcc/config/i386/i386.md | 67 +--
gcc/testsuite/gcc.target/i386/pr103762-1a.c | 647 ++++++++++++++++++++++++++++
gcc/testsuite/gcc.target/i386/pr103762-1b.c | 7 +
gcc/testsuite/gcc.target/i386/pr103762-1c.c | 7 +
5 files changed, 706 insertions(+), 32 deletions(-)
create mode 100644 gcc/testsuite/gcc.target/i386/pr103762-1a.c
create mode 100644 gcc/testsuite/gcc.target/i386/pr103762-1b.c
create mode 100644 gcc/testsuite/gcc.target/i386/pr103762-1c.c
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.