similar to: [LLVMdev] Passing options to opt

Hi folk, I'm a newbie to llvm, please first forgive my naive questions. I want to instrument llvm code to do some run-time monitoring work. After reading some of the llvm documentation, it begins clear to me that I can do the instrumentation in a transformation pass. There are several things I want to do in the transformation pass, but I'm not sure whether they are doable and how to do

Hi folk, I have a Module pass. I tested the pass against the following code. ./gcc.dg/20030721-1.c extern void abort(void); void foo(int) __attribute__((__noinline__)); void foo(int i) { abort(); } int main() { int i; int first= 0; int last= 0; while (last<3) { last = first; while (first<=last) { first++; for (i=0;i<3;i++) last++; if

On 03/04/2012 02:32 PM, Harel Cain wrote: > Thanks, but I'm not sure I understand. I see no such flag in clang 2.9 > nor couldn't I find any mention of it. What does it do? It's called -mllvm. You can use it like this. clang -mllvm -vectorize ... Cheers Tobi

Hi, Is there a way to passing llc options to clang, for example -march -mcpu, etc. ? Some threads suggested using -mllvm flag, I tried ./clang -mllvm -march=X86-64 -mcpu=core2 -o hello hello.c, but got "Unknown command line argument" Thanks, Ziqiang -------------- next part -------------- An HTML attachment was scrubbed... URL:

I have tried to invoke a transformation/optimization pass using -mllvm, without success. I might be missing something. For example I have a shared/dynamic library which contains LLVM passes. I used to invoke them with llvmc like this: >>*llvmc mycode.c -o mycode.o -c -opt -Wo,=-load,libFoo.dylib,-Foo* Can this style of optimization be executed using -mllvm argument? Thx, PMon On Sun,

On 01/16/2012 03:37 PM, Pieter Custers wrote: > Hello Tobi, > > Thank you for the quick reply. > > I updated my complete build suite with your script (http://polly.grosser.es/polly.sh). The make-test fails with some errors, the rest went smoothly; > > -- > Exit Code: 1 > Command Output (stderr): > -- > LLVM ERROR: Could not resolve external global address: stdout

Hmmm, a quick look at the documentation for TargetTransformInfo doesn't look like it. In LegalizeDAG.cpp it uses TLI.getOperationAction() to find out if an SDNode should be expanded by the legalizer or passed down to the target. That's what I need to know, but I need it in a pass pre-legalization. This seems like weird layering, though. Having an "optimization" pass be looking

Dear Friends, I need to pass an option to an llvm analysis pass through clang and dragonegg, to llvm's opt. Right now opt takes the flag, but when I pass the flag through clang with -mllvm, I get an error. I am trying to figure out how other options are passed to llvm through clang (as suggested in the mailing list). But if someone has more inputs on how to do this (also with dragonegg), it

Hi folk, In the Source Level Debugging document, llvm.dbg.declare takes two paramters. "The first argument is the alloca for the variable, cast to a {}*. The second argument is the llvm.dbg.variable containing the description of the variable." The second parameter corresponds to DIVariable, what is the corresponding LLVM class of the first parameter? I want to find which

On Sat, Jul 17, 2010 at 12:00 AM, Neal N. Wang <neal.wang at gmail.com> wrote: > Hi folk, > > In the Source Level Debugging document,  llvm.dbg.declare takes two > paramters.  "The first argument is the alloca for the variable, cast to a > {}*. The second argument is the llvm.dbg.variable containing the description > of the variable."  The second parameter

I'm working on the #pragma STDC FENV_ACCESS ON support, specifically the support for a strict version of the FP to unsigned int conversion. I've got a pass that runs and converts a new intrinsic into code that uses the FP to signed int conversion code similar to how SelectionDAG handles this now. Except that SelectionDAG will let the target handle it if the target says it will. How do I,

Hello Tobi, Thank you for the quick reply. I updated my complete build suite with your script (http://polly.grosser.es/polly.sh). The make-test fails with some errors, the rest went smoothly; -- Exit Code: 1 Command Output (stderr): -- LLVM ERROR: Could not resolve external global address: stdout -- ******************** Testing Time: 10.01s ******************** Failing Tests (3): Polly ::

On 4/3/2018 9:25 AM, Kevin Neal via llvm-dev wrote: > I'm working on the #pragma STDC FENV_ACCESS ON support, specifically > the support for a strict version of the FP to unsigned int conversion. > I've got a pass that runs and converts a new intrinsic into code that > uses the FP to signed int conversion code similar to how SelectionDAG > handles this now. Except that

Hi folk, I get the following stack trace and do have any clue how to fix the problem. 0 opt 0x087ecc99 1 opt 0x087ed265 2 0xb7f6a400 __kernel_sigreturn + 0 3 opt 0x086d4198 llvm::LeakDetector::addGarbageObject(llvm::Value const*) + 29 4 opt 0x0872945f llvm::Instruction::Instruction(llvm::Type const*, unsigned int,

Hello, I've been trying to figure out how to reproduce the results of a single clang -O3 compilation to a binary with a multi-step process using opt. Specifically I have: clang -O3 foo.c -o foo.exe which I want to replicate with: clang -O0 -c -emit-llvm foo.c opt -O3 foo.bc -o foo_o.bc clang foo_o.bc -o foo.exe Any hints / suggestions on what additional flags I need to produce the same

Neal, FYI, my group has added a flag to llvm-gcc for emitting the va_arg instruction (instead of lowering in the front-end), and we also have an implementation of the VAARG instruction for X86-64. (which is currently not implemented in the LLVM backend). Both of these things will be sent upstream to LLVM soon, pending some more testing and review. If you are dire need of these features now, I

Thanks, but I'm not sure I understand. I see no such flag in clang 2.9 nor couldn't I find any mention of it. What does it do? Harel Cain On Sun, Mar 4, 2012 at 15:03, Anton Korobeynikov <anton at korobeynikov.info>wrote: > > In the good old llvmc, the -Wo flag could be used to pass arguments to > the > > optimizer. Is there a similar mechanism anywhere for clang?

Awesome, thanks! I'd like to have the last step (llc in your example) not perform additional optimization passes, such as O3, and simply use the O3 pass from opt in the previous line. Do you happen to know if I should use 'llc -O0 foo_o.bc -o foo.exe' instead to achieve this? On Thu, Jul 2, 2020 at 6:35 PM Mehdi AMINI <joker.eph at gmail.com> wrote: > > > On Thu,

//mllvm Options can be dumped by clang -v -help -mllvm and clang -v --help-hidden --> //mllvm Options can be dumped by clang -v -help -mllvm and clang -v --help-hidden -mllvm On Tue, Jan 9, 2018 at 3:09 AM, toddy wang <wenwangtoddy at gmail.com> wrote: > Thanks, Craig. > > So, clang -Xclang -disable-llvm-passes actually disables all the LLVM > passed populated by clang so

Hi, I was trying to pass llvm option -mem2reg to clang using -mllvm and I found the following error: clang (LLVM option parsing): Unknown command line argument '-mem2reg'. Try: 'clang (LLVM option parsing) -help' clang (LLVM option parsing): Did you mean '-debug'? I would appreciate if anyone could help me. -- Syed Rafiul Hussain