search for: cszide

Hi, everyone, I use opt to optimize some .bc files, but in some cases, when I use a costume passes sequence, I get the following error 1.Running pass 'Function Pass Manager' on module 'xx.bc'. 2.Running pass 'Value Propagation' on function '@yy' Segmentation fault (core dumped) What are the reasons of this error? From the output text, I know that opt runs pass

...is may help you too. Best regards Emanuele Del Sozzo ________________________________ From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Stefano Cherubin via llvm-dev <llvm-dev at lists.llvm.org> Sent: Friday, August 17, 2018 11:44:50 AM To: llvm-dev at lists.llvm.org; cszide Subject: Re: [llvm-dev] Replication -O3 optimizations manually Hi Zide, the scope of opt is limited to the LLVM-IR, which is meant to be always target independent. In order to apply backend optimizations you need to lower the representation to something closer to the machine-level. I would sugges...

Hi, Stefano I also have the problem as described by Emanuele. You say that clang schedules target-independent and target-dependent passes. However, when I use lli to execute bitcode generated by opt with -O3 or with the same optimization passes as -O3, the performance are still different. So, are there some special operations by -O3 option? I read the source code of opt, but I cannot find the

Hi everyone, I want to test the passes in llvm, and I got some passes sequences that caused the crash of opt. Although I can use bugpoint to narrow down the source of problems, I can only get some reduced and simplified IR and passes to reproduce the problem. My question is how to get the reduced IR of the original IR file to reproduce the problem. For example, "opt a.bc -a -b -c -d (where

Hi there, I am working with opt-6.0 and try to generate a call graph of libsndfile, but it seems the call graph doesn't cover all call relationship. Actually, I am doing static analysis on *CVE-2014-8130*, which is a zero division on libtiff/tif_write.c TIFFWriteScanline. (see https://security-tracker.debian.org/tracker/CVE-2014-8130) Theoretically, the main function in

Hi, developers, Recently, I read two papers [1], [2] about finding the root causes of compiler bugs. However, I do not find any information in these paper about how compiler developers find the root causes of compiler bugs in practice. So I am curious whether these techniques are useful in practice. For my experience, the outputs of compilers are always used to isolate the causes of compiler