Displaying 10 results from an estimated 10 matches for "zdebug_rang".
Did you mean:
debug_range
2013 Apr 16
3
[LLVMdev] RFC: Using zlib to decompress debug info sections.
...000053 0000000000000000
29 .zdebug_aranges 00000014 0000000000000000
30 .zdebug_macinfo 00000014 0000000000000000
31 .zdebug_line 0000005b 0000000000000000
32 .zdebug_loc 00000014 0000000000000000
33 .zdebug_pubtypes 00000014 0000000000000000
34 .zdebug_str 00000073 0000000000000000
35 .zdebug_ranges 00000014 0000000000000000
Decompression and proper handling of debug info sections may be needed
in llvm-dwarfdump and llvm-symbolizer tools. We can implement this by:
1) Checking if zlib is present in the system during configuration.
2) Adding zlib decompression to llvm::MemoryBuffer, and secti...
2018 Feb 08
2
LLD: targeting cygwin
...*(.zdebug_varnames)
}
.debug_macro BLOCK(__section_alignment__) (NOLOAD) :
{
*(.debug_macro)
}
.zdebug_macro BLOCK(__section_alignment__) (NOLOAD) :
{
*(.zdebug_macro)
}
/* DWARF 3. */
.debug_ranges BLOCK(__section_alignment__) (NOLOAD) :
{
*(.debug_ranges)
}
.zdebug_ranges BLOCK(__section_alignment__) (NOLOAD) :
{
*(.zdebug_ranges)
}
/* DWARF 4. */
.debug_types BLOCK(__section_alignment__) (NOLOAD) :
{
*(.debug_types .gnu.linkonce.wt.*)
}
.zdebug_types BLOCK(__section_alignment__) (NOLOAD) :
{
*(.zdebug_types .zdebug.gnu.linkonce.wt.*)...
2013 Apr 16
2
[LLVMdev] RFC: Using zlib to decompress debug info sections.
...000000000000000
>> 30 .zdebug_macinfo 00000014 0000000000000000
>> 31 .zdebug_line 0000005b 0000000000000000
>> 32 .zdebug_loc 00000014 0000000000000000
>> 33 .zdebug_pubtypes 00000014 0000000000000000
>> 34 .zdebug_str 00000073 0000000000000000
>> 35 .zdebug_ranges 00000014 0000000000000000
>>
>> Decompression and proper handling of debug info sections may be needed
>> in llvm-dwarfdump and llvm-symbolizer tools. We can implement this by:
>> 1) Checking if zlib is present in the system during configuration.
>> 2) Adding zlib de...
2018 Feb 09
0
LLD: targeting cygwin
...t__) (NOLOAD) :
> {
> *(.debug_macro)
> }
> .zdebug_macro BLOCK(__section_alignment__) (NOLOAD) :
> {
> *(.zdebug_macro)
> }
> /* DWARF 3. */
> .debug_ranges BLOCK(__section_alignment__) (NOLOAD) :
> {
> *(.debug_ranges)
> }
> .zdebug_ranges BLOCK(__section_alignment__) (NOLOAD) :
> {
> *(.zdebug_ranges)
> }
> /* DWARF 4. */
> .debug_types BLOCK(__section_alignment__) (NOLOAD) :
> {
> *(.debug_types .gnu.linkonce.wt.*)
> }
> .zdebug_types BLOCK(__section_alignment__) (NOLOAD) :
>...
2013 Apr 16
0
[LLVMdev] RFC: Using zlib to decompress debug info sections.
...debug_aranges 00000014 0000000000000000
> 30 .zdebug_macinfo 00000014 0000000000000000
> 31 .zdebug_line 0000005b 0000000000000000
> 32 .zdebug_loc 00000014 0000000000000000
> 33 .zdebug_pubtypes 00000014 0000000000000000
> 34 .zdebug_str 00000073 0000000000000000
> 35 .zdebug_ranges 00000014 0000000000000000
>
> Decompression and proper handling of debug info sections may be needed
> in llvm-dwarfdump and llvm-symbolizer tools. We can implement this by:
> 1) Checking if zlib is present in the system during configuration.
> 2) Adding zlib decompression to llvm:...
2013 Apr 16
0
[LLVMdev] RFC: Using zlib to decompress debug info sections.
...> 30 .zdebug_macinfo 00000014 0000000000000000
>>> 31 .zdebug_line 0000005b 0000000000000000
>>> 32 .zdebug_loc 00000014 0000000000000000
>>> 33 .zdebug_pubtypes 00000014 0000000000000000
>>> 34 .zdebug_str 00000073 0000000000000000
>>> 35 .zdebug_ranges 00000014 0000000000000000
>>>
>>> Decompression and proper handling of debug info sections may be needed
>>> in llvm-dwarfdump and llvm-symbolizer tools. We can implement this by:
>>> 1) Checking if zlib is present in the system during configuration.
>>&g...
2013 Apr 16
2
[LLVMdev] RFC: Using zlib to decompress debug info sections.
...00000014 0000000000000000
> >>> 31 .zdebug_line 0000005b 0000000000000000
> >>> 32 .zdebug_loc 00000014 0000000000000000
> >>> 33 .zdebug_pubtypes 00000014 0000000000000000
> >>> 34 .zdebug_str 00000073 0000000000000000
> >>> 35 .zdebug_ranges 00000014 0000000000000000
> >>>
> >>> Decompression and proper handling of debug info sections may be needed
> >>> in llvm-dwarfdump and llvm-symbolizer tools. We can implement this by:
> >>> 1) Checking if zlib is present in the system during confi...
2018 Feb 07
0
LLD: targeting cygwin
COFF lld doesn't support the linker script at the moment, and I'm sad to
say that it is very unlikely to support that in the future. Linker script
support is so huge that I can't imagine we really want it for COFF. GNU BFD
linker supports it because the linker is built as an interpreter for the
built-in linker script (and that's one of the reasons why GNU linker is by
far more
2018 Feb 07
2
LLD: targeting cygwin
Hello, I have a user who is trying to get LLD to link for the cygwin
target: https://github.com/zig-lang/zig/issues/751
Currently the issue they are running into is needing to define a linker
script, but the COFF driver (or MinGW driver) does not have support for
that.
Is there documentation or advice for how to use LLD to link for cygwin? As
a starting point, which driver to use?
Regards,
2013 Apr 16
0
[LLVMdev] RFC: Using zlib to decompress debug info sections.
...00000
>> >>> 31 .zdebug_line 0000005b 0000000000000000
>> >>> 32 .zdebug_loc 00000014 0000000000000000
>> >>> 33 .zdebug_pubtypes 00000014 0000000000000000
>> >>> 34 .zdebug_str 00000073 0000000000000000
>> >>> 35 .zdebug_ranges 00000014 0000000000000000
>> >>>
>> >>> Decompression and proper handling of debug info sections may be needed
>> >>> in llvm-dwarfdump and llvm-symbolizer tools. We can implement this by:
>> >>> 1) Checking if zlib is present in the sys...