Displaying 5 results from an estimated 5 matches for "458804".
Did you mean:
58804
2009 Jul 27
2
[LLVMdev] PROPOSAL : Introduce NamedMetadata
...le.
The idea is to provide a way to have metadata that is not directly
used by any LLVM IR entity. Here the metadata entity can itself use
any other LLVM IR entity. For example
; ModuleID = 'blah.c'
!1 = { i32 459008, metadata !"blah.c", "b", i32 4, i32 6 }
!2 = { i32 458804, metadata !"blah.c", "a", i32 4, i32 6, i32 %a }
a = global i32 42
define void @foo() {
call void @llvm.dbg.declare(!1)
}
---
Here !1 and !2 encodes debug info for a local variable 'b' and global
variable 'a' respectively. !1 is one of the llvm.dbg.declare a...
2009 Jul 27
0
[LLVMdev] PROPOSAL : Introduce NamedMetadata
...to have metadata that is not directly
> used by any LLVM IR entity. Here the metadata entity can itself use
> any other LLVM IR entity. For example
>
> ; ModuleID = 'blah.c'
>
> !1 = { i32 459008, metadata !"blah.c", "b", i32 4, i32 6 }
> !2 = { i32 458804, metadata !"blah.c", "a", i32 4, i32 6, i32 %a }
> a = global i32 42
>
> define void @foo() {
> call void @llvm.dbg.declare(!1)
> }
>
> ---
>
> Here !1 and !2 encodes debug info for a local variable 'b' and global
> variable 'a' res...
2009 Jul 27
0
[LLVMdev] PROPOSAL : Introduce NamedMetadata
On Jul 27, 2009, at 10:10 AM, Devang Patel wrote:
> In LLVM IR metadata is used to attach auxiliary information with
> various IR constructs. Currently metadata information is represented
> using MDNode and MDString. The metadata can refer to LLVM values but
> these references are not counted as regular "uses" of these values
> because metadata is maintained 'on the
2009 Jul 27
4
[LLVMdev] PROPOSAL : Introduce NamedMetadata
In LLVM IR metadata is used to attach auxiliary information with
various IR constructs. Currently metadata information is represented
using MDNode and MDString. The metadata can refer to LLVM values but
these references are not counted as regular "uses" of these values
because metadata is maintained 'on the side'. This ensures that the
optimizer is not influenced by auxiliary
2009 Oct 21
1
[LLVMdev] A few more questions about DIFactory and source-level debugging.
Well, I am much happier now that I understand about dsymutil, and can
actually step through my program in gdb. However, there are still some
issues that are puzzling me.
1) First off, the debugger appears to stop at odd points. The IR for my main
function looks correct to me:
define i32
@"main(tart.core.Array[tart.core.String])->int"(%"tart.core.Array[tart.core.String]"*