search for: metadata

...lt;stdin>' 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 = "i686-pc-linux-gnu" define i32 @f(i32 %x, i32 %y) nounwind { entry: call void @llvm.dbg.value(metadata !{i32 %x}, i64 0, metadata !0) call void @llvm.dbg.value(metadata !{i32 %y}, i64 0, metadata !7) %add = add nsw i32 %x, %y, !dbg !8 ; <i32> [#uses=1] call void @llvm.dbg.value(metadata !{i32 %add}, i64 0, metadata !10), !dbg !8 ret i32 %add, !dbg !11 } declare void @llvm...

...ternal constant [61 x i8] c"---- %3d tests completed. %d tests passed. %d tests FAILED.\0a\00" define void @check(i32* %result, i32* %expect, i32 %n) { L.entry: %tests_passed = alloca i32 %tests_failed = alloca i32 %i = alloca i32 call void @llvm.dbg.value (metadata !{i32* %result}, i64 0, metadata !9), !dbg !4 call void @llvm.dbg.value (metadata !{i32* %expect}, i64 0, metadata !10), !dbg !4 call void @llvm.dbg.value (metadata !{i32 %n}, i64 0, metadata !11), !dbg !4 call void @llvm.dbg.declare (metadata !{i32* %tests_passed}, metadata...

...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: ; preds = %init call void @llvm.dbg.declare(metadata !{i32* %"bar:Int32"}, metadata !13) store i32 1, i32* %"bar:Int32", !dbg !16 store i32 1, i32* %1, !dbg !17 %3 = load i32* %"bar:Int32", !dbg !17 %4 = load i32* %1, !dbg !17 %5 = add i32 %3, %4, !dbg !17 store i32 %5, i32* %"bar:Int32", !dbg !17...

...alayout = > "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 = "i686-pc-linux-gnu" > > define i32 @f(i32 %x, i32 %y) nounwind { > entry: >  call void @llvm.dbg.value(metadata !{i32 %x}, i64 0, metadata !0) >  call void @llvm.dbg.value(metadata !{i32 %y}, i64 0, metadata !7) >  %add = add nsw i32 %x, %y, !dbg !8              ; <i32> [#uses=1] >  call void @llvm.dbg.value(metadata !{i32 %add}, i64 0, metadata !10), !dbg !8 >  ret i32 %add, !dbg !11 >...

...; <i32*> [#uses=2] %0 = alloca i32 ; <i32*> [#uses=2] %tmp = alloca i32 ; <i32*> [#uses=2] %"alloca point" = bitcast i32 0 to i32 ; <i32> [#uses=0] call void @llvm.dbg.declare(metadata !{i32* %j_addr}, metadata !0), !dbg !6 store i32 %j, i32* %j_addr call void @llvm.dbg.declare(metadata !{i32* %i_addr}, metadata !7), !dbg !6 store i32 %i, i32* %i_addr call void @llvm.dbg.declare(metadata !{i32* %tmp}, metadata !8), !dbg !10 %1 = load i32* %j_addr, align 4, !dbg !11...

...-- %3d tests completed. %d > tests passed. %d tests FAILED.\0a\00" > define void @check(i32* %result, i32* %expect, i32 %n) { > L.entry: > %tests_passed = alloca i32 > %tests_failed = alloca i32 > %i = alloca i32 > call void @llvm.dbg.value (metadata !{i32* %result}, i64 0, > metadata !9), !dbg !4 > call void @llvm.dbg.value (metadata !{i32* %expect}, i64 0, > metadata !10), !dbg !4 > call void @llvm.dbg.value (metadata !{i32 %n}, i64 0, metadata > !11), !dbg !4 > call void @llvm.dbg.declare (metadata !...

...; <i32*> [#uses=4] %Y = alloca i32, align 4 ; <i32*> [#uses=4] %Z = alloca i32, align 4 ; <i32*> [#uses=3] %0 = bitcast i32* %X to { }* ; <{ }*> [#uses=1] call void @llvm.dbg.declare({ }* %0, metadata !0), !dbg !7 store i32 21, i32* %X, !dbg !8 %1 = bitcast i32* %Y to { }* ; <{ }*> [#uses=1] call void @llvm.dbg.declare({ }* %1, metadata !9), !dbg !10 store i32 22, i32* %Y, !dbg !11 %2 = bitcast i32* %Z to { }* ; <{ }*> [#uses=1] call...

...ot;---- %3d tests completed. %d tests passed. %d tests FAILED.\0a\00" > define void @check(i32* %result, i32* %expect, i32 %n) { > L.entry: > %tests_passed = alloca i32 > %tests_failed = alloca i32 > %i = alloca i32 > call void @llvm.dbg.value (metadata !{i32* %result}, i64 0, metadata !9), !dbg !4 > call void @llvm.dbg.value (metadata !{i32* %expect}, i64 0, metadata !10), !dbg !4 > call void @llvm.dbg.value (metadata !{i32 %n}, i64 0, metadata !11), !dbg !4 > call void @llvm.dbg.declare (metadata !{i32* %tests_pa...

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 metadata. These flags are in the form of a key / value pair -- much like a dictionary -- making...

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>

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 gmail.com> wrote: > I figured out my previous problem with DIBuilder. However, now I can't seem > to get...

...*> [#uses=2] > %0 = alloca i32 ; <i32*> [#uses=2] > %tmp = alloca i32 ; <i32*> [#uses=2] > %"alloca point" = bitcast i32 0 to i32 ; <i32> [#uses=0] > call void @llvm.dbg.declare(metadata !{i32* %j_addr}, metadata !0), !dbg !6 > store i32 %j, i32* %j_addr > call void @llvm.dbg.declare(metadata !{i32* %i_addr}, metadata !7), !dbg !6 > store i32 %i, i32* %i_addr > call void @llvm.dbg.declare(metadata !{i32* %tmp}, metadata !8), !dbg !10 > %1 = load i32* %j_add...

...d 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 name of the variable "x". Below is the bitcode generated. It seems like the metadata does not mention "x" anywhere. Am I missing something? Thank you, Cindy ========= ; ModuleID = 'post/tests/test1/source.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-f128:128:1...

...d, 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 > >                         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 metadata. These flags are in the > form of a key / value pair -- much lik...

...:32:64" target triple = "x86_64-unknown-linux-gnu" define i32 @h(i32 %j, i32 %i) nounwind readnone { entry: %0 = add nsw i32 %j, 2, !dbg !0 ; <i32> [#uses=1] %1 = add nsw i32 %0, %i, !dbg !0 ; <i32> [#uses=1] ret i32 %1, !dbg !7 } !0 = metadata !{i32 3, i32 0, metadata !1, null} !1 = metadata !{i32 458763, metadata !2, i32 1, i32 0} ; [ DW_TAG_lexical_block ] !2 = metadata !{i32 458798, i32 0, metadata !3, metadata !"h", metadata !"h", metadata !"h", metadata !3, i32 1, metadata !4, i1 false, i1 true, i32 0,...

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 repres...

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 in general, any information which affects the module as a whole could use this feature. ObjC metadata is just an obvious first step. :-) -bw On Jan 19, 2012, at 9:12 AM, Sandeep Patel wr...

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, ;; Reference to context descriptor metadata, ;; Name metadata, ;; Display name (full...

...gt;> tests passed. %d tests FAILED.\0a\00" >> define void @check(i32* %result, i32* %expect, i32 %n) { >> L.entry: >> %tests_passed = alloca i32 >> %tests_failed = alloca i32 >> %i = alloca i32 >> call void @llvm.dbg.value (metadata !{i32* %result}, i64 0, >> metadata !9), !dbg !4 >> call void @llvm.dbg.value (metadata !{i32* %expect}, i64 0, >> metadata !10), !dbg !4 >> call void @llvm.dbg.value (metadata !{i32 %n}, i64 0, metadata >> !11), !dbg !4 >> call void @llvm...

...inkel 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 I'll update the pocl's work-item replicator first (of which output is effectively the same as a fully unrolled parallel wiloop) to mark the iterations with the iteration argument and see where it gets the WG vectorization using the upst...