[llvm-dev] How to avoid or remove llvm.dbg.value?

[Alberto Barbaro via llvm-dev]

Thanks Paul for the info. For now I'm happy without them

Alberto

On Tue, Nov 12, 2019, 17:43 Robinson, Paul <paul.robinson at sony.com> wrote:

> If you are writing a pass and don’t want to bother with debug-info
> instructions at first, that’s fine; but note that the pass will have to
> contend with the debug-info instructions at some point, or your pass is
> likely to behave differently for code compiled with -g which is a Bad Thing.
>
> --paulr
>
>
>
> *From:* llvm-dev <llvm-dev-bounces at lists.llvm.org> *On Behalf Of *Alberto
> Barbaro via llvm-dev
> *Sent:* Friday, November 8, 2019 10:10 AM
> *To:* Tim Northover <t.p.northover at gmail.com>
> *Cc:* llvm-dev <llvm-dev at lists.llvm.org>
> *Subject:* Re: [llvm-dev] How to avoid or remove llvm.dbg.value?
>
>
>
> Hi Tim,
>
> Thank you very much for the message. It indeed solved the problem.
>
>
>
> Thanks
>
>
>
> On Fri, Nov 8, 2019, 15:05 Tim Northover <t.p.northover at gmail.com> wrote:
>
> Hi Alberto,
>
> On Fri, 8 Nov 2019 at 06:59, Alberto Barbaro via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
> > Is there any way for avoiding to use llvm.dbg.value within a bc file?
>
> They're part of LLVM's representation of debugging information (as you
> may have guessed). So if compiling with Clang you can just not pass -g
> and you won't get any (or override with -g0 if your build system
> already adds -g and it's inconvenient to avoid that). Other front-ends
> will have similar options I expect.
>
> > If not, once I have the bc how can I remove all the occurrences?
>
> You can run "opt -strip-debug" will remove it in that situation.
>
> Cheers.
>
> Tim.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20191122/487a0a43/attachment.html>