Displaying 8 results from an estimated 8 matches for "tag_base_typ".
Did you mean:
tag_base_type
2015 Jan 19
2
[LLVMdev] Dropping the DW_ prefix from names in dwarfdump
...AT_name( "y" )
> AT_decl_file( "/llvm_cmake/test.cc <http://test.cc/>" )
> AT_decl_line( 1 )
> AT_type( {0x00000057} ( int ) )
>
> 0x00000056: NULL
>
> 0x00000057: TAG_base_type [4]
> AT_name( "int" )
> AT_encoding( DW_ATE_signed )
> AT_byte_size( 0x04 )
>
> 0x0000005e: NULL
>
>
> and here is the same file with -v:
>
> ------------------------------------------------------...
2015 Jan 19
2
[LLVMdev] Dropping the DW_ prefix from names in dwarfdump
Hey guys,
Frederic is introducing the expression dumping support and in the interests
of tersity is skipping the "DW_" in every "DW_OP" (heck, we could even skip
the "OP" given the context - nothing else textual can appear there, right?)
Any thoughts on skipping the "DW_" (maybe even the AT/TAG/FORM too) in the
rest of dwarfdump? (skipping the AT/TAG (FORM
2015 Jan 19
2
[LLVMdev] Dropping the DW_ prefix from names in dwarfdump
..." )
>> AT_decl_file( "/llvm_cmake/test.cc <http://test.cc/>" )
>> AT_decl_line( 1 )
>> AT_type( {0x00000057} ( int ) )
>>
>> 0x00000056: NULL
>>
>> 0x00000057: TAG_base_type [4]
>> AT_name( "int" )
>> AT_encoding( DW_ATE_signed )
>> AT_byte_size( 0x04 )
>>
>> 0x0000005e: NULL
>>
>>
>> and here is the same file with -v:
>>
>> --------------...
2015 Jan 20
2
[LLVMdev] Dropping the DW_ prefix from names in dwarfdump
...000000184: rsp+16, deref )
AT_name( "y" )
AT_decl_file( "/llvm_cmake/test.cc<http://test.cc/>" )
AT_decl_line( 1 )
AT_type( {0x00000057} ( int ) )
0x00000056: NULL
0x00000057: TAG_base_type [4]
AT_name( "int" )
AT_encoding( DW_ATE_signed )
AT_byte_size( 0x04 )
0x0000005e: NULL
and here is the same file with -v:
----------------------------------------------------------------------
File: out.o {mach64-x86_64-MH_OBJE...
2008 Apr 23
3
[LLVMdev] Compile units in debugging intrinsics / globals
...mpile unit "file2" (and there are
no basic types in file2, so int is not defined), and fn2 appears to be in
compile unit "file3". My dwarf records are therefore incorrect, appearing
something like
TAG_compile_unit "file1"
TAG_subprogram "fn1" ...
...
TAG_base_type "int" ...
TAG_compile_init "file2"
TAG_variable "a" ...
TAG_compile_unit "file3"
TAG_subprogram "fn2" ...
...
When, in fact, these compile units "file2" and "file3" are bogus and
everything should be part of compile_u...
2011 Dec 29
2
[LLVMdev] DW_AT_location not getting generated for local variables
...{i32 720917, i32 0, metadata !"", i32 0, i32 0, i64 0, i64
0, i32 0, i32 0, i32 0, metadata !9, i32 0, i32 0} ; [
DW_TAG_subroutine_type ]
!9 = metadata !{metadata !10}
!10 = metadata !{i32 720932, null, metadata !"Int32", null, i32 0, i64 32,
i64 32, i64 0, i32 0, i32 5} ; [ DW_TAG_base_type ]
!11 = metadata !{metadata !12}
!12 = metadata !{metadata !13}
!13 = metadata !{i32 721152, metadata !14, metadata !"bar", metadata !7,
i32 2, metadata !10, i32 0, i32 0} ; [ DW_TAG_auto_variable ]
!14 = metadata !{i32 720907, metadata !15, i32 1, i32 1, metadata !7, i32
1} ; [ DW_TAG_l...
2008 Apr 24
0
[LLVMdev] Compile units in debugging intrinsics / globals
...are
> no basic types in file2, so int is not defined), and fn2 appears to be in
> compile unit "file3". My dwarf records are therefore incorrect, appearing
> something like
>
> TAG_compile_unit "file1"
> TAG_subprogram "fn1" ...
> ...
> TAG_base_type "int" ...
>
> TAG_compile_init "file2"
> TAG_variable "a" ...
>
> TAG_compile_unit "file3"
> TAG_subprogram "fn2" ...
> ...
>
> When, in fact, these compile units "file2" and "file3" are bog...
2012 Jan 02
0
[LLVMdev] DW_AT_location not getting generated for local variables
...metadata !"", i32 0, i32 0, i64 0, i64 0,
> i32 0, i32 0, i32 0, metadata !9, i32 0, i32 0} ; [ DW_TAG_subroutine_type ]
> !9 = metadata !{metadata !10}
> !10 = metadata !{i32 720932, null, metadata !"Int32", null, i32 0, i64 32,
> i64 32, i64 0, i32 0, i32 5} ; [ DW_TAG_base_type ]
> !11 = metadata !{metadata !12}
> !12 = metadata !{metadata !13}
> !13 = metadata !{i32 721152, metadata !14, metadata !"bar", metadata !7, i32
> 2, metadata !10, i32 0, i32 0} ; [ DW_TAG_auto_variable ]
> !14 = metadata !{i32 720907, metadata !15, i32 1, i32 1, metadat...