Displaying 20 results from an estimated 50000 matches similar to: "[LLVMdev] Aliasing Info. in LLVM."
2009 Jul 13
2
[LLVMdev] Aliasing on bitcode.
Dear All,
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? (does it support multi-threaded apps?) What is the best way of doing it (I want to extract aliasing information in runOnModule() function in the pass I
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 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.
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.
> -----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.
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
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
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.
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 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
2010 Feb 15
3
[LLVMdev] A very basic doubt about LLVM Alias Analysis
Hi,
Using this option I do get all the vars as may alias ie
MayAlias: i32* %j.0, i32* %k
MayAlias: i32* %i.0, i32* %k
MayAlias: i32* %i.0, i32* %j.0
Is there any other analysis which will give them as must aliases.
Actually what I want to do is implement a flow sensitive points-to(not
alias) analysis and then use that information for some optimizations
like PRE.
Will that be
2010 Oct 30
1
[LLVMdev] strict aliasing and LLVM
On Sat, Oct 30, 2010 at 1:44 AM, Nick Lewycky <nicholas at mxc.ca> wrote:
> Xinliang David Li wrote:
>
>>
>>
>> On Fri, Oct 29, 2010 at 12:26 AM, Nick Lewycky <nicholas at mxc.ca
>> <mailto:nicholas at mxc.ca>> wrote:
>>
>> Xinliang David Li wrote:
>>
>> As simple as
>>
>> void foo (int n, double
2016 Apr 18
2
Different index types in GEPs -> non-aliasing?
Hi,
It seems that opt thinks that the two pointers
%_tmp2 = getelementptr [3 x i16], [3 x i16]* %a, i16 0, i64 1
and
%_tmp4 = getelementptr [3 x i16], [3 x i16]* %a, i16 0, i16 1
does not alias? Is this intended or a bug?
Details below:
--------------
I found this when I ran opt on:
define i16 @f () {
%a = alloca [3 x i16]
; Write 98 at index 1 in the array.
; NB: using i64 as
2009 Jun 30
2
[LLVMdev] Limitations of Alias Analysis?
Hi,
Thanks for your advice. I have tried this way:
opt -mem2reg test.bc -o mem2reg.bc
llvm-dis mem2reg.bc
opt -functionattrs -basicaa -aa-eval -print-all-alias-modref-info
mem2reg.bc
The content of main() in mem2reg.ll:
define i32 @main() nounwind {
entry:
%"alloca point" = bitcast i32 0 to i32 ; <i32> [#uses=0]
%0 = call %struct.Location* @getNewLocation(i32 0, i32
2010 Oct 29
2
[LLVMdev] strict aliasing and LLVM
On Oct 29, 2010, at 12:26 AM, Nick Lewycky wrote:
> Xinliang David Li wrote:
>> As simple as
>>
>> void foo (int n, double *p, int *q)
>> {
>> for (int i = 0; i < n; i++)
>> *p += *q;
>> }
>>
>> clang -O2 -fstrict-aliasing -emit-llvm -o foo.bc -c foo.c
>> llc -enable-tbaa -O2 -filetype=asm -o foo.s foo.bc
>
>
2009 Jul 27
2
[LLVMdev] Reachability info in LLVM?
Dear All,
I am new to LLVM and want to know if LLVM provides any reachability information about the instructions inside a function? For example, is instruction 'J' reachable from the instruction 'I'? (just based on CFG)
Thanks a lot,
::Saman
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2009 Jul 28
1
[LLVMdev] Reachability info in LLVM?
Thanks. that's right but I was looking for sth like "successor closure" set for each instruction 'I' that includes all reachable instructions from I.
Does LLVM provide such a set?
Thanks alot,
::Saman
Dear All,
>
>I am new to LLVM and want to know if LLVM provides any reachability information about the instructions inside a function? For example, is instruction
2010 Oct 29
0
[LLVMdev] strict aliasing and LLVM
Xinliang David Li wrote:
> As simple as
>
> void foo (int n, double *p, int *q)
> {
> for (int i = 0; i < n; i++)
> *p += *q;
> }
>
> clang -O2 -fstrict-aliasing -emit-llvm -o foo.bc -c foo.c
> llc -enable-tbaa -O2 -filetype=asm -o foo.s foo.bc
There's a couple things interacting here:
* clang -fstrict-aliasing -O2 does generate the TBAA info, but
2010 Oct 30
0
[LLVMdev] strict aliasing and LLVM
Dan Gohman wrote:
>
> On Oct 29, 2010, at 12:26 AM, Nick Lewycky wrote:
>
>> Xinliang David Li wrote:
>>> As simple as
>>>
>>> void foo (int n, double *p, int *q)
>>> {
>>> for (int i = 0; i< n; i++)
>>> *p += *q;
>>> }
>>>
>>> clang -O2 -fstrict-aliasing -emit-llvm -o foo.bc -c foo.c
2010 Oct 30
0
[LLVMdev] strict aliasing and LLVM
Xinliang David Li wrote:
>
>
> On Fri, Oct 29, 2010 at 12:26 AM, Nick Lewycky <nicholas at mxc.ca
> <mailto:nicholas at mxc.ca>> wrote:
>
> Xinliang David Li wrote:
>
> As simple as
>
> void foo (int n, double *p, int *q)
> {
> for (int i = 0; i < n; i++)
> *p += *q;
> }
>
>