llvm dev - Nov 2016 - Saving private DebugInfo

Hi all,

Sometimes llvm::UpgradeDebugInfo
<http://llvm.org/docs/doxygen/html/namespacellvm.html#ad3c29183c5faa7f5a352807af8aca268>
drops
debug info which is pretty compatible with recent llvm version (
http://stackoverflow.com/questions/27023713/missing-debug-metadata-in-llvm-after-xcode-update
)
and sometimes it drops something really outdated, but acceptable for me. In
both cases I want to keep it, but AFAIK there is no API for this.

I've tried to strip libLLVMCore from that method and it forked for me just
fine, but something has changed in llvm 3.9 and now I can't link with
against hacked libLLVMCore. (
https://travis-ci.org/okutane/sanity/jobs/169662912 line 979 )

What can I do? The best solution for me would be "configuration" of
how LLVMParseIRInContext
deals with "outdated" debug info, but I'm open to any workarounds.
:D

Best regards, Dmitry.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20161125/35e21ae6/attachment.html>

I’ve been in need of a cl::opt to control this behavior and force preserving
debug info, it would be useful for testing at least. That wouldn’t be a
"first class” API though.

CC Adrian for his opinion.

— 
Mehdi
> On Nov 24, 2016, at 2:25 PM, Dmitriy Matveev via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
> 
> Hi all,
> 
> Sometimes llvm::UpgradeDebugInfo
<http://llvm.org/docs/doxygen/html/namespacellvm.html#ad3c29183c5faa7f5a352807af8aca268>
drops debug info which is pretty compatible with recent llvm version (
http://stackoverflow.com/questions/27023713/missing-debug-metadata-in-llvm-after-xcode-update
<http://stackoverflow.com/questions/27023713/missing-debug-metadata-in-llvm-after-xcode-update>
) and sometimes it drops something really outdated, but acceptable for me. In
both cases I want to keep it, but AFAIK there is no API for this.
> 
> I've tried to strip libLLVMCore from that method and it forked for me
just fine, but something has changed in llvm 3.9 and now I can't link with
against hacked libLLVMCore. (
https://travis-ci.org/okutane/sanity/jobs/169662912
<https://travis-ci.org/okutane/sanity/jobs/169662912> line 979 )
> 
> What can I do? The best solution for me would be "configuration"
of how LLVMParseIRInContext deals with "outdated" debug info, but
I'm open to any workarounds. :D
> 
> Best regards, Dmitry.
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20161124/45497827/attachment.html>

any chance to get an opinion for this?

On 25 November 2016 at 01:31, Mehdi Amini <mehdi.amini at apple.com>
wrote:
> I’ve been in need of a cl::opt to control this behavior and force
> preserving debug info, it would be useful for testing at least. That
> wouldn’t be a "first class” API though.
>
> CC Adrian for his opinion.
>
> —
> Mehdi
>
> On Nov 24, 2016, at 2:25 PM, Dmitriy Matveev via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
> Hi all,
>
> Sometimes llvm::UpgradeDebugInfo
>
<http://llvm.org/docs/doxygen/html/namespacellvm.html#ad3c29183c5faa7f5a352807af8aca268>
drops
> debug info which is pretty compatible with recent llvm version (
> http://stackoverflow.com/questions/27023713/missing-
> debug-metadata-in-llvm-after-xcode-update ) and sometimes it drops
> something really outdated, but acceptable for me. In both cases I want to
> keep it, but AFAIK there is no API for this.
>
> I've tried to strip libLLVMCore from that method and it forked for me
just
> fine, but something has changed in llvm 3.9 and now I can't link with
> against hacked libLLVMCore. ( https://travis-ci.org/
> okutane/sanity/jobs/169662912 line 979 )
>
> What can I do? The best solution for me would be "configuration"
of how LLVMParseIRInContext
> deals with "outdated" debug info, but I'm open to any
workarounds. :D
>
> Best regards, Dmitry.
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20161205/80a1c51c/attachment.html>