Displaying 3 results from an estimated 3 matches for "glegacy".
Did you mean:
legacy
2013 Jan 11
1
[LLVMdev] Restoring "pubnames" section in DWARF
...gt; Is there a target hook for generating debug information? Or should I just
> invent a cl::opt flag and guard the code under that?
>
>
I'd prefer a flag really (DwarfDebug.cpp) and just pass that down from the
front end if you really need or invent a front end option to control it.
-glegacy-pubtables or something?
-eric
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130111/b5e7b11f/attachment.html>
2013 Jan 11
0
[LLVMdev] Restoring "pubnames" section in DWARF
On 1/11/2013 4:04 PM, Eric Christopher wrote:
> On Fri, Jan 11, 2013 at 1:49 PM, Robinson, Paul
> <Paul.Robinson at am.sony.com <mailto:Paul.Robinson at am.sony.com>> wrote:
>
> I'd ask that it be made target-dependent, as I don't want it
> (and apparently few do, which is why it was removed).
>
>
> No worries there, it can be put under a flag
2013 Jan 11
2
[LLVMdev] Restoring "pubnames" section in DWARF
On Fri, Jan 11, 2013 at 1:49 PM, Robinson, Paul
<Paul.Robinson at am.sony.com>wrote:
> >We have customers that rely on the symbol information from the
> >"pubnames" section in the DWARF data. Generation of this information
> >was removed in this commit:
> >
> >commit dfa30e1ab243990eda4732a6dffb91e965e7a755
> >Author: Eric Christopher