[llvm-bugs] [Bug 93393] libclang 18.1.6 doesn't identify an implicit cast to int from a boolean expression when used inside of an init list

2024-05-25 Thread LLVM Bugs via llvm-bugs
Issue 93393 Summary libclang 18.1.6 doesn't identify an implicit cast to int from a boolean _expression_ when used inside of an init list Labels new issue

[llvm-bugs] [Bug 93391] Assertion `SDNode::getMaxNumOperands() >= Vals.size() && "too many operands to fit into SDNode"' failed.

2024-05-25 Thread LLVM Bugs via llvm-bugs
Issue 93391 Summary Assertion `SDNode::getMaxNumOperands() >= Vals.size() && "too many operands to fit into SDNode"' failed. Labels new issue Assi

[llvm-bugs] [Bug 93390] clang-scan-deps SegFaults when a .cpp file contains an import statement unbordered with ;

2024-05-25 Thread LLVM Bugs via llvm-bugs
Issue 93390 Summary clang-scan-deps SegFaults when a .cpp file contains an import statement unbordered with ; Labels new issue Assignees

[llvm-bugs] [Bug 93389] [Flang] flang-new crashes with "nonscalar intrinsic argument"

2024-05-25 Thread LLVM Bugs via llvm-bugs
ot;:3:10): nonscalar intrinsic argument LLVM ERROR: aborting PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace. Stack dump: 0. Program arguments: /opt/compiler-explorer/clang-llvmflang-trunk-20240525/bin/flang-new -fc1 -triple x86_64-unknown-linux

[llvm-bugs] [Bug 93386] [[gsl::Pointer]] and [[clang::lifetimebound]] produce duplicate (or near-duplicate) warnings for some code locations

2024-05-25 Thread LLVM Bugs via llvm-bugs
Issue 93386 Summary [[gsl::Pointer]] and [[clang::lifetimebound]] produce duplicate (or near-duplicate) warnings for some code locations Labels clang

[llvm-bugs] Issue 69235 in oss-fuzz: llvm:clang-pseudo-fuzzer: Stack-overflow in auto clang::pseudo::glrRecover

2024-05-25 Thread ClusterFuzz-External via monorail via llvm-bugs
Status: New Owner: CC: k...@google.com, masc...@google.com, igm...@gmail.com, sammcc...@google.com, da...@adalogics.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, jo...@devlieghere.com, j...@chromium.org, v...@apple.com, mitch...@ou

[llvm-bugs] Issue 68141 in oss-fuzz: llvm: Coverage build failure

2024-05-25 Thread ClusterFuzz-External via monorail via llvm-bugs
Comment #6 on issue 68141 by ClusterFuzz-External: llvm: Coverage build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68141#c6 Friendly reminder that the build is still failing. Please try to fix this failure to ensure that fuzzing remains productive. Latest build log: https://os

[llvm-bugs] [Bug 93378] [Flang] llvm-project/flang/lib/Lower/Bridge.cpp:2027: void (anonymous namespace)::FirConverter::genFIRIncrementLoopBegin((anonymous namespace)::IncrementLoopNestInfo &): Assert

2024-05-25 Thread LLVM Bugs via llvm-bugs
h into loop body from outside goto 30 ^^^ /app/example.f90:3:1: the loop branched into do 30 concurrent(i=10:0:-2, i/=5) ^ PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace. Stack dump: 0. Program arguments:

[llvm-bugs] [Bug 93375] libc++ test runner fails on Python 3.13: `ModuleNotFoundError: No module named 'pipes'`

2024-05-25 Thread LLVM Bugs via llvm-bugs
Issue 93375 Summary libc++ test runner fails on Python 3.13: `ModuleNotFoundError: No module named 'pipes'` Labels libc++ Assignees