[llvm-bugs] [Bug 36997] New: lit: unable to parse tools/lldb/lit/lit.cfg

https://bugs.llvm.org/show_bug.cgi?id=36997 Bug ID: 36997 Summary: lit: unable to parse tools/lldb/lit/lit.cfg Product: lldb Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: normal

[llvm-bugs] [Bug 35999] [AMDGPU][MC] Image atomics should support 3-element addresses

https://bugs.llvm.org/show_bug.cgi?id=35999 Dmitry changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[llvm-bugs] [Bug 36958] [AMDGPU][MC][SI][CI] Missing instruction TBUFFER_LOAD_FORMAT_XYZ

https://bugs.llvm.org/show_bug.cgi?id=36958 Dmitry changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[llvm-bugs] [Bug 36998] New: [LLVM-COV] In the for (; ; ) loop, a goto statement will lead an incorrect code coverage in llvm-cov

https://bugs.llvm.org/show_bug.cgi?id=36998 Bug ID: 36998 Summary: [LLVM-COV] In the for (;;) loop, a goto statement will lead an incorrect code coverage in llvm-cov Product: clang Version: trunk Hardware: PC

[llvm-bugs] [Bug 36999] New: Crash in compilation time with std::bad_alloc when using vector::emplace_back

https://bugs.llvm.org/show_bug.cgi?id=36999 Bug ID: 36999 Summary: Crash in compilation time with std::bad_alloc when using vector::emplace_back Product: clang Version: 4.0 Hardware: PC OS: Linux

[llvm-bugs] [Bug 37000] New: Assertion `NumValues == VTs.NumVTs && "NumValues wasn't wide enough for its operands!"' failed

https://bugs.llvm.org/show_bug.cgi?id=37000 Bug ID: 37000 Summary: Assertion `NumValues == VTs.NumVTs && "NumValues wasn't wide enough for its operands!"' failed Product: tools Version: trunk Hardware: PC OS

[llvm-bugs] Issue 6716 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: NumValues == VTs.NumVTs && "NumValues wasn't wide enough for its operands!"

Comment #2 on issue 6716 by gli...@chromium.org: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: NumValues == VTs.NumVTs && "NumValues wasn't wide enough for its operands!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6716#c2 I've also hit a similar bug today, filed https://bugs.llvm.

[llvm-bugs] [Bug 37001] New: [LLVM-COV] a pointer assignment after the return statement is wrongly marked as executed in llvm-cov

https://bugs.llvm.org/show_bug.cgi?id=37001 Bug ID: 37001 Summary: [LLVM-COV] a pointer assignment after the return statement is wrongly marked as executed in llvm-cov Product: clang Version: trunk Hardware: PC

[llvm-bugs] [Bug 37002] New: MIPS: Does not attempt to build anything when GCC 7 is the host compiler

https://bugs.llvm.org/show_bug.cgi?id=37002 Bug ID: 37002 Summary: MIPS: Does not attempt to build anything when GCC 7 is the host compiler Product: compiler-rt Version: unspecified Hardware: PC OS: Linux

[llvm-bugs] Issue 5236 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::Parser::ConsumeAndStoreUntil

Updates: Labels: Deadline-Approaching Comment #3 on issue 5236 by sheriff...@chromium.org: llvm/clang-fuzzer: Stack-overflow in clang::Parser::ConsumeAndStoreUntil https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5236#c3 This bug is approaching its deadline for being fixed, and w

[llvm-bugs] Issue 5250 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: ((OffsetImm & 1) == 0) && "Unexpected offset to merge"

Updates: Labels: Deadline-Approaching Comment #3 on issue 5250 by sheriff...@chromium.org: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: ((OffsetImm & 1) == 0) && "Unexpected offset to merge" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5250#c3 This bug is approaching its dead

[llvm-bugs] [Bug 37003] New: [LLVM-COV] A return statement after the for(; 1; ) return statement is wrongly marked as executed in llvm-cov

https://bugs.llvm.org/show_bug.cgi?id=37003 Bug ID: 37003 Summary: [LLVM-COV] A return statement after the for(;1;) return statement is wrongly marked as executed in llvm-cov Product: clang Version: trunk

[llvm-bugs] [Bug 37004] New: assertion failure in induction variable simplification with zext

https://bugs.llvm.org/show_bug.cgi?id=37004 Bug ID: 37004 Summary: assertion failure in induction variable simplification with zext Product: new-bugs Version: trunk Hardware: PC OS: Windows NT St

[llvm-bugs] [Bug 37005] New: [InstCombine] Incorrect reassociation of loop invariant vector GEP

https://bugs.llvm.org/show_bug.cgi?id=37005 Bug ID: 37005 Summary: [InstCombine] Incorrect reassociation of loop invariant vector GEP Product: new-bugs Version: trunk Hardware: PC OS: All Status:

[llvm-bugs] [Bug 37006] New: lld should typo-correct flags

https://bugs.llvm.org/show_bug.cgi?id=37006 Bug ID: 37006 Summary: lld should typo-correct flags Product: lld Version: unspecified Hardware: PC OS: All Status: NEW Severity: enhancement Priority:

[llvm-bugs] [Bug 37007] New: clang-with-thin-lto-windows failing stage 2 clean without error message

https://bugs.llvm.org/show_bug.cgi?id=37007 Bug ID: 37007 Summary: clang-with-thin-lto-windows failing stage 2 clean without error message Product: new-bugs Version: unspecified Hardware: PC OS: Linux

[llvm-bugs] [Bug 37008] New: parser heap use after free

https://bugs.llvm.org/show_bug.cgi?id=37008 Bug ID: 37008 Summary: parser heap use after free Product: clang Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P

[llvm-bugs] [Bug 37009] New: Assertion Failed: CGOpenMPRuntime::emitCall() when generating source-level debug info

https://bugs.llvm.org/show_bug.cgi?id=37009 Bug ID: 37009 Summary: Assertion Failed: CGOpenMPRuntime::emitCall() when generating source-level debug info Product: clang Version: trunk Hardware: PC OS: Linux

[llvm-bugs] [Bug 37010] New: Large call sequence causes FastISel compile time problems

https://bugs.llvm.org/show_bug.cgi?id=37010 Bug ID: 37010 Summary: Large call sequence causes FastISel compile time problems Product: libraries Version: trunk Hardware: PC OS: Windows NT Status:

[llvm-bugs] [Bug 37011] New: linker script: SIZEOF(.empty.output.section) != 0

https://bugs.llvm.org/show_bug.cgi?id=37011 Bug ID: 37011 Summary: linker script: SIZEOF(.empty.output.section) != 0 Product: lld Version: unspecified Hardware: Other OS: other Status: NEW Severity: enhanc

[llvm-bugs] [Bug 37012] New: [LLVM-COV] A statement with no side effect after the break statement is wrongly marked as executed in llvm-cov

https://bugs.llvm.org/show_bug.cgi?id=37012 Bug ID: 37012 Summary: [LLVM-COV] A statement with no side effect after the break statement is wrongly marked as executed in llvm-cov Product: clang Version: trunk

[llvm-bugs] Issue 7398 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in Evaluate

Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, llvm-b...@lists.llvm.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzze