This is an automated email from the git hooks/post-receive script.
"Maxim Kuvyrkov pushed a change to branch llvm-kernel
in repository toolchain/jenkins-scripts.
discards 37f180c tcwg-rr-llvm-kernel.sh: New job script.
new 367f8d7 tcwg-rr-llvm-kernel.sh: New job script.
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 (37f180c)
\
N -- N -- N refs/heads/llvm-kernel (367f8d7)
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:
tcwg-rr-llvm-kernel.sh | 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.
unknown user pushed a change to branch master
in repository gcc.
from 009d78d802d Fix bootstrap with --enable-fully-dynamic-string
new 576bc6e9e0b * expmed.h (canonicalize_comparison): New declaration. * [...]
new 2bf45a0ac7d Remove rtl.texi references to old RTX code class names
The 2 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 | 14 ++++
gcc/doc/rtl.texi | 29 ++++---
gcc/expmed.c | 93 ++++++++++++++++++++++
gcc/expmed.h | 2 +
gcc/optabs.c | 3 +
gcc/rtl.h | 9 +++
gcc/testsuite/ChangeLog | 4 +
.../gcc.target/aarch64/imm_choice_comparison.c | 54 +++++++++++++
8 files changed, 195 insertions(+), 13 deletions(-)
create mode 100644 gcc/testsuite/gcc.target/aarch64/imm_choice_comparison.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/llvm-kernel-aarch64-tested
in repository toolchain/llvm/llvm.
from 89bba358f5f Add support for AVX-512 CodeView registers.
adds 6a67b308fac Fix -Wmicrosoft-goto warnings.
adds fd8c4124545 [MC][X86] Enhance X86 Register expression handling to more [...]
No new revisions were added by this update.
Summary of changes:
include/llvm/MC/MCExpr.h | 2 ++
include/llvm/MC/MCParser/MCAsmParserUtils.h | 2 +-
include/llvm/MC/MCParser/MCTargetAsmParser.h | 6 +++---
lib/Demangle/MicrosoftDemangle.cpp | 20 +++++++++++++-------
lib/MC/MCExpr.cpp | 16 +++++++++++++++-
lib/MC/MCParser/AsmParser.cpp | 23 ++++++++++-------------
lib/Target/X86/AsmParser/X86AsmParser.cpp | 14 ++++++++------
lib/Target/X86/MCTargetDesc/X86MCExpr.h | 7 ++++++-
test/MC/X86/pr37425.s | 18 +++++++++++-------
9 files changed, 69 insertions(+), 39 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 89bba358f5f Add support for AVX-512 CodeView registers.
new 6a67b308fac Fix -Wmicrosoft-goto warnings.
new fd8c4124545 [MC][X86] Enhance X86 Register expression handling to more [...]
The 2 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/MC/MCExpr.h | 2 ++
include/llvm/MC/MCParser/MCAsmParserUtils.h | 2 +-
include/llvm/MC/MCParser/MCTargetAsmParser.h | 6 +++---
lib/Demangle/MicrosoftDemangle.cpp | 20 +++++++++++++-------
lib/MC/MCExpr.cpp | 16 +++++++++++++++-
lib/MC/MCParser/AsmParser.cpp | 23 ++++++++++-------------
lib/Target/X86/AsmParser/X86AsmParser.cpp | 14 ++++++++------
lib/Target/X86/MCTargetDesc/X86MCExpr.h | 7 ++++++-
test/MC/X86/pr37425.s | 18 +++++++++++-------
9 files changed, 69 insertions(+), 39 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.
"Maxim Kuvyrkov pushed a change to branch llvm-kernel
in repository toolchain/jenkins-scripts.
discards 49ad6a7 tcwg-rr-llvm-kernel.sh: New job script.
new 37f180c tcwg-rr-llvm-kernel.sh: New job script.
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 (49ad6a7)
\
N -- N -- N refs/heads/llvm-kernel (37f180c)
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:
tcwg-rr-llvm-kernel.sh | 4 ++--
1 file changed, 2 insertions(+), 2 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.
"Maxim Kuvyrkov pushed a change to branch llvm-kernel
in repository toolchain/jenkins-scripts.
discards 8821778 tcwg-rr-llvm-kernel.sh: New job script.
new 49ad6a7 tcwg-rr-llvm-kernel.sh: New job script.
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 (8821778)
\
N -- N -- N refs/heads/llvm-kernel (49ad6a7)
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:
tcwg-rr-llvm-kernel.sh | 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 llvm.
from 37d2a3546f0 [TableGen] Avoid self getPredicates() != comparison. NFCI.
new 5ae4a74cc0d [ConstantFolding] add tests for funnel shift intrinsics; NFC
new fc96bec77d1 [TableGen] TypeSetByHwMode::operator== optimization
new 8d7767b85e2 [MS Demangler] Don't fail on MD5-mangled names.
new 404ae7db546 [MS Demangler] Demangle string literals.
new 89bba358f5f Add support for AVX-512 CodeView registers.
The 5 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:
.../llvm/DebugInfo/CodeView/CodeViewRegisters.def | 59 ++
lib/Demangle/MicrosoftDemangle.cpp | 414 ++++++++++-
lib/Target/X86/MCTargetDesc/X86MCTargetDesc.cpp | 284 ++++----
test/Analysis/ConstantFolding/funnel-shift.ll | 89 +++
test/Demangle/ms-md5.test | 11 +
test/Demangle/ms-string-literals.test | 758 +++++++++++++++++++++
utils/TableGen/CodeGenDAGPatterns.cpp | 18 +-
7 files changed, 1508 insertions(+), 125 deletions(-)
create mode 100644 test/Analysis/ConstantFolding/funnel-shift.ll
create mode 100644 test/Demangle/ms-md5.test
create mode 100644 test/Demangle/ms-string-literals.test
--
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.
"Maxim Kuvyrkov pushed a change to branch llvm-kernel
in repository toolchain/jenkins-scripts.
discards e9d57e1 tcwg-rr-llvm-kernel.sh: New job script.
new 8821778 tcwg-rr-llvm-kernel.sh: New job script.
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 (e9d57e1)
\
N -- N -- N refs/heads/llvm-kernel (8821778)
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:
tcwg-rr-llvm-kernel.sh | 14 +++++++++++---
1 file changed, 11 insertions(+), 3 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.