This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch master
in repository gcc.
from 01d043c836d S/390: Remove code duplication in vec_unordered<mode>
new 489e786b57f [x86] Cache result of expensive_function_p between frame layouts
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 | 8 ++++++++
gcc/config/i386/i386.c | 19 ++++++++++++++++---
gcc/config/i386/i386.h | 5 +++++
3 files changed, 29 insertions(+), 3 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-allnoconfig
in repository toolchain/ci/base-artifacts.
discards aa2ae10a 0: update: llvm-linux: all
new d4b3291d 0: update: llvm-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 (aa2ae10a)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-arm-s [...]
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 | 168 +-
02-build_llvm/console.log | 12173 ++++++-------
03-build_linux/console.log | 24294 ++++++++++++-------------
04-boot_linux/console.log | 2 +-
05-check_regression/console.log | 8 +-
console.log | 36645 +++++++++++++++++++-------------------
jenkins/manifest.sh | 8 +-
7 files changed, 36650 insertions(+), 36648 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 binutils-gdb.
from 4a56a52007 Disable all warnings in gdb.rust/traits.rs
new 6fb08628e0 Use std::sort instead of qsort in minsyms.c
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:
gdb/ChangeLog | 8 ++++++++
gdb/minsyms.c | 38 ++++++++++++++++----------------------
2 files changed, 24 insertions(+), 22 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-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 2ed39513 0: update: llvm-linux: all
new 60e38018 0: update: llvm-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 (2ed39513)
\
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 | 184 +-
02-build_llvm/console.log | 11954 +++++++++++++++++------------------
03-build_linux/console.log | 686 +-
04-boot_linux/console.log | 2 +-
05-check_regression/console.log | 8 +-
06-update_baseline/console.log | 8 +-
console.log | 12859 +++++++++++++++++++-------------------
jenkins/manifest.sh | 8 +-
8 files changed, 12867 insertions(+), 12842 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 llvm.
from c3653dcda66 Revert "[MC] Emit unused undefined symbol even if its bindi [...]
new a58dc36a768 Fix build warning for r373240.
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:
include/llvm/CodeGen/MachineModuleInfo.h | 3 ++-
1 file changed, 2 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 clang.
from 5d31b2abee Fix buildbot failure from r373217 (don't match metadata id exactly)
new 051067842e [OPENMP50]Do not emit warning for the function with the curr [...]
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:
lib/Sema/SemaOpenMP.cpp | 5 +++--
test/OpenMP/declare_variant_messages.c | 6 +++++-
test/OpenMP/declare_variant_messages.cpp | 6 +++++-
3 files changed, 13 insertions(+), 4 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-defconfig
in repository toolchain/ci/base-artifacts.
discards 2bfd4761 0: update: llvm-linux: boot
new 826b1d7c 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 (2bfd4761)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-arm-s [...]
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 | 264 +-
02-build_llvm/console.log | 12175 +-
03-build_linux/console.log | 263912 ++++++++++++++++++------------------
04-boot_linux/console.log | 472 +-
console.log | 275770 +++++++++++++++++++-------------------
jenkins/manifest.sh | 8 +-
6 files changed, 276314 insertions(+), 276287 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.