similar to: [LLVMdev] Aliasing on bitcode.

Displaying 20 results from an estimated 2000 matches similar to: "[LLVMdev] Aliasing on bitcode."

2009 Jul 13
0
[LLVMdev] Aliasing on bitcode.
On Mon, Jul 13, 2009 at 3:28 PM, saman aliari<samy_442 at yahoo.com> wrote: > I am working on a LLVM bitcode based project in which we do static lockset > analysis. I need to get Aliasing information statically given the .bc file > of the application. Is there any library in LLVM which already implements > the aliasing? There's an alias analysis interface that comes standard
2009 Jul 09
5
[LLVMdev] Source file information.
Hi, I am new to LLVM, and need to find the line number and cpp source file name for each instruction in a .bc file. I suppose llvm debugger might have that feature but there is no documentation on it. Would you please give me some help how to do it? Thanks, ::Saman Zonouz University of Illinois -------------- next part -------------- An HTML attachment was scrubbed... URL:
2009 Jul 09
3
[LLVMdev] Source file information.
>> -----Original Message----- >> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On >> Behalf Of Saman Aliari Zonouz >> Sent: Thursday, July 09, 2009 11:44 AM >> To: llvmdev at cs.uiuc.edu >> Subject: [LLVMdev] Source file information. >> >> Hi, >> >> I am new to LLVM, and need to find the line number
2009 Jul 09
0
[LLVMdev] Source file information.
Thanks for your reply. Is it not possible to do with llvm-g++ -g? and furthermore, where are SDNode and DebugLoc fields stored? are they in a file which I have to parse myself? if so, is there any way that I use a library to get the file/line information for each instruction? since, I am writing a pass for opt tool that manipulates the callgraph and want to get the line number information in
2009 Jul 09
0
[LLVMdev] Source file information.
On 2009-07-09 11:17, Aaron Gray wrote: >>> -----Original Message----- >>> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] >>> >> On >> >>> Behalf Of Saman Aliari Zonouz >>> Sent: Thursday, July 09, 2009 11:44 AM >>> To: llvmdev at cs.uiuc.edu >>> Subject: [LLVMdev] Source file
2009 Jun 15
1
[LLVMdev] VmKit Question.
Hi, I compiled VmKit and got it running, but do not know how it is possible to emit llvm-bitcode fram .java code. Would you please help me? Thanks, ::Saman -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090615/79240d35/attachment.html>
2009 Jul 07
1
[LLVMdev] LLVM Question.
Hi, I am Saman, a UIUC PhD student working with LLVM. Would you please let me know how I can extract CG and CFG for a given application? Thanks a lot, ::Saman -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090707/951958b6/attachment.html>
2009 Jul 09
0
[LLVMdev] Source file information.
> -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On > Behalf Of Saman Aliari Zonouz > Sent: Thursday, July 09, 2009 11:44 AM > To: llvmdev at cs.uiuc.edu > Subject: [LLVMdev] Source file information. > > Hi, > > I am new to LLVM, and need to find the line number and cpp source file > name for each
2009 Jul 09
5
[LLVMdev] Source file information.
Dear All, To add to this, what you want to do is find the appropriate debug stop point intrinsic and then use it to look up the information for that instruction. Here is some sample code from SAFECode that finds the debug information associated with a CallInst (LLVM call instruction) held in the variable CI. It uses the findStopPoint() function in llvm/Analyis/DebugInfo.h: // // Get the
2009 Jul 17
1
[LLVMdev] Function Argument in LLVM
Hi, I am new to LLVM, and want to get the name of each argument for a given Function in a .bc file. Function.Argument.getName() returns "". Could somebody please help me figure this out? Thanks, ::Saman Zonouz -------------- next part -------------- An HTML attachment was scrubbed... URL:
2009 Jul 09
0
[LLVMdev] Source file information.
Dear All, To add to this, what you want to do is find the appropriate debug stop point intrinsic and then use it to look up the information for that instruction. Here is some sample code from SAFECode that finds the debug information associated with a CallInst (LLVM call instruction) held in the variable CI. It uses the findStopPoint() function in llvm/Analyis/DebugInfo.h: // // Get the
2009 Jul 09
3
[LLVMdev] Source file information.
Aaron Gray wrote: > Dear All, > > To add to this, what you want to do is find the appropriate debug stop > point intrinsic and then use it to look up the information for that > instruction. > > Here is some sample code from SAFECode that finds the debug information > associated with a CallInst (LLVM call instruction) held in the variable > CI. It uses the
2016 Jan 27
2
Skip redundant checks in AliasSet::aliasesUnknownInst
On 01/27/2016 07:53 AM, Daniel Berlin wrote: > > > On Wed, Jan 27, 2016 at 1:27 AM, Roman Gareev <gareevroman at gmail.com > <mailto:gareevroman at gmail.com>> wrote: > > Thank you for the idea! Could you please explain it? > > > Which part are you having trouble with, so i know where to concetrate? > > If I’m not > mistaken, you advise
2006 May 14
2
[LLVMdev] __main() function and AliasSet
In a code segment of my pass plugin, I try to gather AliasSets for all StoreInst, LoadInst and CallInst instructions in a function. Some behaviors of the pass puzzled me. Below is the *.ll of the test program which I run the pass on, it was get with "llvm-gcc -Wl,--disable-opt" from a rather simple *.c program. ---------------------------------- ; ModuleID = 'ptralias.bc'
2006 May 15
2
[LLVMdev] Re: __main() function and AliasSet
Hi Chris, I took a haste look at the "Points-to Analysis in Almost Linear Time" by Steens , your PHD thesis and SteensGaard.cpp in LLVM this afternoon. So I think: 1. Actually the basic algorithm described originally by SteensGaard does not provide MOD/REF information for functions. 2. The context insensitive part of Data Structure Analysis (LocalAnalysis) can be deemed as an
2006 May 14
0
[LLVMdev] Re: __main() function and AliasSet
Oh, I appologize that I should not have asked about __main() ---- it appears in FAQ. But the question remains that why call to __main() can alias stack location? I think the memory location pointed by data_X pointers are not visible to __main(). In comparison, calls to printf() do not have similar effect. On 5/14/06, Nai Xia <nelson.xia at gmail.com> wrote: > > In a code segment of
2006 May 15
0
[LLVMdev] Re: __main() function and AliasSet
On Mon, 15 May 2006, Nai Xia wrote: > In other words, if I only use -steens-aa and the data_XXXs are all > external global variables( and so inComplete ), Sounds right! > the call to printf will > make the same effect, which I have tested it. > > Am I right ? :) If you've tested it then, yes you're right :). I haven't played with this stuff for a long time,
2009 Jul 09
1
[LLVMdev] Source file information.
Thanks for your reply. Is it not possible to do with llvm-g++ -g? Yes and furthermore, where are SDNode and DebugLoc fields stored? They are probably classes in the Clang API are they in a file which I have to parse myself? if so, is there any way that I use a library to get the file/line information for each instruction? Yes Clang API :- http://clang.llvm.org/doxygen/classes.html
2006 May 17
2
[LLVMdev] Re: __main() function and AliasSet
On Tuesday 16 May 2006 03:19, Chris Lattner wrote: > On Mon, 15 May 2006, Nai Xia wrote: > > > In other words, if I only use -steens-aa and the data_XXXs are all > > external global variables( and so inComplete ), > > Sounds right! > > > the call to printf will > > make the same effect, which I have tested it. > > > > Am I right ? :) >
2006 May 17
0
[LLVMdev] Re: __main() function and AliasSet
On Wed, 17 May 2006, Nai Xia wrote: > Unfortunately, I did not locate the lines in steens-aa for "printf" special case. > In ds-aa, I found the lines below: Right, steens-aa and ds-aa share code for "local analysis", they just stitch it together into an interprocedural analysis in different ways. The code below is used for steens-aa. >