search for: standardpass

...VM/Clang are being developed, it's a big task and becoming > too much for one person. > Thanks, > Tanya A suggestion to include: I've recently been trying to adapt our project to LLVM 3.0 rc2, and it took me several hours to track down what happened to "include/llvm/Support/StandardPasses.h". There is no mention of this topic in the current release notes page for 3.0 on the website (http://llvm.org/docs/ReleaseNotes.html#whatsnew), or the equivalent page in the kit itself. And it isn't easy to find how it has transmogrified just by searching the LLVM sources, because al...

...CodeGenOpt::None is checked at few places to ensure that we are doing optimization, but it is not checking *level* of optimization. If seems you want better approach to influence pass selection in addCommonCodeGenPasses() for your needs. If so, why not try to do what we did in 'opt' using StandardPasses.h ? (Note, I have not thought through this suggestion, I am just thinking loudly here) - Devang

Chris Lattner <clattner at apple.com> writes: >> class CodeGenOpt { >> ... >> public >> getOptLevel() ...; >> getFPLevel() ...; >> getMemLevel() ...; >> }; >> >> Does this sound reasonable? > > I don't think that this is the right way to go. Higher level > decisions like that should affect your choice of passes to

Soumya_Prasad_Ukil wrote: > Pls help. You didn't say what was actually running the passes. (llvm-gcc? clang? opt -some -passes?) What you probably want is to modify one of the lists in include/llvm/Support/StandardPasses.h. Nick > > On 21 August 2010 17:32, Soumya_Prasad_Ukil <ukil.soumya at gmail.com > <mailto:ukil.soumya at gmail.com>> wrote: > > I have written a simple pass. I have been successful to execute it. > I want LLVM to execute it. I don't know how to includ...

Look I have written a PRE pass. opt is running that pass. I have included my pass name there in include/llvm/Support/StandardPasses.h file. To do that, I have got some error. Because it also requires the definition of the pass in some other file also. I observed how gvn pre pass is added to the pass list. I had followed the same way, but failed. Cna you kindly tell what needs to be done in this regard? On 23 August 2010 00:1...

Soumya_Prasad_Ukil wrote: > Look I have written a PRE pass. opt is running that pass. I have > included my pass name there in include/llvm/Support/StandardPasses.h > file. To do that, I have got some error. Because it also requires the > definition of the pass in some other file also. I observed how gvn pre > pass is added to the pass list. I had followed the same way, but failed. > Cna you kindly tell what needs to be done in this regard? Wh...

...he others existing only in case they are needed by the dynamically-generated code that I'm JITing? It seems that the combinatorics of which passes to apply, and in which order (including doing some multiple times), are pretty daunting. Other than the Kaleidescope tutorial (too simple) and the StandardPasses.h (too complex?) I can't find any other examples, much less pro/con discussion or guidance. Does anybody have any pointers to web pages or other docs where people have shared their experiences walking through the space of possible pass combinations? The application of all of this for me is...

...filename.o > instead of steps 1-4. > > The question is: does llvm-gcc (or Clang, or whatever) allow to > register a custom optimization pass as a default one (by means of env > vars, configuration files or anything besides rebuilding the > compiler)? You can modify llvm/Support/StandardPasses.h to include your pass by default one appropriate optimization level is used. However, llvm-gcc or clang works on one source file at a time, so it won't do your step 2) automatically for you. What you want is link time optimization. See http://llvm.org/docs/LinkTimeOptimization.html and h...

...istry.h:20, from /waflhome/trapni/local/include/llvm/PassSupport.h:25, from /waflhome/trapni/local/include/llvm/Pass.h:366, from /waflhome/trapni/local/include/llvm/PassManager.h:20, from /waflhome/trapni/local/include/llvm/Support/StandardPasses.h:22, from /waflhome/trapni/local/src/flow/src/Runner.cpp:19: /waflhome/trapni/local/include/llvm/Support/AlignOf.h:57:24: error: expected unqualified-id before 'alignof' In file included from /waflhome/trapni/local/include/llvm/ADT/StringMap.h:18:0, from...

...+ long(i)), induction variable long(i) may be unused, depending on whether long(i) can participate in creating an another induction variable. Thus, it is not known until the algorithm is done, which of the created induction variables are unused. FWIW I noticed that other optimizations (as seen in StandardPasses.h) are followed by -instcombine for cleanup. I thought requiring or suggesting running -instcombine after -osr would be SOP. FWIW2 our intent in creating OSR was not to replace LSR, just provide an alternative strength reduction optimization. > -Eli Brian

