[llvm-bugs] [Bug 41369] New: llvm oss-fuzz build broken

https://bugs.llvm.org/show_bug.cgi?id=41369 Bug ID: 41369 Summary: llvm oss-fuzz build broken Product: new-bugs Version: unspecified Hardware: PC OS: All Status: NEW Severity: enhancement

[llvm-bugs] [Bug 41368] New: clang++ accepts self-referring static member initialization

https://bugs.llvm.org/show_bug.cgi?id=41368 Bug ID: 41368 Summary: clang++ accepts self-referring static member initialization Product: clang Version: 8.0 Hardware: PC OS: Linux Status: NEW

[llvm-bugs] [Bug 41366] New: `__builtin_hypot` is lowered incorrectly on Windows

https://bugs.llvm.org/show_bug.cgi?id=41366 Bug ID: 41366 Summary: `__builtin_hypot` is lowered incorrectly on Windows Product: libraries Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity:

[llvm-bugs] [Bug 41365] New: [codeview] Clang should use a better DISubprogram name for dynamic initializer functions

https://bugs.llvm.org/show_bug.cgi?id=41365 Bug ID: 41365 Summary: [codeview] Clang should use a better DISubprogram name for dynamic initializer functions Product: clang Version: unspecified Hardware: PC

[llvm-bugs] [Bug 41364] New: `operator new(size_t, align_val_t)` doesn't work in a module

https://bugs.llvm.org/show_bug.cgi?id=41364 Bug ID: 41364 Summary: `operator new(size_t, align_val_t)` doesn't work in a module Product: clang Version: 8.0 Hardware: PC OS: All Status: NEW

[llvm-bugs] [Bug 41363] New: ARM backend doesn't realize when behavior of left shift of 32 can be used to eliminate branches

https://bugs.llvm.org/show_bug.cgi?id=41363 Bug ID: 41363 Summary: ARM backend doesn't realize when behavior of left shift of 32 can be used to eliminate branches Product: new-bugs Version: 8.0 Hardware: PC

