search for: debughandlerbase

...fter EmitSchedule(), SelectionDAG will be converted to a list of MI instructions. In the function, we will generate DBG_LABEL MachineInstr from SDDbgLabel. For FastISel and GlobalISel, we could convert llvm.dbg.label to DBG_LABEL directly. 5. Collect debug information of labels from MI listing to DebugHandlerBase. Before generating actual debug information in assembly format or object format, we need to keep debug format-independent data in DebugHandlerBase. Afterwards, we could convert these data to CodeView format or DWARF format. 6. Create DWARF DIE specific data structure in DwarfDebug. In class Dwar...

...anitizer-x86_64-linux/build/llvm/lib/CodeGen/AsmPrinter/DwarfDebug.cpp:1005:0 #14 0x00000000025f9ae8 llvm::DwarfDebug::endFunctionImpl(llvm::MachineFunction const*) /mnt/b/sanitizer-buildbot1/sanitizer-x86_64-linux/build/llvm/lib/CodeGen/AsmPrinter/DwarfDebug.cpp:1208:0 #15 0x000000000262f75a llvm::DebugHandlerBase::endFunction(llvm::MachineFunction const*) /mnt/b/sanitizer-buildbot1/sanitizer-x86_64-linux/build/llvm/lib/CodeGen/AsmPrinter/DebugHandlerBase.cpp:256:0 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170508...

...nux/build/llvm/lib/CodeGen/AsmPrinter/DwarfDebug.cpp:1005:0 >> #14 0x00000000025f9ae8 llvm::DwarfDebug::endFunctionImpl(llvm::MachineFunction const*) /mnt/b/sanitizer-buildbot1/sanitizer-x86_64-linux/build/llvm/lib/CodeGen/AsmPrinter/DwarfDebug.cpp:1208:0 >> #15 0x000000000262f75a llvm::DebugHandlerBase::endFunction(llvm::MachineFunction const*) /mnt/b/sanitizer-buildbot1/sanitizer-x86_64-linux/build/llvm/lib/CodeGen/AsmPrinter/DebugHandlerBase.cpp:256:0 >> >> >> _______________________________________________ >> LLVM Developers mailing list >> llvm-dev at lists.llvm....

...will be converted to a list of MI > instructions. In the function, we will generate DBG_LABEL MachineInstr > from SDDbgLabel. > > For FastISel and GlobalISel, we could convert llvm.dbg.label to > DBG_LABEL directly. > > 5. Collect debug information of labels from MI listing to DebugHandlerBase. > > Before generating actual debug information in assembly format or > object format, we need to keep debug format-independent data in > DebugHandlerBase. Afterwards, we could convert these data to CodeView > format or DWARF format. > > 6. Create DWARF DIE specific data struct...

...will be converted to a list of MI > instructions. In the function, we will generate DBG_LABEL MachineInstr > from SDDbgLabel. > > For FastISel and GlobalISel, we could convert llvm.dbg.label to > DBG_LABEL directly. > > 5. Collect debug information of labels from MI listing to DebugHandlerBase. > > Before generating actual debug information in assembly format or > object format, we need to keep debug format-independent data in > DebugHandlerBase. Afterwards, we could convert these data to CodeView > format or DWARF format. > > 6. Create DWARF DIE specific data struct...

...ill be converted to a list of MI > instructions. In the function, we will generate DBG_LABEL MachineInstr > from SDDbgLabel. > > For FastISel and GlobalISel, we could convert llvm.dbg.label to > DBG_LABEL directly. > > 5. Collect debug information of labels from MI listing to DebugHandlerBase. > > Before generating actual debug information in assembly format or > object format, we need to keep debug format-independent data in > DebugHandlerBase. Afterwards, we could convert these data to CodeView > format or DWARF format. > > 6. Create DWARF DIE specific data stru...

I mean, we just skip over instructions without a DebugLoc: void CodeViewDebug::beginInstruction(const MachineInstr *MI) { DebugHandlerBase::beginInstruction(MI); // Ignore DBG_VALUE locations and function prologue. if (!Asm || !CurFn || MI->isDebugValue() || MI->getFlag(MachineInstr::FrameSetup)) return; DebugLoc DL = MI->getDebugLoc(); if (DL == PrevInstLoc || !DL) return; maybeRecordLocation(DL, Asm...

...of MI >> instructions. In the function, we will generate DBG_LABEL MachineInstr >> from SDDbgLabel. >> >> For FastISel and GlobalISel, we could convert llvm.dbg.label to >> DBG_LABEL directly. >> >> 5. Collect debug information of labels from MI listing to DebugHandlerBase. >> >> Before generating actual debug information in assembly format or >> object format, we need to keep debug format-independent data in >> DebugHandlerBase. Afterwards, we could convert these data to CodeView >> format or DWARF format. >> >> 6. Create DW...

I've been playing with Fred Riss's "line 0" patch for DWARF (https://reviews.llvm.org/D16569) but in adapting it for current trunk, I find the DwarfDebug stuff has been refactored to allow either DWARF or CodeView. That's all good, but the question is whether the "line 0" patch should be DWARF-specific or common. The DWARF spec explicitly states that code not

What program did you use to test the feature, and what was missing information? I'd like to file that as a bug so that we can fix this later. On Thu, Mar 16, 2017 at 2:34 PM, David Blaikie <dblaikie at gmail.com> wrote: > FWIW - selfhosting I did find that GDB wasn't able to find the source code > for some functions when using LLD's gdb_index, so I've switched back to