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-allmodconfig
in repository toolchain/ci/binutils-gdb.
from 19892fedb7 x86: Properly check invalid relocation against protected symbol
adds 5c0b4ee406 i386: Don't allow GOTOFF relocation against IFUNC symbol for PIC
No new revisions were added by this update.
Summary of changes:
bfd/elf32-i386.c | 5 +++++
ld/testsuite/ld-i386/pr27998a.d | 2 +-
ld/testsuite/ld-i386/pr27998b.d | 6 +-----
ld/testsuite/ld-ifunc/ifunc-2-i386-now.d | 2 +-
ld/testsuite/ld-ifunc/ifunc-2-i386.s | 2 +-
ld/testsuite/ld-ifunc/ifunc-2-local-i386-now.d | 2 +-
ld/testsuite/ld-ifunc/ifunc-2-local-i386.s | 2 +-
7 files changed, 11 insertions(+), 10 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-mainline-allmodconfig
in repository toolchain/ci/base-artifacts.
discards bc20f0f1 0: update: binutils-gcc-linux-qemu: boot
new 788bf845 0: update: binutils-gcc-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 (bc20f0f1)
\
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 1840 -> 1648 bytes
02-prepare_abe/console.log.xz | Bin 2748 -> 2748 bytes
03-build_abe-binutils/console.log.xz | Bin 30764 -> 30540 bytes
04-build_abe-stage1/console.log.xz | Bin 68188 -> 68016 bytes
05-build_abe-qemu/console.log.xz | Bin 31656 -> 30836 bytes
06-build_linux/console.log.xz | Bin 3492 -> 3348 bytes
07-boot_linux/console.log.xz | Bin 508 -> 508 bytes
08-check_regression/console.log.xz | Bin 412 -> 412 bytes
09-update_baseline/console.log | 16 ++++++++--------
jenkins/manifest.sh | 22 +++++++++++-----------
results | 2 +-
11 files changed, 20 insertions(+), 20 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-stable-defconfig
in repository toolchain/ci/base-artifacts.
discards 4c2d87e9 0: update: binutils-gcc-linux-qemu: boot
new 266cfe13 0: update: binutils-gcc-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 (4c2d87e9)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-arm-st [...]
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 1656 -> 1856 bytes
02-prepare_abe/console.log.xz | Bin 2756 -> 2756 bytes
03-build_abe-binutils/console.log.xz | Bin 30212 -> 30760 bytes
04-build_abe-stage1/console.log.xz | Bin 91368 -> 92748 bytes
05-build_abe-qemu/console.log.xz | Bin 31220 -> 31116 bytes
06-build_linux/console.log.xz | Bin 6624 -> 7224 bytes
07-boot_linux/console.log.xz | Bin 5796 -> 5772 bytes
08-check_regression/console.log.xz | Bin 412 -> 412 bytes
09-update_baseline/console.log | 10 +++++-----
jenkins/manifest.sh | 22 +++++++++++-----------
10 files changed, 16 insertions(+), 16 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-stable-allyesconfig
in repository toolchain/ci/base-artifacts.
from 654a0451 2: update: qemu-5288bee45fbd33203b61f8c76e41b15bb5913e6e: 20387
new a98723cc 3: reset: llvm-2a721374aef326d4668f750d341c86d1aa1a0309: 20386
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 1692 -> 1552 bytes
02-prepare_abe/console.log.xz | Bin 2744 -> 2752 bytes
03-build_abe-binutils/console.log.xz | Bin 29572 -> 29500 bytes
04-build_kernel_llvm/console.log.xz | Bin 65060 -> 64024 bytes
05-build_abe-qemu/console.log.xz | Bin 30712 -> 31964 bytes
06-build_linux/console.log.xz | Bin 6520 -> 6552 bytes
08-check_regression/console.log.xz | Bin 480 -> 1268 bytes
08-check_regression/jira-body.txt | 2 +
08-check_regression/mail-body.txt | 37 +++++++++
08-check_regression/mail-subject.txt | 1 +
08-check_regression/results.regressions | 11 +++
08-check_regression/trigger-bisect | 2 +
09-update_baseline/console.log | 128 +++++---------------------------
jenkins/manifest.sh | 10 +--
mail/jira-body.txt | 5 ++
mail/mail-body.txt | 40 ++++++++++
mail/mail-subject.txt | 1 +
reset-baseline | 0
results | 13 +++-
19 files changed, 134 insertions(+), 116 deletions(-)
create mode 100644 08-check_regression/jira-body.txt
create mode 100644 08-check_regression/mail-body.txt
create mode 100644 08-check_regression/mail-subject.txt
create mode 100644 08-check_regression/results.regressions
create mode 100644 08-check_regression/trigger-bisect
create mode 100644 mail/jira-body.txt
create mode 100644 mail/mail-body.txt
create mode 100644 mail/mail-subject.txt
create mode 100644 reset-baseline
--
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-arm-bootstrap_O3
in repository toolchain/ci/gcc.
from f8e6e2c046e Adding three new function attributes for static analysis of [...]
adds 0e6fa997306 Daily bump.
new 76d6224b944 PR target/106303: Fix TImode STV related failures on x86.
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/ChangeLog | 10 +++
gcc/DATESTAMP | 2 +-
gcc/analyzer/ChangeLog | 15 ++++
gcc/c-family/ChangeLog | 6 ++
gcc/config/i386/i386-features.cc | 116 +++++++++++++++++--------------
gcc/config/i386/i386-features.h | 12 ++--
gcc/testsuite/ChangeLog | 7 ++
gcc/testsuite/gcc.target/i386/pr106303.c | 25 +++++++
gcc/testsuite/gcc.target/i386/pr106347.c | 24 +++++++
9 files changed, 158 insertions(+), 59 deletions(-)
create mode 100644 gcc/testsuite/gcc.target/i386/pr106303.c
create mode 100644 gcc/testsuite/gcc.target/i386/pr106347.c
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.