[llvm-bugs] [Bug 49141] New: opt -indvars -loop-load-elim fails with old PM
https://bugs.llvm.org/show_bug.cgi?id=49141 Bug ID: 49141 Summary: opt -indvars -loop-load-elim fails with old PM Product: libraries Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Scalar Optimizations Assignee: unassignedb...@nondot.org Reporter: mikael.hol...@ericsson.com CC: llvm-bugs@lists.llvm.org Created attachment 24513 --> https://bugs.llvm.org/attachment.cgi?id=24513&action=edit bbi-52668.ll reproducer Reproduce with opt -enable-new-pm=0 -S -o /dev/null bbi-52668.ll -indvars -loop-load-elim Result opt: ../include/llvm/IR/ValueHandle.h:490: ValueTy *llvm::PoisoningVH::getValPtr() const [ValueTy = llvm::BasicBlock]: Assertion `!Poisoned && "Accessed a poisoned value handle!"' failed. PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash backtrace. This starts happening with commit 664e1da485d2: [LoopLoadElim] Make sure all loops are in simplify form. PR48150 LoopLoadElim may end up expanding an AddRec from a loop which is not the current loop. This loop may not be in simplify form. We figure it out after the no-return point, so cannot bail in this case. AddRec requires simplify form to expand. The only way to ensure this does not crash is to simplify all loops beforehand. The issue only exists in new PM. Old PM requests LoopSimplify required pass and it simplifies all loops before the opt begins. Differential Revision: https://reviews.llvm.org/D91525 Reviewed By: asbirlea, aeubanks -- 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 49143] New: The -finstrument-functions is not enabled with -O0
https://bugs.llvm.org/show_bug.cgi?id=49143
Bug ID: 49143
Summary: The -finstrument-functions is not enabled with -O0
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: Driver
Assignee: unassignedclangb...@nondot.org
Reporter: adhemerval.zane...@linaro.org
CC: llvm-bugs@lists.llvm.org, neeil...@live.com,
richard-l...@metafoo.co.uk
The 'foo' function below is not instrumented when built with -O0, only when
using higher optimization options (such as -O1):
---
$ ./bin/clang -v 2>&1 | head -n2
clang version 13.0.0 (https://github.com/llvm/llvm-project.git
90081f3020e38727eb30506d052cbb4e3a489eb6)
Target: aarch64-unknown-linux-gnu
$ cat test.c
void foo ()
{
}
static int count;
__attribute__ ((noinline)) __attribute__ ((no_instrument_function))
void __cyg_profile_func_enter (void *fn, void *parent)
{
count++;
}
__attribute__ ((noinline)) __attribute__ ((no_instrument_function))
void __cyg_profile_func_exit (void *fn, void *parent)
{
count++;
}
$ ./bin/clang -O0 -finstrument-functions -S -emit-llvm test.c -S -o - | head -n
12
$ ./bin/clang -O1 -finstrument-functions -S -emit-llvm test.c -S -o - | head -n
14
; ModuleID = 'test.c'
source_filename = "test.c"
target datalayout = "e-m:e-i8:8:32-i16:16:32-i64:64-i128:128-n32:64-S128"
target triple = "aarch64-unknown-linux-gnu"
@count = internal unnamed_addr global i32 0, align 4
; Function Attrs: nofree norecurse nounwind uwtable willreturn
define dso_local void @foo() local_unnamed_addr #0 {
entry:
call void @__cyg_profile_func_enter(i8* undef, i8* undef)
call void @__cyg_profile_func_exit(i8* undef, i8* undef)
ret void
}
--
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 49144] New: Multiple debug variables sharing a stack slot are incorrectly formatted in MIR
https://bugs.llvm.org/show_bug.cgi?id=49144
Bug ID: 49144
Summary: Multiple debug variables sharing a stack slot are
incorrectly formatted in MIR
Product: libraries
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Common Code Generator Code
Assignee: unassignedb...@nondot.org
Reporter: stephen.to...@sony.com
CC: llvm-bugs@lists.llvm.org
Created attachment 24514
--> https://bugs.llvm.org/attachment.cgi?id=24514&action=edit
Call with llc -run-pass=stack-coloring to reproduce; also functions as a lit
test.
This is a bug that occurs when we have two (or more) stack slots that have
associated debug declares, and the stack coloring pass merges them so that we
have a stack slot with multiple debug declares. Instead of printing them out as
a list of some kind, we simply print them off adjacent in a syntactically
invalid format; attempting to parse the resulting MIR simply results in a
crash.
For example, from the reproducer:
stack:
- { id: 0, ...,
debug-info-variable: '!4', debug-info-expression: '!DIExpression()',
debug-info-location: '!7' }
- { id: 1, ...,
debug-info-variable: '!8', debug-info-expression: '!DIExpression()',
debug-info-location: '!7' }
llc -run-pass=stack-coloring reproducer.mir
stack:
- { id: 0, ...,
debug-info-variable: '!4!8', debug-info-expression:
'!DIExpression()!DIExpression()',
debug-info-location: '!7!7' }
This issue can be traced back to MIRPrinter::printStackObjectDbgInfo, and its
single caller MIRPrinter::convertStackObjects. In these functions, we iterate
through the VariableDbgInfo for the function, fetch the string streams for the
associated stack slots, and append the debug info to those. Instead of simply
directly appending, there should be some kind of separator if a value has
already been written to the stream; the parser will also need to be updated to
support this.
--
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 30824 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in StmtProfiler::VisitStmt
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevl...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2021-02-11 Type: Bug New issue 30824 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in StmtProfiler::VisitStmt https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=30824 Detailed Report: https://oss-fuzz.com/testcase?key=5358392052940800 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffe67adffe8 Crash State: StmtProfiler::VisitStmt clang::StmtVisitorBase::Visit Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202102070603:202102080628 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5358392052940800 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 49145] New: LLVM ERROR: Unsupported dynamic stack allocation
https://bugs.llvm.org/show_bug.cgi?id=49145 Bug ID: 49145 Summary: LLVM ERROR: Unsupported dynamic stack allocation Product: libraries Version: 11.0 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: Backend: BPF Assignee: unassignedb...@nondot.org Reporter: sbezv...@cisco.com CC: llvm-bugs@lists.llvm.org Hello, I am getting core dump when I try to compile ebpf code. Stack dump: 0. Program arguments: llc-11 -march=bpf -mcpu=probe -filetype=obj -o interceptor.o 1. Running pass 'Function Pass Manager' on module ''. 2. Running pass 'BPF DAG->DAG Pattern Instruction Selection' on function '@egress_interceptor' #0 0x7f854314b51f llvm::sys::PrintStackTrace(llvm::raw_ostream&) (/lib/x86_64-linux-gnu/libLLVM-11.so.1+0xaa651f) #1 0x7f8543149880 llvm::sys::RunSignalHandlers() (/lib/x86_64-linux-gnu/libLLVM-11.so.1+0xaa4880) #2 0x7f854314b9f5 (/lib/x86_64-linux-gnu/libLLVM-11.so.1+0xaa69f5) #3 0x7f85426973c0 __restore_rt (/lib/x86_64-linux-gnu/libpthread.so.0+0x153c0) #4 0x7f854218b18b raise /build/glibc-eX1tMB/glibc-2.31/signal/../sysdeps/unix/sysv/linux/raise.c:51:1 #5 0x7f854216a859 abort /build/glibc-eX1tMB/glibc-2.31/stdlib/abort.c:81:7 #6 0x7f854309ed18 (/lib/x86_64-linux-gnu/libLLVM-11.so.1+0x9f9d18) #7 0x7f854309eb38 (/lib/x86_64-linux-gnu/libLLVM-11.so.1+0x9f9b38) #8 0x7f8544bdd6ff (/lib/x86_64-linux-gnu/libLLVM-11.so.1+0x25386ff) #9 0x7f8543683165 (/lib/x86_64-linux-gnu/libLLVM-11.so.1+0xfde165) #10 0x7f85436828c4 llvm::SelectionDAG::Legalize() (/lib/x86_64-linux-gnu/libLLVM-11.so.1+0xfdd8c4) #11 0x7f85437ad1c5 llvm::SelectionDAGISel::CodeGenAndEmitDAG() (/lib/x86_64-linux-gnu/libLLVM-11.so.1+0x11081c5) #12 0x7f85437ac612 llvm::SelectionDAGISel::SelectAllBasicBlocks(llvm::Function const&) (/lib/x86_64-linux-gnu/libLLVM-11.so.1+0x1107612) #13 0x7f85437aa311 llvm::SelectionDAGISel::runOnMachineFunction(llvm::MachineFunction&) (/lib/x86_64-linux-gnu/libLLVM-11.so.1+0x1105311) #14 0x7f854341d4ae llvm::MachineFunctionPass::runOnFunction(llvm::Function&) (/lib/x86_64-linux-gnu/libLLVM-11.so.1+0xd784ae) #15 0x7f854325a689 llvm::FPPassManager::runOnFunction(llvm::Function&) (/lib/x86_64-linux-gnu/libLLVM-11.so.1+0xbb5689) #16 0x7f854325fc33 llvm::FPPassManager::runOnModule(llvm::Module&) (/lib/x86_64-linux-gnu/libLLVM-11.so.1+0xbbac33) #17 0x7f854325aca0 llvm::legacy::PassManagerImpl::run(llvm::Module&) (/lib/x86_64-linux-gnu/libLLVM-11.so.1+0xbb5ca0) #18 0x0040d792 main (/usr/lib/llvm-11/bin/llc+0x40d792) #19 0x7f854216c0b3 __libc_start_main /build/glibc-eX1tMB/glibc-2.31/csu/../csu/libc-start.c:342:3 #20 0x0040b0ce _start (/usr/lib/llvm-11/bin/llc+0x40b0ce) Aborted (core dumped) -- 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 49146] New: Crash with MIPS16 multiply
https://bugs.llvm.org/show_bug.cgi?id=49146
Bug ID: 49146
Summary: Crash with MIPS16 multiply
Product: new-bugs
Version: 11.0
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: jesse.a.degu...@gmail.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org
Created attachment 24515
--> https://bugs.llvm.org/attachment.cgi?id=24515&action=edit
Clang output and crash report files
Clang 11.0.1 crashes with a stack trace and message telling me to file a bug
here when I build a module containing the following code in MIPS16 mode:
--
static unsigned baz(unsigned n, unsigned m)
{
/* NOTE: Using any of these other operators works fine,
only the multiply causes the crash.
*/
//return n + m;
//return n - m;
return n * m;
//return n / m;
}
int bar(void)
{
return 42;
}
void foo(void)
{
int bleh = bar();
baz(bleh, 55);
}
--
This is on a version of Clang I built in Debug mode for x86, MIPS, and ARM
targets on Ubuntu 20.04 on Windows 10 WSL.
Here is the start of the output from Clang, the rest is included in the
attached ZIP file:
--
fatal error: error in backend: Not supported instr: >
PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash
backtrace, preprocessed source, and associated run script.
Stack dump:
0. Program arguments: ./pic32clang/install/bin/clang -c mips16_simple.c -o
mips16_simple.o -target mipsel-linux-gnu-musl -march=mips32r2 -g -O0
-msoft-float -mfloat-abi=soft -mips16
1. parser at end of file
2. Code generation
3. Running pass 'Function Pass Manager' on module 'mips16_simple.c'.
4. Running pass 'Mips Assembly Printer' on function '@baz'
--
Also included in the ZIP file are the two files that the crash report told me
to include. The document "How To Submit an LLVM Bug Report" says to run "llc"
to see if that crashes, but it does not (this is different from my
previously-submitted bug #49042, which does crash llc).
--
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 49147] New: [FastMath] Failure to fold 1 / powf(x, y) -> powf(x, -y)
https://bugs.llvm.org/show_bug.cgi?id=49147
Bug ID: 49147
Summary: [FastMath] Failure to fold 1 / powf(x,y) -> powf(x,
-y)
Product: libraries
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: Scalar Optimizations
Assignee: unassignedb...@nondot.org
Reporter: llvm-...@redking.me.uk
CC: llvm-bugs@lists.llvm.org
#include
float invpow_i(float x, int y) {
return 1.0f / __builtin_powf(x, y);
}
float invpow_f(float x, float y) {
return 1.0f / __builtin_powf(x, y);
}
https://simd.godbolt.org/z/YxaW96
Clang fails to merge the fdiv into the pow by negating the exponent arg
--
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 46943] Loop Strength Reduction (`opt -loop-reduce`) reorders `icmp` with -1 and `add nuw`, yielding poison
https://bugs.llvm.org/show_bug.cgi?id=46943 Nikita Popov changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #13 from Nikita Popov --- This has been fixed by https://reviews.llvm.org/D95286. -- 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 49148] New: Default template parameter value from brace-initialization
https://bugs.llvm.org/show_bug.cgi?id=49148
Bug ID: 49148
Summary: Default template parameter value from
brace-initialization
Product: clang
Version: 11.0
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: C++
Assignee: unassignedclangb...@nondot.org
Reporter: tom...@gmail.com
CC: blitzrak...@gmail.com, dgre...@apple.com,
erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk
Clang does not allow brace-initialization in default value of template
parameter. I hope I used the right terminology.
Example:
template void foo(int i = {});
error: expected expression
Default value of the function parameter is accepted, but the template one is
not.
I did not figure out whether this is covered in the standard, however I think
that the current state is inconsistent (is it alright for function, but not for
template).
(Works in GCC.)
--
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 49149] New: Exegesis commit 8383fddc4fa9 breaks aarch64-windows-msvc build
https://bugs.llvm.org/show_bug.cgi?id=49149 Bug ID: 49149 Summary: Exegesis commit 8383fddc4fa9 breaks aarch64-windows-msvc build Product: tools Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: llvm-exegesis Assignee: unassignedb...@nondot.org Reporter: maxim.kuvyr...@gmail.com CC: clement.cour...@gmail.com, gchate...@google.com, llvm-bugs@lists.llvm.org Commit llvm-exegesis commit https://reviews.llvm.org/rG8383fddc4fa9b4e61954e5ac93b00719a39d2291 breaks build on aarch64-windows-msvc host. X86-specific intrinsics are used under #ifdef _MSC_VER. With addition of Windows on Arm platform _MSC_VER no longer implied x86. Proposed patch to fix this is at https://reviews.llvm.org/D96498 . -- 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 48503] clangd not able to navigate from declaration to implementation
https://bugs.llvm.org/show_bug.cgi?id=48503 Anthony Leonardo Gracio changed: 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 49023] clang's integrated assembler doesn't permit setting -Wa, -mimplicit-it=always for ARM
https://bugs.llvm.org/show_bug.cgi?id=49023 Nick Desaulniers changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Nick Desaulniers --- https://reviews.llvm.org/rGa680bc3a31d36d321ccf3801bdcff74d58842bfa -- 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 49023, which changed state. Bug 49023 Summary: clang's integrated assembler doesn't permit setting -Wa,-mimplicit-it=always for ARM https://bugs.llvm.org/show_bug.cgi?id=49023 What|Removed |Added Status|CONFIRMED |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 49150] New: [OpenMP 5.0] Undefined reference error with task reduction in target region
https://bugs.llvm.org/show_bug.cgi?id=49150 Bug ID: 49150 Summary: [OpenMP 5.0] Undefined reference error with task reduction in target region Product: OpenMP Version: unspecified Hardware: Other OS: Linux Status: NEW Severity: normal Priority: P Component: Runtime Library Assignee: unassignedb...@nondot.org Reporter: jhda...@udel.edu CC: llvm-bugs@lists.llvm.org Created attachment 24516 --> https://bugs.llvm.org/attachment.cgi?id=24516&action=edit Source of reproducer for the OpenMP task reduction on target bug. Overview: Clang 12 crashes at compile with undefined reference errors for a program using a target parallel construct with reduction(task...) and a task clause with in_reduction within. Steps to reproduce: 1. Compile attached reproducer with `clang -lm -fopenmp -fopenmp-targets=nvptx64-nvidia-cuda task_reduction_device_bug.c` Actual results: `nvlink error : Undefined reference to '__kmpc_taskred_modifier_init' in '/tmp/task_reduction_device_bug-fd3d8f.cubin' nvlink error : Undefined reference to '__kmpc_task_reduction_modifier_fini' in '/tmp/task_reduction_device_bug-fd3d8f.cubin' nvlink error : Undefined reference to '__kmpc_task_reduction_get_th_data' in '/tmp/task_reduction_device_bug-fd3d8f.cubin' clang-12: error: nvlink command failed with exit code 255 (use -v to see invocation) clang version 12.0.0 (https://github.com/llvm/llvm-project.git d36812892c16b551f058774babbc8727737f80cd) Target: powerpc64le-unknown-linux-gnu Thread model: posix InstalledDir: /sw/summit/ums/stf010/llvm/12.0.0-20210125/bin clang-12: note: diagnostic msg: Error generating preprocessed source(s).` Expected results: Successful compilation. Build & Hardware: clang version 12.0.0 (https://github.com/llvm/llvm-project.git d36812892c16b551f058774babbc8727737f80cd) Target: powerpc64le-unknown-linux-gnu Thread model: posix InstalledDir: /sw/summit/ums/stf010/llvm/12.0.0-20210125/bin Additional information: Reproducer source attached. -- 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 49137] Too restrictive compute capability
https://bugs.llvm.org/show_bug.cgi?id=49137 Shilei Tian changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED -- 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 48902] [meta] 12.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=48902 Bug 48902 depends on bug 49137, which changed state. Bug 49137 Summary: Too restrictive compute capability https://bugs.llvm.org/show_bug.cgi?id=49137 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 49151] New: AA query leads to stack overflow
https://bugs.llvm.org/show_bug.cgi?id=49151 Bug ID: 49151 Summary: AA query leads to stack overflow Product: libraries Version: trunk Hardware: PC OS: All Status: NEW Severity: release blocker Priority: P Component: Global Analyses Assignee: unassignedb...@nondot.org Reporter: alina.sbir...@gmail.com CC: llvm-bugs@lists.llvm.org Created attachment 24517 --> https://bugs.llvm.org/attachment.cgi?id=24517&action=edit Test Seeing a failure following D90094. To reproduce with ToT clang: bin/clang -cc1 -emit-obj -O2 -o /tmp/b.o AA_stackoverflow.ll It helps to reduce stack: e.g. ulimit -s 4096 -- 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 30848 in oss-fuzz: llvm:llvm-isel-fuzzer--x86_64-O2: ASSERT: MBB != &MF->front() && "Can't find reaching def for virtreg"
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevl...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2021-02-12 Type: Bug New issue 30848 by ClusterFuzz-External: llvm:llvm-isel-fuzzer--x86_64-O2: ASSERT: MBB != &MF->front() && "Can't find reaching def for virtreg" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=30848 Detailed Report: https://oss-fuzz.com/testcase?key=5700617597222912 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: llvm-isel-fuzzer--x86_64-O2 Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: MBB != &MF->front() && "Can't find reaching def for virtreg" llvm::LiveVariables::MarkVirtRegAliveInBlock llvm::LiveVariables::MarkVirtRegAliveInBlock Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202102100618:202102110620 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5700617597222912 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 49152] New: [NewPM] BuildBot failure http://lab.llvm.org:8011/#/builders/8
https://bugs.llvm.org/show_bug.cgi?id=49152 Bug ID: 49152 Summary: [NewPM] BuildBot failure http://lab.llvm.org:8011/#/builders/8 Product: libraries Version: trunk Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: Support Libraries Assignee: unassignedb...@nondot.org Reporter: pauls...@linux.vnet.ibm.com CC: llvm-bugs@lists.llvm.org libfuzzer is failing since NewPM became default. -- 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 30854 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in ExprEvaluatorBase::VisitCallExpr
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevl...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2021-02-12 Type: Bug New issue 30854 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in ExprEvaluatorBase::VisitCallExpr https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=30854 Detailed Report: https://oss-fuzz.com/testcase?key=5189180944678912 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffcc3622f28 Crash State: ExprEvaluatorBase::VisitCallExpr clang::StmtVisitorBase::Visit ExprEvaluatorBase::VisitCastExpr Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201712090607:201712100011 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5189180944678912 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] Issue 30856 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::Preprocessor::CachingLex
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevl...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2021-02-12 Type: Bug New issue 30856 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::Preprocessor::CachingLex https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=30856 Detailed Report: https://oss-fuzz.com/testcase?key=5734754668380160 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffcc1c5fe98 Crash State: clang::Preprocessor::CachingLex clang::Preprocessor::Lex clang::Parser::ParseStatementOrDeclarationAfterAttributes Sanitizer: address (ASAN) Crash Revision: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&revision=202102110620 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5734754668380160 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 49153] New: [DebugInfo] Missing debug-info for `enums` declared inside a C function
https://bugs.llvm.org/show_bug.cgi?id=49153
Bug ID: 49153
Summary: [DebugInfo] Missing debug-info for `enums` declared
inside a C function
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: DebugInfo
Assignee: unassignedb...@nondot.org
Reporter: sourav0...@gmail.com
CC: aloksharma.k...@gmail.com, apra...@apple.com,
dblai...@gmail.com, jdevliegh...@apple.com,
jini.susan.geo...@gmail.com, keith.wal...@arm.com,
llvm-bugs@lists.llvm.org, paul.robin...@am.sony.com,
paul_robin...@playstation.sony.com
$cat enum.c
int main() {
enum {
Hello = 1,
};
printf("%d\n", Hello);
}
-
DWARF generated by CLANG(trunk):
0x000b: DW_TAG_compile_unit
...
0x002a: DW_TAG_subprogram
DW_AT_name ("main")
...
0x0043: DW_TAG_base_type
DW_AT_name ("int")
...
0x004a: NULL
--
DWARF generated by GCC(trunk):
x002e: DW_TAG_subprogram
DW_AT_name ("main")
...
0x0050: DW_TAG_enumeration_type
DW_AT_encoding(DW_ATE_unsigned)
DW_AT_byte_size (0x04)
DW_AT_type(0x007f "unsigned int")
...
0x005e: DW_TAG_enumerator
DW_AT_name ("Hello")
DW_AT_const_value (0x01)
I think this is mostly due to design of enums in debug-info. Enums are
represented as part of CompileUnit as:
!0 = distinct !DICompileUnit(. enums: !2, )
While this works well for cases when enum is at Global/CU scope, but leaves no
room for addressing the case depicted here, i.e Enum declared inside a
function.
--
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 49154] New: Assertion `S1->getType() == S2->getType() && "Cannot create binary operator with two operands of differing type!"'
https://bugs.llvm.org/show_bug.cgi?id=49154 Bug ID: 49154 Summary: Assertion `S1->getType() == S2->getType() && "Cannot create binary operator with two operands of differing type!"' Product: new-bugs Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: pho...@chromium.org CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org Created attachment 24518 --> https://bugs.llvm.org/attachment.cgi?id=24518&action=edit Clang crash reproducer We're hitting the following issue with the attached reproducer: clang++: /src/clang-llvm/llvm-project/llvm/lib/IR/Instructions.cpp:2523: static llvm::BinaryOperator *llvm::BinaryOperator::Create(llvm::Instruction::BinaryOps, llvm::Value *, llvm::Value *, const llvm::Twine &, llvm::Instruction *): Assertion `S1->getType() == S2->getType() && "Cannot create binary operator with two operands of differing type!"' failed. Stack dump: #0 0x089312ba llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) /src/clang-llvm/llvm-project/llvm/lib/Support/Unix/Signals.inc:565:11 #1 0x089313cb PrintStackTraceSignalHandler(void*) /src/clang-llvm/llvm-project/llvm/lib/Support/Unix/Signals.inc:632:1 #2 0x0892fc83 llvm::sys::RunSignalHandlers() /src/clang-llvm/llvm-project/llvm/lib/Support/Signals.cpp:71:5 #3 0x08931a05 SignalHandler(int) /src/clang-llvm/llvm-project/llvm/lib/Support/Unix/Signals.inc:407:1 #4 0x7f92d0d72140 __restore_rt (/lib/x86_64-linux-gnu/libpthread.so.0+0x14140) #5 0x7f92d0a31ce1 raise ./signal/../sysdeps/unix/sysv/linux/raise.c:51:1 #6 0x7f92d0a1b537 abort ./stdlib/abort.c:81:7 #7 0x7f92d0a1b40f get_sysdep_segment_value ./intl/loadmsgcat.c:509:8 #8 0x7f92d0a1b40f _nl_load_domain ./intl/loadmsgcat.c:970:34 #9 0x7f92d0a2a662 (/lib/x86_64-linux-gnu/libc.so.6+0x34662) #10 0x07d02604 llvm::BinaryOperator::Create(llvm::Instruction::BinaryOps, llvm::Value*, llvm::Value*, llvm::Twine const&, llvm::Instruction*) /src/clang-llvm/llvm-project/llvm/lib/IR/Instructions.cpp:2524:10 #11 0x0570185f llvm::IRBuilderBase::CreateInsertNUWNSWBinOp(llvm::Instruction::BinaryOps, llvm::Value*, llvm::Value*, llvm::Twine const&, bool, bool) /src/clang-llvm/llvm-project/llvm/include/llvm/IR/IRBuilder.h:1210:33 #12 0x05b86e03 llvm::IRBuilderBase::CreateAdd(llvm::Value*, llvm::Value*, llvm::Twine const&, bool, bool) /src/clang-llvm/llvm-project/llvm/include/llvm/IR/IRBuilder.h:1277:5 #13 0x082f23b2 llvm::InstrProfiling::lowerIncrement(llvm::InstrProfIncrementInst*) /src/clang-llvm/llvm-project/llvm/lib/Transforms/Instrumentation/InstrProfiling.cpp:698:11 #14 0x082f1e41 llvm::InstrProfiling::lowerIntrinsics(llvm::Function*) /src/clang-llvm/llvm-project/llvm/lib/Transforms/Instrumentation/InstrProfiling.cpp:453:20 #15 0x082f1acf llvm::InstrProfiling::run(llvm::Module&, std::__2::function) /src/clang-llvm/llvm-project/llvm/lib/Transforms/Instrumentation/InstrProfiling.cpp:572:19 #16 0x082f662e (anonymous namespace)::InstrProfilingLegacyPass::runOnModule(llvm::Module&) /src/clang-llvm/llvm-project/llvm/lib/Transforms/Instrumentation/InstrProfiling.cpp:162:22 #17 0x07d41999 (anonymous namespace)::MPPassManager::runOnModule(llvm::Module&) /src/clang-llvm/llvm-project/llvm/lib/IR/LegacyPassManager.cpp:1549:23 #18 0x07d4150d llvm::legacy::PassManagerImpl::run(llvm::Module&) /src/clang-llvm/llvm-project/llvm/lib/IR/LegacyPassManager.cpp:540:16 #19 0x07d46051 llvm::legacy::PassManager::run(llvm::Module&) /src/clang-llvm/llvm-project/llvm/lib/IR/LegacyPassManager.cpp:1676:3 #20 0x08d14649 (anonymous namespace)::EmitAssemblyHelper::EmitAssembly(clang::BackendAction, std::__2::unique_ptr >) /src/clang-llvm/llvm-project/clang/lib/CodeGen/BackendUtil.cpp:1017:3 #21 0x08d1173e clang::EmitBackendOutput(clang::DiagnosticsEngine&, clang::HeaderSearchOptions const&, clang::CodeGenOptions const&, clang::TargetOptions const&, clang::LangOptions const&, llvm::DataLayout const&, llvm::Module*, clang::BackendAction, std::__2::unique_ptr >) /src/clang-llvm/llvm-project/clang/lib/CodeGen/BackendUtil.cpp:1607:17 #22 0x0993aeec clang::BackendConsumer::HandleTranslationUnit(clang::ASTContext&) /src/clang-llvm/llvm-project/clang/lib/CodeGen/CodeGenAction.cpp:348:7 #23 0x0bf10ed1 clang::ParseAST(clang::Sema&, bool, bool) /src/clang-llvm/llvm-project/clang/lib/Parse/ParseAST.cpp:178:12 #24 0x0977e12c clang::ASTFrontendAction::ExecuteAction() /src/clang-llvm/llvm-project/clang/lib/Frontend/FrontendAction.cpp:1058:1 #25 0x09936d20 clang::CodeGenAction::ExecuteAction() /src/clang-llvm/llvm-project/clang/lib/CodeGen/CodeGenAction.cpp:1083:5 #26 0x0977db5c clan