Hi all, we're working on compile-time instrumentation for ThreadSanitizer (a data race detector, see http://code.google.com/p/data-race-test and http://code.google.com/p/data-race-test/wiki/CompileTimeInstrumentation), which is implemented as an opt plugin that is ran for each client C/C++ module we compile. To build a binary consisting of several modules the following steps are performed:

...in case they are needed by > the dynamically-generated code that I'm JITing? > > It seems that the combinatorics of which passes to apply, and in which > order (including doing some multiple times), are pretty daunting. Other > than the Kaleidescope tutorial (too simple) and the StandardPasses.h (too > complex?) I can't find any other examples, much less pro/con discussion or > guidance. Does anybody have any pointers to web pages or other docs where > people have shared their experiences walking through the space of possible > pass combinations? > I am afraid, the...

...advice from the community. First off, I'm not sure where it's appropriate to put these. For llvm-c, most files live in a header named after the library that includes the functions, and we don't have a corresponding place for these functions. Perhaps they could go in a llvm-c/Transforms/StandardPasses.h? Second, createStandardModulePasses accepts an inlining pass an an argument, but llvm-c doesn't expose a way to directly create any passes. So, should I just not expose that argument, or should I add: LLVMPassRef LLVMCreateFunctionInliningPass LLVMCreateAlwaysInlinerPass LLVMCreatePartial...

While going through the header file llvm/Support/StandardPasses.h in support of some LLVM bindings that I have been working on I noticed that some passes are not exposed in the LLVM C bindings. Attached is a patch that adds the following passes the the C bindings: LLVMAddIPSCCPPass LLVMAddInternalizePass I can commit this patch once someone gives me the go...

...l.cpp" the functions where clang builds the > passes to emit code. The optimization passes used are there and you can > simulate them via the "opt" utility, by running each pass one at a time. > LLVM also declares standard module/function passes on > include/llvm/Support/StandardPasses.h. Have a look and see if that's > what you want. Thanks. Here's a very simple example where I can't get llc do what clang does. Just taking int f(int a, int b) { return a + b; } and compiling it on the one hand with clang -cc1 -O3 x.c -S -o 1.s and on the other hand with...

...t; variable. Thus, it is not known until the algorithm is done, which of the > created induction variables are unused. Sure, but you know which induction variables you created; you can just zap the unused ones at the end of the pass, no? > FWIW I noticed that other optimizations (as seen in StandardPasses.h) are > followed by -instcombine for cleanup. I thought requiring or suggesting > running > -instcombine after -osr would be SOP. Strength reduction is sort of a special case; it runs extremely late because it interferes with other optimizations. > FWIW2 our intent in creating OSR...

....source/gcc/llvm-backend.cpp:38:42: error: llvm/Target/SubtargetFeature.h: No such file or directory ../../llvm-gcc-4.2-2.9.source/gcc/llvm-backend.cpp:42:40: error: llvm/Target/TargetRegistry.h: No such file or directory ../../llvm-gcc-4.2-2.9.source/gcc/llvm-backend.cpp:50:41: error: llvm/Support/StandardPasses.h: No such file or directory These headers really aren't in the indicated paths. The last header there isn't on tree. If i try to replace the first and second include paths i have others errors. Somebody can help me ? I could not understand why the llvm-backend.cpp isn't compiling....

...b/CodeGen/BackendUtil.cpp" the functions where clang builds the passes to emit code. The optimization passes used are there and you can simulate them via the "opt" utility, by running each pass one at a time. LLVM also declares standard module/function passes on include/llvm/Support/StandardPasses.h. Have a look and see if that's what you want. > -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu > [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Edmund Grimley-Evans > Sent: 16 July 2010 11:25 > To: llvmdev at cs.uiuc.edu > Subject: [LLVMdev] How...

...existing only in case they are needed by the dynamically-generated code that I'm JITing? > > It seems that the combinatorics of which passes to apply, and in which order (including doing some multiple times), are pretty daunting. Other than the Kaleidescope tutorial (too simple) and the StandardPasses.h (too complex?) I can't find any other examples, much less pro/con discussion or guidance. Does anybody have any pointers to web pages or other docs where people have shared their experiences walking through the space of possible pass combinations? > > The application of all of this...

...UnifiedReturnBlock, and replaces ret instructions with jumps to UnifiedReturnBlock. So, it does not eliminates any block but it creates one. (I think its task is to merge the ret instructions (and not the blocks).) The -simplifycfg pass does not affect my code at all. Moreover, according to 'StandardPasses.h' I guess the pass already runs (about 4 times) as a part of -O3. I have yet not looked at the actual code of simplifycfg but the comment in 'StandarPasses.h' says it should merge and eliminate basic blocks. include/llvm/Support/StandardPasses.h, line 129 (SVN-97366): PM->add(cr...