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-arm-mainline-allnoconfig
in repository toolchain/ci/gcc.
from e1a08689ce2 Daily bump.
adds a27067c70b7 Put PREFETCHW back to march=broadwell
new 6abef270285 Daily bump.
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 | 5 +++++
gcc/DATESTAMP | 2 +-
gcc/config/i386/i386.h | 3 ++-
gcc/doc/invoke.texi | 25 +++++++++++++------------
4 files changed, 21 insertions(+), 14 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-arm-mainline-allnoconfig
in repository toolchain/ci/base-artifacts.
discards d8ac71108 0: update: binutils-gcc-linux: all
new 6ad3e67ca 0: update: binutils-gcc-linux: 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 (d8ac71108)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-arm-m [...]
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-prepare_abe/console.log | 226 +-
03-build_abe-binutils/console.log | 11174 +++++------
04-build_abe-stage1/console.log | 17890 +++++++++---------
05-build_linux/console.log | 656 +-
06-boot_linux/console.log | 2 +-
07-check_regression/console.log | 2 +-
07-check_regression/results.regressions | 2 +-
08-update_baseline/console.log | 2 +-
08-update_baseline/results.regressions | 2 +-
console.log | 30114 +++++++++++++++---------------
jenkins/manifest.sh | 12 +-
12 files changed, 30124 insertions(+), 30120 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-release-arm-next-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 8766106e2 5: reset: linux-77d8f3068c63ee0983f0b5ba3207d3f7cce11be4: 21099
discards 2fff2ef68 4: update: llvm-linux: 21201
new 81c7d61d8 4: update: llvm-linux: 21203
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 (8766106e2)
\
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 | 214 +-
02-build_llvm/console.log | 12541 ++++++++++++++-------------
03-build_linux/console.log | 882 +-
05-check_regression/console.log | 89 +-
05-check_regression/results.regressions | 7 +-
05-check_regression/trigger-bisect | 3 -
06-update_baseline/console.log | 130 +-
06-update_baseline/results.regressions | 7 +-
console.log | 13856 +++++++++++++++---------------
jenkins/manifest.sh | 14 +-
reset-baseline | 0
results | 8 +-
12 files changed, 14107 insertions(+), 13644 deletions(-)
delete mode 100644 05-check_regression/trigger-bisect
delete 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.
unknown user pushed a change to branch releases/gcc-8
in repository gcc.
from 7dbed9dead9 libstdc++: Fix std::gcd and std::lcm for unsigned integers [...]
new 3182e62d8c2 Daily bump.
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/DATESTAMP | 2 +-
libstdc++-v3/ChangeLog | 22 ++++++++++++++++++++++
2 files changed, 23 insertions(+), 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.
unknown user pushed a change to branch releases/gcc-9
in repository gcc.
from a27067c70b7 Put PREFETCHW back to march=broadwell
new 6abef270285 Daily bump.
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 | 5 +++++
gcc/DATESTAMP | 2 +-
2 files changed, 6 insertions(+), 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.
unknown user pushed a change to branch master
in repository gcc.
from be39636d9f6 Improve code generation for x86_64 [PR 92180]
new 948ef142253 [RS6000] Use LIB2_SIDITI_CONV_FUNCS in place of ppc64-fp.c
new a019766f996 Update documentation for spec files
new 29c5d9ceb9b Daily bump.
The 3 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:
ChangeLog | 4 +
contrib/ChangeLog | 5 +
gcc/ChangeLog | 161 +++++++++++++++++++++++++++
gcc/DATESTAMP | 2 +-
gcc/c-family/ChangeLog | 5 +
gcc/doc/invoke.texi | 115 +++++++++++++++++--
gcc/fortran/ChangeLog | 5 +
gcc/gcc.c | 6 +
gcc/testsuite/ChangeLog | 78 +++++++++++++
libgcc/ChangeLog | 6 +
libgcc/config/rs6000/ppc64-fp.c | 237 ----------------------------------------
libgcc/config/rs6000/t-ppc64-fp | 3 +-
libstdc++-v3/ChangeLog | 6 +
13 files changed, 383 insertions(+), 250 deletions(-)
delete mode 100644 libgcc/config/rs6000/ppc64-fp.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.
unknown user pushed a change to branch releases/gcc-10
in repository gcc.
from 730e1357dfb libstdc++: Remove redundant overflow check for futex timeou [...]
new 89c56456573 Daily bump.
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 | 5 +++++
gcc/DATESTAMP | 2 +-
libstdc++-v3/ChangeLog | 29 +++++++++++++++++++++++++++++
3 files changed, 35 insertions(+), 1 deletion(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.