Displaying 20 results from an estimated 11437 matches for "metadatas".
Did you mean:
metadata
2010 Jul 14
2
[LLVMdev] Trying to access the user defined variable name
Dear all,
I have the following source code:
long f(long x, long y)
{
long u;
u = x+y;
return u;
};
After clang (with debug option set) and llvm opt using mem2reg, I get
the following .ll file
***************************************************************************
; ModuleID = '<stdin>'
target datalayout =
2012 Mar 02
2
[LLVMdev] Question on debug information
Hi all,
I'm using my own front-end to generate following code .ll file targeting
x86 32-bit:
; ModuleID = 'check.c'
target datalayout =
"e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:32:64-f32:32:32-f64:32:64-v64:64:64-v128:128:128-a0:0:64-f80:32:32-n8:16:32"
target triple = "i386-pc-linux-gnu"
@.str581 = internal constant [52 x i8] c"---- test number %d
2011 Dec 29
2
[LLVMdev] DW_AT_location not getting generated for local variables
I figured out my previous problem with DIBuilder. However, now I can't seem
to get the compiler to emit location information for local variables.
Here's how my IR looks:
---
define i32 @"\01_main"() {
init:
%exception1 = alloca i8*
%0 = alloca i32
%"bar:Int32" = alloca i32
%1 = alloca i32
%2 = alloca i32*
br label %code
code:
2010 Jul 15
0
[LLVMdev] Trying to access the user defined variable name
On Wed, Jul 14, 2010 at 3:03 PM, Arvind Sudarsanam
<arvind.sudarsanam at aggiemail.usu.edu> wrote:
> Dear all,
>
> I have the following source code:
>
> long f(long x, long y)
> {
> long u;
>
> u = x+y;
> return u;
> };
>
> After clang (with debug option set) and llvm opt using mem2reg, I get
> the following .ll file
>
2010 May 13
4
[LLVMdev] How to get the variable mapping between the source and llvm bytecode
Hi,
I want to know the variable mapping between the source and llvm bytecode. It seems that current llvm debugging information cannot provide this mapping directly.
Here is my examples (llvm 2.7). In this exmaple, I want to know the mapping: tmp<--->%4. But current llvm's debugging information can only provide that the instruction "%4 = add nsw i32 %3, 2" is at line 3 in
2012 Mar 06
0
[LLVMdev] Question on debug information
Hi all,
Anyone have ideas/info on this topic ?
Thanks
Seb
2012/3/2 Seb <babslachem at gmail.com>
> Hi all,
>
> I'm using my own front-end to generate following code .ll file targeting
> x86 32-bit:
>
> ; ModuleID = 'check.c'
> target datalayout =
>
2010 Apr 26
0
[LLVMdev] Does llvm-gcc emit column # info?
Hi Duncan,
But in the doc "Source Level Debugging with LLVM", it shows that llvm 2.6 could get column number. There's an example in the doc as following:
http://llvm.org/docs/SourceLevelDebugging.html
1. void foo() {
2. int X = 21;
3. int Y = 22;
4. {
5. int Z = 23;
6. Z = X;
7. }
8. X = Y;
9. }
Compiled to LLVM, this function would be represented
2012 Mar 06
2
[LLVMdev] Question on debug information
On Mar 6, 2012, at 5:31 AM, Seb <babslachem at gmail.com> wrote:
> Hi all,
>
> Anyone have ideas/info on this topic ?
> Thanks
> Seb
>
> 2012/3/2 Seb <babslachem at gmail.com>
> Hi all,
>
> I'm using my own front-end to generate following code .ll file targeting x86 32-bit:
>
> ; ModuleID = 'check.c'
> target datalayout =
2012 Jan 18
7
[LLVMdev] [RFC] Module Flags Metadata
Hello,
This is a proposal for implementing "module flags". Please take a look at this and give any feedback you may have.
Thanks!
-bw
Module Flags Metadata
Information about the module as a whole is difficult to convey to LLVM's
subsystems. The LLVM IR isn't sufficient to transmit this information. One
should instead use the llvm.module.flags named
2010 Apr 26
3
[LLVMdev] Does llvm-gcc emit column # info?
Hi,
I tried llvm-gcc -g -O0 on several cases, but the column field of meta data
always shows zero in created ll code.
Does llvm-gcc emit column # info ? Or I should add some option?
Thanks in advance.
Sheng.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100426/76b52b1f/attachment.html>
2012 Jan 02
0
[LLVMdev] DW_AT_location not getting generated for local variables
I found the problem. The llvm.dbg.declare call must have a !dbg tag,
otherwise the location info is not generated. Changing the invocation
in my original example to "call void @llvm.dbg.declare(metadata !{i32*
%"bar:Int32"}, metadata !13), !dbg !16" causes MC to generate the
local location as expected.
-Joe
On Thu, Dec 29, 2011 at 12:41 PM, Joe Groff <arcata at
2010 May 13
0
[LLVMdev] How to get the variable mapping between the source andllvm bytecode
Hi,
I want to get the mapping between C source's variables and bytecode variables. It seems that llvm doesn't provide this mapping, so I think a walk-around method is to get the instruction's mapping. I have to use llvm-gcc, not clang. Any advice? Thanks.
Best,
Kecheng
2010-05-13
From: Eli Friedman
Date: 2010-05-13 15:38:36
To: Kecheng
Cc: llvmdev
Subject: Re: [LLVMdev] How
2011 Aug 16
1
[LLVMdev] Missing metadata for volatile variables
Hi everyone,
I am using the dragonegg plugin to produce bitcode for the following
small C program:
int main() {
1: int x = -5;
2: x = 6;
3: return 0;
}
The assignments on lines 1 and 2 are removed even when no optimization
flags are specified. I tried making variable "x" volatile, which
prevents the assignments from being removed, however I am no longer
able to recover the original
2012 Jan 19
1
[LLVMdev] [cfe-dev] [RFC] Module Flags Metadata
Could you expand on likely uses other than ObjC? For example, should
float ABI (soft/softfp/hard) be conveyed via this mechanism?
deep
On Wed, Jan 18, 2012 at 9:36 PM, Bill Wendling <wendling at apple.com> wrote:
> Hello,
>
> This is a proposal for implementing "module flags". Please take a look at this and give any feedback you may have.
>
> Thanks!
> -bw
>
2010 May 14
2
[LLVMdev] How to get the variable mapping between the sourceandllvm bytecode
Eli,
Thanks very much for your reply. That's what I want to know. It works for this example. But I usually have to deal with the optimized bytecode with "-O".
See the example:
**************
C source
**************
int h (int j, int i) {
int tmp;
tmp = j+i+2;
return tmp;
}
+++++++++++++++++++++++++++++++++++++
.ll file:
; ModuleID = 'simplecase.c'
target
2011 Mar 25
1
[LLVMdev] Named metadata to represent language specific logic
Hi all,
I was wondering if we could use named metadata to store some of C++
logic without changing the IR. This is primarily only for front-end
buiding and the resulting IR (with or without metadata) should be the
same as it is today (or better).
I say this because of the number of global variables front-ends need
to keep because LLVM IR cannot represent all the information of types,
vatriables,
2012 Jan 19
0
[LLVMdev] [cfe-dev] [RFC] Module Flags Metadata
Hi Sandeep,
ObjC is the first place that I will use it, of course (we need it to fix LTO). Other uses will come along later. (I don't know enough about the float ABI issues to say whether they should be done via module flags or not.) The OpenCL people have a need for named metadata for their stuff. I would hope that module flags would be a good fit for that, but that remains to be seen. But
2011 Dec 15
2
[LLVMdev] LLVM 2.9 metadata
Hi all,
In LLVM documentation about source level debugging
(http://www.llvm.org/releases/2.9/docs/SourceLevelDebugging.html)
Subprogram descriptor is defined as:
!2 = metadata !{
i32, ;; Tag = 46 + LLVMDebugVersion
<http://www.llvm.org/releases/2.9/docs/SourceLevelDebugging.html#LLVMDebugVersion>
;; (DW_TAG_subprogram)
i32, ;; Unused field.
metadata, ;;
2012 Mar 07
0
[LLVMdev] Question on debug information
Hi Jim,
Thanks for the advice. Since I'm using LLVM 2.9 style of debug information.
Will this code benefit from those improvement or should I generate LLVM 3.0
style of debug information ?
Best Regards
Seb
2012/3/6 Jim Grosbach <grosbach at apple.com>
>
> On Mar 6, 2012, at 5:31 AM, Seb <babslachem at gmail.com> wrote:
>
> Hi all,
>
> Anyone have ideas/info on
2013 Feb 19
0
[LLVMdev] Pointer Context Metadata (was: Parallel Loop Metadata)
On 02/19/2013 05:51 PM, Hal Finkel wrote:
> Understood. If you have some time, it seems that there are several sub-tasks:
>
> - Update the language reference
Document the additional optional iteration id argument to
llvm.mem.parallel_loop_access? I'll do this.
> - Update the loop vectorizer (to update the metadata when it unrolls)
> - Update the regular unroller