Displaying 3 results from an estimated 3 matches for "hasdotlocanddotfil".
Did you mean:
hasdotlocanddotfile
2009 Oct 20
2
[LLVMdev] No DWARF line number info with HasDotLocAndDotFile = true
It seems to me that emitting DWARF line number information using .loc
directives is currently broken. CellSPU is currently the only in tree
target that sets HasDotLocAndDotFile in its MCAsmInfo and I can't get it
to produce any line number information.
Is this a known issue? I understand that there are lots of changes going
on in this area. Any idea what it would take to fix?
--
Richard Osborne | XMOS
http://www.xmos.com
2009 Oct 20
0
[LLVMdev] No DWARF line number info with HasDotLocAndDotFile = true
Richard Osborne wrote:
> It seems to me that emitting DWARF line number information using .loc
> directives is currently broken. CellSPU is currently the only in tree
> target that sets HasDotLocAndDotFile in its MCAsmInfo and I can't get it
> to produce any line number information.
>
I think I understand why this is happening. Since HasDotLocAndDotFile is
set the DwarfDebug class doesn't emit the line number table as a series
of bytes:
// If the target is using .loc/.file, th...
2008 Jul 17
3
[LLVMdev] RFC: debug_line Emission
In CodeGen/DwarfWriter.cpp's EmitDebugLine file, these lines are
causing havoc on Mac OS X systems:
// If there are no lines to emit (such as when we're using .loc
directives
// to emit .debug_line information) don't emit a .debug_line
header.
if (SectionSourceLines.empty())
return;
Basically, if there's a file with only data in it, we still need the
debug_line