search for: bartolomeo

...sh. Handling CodeView would encourage that direction, rather than being a more fundamental shift. --paulr From: cfe-dev [mailto:cfe-dev-bounces at lists.llvm.org<mailto:cfe-dev-bounces at lists.llvm.org>] On Behalf Of David Blaikie via cfe-dev Sent: Friday, October 30, 2015 8:07 PM To: Dave Bartolomeo Cc: llvm-dev; Clang Dev Subject: Re: [cfe-dev] [llvm-dev] RFC: CodeView debug info emission in Clang/LLVM Brief answer, but can go into detail later: If this is the right idea, lets do it for dwarf too & generalize the support to work for both. It's certainly something we've consider...

...ling CodeView would encourage that direction, rather than being a more > fundamental shift. > > --paulr > > > > *From:* cfe-dev [mailto:cfe-dev-bounces at lists.llvm.org] *On Behalf Of *David > Blaikie via cfe-dev > *Sent:* Friday, October 30, 2015 8:07 PM > *To:* Dave Bartolomeo > *Cc:* llvm-dev; Clang Dev > *Subject:* Re: [cfe-dev] [llvm-dev] RFC: CodeView debug info emission in > Clang/LLVM > > > > Brief answer, but can go into detail later: > > If this is the right idea, lets do it for dwarf too & generalize the > support to work for bo...

...it could be used for codeview emission. It might be worth talking more & considering what other language features codeview uses that we haven't already plumbed through for dwarf (& dwarf based debuggers use dwarf for expression evaluation too, fwiw) On Oct 30, 2015 5:12 PM, "Dave Bartolomeo via cfe-dev" < cfe-dev at lists.llvm.org> wrote: > > > > > *From:* Saleem Abdulrasool [mailto:compnerd at compnerd.org] > *Sent:* Thursday, October 29, 2015 10:02 PM > *To:* Adrian Prantl <aprantl at apple.com> > *Cc:* Dave Bartolomeo <Dave.Bartolomeo at...

...sh. Handling CodeView would encourage that direction, rather than being a more fundamental shift. --paulr From: cfe-dev [mailto:cfe-dev-bounces at lists.llvm.org<mailto:cfe-dev-bounces at lists.llvm.org>] On Behalf Of David Blaikie via cfe-dev Sent: Friday, October 30, 2015 8:07 PM To: Dave Bartolomeo Cc: llvm-dev; Clang Dev Subject: Re: [cfe-dev] [llvm-dev] RFC: CodeView debug info emission in Clang/LLVM Brief answer, but can go into detail later: If this is the right idea, lets do it for dwarf too & generalize the support to work for both. It's certainly something we've consider...

On Thu, Oct 29, 2015 at 2:08 PM, Adrian Prantl via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > > On Oct 29, 2015, at 10:11 AM, Dave Bartolomeo via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > Proposed Design > > How Debug Info is Generated > > The CodeView type records for a compilation unit will be generated by > the front-end for the source language (Clang, in the case of C and C++). > T...

Hello, LLVM currently supports emission of CodeView's line table subsection. However, we'd like to increase the fidelity of this debug info with column information. I was wondering if anybody had any pointers as to how CodeView represents such information. Thanks! -- David Majnemer -------------- next part -------------- An HTML attachment was scrubbed... URL:

RFC: CodeView debug info emission in Clang/LLVM Overview On Windows, the de facto debug information format is CodeView, most commonly encountered in the form of a .pdb file. This is the format emitted by the Visual C++, C#, and VB.NET compilers, consumed by the Visual Studio debugger and the Windows debugger (WinDbg), and exposed for read-only access via the DIA SDK. The CodeView format has never

...location info and scope info, to emit inline line tables and variable > locations, so I think we did OK on reusing the existing infrastructure. > Compromising at not reusing the type representation seems OK. > > I haven't come up with any ideas better than the design that Dave > Bartolomeo outlined below, so I think we should go ahead with that. One > thing I considered was extending DITypeRef to be a union between MDString*, > DIType*, and a type index, but I think that's too invasive. I also don't > want to make a whole DIType heap allocation just to wrap a 32-bit...