search for: wincodeviewlinetables

...t" as the clang-cl flag name? ("minimal line tables") 2) Am I right that DWARF is pretty much the only debug info format supported by LLVM/AsmPrinter right now? Do we want to take an effort to come up with a generic debuginfogenerator interface to share between DwarfDebug and WinCodeViewLineTables? Then AsmPrinter should just hold a SmallVector<DebugInfoEmitter*> rather than a pair of DD/DE pointers. 3) How would you suggest to write WinCodeViewLineTables tests given that dumpbin is not available everywhere except Windows? // Yeah, I should have looked at the DwarfDebug LIT te...

...flag name? ("minimal line tables") > > 2) Am I right that DWARF is pretty much the only debug info format > supported by LLVM/AsmPrinter right now? Do we want to take > an effort to come up with a generic debuginfogenerator interface > to share between DwarfDebug and WinCodeViewLineTables? > Then AsmPrinter should just hold a SmallVector<DebugInfoEmitter*> > rather than a pair of DD/DE pointers. > > 3) How would you suggest to write WinCodeViewLineTables tests > given that dumpbin is not available everywhere except Windows? > // Yeah, I should have lo...

...line tables") > > > > 2) Am I right that DWARF is pretty much the only debug info format > > supported by LLVM/AsmPrinter right now? Do we want to take > > an effort to come up with a generic debuginfogenerator interface > > to share between DwarfDebug and WinCodeViewLineTables? > > Then AsmPrinter should just hold a SmallVector<DebugInfoEmitter*> > > rather than a pair of DD/DE pointers. > > > > 3) How would you suggest to write WinCodeViewLineTables tests > > given that dumpbin is not available everywhere except Windows? > &g...

On Mon, Sep 15, 2014 at 10:11 AM, Carlo Kok <ck at remobjects.com> wrote: > > I think I have VS2010 somewhere yes. Any hints on where to find this > problem so I can try to solve it myself? > Sure, llvm/lib/CodeGen/AsmPrinter/WinCodeViewLineTables.cpp -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140915/660572f1/attachment.html>

...>> > >> > 2) Am I right that DWARF is pretty much the only debug info format >> > supported by LLVM/AsmPrinter right now? Do we want to take >> > an effort to come up with a generic debuginfogenerator interface >> > to share between DwarfDebug and WinCodeViewLineTables? >> > Then AsmPrinter should just hold a SmallVector<DebugInfoEmitter*> >> > rather than a pair of DD/DE pointers. >> > >> > 3) How would you suggest to write WinCodeViewLineTables tests >> > given that dumpbin is not available everywhere exc...

...t;>>> > supported by LLVM/AsmPrinter right now? Do we want to take >> >>>>>> > an effort to come up with a generic debuginfogenerator >> >>>>>> > interface >> >>>>>> > to share between DwarfDebug and WinCodeViewLineTables? >> >>>>>> > Then AsmPrinter should just hold a >> >>>>>> > SmallVector<DebugInfoEmitter*> >> >>>>>> > rather than a pair of DD/DE pointers. >> >>>>>> > >> >>>>&gt...

...t;>> > 2) Am I right that DWARF is pretty much the only debug info format >>> > supported by LLVM/AsmPrinter right now? Do we want to take >>> > an effort to come up with a generic debuginfogenerator interface >>> > to share between DwarfDebug and WinCodeViewLineTables? >>> > Then AsmPrinter should just hold a SmallVector<DebugInfoEmitter*> >>> > rather than a pair of DD/DE pointers. >>> > >>> > 3) How would you suggest to write WinCodeViewLineTables tests >>> > given that dumpbin is not avai...

...> supported by LLVM/AsmPrinter right now? Do we want to take > >> >>>>>> > an effort to come up with a generic debuginfogenerator > >> >>>>>> > interface > >> >>>>>> > to share between DwarfDebug and WinCodeViewLineTables? > >> >>>>>> > Then AsmPrinter should just hold a > >> >>>>>> > SmallVector<DebugInfoEmitter*> > >> >>>>>> > rather than a pair of DD/DE pointers. > >> >>>>>> > > &gt...

...rted by LLVM/AsmPrinter right now? Do we want to take >> >> >>>>>> > an effort to come up with a generic debuginfogenerator >> >> >>>>>> > interface >> >> >>>>>> > to share between DwarfDebug and WinCodeViewLineTables? >> >> >>>>>> > Then AsmPrinter should just hold a >> >> >>>>>> > SmallVector<DebugInfoEmitter*> >> >> >>>>>> > rather than a pair of DD/DE pointers. >> >> >>>>>&g...

...WARF is pretty much the only debug info format >>>>>> > supported by LLVM/AsmPrinter right now? Do we want to take >>>>>> > an effort to come up with a generic debuginfogenerator interface >>>>>> > to share between DwarfDebug and WinCodeViewLineTables? >>>>>> > Then AsmPrinter should just hold a SmallVector<DebugInfoEmitter*> >>>>>> > rather than a pair of DD/DE pointers. >>>>>> > >>>>>> > 3) How would you suggest to write WinCodeViewLineTables tests &g...

...much the only debug info format > >>>>>> > supported by LLVM/AsmPrinter right now? Do we want to take > >>>>>> > an effort to come up with a generic debuginfogenerator interface > >>>>>> > to share between DwarfDebug and WinCodeViewLineTables? > >>>>>> > Then AsmPrinter should just hold a > SmallVector<DebugInfoEmitter*> > >>>>>> > rather than a pair of DD/DE pointers. > >>>>>> > > >>>>>> > 3) How would you suggest to write WinCo...

...gt; 2) Am I right that DWARF is pretty much the only debug info format >>>> > supported by LLVM/AsmPrinter right now? Do we want to take >>>> > an effort to come up with a generic debuginfogenerator interface >>>> > to share between DwarfDebug and WinCodeViewLineTables? >>>> > Then AsmPrinter should just hold a SmallVector<DebugInfoEmitter*> >>>> > rather than a pair of DD/DE pointers. >>>> > >>>> > 3) How would you suggest to write WinCodeViewLineTables tests >>>> > given that...

...right that DWARF is pretty much the only debug info format >>>>> > supported by LLVM/AsmPrinter right now? Do we want to take >>>>> > an effort to come up with a generic debuginfogenerator interface >>>>> > to share between DwarfDebug and WinCodeViewLineTables? >>>>> > Then AsmPrinter should just hold a SmallVector<DebugInfoEmitter*> >>>>> > rather than a pair of DD/DE pointers. >>>>> > >>>>> > 3) How would you suggest to write WinCodeViewLineTables tests >>>>&g...

Hi Carlo, Do you have VS2010 handy? It should read the DI fine. Unfortunately, VS2013 is not able to use the debug info we generate. It is on my plans to investigate and fix the generator, but I didn't have enough free cycles recently. -- Tim 2014-09-15 20:30 GMT+04:00 Reid Kleckner <rnk at google.com>: > +Timur > > Hm, this didn't work out of the box for me. > >

...>> > >> > 2) Am I right that DWARF is pretty much the only debug info format >> > supported by LLVM/AsmPrinter right now? Do we want to take >> > an effort to come up with a generic debuginfogenerator interface >> > to share between DwarfDebug and WinCodeViewLineTables? >> > Then AsmPrinter should just hold a SmallVector<DebugInfoEmitter*> >> > rather than a pair of DD/DE pointers. >> > >> > 3) How would you suggest to write WinCodeViewLineTables tests >> > given that dumpbin is not available everywhere exc...

...+Asserts build llvm[4]: Compiling X86AsmParser.cpp for Release+Asserts build llvm[3]: Compiling OcamlGCPrinter.cpp for Release+Asserts build llvm[3]: Compiling InstCombineShifts.cpp for Release+Asserts build llvm[3]: Compiling PartiallyInlineLibCalls.cpp for Release+Asserts build llvm[3]: Compiling WinCodeViewLineTables.cpp for Release+Asserts build llvm[3]: Compiling PlaceSafepoints.cpp for Release+Asserts build llvm[3]: Compiling InstCombineSimplifyDemanded.cpp for Release+Asserts build llvm[3]: Compiling WinException.cpp for Release+Asserts build llvm[4]: Building Release+Asserts Archive Library libLLVMX86AsmPa...