similar to: [LLVMdev] [Fwd: Re: [Fwd: Regarding alias analysis pass]]

Hi, I wanted to make a critical evaluation of the kind of aliases recognized by basicaa (Basic Alias Analysis Pass). aa-eval pass just gives the number of aliases discovered but not the actual variables aliased. i tried adding some print statements to BasicAliasAnalysis.cpp to get the above effect. However,my changes are not being reflected in the output.I did make and make install. But even

Hi, I used the following commands on the program attached below: llvm-gcc --emit-llvm main.c -c -o main.bc opt -ipconstprop main.bc -o main1.bc diff main.bc main1.bc no difference was o/p :( The Program Segment is as shown below: #include <stdio.h> void f1(int a) { a=a+1; printf("%d",a); } void f2() { int b; b=1; f1(b); } int main() { int

llvm itself is a plain C++ program, so you can use gdb on it. gdb doesn't know how to step through compiled IR, yet. On Tue, Feb 9, 2010 at 12:13 PM, ambika <ambika at cse.iitb.ac.in> wrote: > No, this is not what I am looking for. I am looking for something like > may be a debugger so that I can trace the function calls in source of llvm. > llvm-db dosent work it says

Dear LLVM, I would like to understand how to improve the LLVM alias analysis accuracy. I am currently using llvmgcc 2.9 and llvm 3.0. Here is the C code: void foo(int a[SIZE], int b[SIZE], int c[SIZE]) { for(int i=0; i<SIZE; i++) c[i] = a[i] + b[i]; } Here is the IR: target datalayout =

Hi I am completely new to LLVM, and I am trying to explore the alias analysis part of it. It seems to me that -basicaa is the most simple alias analysis pass in LLVM. So I would like to try and make it work (to see some alias analysis results of some sample bit code). What I have done is that I ---make lib/Analysis/BasicAliasAnalysis.cpp into a .so file ---write a sample c program, hello.c,

On Tue, Jan 3, 2012 at 4:55 PM, Chris Lattner <clattner at apple.com> wrote: > On Jan 3, 2012, at 1:53 PM, Jianzhou Zhao wrote: >> I see. I asked the question because LLVM provides several alias >> analysis, and I was wondering how to decide which one should be used >> for compiling most programs. >> >> I think the basicaa is the default one, but by looking

On Thu, April 3, 2008 7:33 pm, Chris Lattner wrote: > On Apr 3, 2008, at 1:00 PM, Dan Gohman wrote: >> * BasicAliasAnalysis, the default AliasAnalysis implementation, >> doesn't >> understand lowered GEPs, integer arithmetic, or PHIs, and the >> regular codegen process involves passes that lower GEPs. > > Sure. > >> One way to solve this is to use

On Apr 3, 2008, at 1:00 PM, Dan Gohman wrote: > * BasicAliasAnalysis, the default AliasAnalysis implementation, > doesn't > understand lowered GEPs, integer arithmetic, or PHIs, and the > regular codegen process involves passes that lower GEPs. Sure. > One way to solve this is to use a different AliasAnalysis > implementation. > I haven't looked at it in

dirac wrote: > Hi, > I am using LLVM 2.4 on a Linux RHEL5 machine. I was trying to figure > out how the chaining of the alias analysis passes works in LLVM. Here > are the command I used to test the chaining part. > 1. ./opt hello_world_1_nest_func.bc -o hello_world_1_nest_func_AA.bc > -no-aa -anders-aa -licm > Result: Anderson's AA and No Alias Analysis both are

[+llvmdev] Rajeshwar Vanka wrote: > -----Original Message----- > From: Nick Lewycky [mailto:nicholas at mxc.ca] > Sent: Wednesday, November 24, 2010 3:51 PM > To: dirac > Cc: llvmdev at cs.uiuc.edu > Subject: Re: [LLVMdev] Question regarding the alias analysis chaining > behaviour > > dirac wrote: >> Hi, >> I am using LLVM 2.4 on a Linux RHEL5 machine.

Hi, I have the following C loop to vectorize: struct box { double* source; }; void test(double* restrict result, struct box my_struct, int len) { for (int i=0 ; i<len; i++) { result[i] = my_struct.source[i] * my_struct.source[i]; } } There are two references in the loop, result[i] (restrict) and my_struct.source[i] (readonly). The compiler should easily figure out that

Kenneth Uildriks wrote: > On Wed, Nov 24, 2010 at 2:50 PM, Nick Lewycky<nicholas at mxc.ca> wrote: > >> The AA that you specify will be created when you specify it and live >> until that pass is invalidated (not explicitly preserved by a pass that >> runs). The next time a pass requires AA, the pass manager will create >> the default AA (BasicAA) and not the

Hi, I am using LLVM 2.4 on a Linux RHEL5 machine. I was trying to figure out how the chaining of the alias analysis passes works in LLVM. Here are the command I used to test the chaining part. 1. ./opt hello_world_1_nest_func.bc -o hello_world_1_nest_func_AA.bc -no-aa -anders-aa -licm Result: Anderson's AA and No Alias Analysis both are called. 2. ./opt hello_world_1_nest_func.bc -o

On Fri, 2012-01-27 at 16:46 -0800, Dan Gohman wrote: > On Jan 27, 2012, at 4:15 PM, Maurice Marks wrote: > > > Our application generates IR that is used to generate X86_64 code for a Jit. We noticed that code generated with llvm 3.0 is worse in some circumstances that it was with 2.9. I traced the differences to alias analysis differences. Our IR references data structures that have

On Sep 14, 2007, at 1:43 PM, David Greene wrote: > Can someone explain how RegisterPass and RegisterAnalysisGroup > conspire to pick the right member of an analysis group when command- > line > options dictate non-default implementations? > > For example, when I pass -anders-aa to opt, where in the code is > that option > parsed and setNormalCtor called on the analysis

No, this is not what I am looking for. I am looking for something like may be a debugger so that I can trace the function calls in source of llvm. llvm-db dosent work it says "debugger not implemented" when i try to use it. Can I use gdb or something like that with llvm. What I basically want is to know that when I run some Alias Analysis then from where the functions of file

Hi, I am a Mtech student at IIT,Bombay and presently studying llvm as a part of my Seminar work.Currently,i am writing a simple pass that would detect function pointer call,use and declarations in the src program. I could detect function pointer calls using the getCalledFunction(). However,i am stuck in identifying function pointer declaration and use. is there a way one can distinguish between

On Jan 3, 2012, at 1:53 PM, Jianzhou Zhao wrote: > I see. I asked the question because LLVM provides several alias > analysis, and I was wondering how to decide which one should be used > for compiling most programs. > > I think the basicaa is the default one, but by looking into its code, > it is not inter-procedural or context-sensitive (I am not 100% sure), > so does not

On Fri, Mar 13, 2015 at 2:54 PM Daniel Berlin <dberlin at dberlin.org> wrote: > On Fri, Mar 13, 2015 at 2:39 PM Olivier H Sallenave <ohsallen at us.ibm.com> > wrote: > >> Hi, >> >> I have the following C loop to vectorize: >> >> struct box { >> double* source; >> }; >> >> void test(double* restrict result, struct box

On Thu, Nov 25, 2010 at 3:05 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > Kenneth Uildriks wrote: >> >> On Wed, Nov 24, 2010 at 2:50 PM, Nick Lewycky<nicholas at mxc.ca>  wrote: >> >> I thought analysis passes just rebuilt their state after they got >> invalidated.  Shouldn't that happen with an AA pass as well?  Or is AA >> special? >