[llvm-bugs] [Bug 43519] Failing compilation of dereferencing pointer-to-member function in constexpr function context
https://bugs.llvm.org/show_bug.cgi?id=43519 Richard Smith changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Richard Smith --- Fixed in r373553. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43539] New: #pragma clang loop vectorize(disable) should actually disable vectorization
https://bugs.llvm.org/show_bug.cgi?id=43539
Bug ID: 43539
Summary: #pragma clang loop vectorize(disable) should actually
disable vectorization
Product: clang
Version: trunk
Hardware: Other
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: LLVM Codegen
Assignee: unassignedclangb...@nondot.org
Reporter: husseyde...@gmail.com
CC: llvm-bugs@lists.llvm.org, neeil...@live.com,
richard-l...@metafoo.co.uk
**#pragma clang loop vectorize(disable) is useless.**
It only works on tiny loops. Anything relatively complicated will be vectorized
regardless.
(I'm guessing that the cost model overrides it):
#include
#include
uint64_t some_func(uint64_t *p, size_t len)
{
uint64_t sum1 = 0, sum2 = 0;
len &= ~(size_t)3; // always multiple of 4
#pragma clang loop vectorize(disable)
for (size_t i = 0; i < len; i++) {
sum1 += *p++ ^ 12345;
sum2 += *p++ ^ 12345;
}
return sum1 ^ sum2;
}
I'd expect this for aarch64 with -O3 (actual output from
-march=armv8-a+nosimd):
some_func:
// %bb.0:
mov x8, xzr
andsx10, x1, #0xfffc
b.eq.LBB0_4
// %bb.1:
mov x9, xzr
mov x11, xzr
mov x12, xzr
add x13, x0, #16
mov w14, #12345
.LBB0_2:
ldp x15, x16, [x13, #-16]
ldp x17, x0, [x13], #32
subsx10, x10, #2
eor x15, x15, x14
eor x17, x17, x14
eor x16, x16, x14
eor x0, x0, x14
add x11, x15, x11
add x12, x17, x12
add x8, x16, x8
add x9, x0, x9
b.ne.LBB0_2
// %bb.3:
add x10, x12, x11
add x8, x9, x8
.LBB0_4:
eor x0, x8, x10
ret
However, I get this, a clearly vectorized loop:
some_func:
// %bb.0:
andsx8, x1, #0xfffc
b.eq.LBB0_4
// %bb.1:
mov w10, #12345
add x9, x0, #16
moviv0.2d, #
dup v1.2d, x10
moviv2.2d, #
.LBB0_2:
ldp q3, q4, [x9, #-16]
subsx8, x8, #2
add x9, x9, #32
eor v3.16b, v3.16b, v1.16b
eor v4.16b, v4.16b, v1.16b
add v2.2d, v3.2d, v2.2d
add v0.2d, v4.2d, v0.2d
b.ne.LBB0_2
// %bb.3:
add v0.2d, v0.2d, v2.2d
fmovx8, d0
mov x9, v0.d[1]
eor x0, x9, x8
ret
.LBB0_4:
moviv0.2d, #
fmovx8, d0
mov x9, v0.d[1]
eor x0, x9, x8
ret
Similar things are output on SSE2, NEON32, etc.
#pragma clang loop vectorize(disable) needs to completely shut off
vectorization for the loop.
Need I say more?
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43523] [InstCombine] Extract high bits + sext -> Extract high bits with sext
https://bugs.llvm.org/show_bug.cgi?id=43523 Roman Lebedev changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED Fixed By Commit(s)||373542 --- Comment #1 from Roman Lebedev --- There's more opportunities for dropping redundant masking and canonicalizing other variants of (variable) sign-extension, but it seems here only the "basic" pattern exists.. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 17914 in oss-fuzz: llvm:llvm-itanium-demangle-fuzzer: Out-of-memory in llvm-itanium-demangle-fuzzer
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, mit...@google.com, bigchees...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2019-10-02 Type: Bug New issue 17914 by ClusterFuzz-External: llvm:llvm-itanium-demangle-fuzzer: Out-of-memory in llvm-itanium-demangle-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=17914 Detailed Report: https://oss-fuzz.com/testcase?key=5677297201315840 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: llvm-itanium-demangle-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Out-of-memory (exceeds 2048 MB) Crash Address: Crash State: llvm-itanium-demangle-fuzzer Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201901070410:201901080410 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5677297201315840 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. When you fix this bug, please * mention the fix revision(s). * state whether the bug was a short-lived regression or an old bug in any stable releases. * add any other useful information. This information can help downstream consumers. If you need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43427] licm crashes: Assertion `dominates(MP, U) && "Memory PHI does not dominate it's uses"' failed.
https://bugs.llvm.org/show_bug.cgi?id=43427 Alina Sbirlea changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #9 from Alina Sbirlea --- Should be resolved by r373505. Please let me know if you see other issues. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43538] New: Risc-V clang++ does not generate correct .eh_frame data
https://bugs.llvm.org/show_bug.cgi?id=43538
Bug ID: 43538
Summary: Risc-V clang++ does not generate correct .eh_frame
data
Product: clang
Version: 9.0
Hardware: Other
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: C++
Assignee: unassignedclangb...@nondot.org
Reporter: grog...@micron.com
CC: blitzrak...@gmail.com, dgre...@apple.com,
erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk
The attached simple c++ program won't link because lld can't find the correct
information in .eh_frame to relocate things.
#include
int
main() {
printf("thanks for all of the fish\n");
}
mfed04: grogers: tmp $ clang++ main.cpp
ld: error: .eh_frame: relocation is not in any piece
clang-9: error: ld command failed with exit code 1 (use -v to see invocation)
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41772] MachineMemOperand::print - null pointer dereferences
https://bugs.llvm.org/show_bug.cgi?id=41772 Simon Pilgrim changed: What|Removed |Added Fixed By Commit(s)||r373484 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Simon Pilgrim --- The unused print calls were removed at rL373484 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 15749 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-guard_widening: Use-of-uninitialized-value in initStream
Updates: Labels: Deadline-Approaching Comment #3 on issue 15749 by sheriff...@chromium.org: llvm/llvm-opt-fuzzer--x86_64-guard_widening: Use-of-uninitialized-value in initStream https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15749#c3 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 15748 in oss-fuzz: llvm/clang-fuzzer: Null-dereference READ in clang::Decl::AccessDeclContextSanity
Updates: Labels: Deadline-Approaching Comment #2 on issue 15748 by sheriff...@chromium.org: llvm/clang-fuzzer: Null-dereference READ in clang::Decl::AccessDeclContextSanity https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15748#c2 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 15734 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: Abrt in llvm::Expected::fatalUncheckedExpected
Updates: Labels: Deadline-Approaching Comment #2 on issue 15734 by sheriff...@chromium.org: llvm/llvm-isel-fuzzer--x86_64-O2: Abrt in llvm::Expectedint>::fatalUncheckedExpected https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15734#c2 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43129] exhaustive switch with unreachable defaultdest should get cleaned up
https://bugs.llvm.org/show_bug.cgi?id=43129 Hans Wennborg changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #7 from Hans Wennborg --- Re-landed with fix in r373477. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 4068] [Meta] Compiling the Linux kernel with clang
https://bugs.llvm.org/show_bug.cgi?id=4068 Bug 4068 depends on bug 43129, which changed state. Bug 43129 Summary: exhaustive switch with unreachable defaultdest should get cleaned up https://bugs.llvm.org/show_bug.cgi?id=43129 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43537] New: ICE with list-initialization and array of unknown bound
https://bugs.llvm.org/show_bug.cgi?id=43537
Bug ID: 43537
Summary: ICE with list-initialization and array of unknown
bound
Product: clang
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: C++2a
Assignee: unassignedclangb...@nondot.org
Reporter: pola...@redhat.com
CC: blitzrak...@gmail.com, erik.pilking...@gmail.com,
llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk
The following (valid C++20, with P0388R4) code triggers an ICE:
const int ()[]{1};
This is
clang version 8.0.0 (Fedora 8.0.0-1.fc30)
Target: x86_64-unknown-linux-gnu
but trunk seems to crash too.
Stack dump:
0. Program arguments: /usr/bin/clang-8 -cc1 -triple
x86_64-unknown-linux-gnu -emit-obj -mrelax-all -disable-free
-disable-llvm-verifier -discard-value-names -main-file-name clang.C
-mrelocation-model static -mthread-model posix -mdisable-fp-elim -fmath-errno
-masm-verbose -mconstructor-aliases -munwind-tables -fuse-init-array
-target-cpu x86-64 -dwarf-column-info -debugger-tuning=gdb -coverage-notes-file
/home/marek/x/trunk/gcc/clang.gcno -resource-dir /usr/lib64/clang/8.0.0
-internal-isystem
/usr/bin/../lib/gcc/x86_64-redhat-linux/9/../../../../include/c++/9
-internal-isystem
/usr/bin/../lib/gcc/x86_64-redhat-linux/9/../../../../include/c++/9/x86_64-redhat-linux
-internal-isystem
/usr/bin/../lib/gcc/x86_64-redhat-linux/9/../../../../include/c++/9/backward
-internal-isystem /usr/local/include -internal-isystem
/usr/lib64/clang/8.0.0/include -internal-externc-isystem /include
-internal-externc-isystem /usr/include -fdeprecated-macro
-fdebug-compilation-dir /home/marek/x/trunk/gcc -ferror-limit 19
-fmessage-length 107 -fobjc-runtime=gcc -fcxx-exceptions -fexceptions
-fdiagnostics-show-option -fcolor-diagnostics -o clang.o -x c++ clang.C
-faddrsig
1. parser at end of file
2. clang.C:1:13: LLVM IR generation of declaration 'r'
3. clang.C:1:13: Generating code for declaration 'r'
#0 0x7fa3c23ab06e llvm::sys::PrintStackTrace(llvm::raw_ostream&)
(/lib64/libLLVM-8.so+0xabd06e)
#1 0x7fa3c23a9014 llvm::sys::RunSignalHandlers()
(/lib64/libLLVM-8.so+0xabb014)
#2 0x7fa3c23a9195 (/lib64/libLLVM-8.so+0xabb195)
#3 0x7fa3c0729ec0 __restore_rt (/lib64/libc.so.6+0x37ec0)
#4 0x7fa3c12884c6
clang::CodeGen::ConstantEmitter::tryEmitPrivate(clang::APValue const&,
clang::QualType) (/lib64/libclangCodeGen.so.8+0x22e4c6)
#5 0x7fa3c12892aa
clang::CodeGen::ConstantEmitter::tryEmitPrivateForMemory(clang::APValue const&,
clang::QualType) (/lib64/libclangCodeGen.so.8+0x22f2aa)
#6 0x7fa3c13fc860
clang::CodeGen::CodeGenModule::GetAddrOfGlobalTemporary(clang::MaterializeTemporaryExpr
const*, clang::Expr const*) (/lib64/libclangCodeGen.so.8+0x3a2860)
#7 0x7fa3c1288a4d
clang::CodeGen::ConstantEmitter::tryEmitPrivate(clang::APValue const&,
clang::QualType) (/lib64/libclangCodeGen.so.8+0x22ea4d)
#8 0x7fa3c12892aa
clang::CodeGen::ConstantEmitter::tryEmitPrivateForMemory(clang::APValue const&,
clang::QualType) (/lib64/libclangCodeGen.so.8+0x22f2aa)
#9 0x7fa3c128c0ff
clang::CodeGen::ConstantEmitter::tryEmitPrivateForVarInit(clang::VarDecl
const&) (/lib64/libclangCodeGen.so.8+0x2320ff)
#10 0x7fa3c128c3c4
clang::CodeGen::ConstantEmitter::tryEmitForInitializer(clang::VarDecl const&)
(/lib64/libclangCodeGen.so.8+0x2323c4)
#11 0x7fa3c140f1e6
clang::CodeGen::CodeGenModule::EmitGlobalVarDefinition(clang::VarDecl const*,
bool) (/lib64/libclangCodeGen.so.8+0x3b51e6)
#12 0x7fa3c142e0e5
clang::CodeGen::CodeGenModule::EmitGlobalDefinition(clang::GlobalDecl,
llvm::GlobalValue*) (/lib64/libclangCodeGen.so.8+0x3d40e5)
#13 0x7fa3c142e89b
clang::CodeGen::CodeGenModule::EmitGlobal(clang::GlobalDecl)
(/lib64/libclangCodeGen.so.8+0x3d489b)
#14 0x7fa3c14342fd
clang::CodeGen::CodeGenModule::EmitTopLevelDecl(clang::Decl*)
(/lib64/libclangCodeGen.so.8+0x3da2fd)
#15 0x7fa3c14a677f (/lib64/libclangCodeGen.so.8+0x44c77f)
#16 0x7fa3c13d00a1 (/lib64/libclangCodeGen.so.8+0x3760a1)
#17 0x7fa3bfe62214 clang::ParseAST(clang::Sema&, bool, bool)
(/lib64/libclangParse.so.8+0x3c214)
#18 0x7fa3c13d5a61 clang::CodeGenAction::ExecuteAction()
(/lib64/libclangCodeGen.so.8+0x37ba61)
#19 0x7fa3c0da6066 clang::FrontendAction::Execute()
(/lib64/libclangFrontend.so.8+0xef066)
#20 0x7fa3c0d58406
clang::CompilerInstance::ExecuteAction(clang::FrontendAction&)
(/lib64/libclangFrontend.so.8+0xa1406)
#21 0x7fa3c0cb2ac2
clang::ExecuteCompilerInvocation(clang::CompilerInstance*)
(/lib64/libclangFrontendTool.so.8+0x5ac2)
#22 0x55e05a2a2378 cc1_main(llvm::ArrayRef, char const*,
void*) (/usr/bin/clang-8+0x16378)
#23 0x55e05a29deb3 main (/usr/bin/clang-8+0x11eb3)
#24 0x7fa3c0715f43 __libc_start_main
[llvm-bugs] [Bug 43536] New: Static analyzer isa and dyn_cast mismatch for the same pointer
https://bugs.llvm.org/show_bug.cgi?id=43536
Bug ID: 43536
Summary: Static analyzer isa and dyn_cast mismatch for the same
pointer
Product: clang
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: Static Analyzer
Assignee: dcough...@apple.com
Reporter: llvm-...@redking.me.uk
CC: dcough...@apple.com, llvm-bugs@lists.llvm.org,
noqnoq...@gmail.com
https://llvm.org/reports/scan-build/report-LoopCacheAnalysis.cpp-getLastCoefficient-5-1.html#EndPath
const SCEV *IndexedReference::getLastCoefficient() const {
const SCEV *LastSubscript = getLastSubscript();
assert(isa(LastSubscript) &&
"Expecting a SCEV add recurrence expression");
const SCEVAddRecExpr *AR = dyn_cast(LastSubscript);
return AR->getStepRecurrence(SE);
}
The analyzer assumes that LastSubscript is a SCEVAddRecExpr in the assert but
in the following line assumes that it isn't a SCEVAddRecExpr and then warns
about a null dereference.
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43129] exhaustive switch with unreachable defaultdest should get cleaned up
https://bugs.llvm.org/show_bug.cgi?id=43129 Hans Wennborg changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #6 from Hans Wennborg --- Reverted in r373454 due to asserts. Hopefully it's simple to fix.. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 4068] [Meta] Compiling the Linux kernel with clang
https://bugs.llvm.org/show_bug.cgi?id=4068 Bug 4068 depends on bug 43129, which changed state. Bug 43129 Summary: exhaustive switch with unreachable defaultdest should get cleaned up https://bugs.llvm.org/show_bug.cgi?id=43129 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 17943] Clang crash while building libcxx
https://bugs.llvm.org/show_bug.cgi?id=17943 Florian Hahn changed: What|Removed |Added Status|NEW |RESOLVED CC||florian_h...@apple.com Resolution|--- |WORKSFORME --- Comment #6 from Florian Hahn --- I cannot reproduce the issue with current trunk. Please feel free to re-open with a new reproducer, if it is still a problem. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43498] ICE when compiling minisat in LLVM test suite.
https://bugs.llvm.org/show_bug.cgi?id=43498 David Bolvansky changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED Fixed By Commit(s)||r373418 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43129] exhaustive switch with unreachable defaultdest should get cleaned up
https://bugs.llvm.org/show_bug.cgi?id=43129 Hans Wennborg changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #5 from Hans Wennborg --- > I think we just need this: https://reviews.llvm.org/D68131 That was committed in r373431. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 4068] [Meta] Compiling the Linux kernel with clang
https://bugs.llvm.org/show_bug.cgi?id=4068 Bug 4068 depends on bug 43129, which changed state. Bug 43129 Summary: exhaustive switch with unreachable defaultdest should get cleaned up https://bugs.llvm.org/show_bug.cgi?id=43129 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 42701] Assertion `(ResTy == Op0Ty && ResTy == Op1Ty) && "type mismatch`
https://bugs.llvm.org/show_bug.cgi?id=42701 Simon Pilgrim changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #3 from Simon Pilgrim --- (In reply to Andrew Kelley from comment #2) > Can I request the fix to this be merged into the release/9.x branch? That requires a bisect to work out what fixed it - I'm not sure if/when I'll be able to get around to that - are you in a position to try? The fuzz test report indicates it was in the range: 2019-07-24-03-13 : 2019-07-25-03-16 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 32674] LLD COFF .lib files inside .lib files not supported
https://bugs.llvm.org/show_bug.cgi?id=32674 Rui Ueyama changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #21 from Rui Ueyama --- Should be fixed by https://reviews.llvm.org/rL373424 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
