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-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 5cb542d4 2: update: binutils-gcc-linux: 17065
new b52e5aad 2: update: binutils-gcc-linux-qemu: 18035
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 (5cb542d4)
\
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 | 181 +-
02-prepare_abe/console.log | 440 +-
03-build_abe-binutils/console.log | 11661 +++---
04-build_abe-stage1/console.log | 20450 +++++-----
05-build_linux/console.log | 7383 ++--
07-check_regression/results.regressions | 11 -
.../console.log | 12 +-
08-check_regression/results.regressions | 11 +
08-update_baseline/console.log | 104 -
08-update_baseline/results.regressions | 11 -
09-update_baseline/console.log | 104 +
09-update_baseline/results.regressions | 11 +
console.log | 40271 ++++++++++---------
jenkins/manifest.sh | 22 +-
results | 2 +-
15 files changed, 40513 insertions(+), 40161 deletions(-)
delete mode 100644 07-check_regression/results.regressions
rename {07-check_regression => 08-check_regression}/console.log (87%)
create mode 100644 08-check_regression/results.regressions
delete mode 100644 08-update_baseline/console.log
delete mode 100644 08-update_baseline/results.regressions
create mode 100644 09-update_baseline/console.log
create mode 100644 09-update_baseline/results.regressions
--
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 59482fa1e72 i386: Make -march=x86-64-v[234] behave more like other -mar [...]
new cab1b0ebc00 lto: set nthreads_var to 1 if it is zero
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/lto-wrapper.c | 2 ++
1 file changed, 2 insertions(+)
--
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-arm-next-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 4069f5d7 0: update: llvm-linux: all
new de8ecd7b 0: update: llvm-linux-qemu: all
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 (4069f5d7)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-release-arm- [...]
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 | 175 +-
02-build_llvm/console.log | 6411 -------
02-prepare_abe/console.log | 254 +
03-build_linux/console.log | 387 -
03-build_llvm/console.log | 6671 ++++++++
04-boot_linux/console.log | 333 -
04-build_linux/console.log | 387 +
05-build_abe-qemu/console.log | 2388 +++
06-boot_linux/console.log | 11 +
06-update_baseline/console.log | 99 -
.../console.log | 4 +-
.../results.regressions | 0
.../console.log | 24 +-
.../results.regressions | 0
console.log | 16790 +++++++++++--------
jenkins/manifest.sh | 19 +-
results | 2 +-
17 files changed, 19469 insertions(+), 14486 deletions(-)
delete mode 100644 02-build_llvm/console.log
create mode 100644 02-prepare_abe/console.log
delete mode 100644 03-build_linux/console.log
create mode 100644 03-build_llvm/console.log
delete mode 100644 04-boot_linux/console.log
create mode 100644 04-build_linux/console.log
create mode 100644 05-build_abe-qemu/console.log
create mode 100644 06-boot_linux/console.log
delete mode 100644 06-update_baseline/console.log
copy {05-check_regression => 07-check_regression}/console.log (95%)
rename {05-check_regression => 07-check_regression}/results.regressions (100%)
rename {05-check_regression => 08-update_baseline}/console.log (65%)
rename {06-update_baseline => 08-update_baseline}/results.regressions (100%)
--
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 efd08ad579a gcov: fix line output for nested functions in JSON format
new 59482fa1e72 i386: Make -march=x86-64-v[234] behave more like other -mar [...]
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.gcc | 4 +---
gcc/config/i386/i386-options.c | 11 -----------
gcc/doc/invoke.texi | 5 +++--
gcc/testsuite/gcc.target/i386/x86-64-v2-msabi.c | 5 +++++
gcc/testsuite/gcc.target/i386/x86-64-v2-other.c | 5 +++++
gcc/testsuite/gcc.target/i386/x86-64-v2.c | 6 ++++--
gcc/testsuite/gcc.target/i386/x86-64-v3-msabi.c | 5 +++++
gcc/testsuite/gcc.target/i386/x86-64-v3-other.c | 5 +++++
gcc/testsuite/gcc.target/i386/x86-64-v3.c | 8 +++++---
gcc/testsuite/gcc.target/i386/x86-64-v4-msabi.c | 5 +++++
gcc/testsuite/gcc.target/i386/x86-64-v4-other.c | 5 +++++
gcc/testsuite/gcc.target/i386/x86-64-v4.c | 6 ++++--
12 files changed, 47 insertions(+), 23 deletions(-)
create mode 100644 gcc/testsuite/gcc.target/i386/x86-64-v2-msabi.c
create mode 100644 gcc/testsuite/gcc.target/i386/x86-64-v2-other.c
create mode 100644 gcc/testsuite/gcc.target/i386/x86-64-v3-msabi.c
create mode 100644 gcc/testsuite/gcc.target/i386/x86-64-v3-other.c
create mode 100644 gcc/testsuite/gcc.target/i386/x86-64-v4-msabi.c
create mode 100644 gcc/testsuite/gcc.target/i386/x86-64-v4-other.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-stable-allnoconfig
in repository toolchain/ci/base-artifacts.
discards c929e3cf 0: update: binutils-gcc-linux: boot
new 3f300b46 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 (c929e3cf)
\
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 | 166 +-
02-prepare_abe/console.log | 282 +-
03-build_abe-binutils/console.log | 11813 ++++----
04-build_abe-stage1/console.log | 13900 ++++-----
05-build_linux/console.log | 721 +-
06-boot_linux/console.log | 334 -
06-build_abe-qemu/console.log | 2408 ++
07-boot_linux/console.log | 12 +
07-check_regression/results.regressions | 2 -
.../console.log | 2 +-
08-check_regression/results.regressions | 2 +
08-update_baseline/results.regressions | 2 -
.../console.log | 2 +-
09-update_baseline/results.regressions | 2 +
console.log | 29800 ++++++++++---------
jenkins/manifest.sh | 23 +-
results | 2 +-
17 files changed, 31950 insertions(+), 27523 deletions(-)
delete mode 100644 06-boot_linux/console.log
create mode 100644 06-build_abe-qemu/console.log
create mode 100644 07-boot_linux/console.log
delete mode 100644 07-check_regression/results.regressions
rename {07-check_regression => 08-check_regression}/console.log (98%)
create mode 100644 08-check_regression/results.regressions
delete mode 100644 08-update_baseline/results.regressions
rename {08-update_baseline => 09-update_baseline}/console.log (98%)
create mode 100644 09-update_baseline/results.regressions
--
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 fbbe542f 0: update: linux-39b3342de9bb71531c8d9b41ee0ad901145c7a91: all
new f8b10d63 0: update: qemu-aa14de086675280206dbc1849da6f85b75f62f1b: all
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 (fbbe542f)
\
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 | 165 +-
02-prepare_abe/console.log | 446 +-
03-build_llvm/console.log | 13112 +++++++-------
04-build_linux/console.log | 15434 ++++++++--------
05-build_abe-qemu/console.log | 6633 +++----
06-boot_linux/console.log | 2 +-
07-check_regression/console.log | 4 +-
08-update_baseline/console.log | 250 +-
console.log | 36046 +++++++++++++++++++-------------------
jenkins/manifest.sh | 10 +-
10 files changed, 35785 insertions(+), 36317 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.