[llvm-bugs] [Bug 38727] clang-format consumes all available memory formatting Doug Lea`s malloc

https://bugs.llvm.org/show_bug.cgi?id=38727 Vlad Bespalov changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[llvm-bugs] Issue 14045 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-strength_reduce: Timeout in llvm_llvm-opt-fuzzer--x86_64-strength_reduce

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,

[llvm-bugs] [Bug 37501] Assertion failure in clang::ento::ExprEngine::VisitLogicalExpr(...): N->pred_size() == 1

https://bugs.llvm.org/show_bug.cgi?id=37501 Artem Dergachev changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED

[llvm-bugs] [Bug 40323] incorrect static object initialization on Windows

https://bugs.llvm.org/show_bug.cgi?id=40323 Jennifer Yu changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|---

[llvm-bugs] [Bug 41239] Assertion failure at clang/lib/Basic/SourceManager.cpp:1370 in SrcMgr::CharacteristicKind clang::SourceManager::getFileCharacteristic(clang::SourceLocation) const: Loc.isValid(

https://bugs.llvm.org/show_bug.cgi?id=41239 Artem Dergachev changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|---

[llvm-bugs] [Bug 41362] New: Referencing LLVMConstGEP2 or LLVMConstInBoundsGEP2 in Core.h leads to link errors

https://bugs.llvm.org/show_bug.cgi?id=41362 Bug ID: 41362 Summary: Referencing LLVMConstGEP2 or LLVMConstInBoundsGEP2 in Core.h leads to link errors Product: libraries Version: 8.0 Hardware: PC OS: All

[llvm-bugs] [Bug 41361] New: [AMDGPU][MC][GFX9] Incorrect parsing of op_sel* and neg_* modifiers

https://bugs.llvm.org/show_bug.cgi?id=41361 Bug ID: 41361 Summary: [AMDGPU][MC][GFX9] Incorrect parsing of op_sel* and neg_* modifiers Product: libraries Version: trunk Hardware: PC OS: All

[llvm-bugs] Issue 13260 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Out-of-memory in llvm_llvm-microsoft-demangle-fuzzer

Comment #3 on issue 13260 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: Out-of-memory in llvm_llvm-microsoft-demangle-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13260#c3 Fix for all of these: https://reviews.llvm.org/D60207 -- You received this message

[llvm-bugs] Issue 12897 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Heap-buffer-overflow in llvm::ms_demangle::Node** llvm::ms_demangle::ArenaAllocator::allocArray

Comment #5 on issue 12897 by infe...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: Heap-buffer-overflow in llvm::ms_demangle::Node** llvm::ms_demangle::ArenaAllocator::allocArray https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12897#c5 Can you try accessing it again. -- You

[llvm-bugs] Issue 13260 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Out-of-memory in llvm_llvm-microsoft-demangle-fuzzer

Comment #2 on issue 13260 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: Out-of-memory in llvm_llvm-microsoft-demangle-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13260#c2 The original test case is '? @@ YMMC@' The slightly shorter one '? @@ YC@'

[llvm-bugs] Issue 12897 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Heap-buffer-overflow in llvm::ms_demangle::Node** llvm::ms_demangle::ArenaAllocator::allocArray

Comment #4 on issue 12897 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: Heap-buffer-overflow in llvm::ms_demangle::Node** llvm::ms_demangle::ArenaAllocator::allocArray https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12897#c4 https://reviews.llvm.org/D60202 fixes at

[llvm-bugs] Issue 12432 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: QN->Components->Count >= 2

Comment #5 on issue 12432 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: QN->Components->Count >= 2 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12432#c5 Fix: https://reviews.llvm.org/D60206 -- You received this message because: 1. You were specifically CC'd

[llvm-bugs] Issue 12429 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Global-buffer-overflow in llvm::ms_demangle::Demangler::demangleFunctionIdentifierCode

Comment #5 on issue 12429 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: Global-buffer-overflow in llvm::ms_demangle::Demangler::demangleFunctionIdentifierCode https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12429#c5 Fix: https://reviews.llvm.org/D60204 -- You received

[llvm-bugs] Issue 12468 in oss-fuzz: llvm/clang-fuzzer: ASSERT: !Old || Old->getCachedLinkage() == D->getCachedLinkage()

Updates: Labels: Deadline-Approaching Comment #4 on issue 12468 by sheriff...@chromium.org: llvm/clang-fuzzer: ASSERT: !Old || Old->getCachedLinkage() == D->getCachedLinkage() https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12468#c4 This bug is approaching its deadline for

[llvm-bugs] Issue 12428 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: !empty()

Comment #5 on issue 12428 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: ASSERT: !empty() https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12428#c5 Fix: https://reviews.llvm.org/D60204 -- You received this message because: 1. You were specifically CC'd on the issue You

[llvm-bugs] Issue 12435 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::ms_demangle::Demangler::demangleVariableEncoding

Comment #5 on issue 12435 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::ms_demangle::Demangler::demangleVariableEncoding https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12435#c5 Fix: https://reviews.llvm.org/D60202 -- You received this

[llvm-bugs] Issue 12438 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::microsoftDemangle

Comment #5 on issue 12438 by tha...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::microsoftDemangle https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12438#c5 Fix: https://reviews.llvm.org/D60202 -- You received this message because: 1. You were

[llvm-bugs] [Bug 41305] --rename-section flags should be case insensitive

https://bugs.llvm.org/show_bug.cgi?id=41305 James Henderson changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|---

[llvm-bugs] [Bug 41337] ctpop/popcount missing folds

https://bugs.llvm.org/show_bug.cgi?id=41337 David Bolvansky changed: What|Removed |Added Status|NEW |RESOLVED Fixed By Commit(s)|

[llvm-bugs] [Bug 41360] New: Set of pointer to incomplete type gives wrong warning message.

https://bugs.llvm.org/show_bug.cgi?id=41360 Bug ID: 41360 Summary: Set of pointer to incomplete type gives wrong warning message. Product: libc++ Version: unspecified Hardware: All OS: All

[llvm-bugs] [Bug 41359] New: [TargetLowering] Merge preferShiftsToClearExtremeBits into shouldFoldShiftPairToMask

https://bugs.llvm.org/show_bug.cgi?id=41359 Bug ID: 41359 Summary: [TargetLowering] Merge preferShiftsToClearExtremeBits into shouldFoldShiftPairToMask Product: libraries Version: trunk Hardware: PC OS:

[llvm-bugs] [Bug 41358] New: Bad codegen for rotate ops

https://bugs.llvm.org/show_bug.cgi?id=41358 Bug ID: 41358 Summary: Bad codegen for rotate ops Product: libraries Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority:

[llvm-bugs] [Bug 41204] 8.0 regression: Search to crt*.o fails on mips64el

https://bugs.llvm.org/show_bug.cgi?id=41204 Simon Atanasyan changed: What|Removed |Added Fixed By Commit(s)||357506 Resolution|---

[llvm-bugs] [Bug 41221] [meta] 8.0.1 Release Blockers

https://bugs.llvm.org/show_bug.cgi?id=41221 Bug 41221 depends on bug 41204, which changed state. Bug 41204 Summary: 8.0 regression: Search to crt*.o fails on mips64el https://bugs.llvm.org/show_bug.cgi?id=41204 What|Removed |Added

[llvm-bugs] Issue 14038 in oss-fuzz: llvm: Build failure

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,

[llvm-bugs] [Bug 41356] New: LLD does not handle " " in InputSectionDescriptions correctly

https://bugs.llvm.org/show_bug.cgi?id=41356 Bug ID: 41356 Summary: LLD does not handle " " in InputSectionDescriptions correctly Product: lld Version: unspecified Hardware: All OS: All Status: