Displaying 4 results from an estimated 4 matches for "dwarf_loc".
2009 Oct 20
0
[LLVMdev] No DWARF line number info with HasDotLocAndDotFile = true
...the target is using .loc/.file, the assembler will be emitting the
// .debug_line table automatically.
if (MAI->hasDotLocAndDotFile())
return;
Previously .loc directives are printed by selecting ISD::DEBUG_LOC nodes
to pseudo instructions which print as the directive. For example:
def DWARF_LOC : Pseudo<(outs), (ins i32imm:$line, i32imm:$col,
i32imm:$file),
".loc $file, $line, $col",
[(dwarf_loc (i32 imm:$line), (i32 imm:$col), (i32 imm:$file))]>;
ISD::DEBUG_LOC nodes are produced when debug stoppoints are expanded.
However debug stoppoints are no...
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
2008 Apr 16
0
[LLVMdev] Being able to know the jitted code-size before emitting
...AI = MF->getTarget().getTargetAsmInfo();
> + FinalSize += AI->getInlineAsmLength(AsmStr);
> + break;
> + }
> + case TargetInstrInfo::LABEL:
> + break;
> + case TargetInstrInfo::IMPLICIT_DEF:
> + case TargetInstrInfo::DECLARE:
> + case X86::DWARF_LOC:
> + case X86::FP_REG_KILL:
> + break;
> + case X86::MOVPC32r: {
> + // This emits the "call" portion of this pseudo instruction.
> + ++FinalSize;
> + FinalSize += sizeConstant(X86InstrInfo::sizeOfImm(Desc));
> + break;
> + }
>...
2008 Apr 15
4
[LLVMdev] Being able to know the jitted code-size before emitting
OK, here's a new patch that adds the infrastructure and the
implementation for X86, ARM and PPC of GetInstSize and GetFunctionSize.
Both functions are virtual functions defined in TargetInstrInfo.h.
For X86, I moved some commodity functions from X86CodeEmitter to
X86InstrInfo.
What do you think?
Nicolas
Evan Cheng wrote:
>
> I think both of these belong to TargetInstrInfo. And