similar to: [LLVMdev] Unnamed pass in on the fly pass manager

Solved... For the record, there were two issues: 1) I was not passing the Function to getAnalysis for the PDT. 2) I was attempting to getAnalysis on external functions. On Thu, Jul 9, 2009 at 5:49 PM, Scott Ricketts<sricketts at maxentric.com> wrote: > Update: the "unnamed pass" is PostDominatorTree. My module pass > requires PDT (specified in its getAnalysisUsage). When it

Update: the "unnamed pass" is PostDominatorTree. My module pass requires PDT (specified in its getAnalysisUsage). When it visits a function, it calls getAnalysis<PostDominatorTree>(), which triggers the failed assertion "getAnalysis*() called on an analysis that was not 'required' by pass!" This issue has been addressed on this mailing list, but it seems the

On Thu, Jul 2, 2009 at 2:48 PM, Chris Lattner<clattner at apple.com> wrote: > VMCore will auto-unique value names for you. Most passes just create > all instructions with a name like "tmp" and let VMCore unique them. > Is this enough for you? On Thu, Jul 2, 2009 at 2:50 PM, Eli Friedman<eli.friedman at gmail.com> wrote: > The relevant code is

On Thu, Dec 2, 2010 at 3:20 PM, Chris Lattner <clattner at apple.com> wrote: > > On Dec 2, 2010, at 3:13 PM, Scott Ricketts wrote: > >> The only Transforms check that fails is LLVM :: >> Transforms/GVN/null-aliases-nothing.ll >> >> Could that be related? > > running "opt -basicaa -gvn -S null-aliases-nothing.ll" should produce this output,

Is there a way through the Value class to get the identifier for an unnamed temporary? Or alternatively, could someone point me to the code where temporaries are assigned sequential numbers as identifiers so I can better understand this issue? Thanks, Scott

I want to be able to detect reduction operations using a method similar to that described here: http://portal.acm.org/citation.cfm?id=237578.237581 (I am open to other suggestions if there is a better technique). I am curious if anyone has done this with LLVM or if there are and recommendations for where to start with my implementation. I am only interested in identifying the reductions -- I

I am still having problems getting everything installed. I realized that the successful build of llvm-2.5 had in fact been configured to use the system gcc (4.1.2). However, I was unable to sucessfully build llvm-gcc with gcc 4.1.2. I went back and attempted to build llvm-2.5 with gcc-4.2.4 (installed in a separate directory from system gcc). However, I got the same build error as before. Then I

Here is the output of the test: ******************** FAIL: LLVM :: Transforms/GVN/null-aliases-nothing.ll (4084 of 5497) ******************** TEST 'LLVM :: Transforms/GVN/null-aliases-nothing.ll' FAILED ******************** Script: -- opt /Users/beresini/Desktop/workspace/downloads/llvm-2.8/test/Transforms/GVN/null-aliases-nothing.ll -gvn -S | FileCheck

I am attempting to install llvm on CentOS 5.3, which uses gcc-4.1.2 as its system compiler. Since this compiler has reported to behave poorly with llvm, I built gcc-4.2.4 in an insulated directory for use with my llvm installation. However, I am not sure I am configuring properly. The gcc-4.2.4 installation is in /pkg/bin/gcc-4.2.4. Here is my config line: ../llvm-2.5/configure

To be more specific, it would be helpful to have some utilities for finding dependencies (true, output, and anti-). Where is a good place to start for this kind of analysis? Thanks, Scott On Fri, Oct 9, 2009 at 11:06 AM, Scott Ricketts <sricketts at maxentric.com> wrote: > I want to be able to detect reduction operations using a method > similar to that described here: > >

Ah, nevermind... just needed to make clean to clear out some of the junk I compiled with gcc-4.1.2. The build completed without error. On Fri, May 1, 2009 at 2:14 PM, Scott Ricketts <sricketts at maxentric.com>wrote: > I am attempting to install llvm on CentOS 5.3, which uses gcc-4.1.2 as its > system compiler. Since this compiler has reported to behave poorly with > llvm, I built

Hi all, I recently experienced the same issue as below with LLVM 2.8 on Mac OS 10.5.8. I can load the pass with the debug version of opt, but not the optimized version. Does anyone know what the problem is or have any suggestions for debugging this? My install went fine except for some failures during make check (Unexpected Failures: 92). All failures were in one of the following:

Hello, I just built a virgin ToT (r98634) for release on vanilla Snow Leopard. It seems that the Hello pass doesn't want to load because of undefined symbols: builddir% ../llvm/configure --prefix=$(PWD)/../installdir --enable-optimized builddir% make builddir% make install && cd ../installdir installdir% bin/opt -load lib/libLLVMHello.dylib Error opening

To get Tutorial 1 to compile, I had to cast cout as a raw_osstream, as in: PM.add(createPrintModulePass(&llvm::cout)); ----> PM.add(createPrintModulePass((raw_ostream*)&llvm::cout)); I was getting the following error: $ c++ -g tut1.cpp `llvm-config --cxxflags --ldflags --libs core` -o tut1 tut1.cpp: In function ‘int main(int, char**)’: tut1.cpp:19: error: cannot convert

I am trying to get the address ranges that are allocated by the global variable list of a module. I cannot seem to find an easy way to get the size of a global variable. That is, if the C source looks like: int a[3]; then printing the description of the type of this global looks like: [3 x i32]* Is there some nice way to get "3 words" or "12 bytes" from the above example?

I wrote a pass that attempts to add up the total size of the global data in a module. Currently, it iterates through all of the global values and checks their type sizes using TargetData. I have realized that this is not quite right because global values can point to the same data in memory (or can at least overlap) as in the case of constant strings. Is there an easier way to approach this? It

Did you try changing the name from Hello to MyHello or something like that? I seem to remember having a similar problem. My tutorial code names the struct MyHello and then registers it as follows: RegisterPass<MyHello> X("myhello", "My Hello World Pass"); You will likely need to change the Makefile as well. Scott On Fri, Jun 19, 2009 at 11:15 AM, Juan Carlos Martinez

I would like to be able to instrument va_arg, but when I generate a bc file for a test case using: llvm-gcc -O3 -emit-llvm vararg.c -c -o vararg.bc I do not see va_arg. Instead, it seems the args are accessed through %struct.__va_list_tag, which makes things a bit trickier to instrument. Is there a way to force llvm-gcc to use va_arg? Perhaps there is some documentation about va_list_tag or

I recently began hacking around with my first LLVM pass. The big picture is that I would like to insert function calls for each instruction type, and pass some parameters based on the instruction type. Then I will link the output to some C file that implements those functions. Things were going well until I started trying to make function calls with a pointer as a parameter. For example, I would

Hello, Following the tutorial for writing a pass, I found the next problem. ***************************** :~/llvm/test$ opt -load ../llvm/Debug/lib/mypass.so -mypass < hello.bc > /dev/null opt: Pass.cpp:151: void<unnamed>::PassRegistrar::RegisterPass(const llvm::PassInfo&): Assertion `Inserted && "Pass registered multiple times!"' failed. Aborted