[Lldb-commits] [PATCH] D39727: Make TestTopLevelExprs more robust in face of linker GC

Zachary Turner via lldb-commits lldb-commits at lists.llvm.org
Tue Nov 7 05:29:58 PST 2017


If it works, is easy, and doesn’t regress anything I’d honestly rather just
disable linker gc.

But I’m not familiar with the method you mentioned. I thought linker gc
happens when you have -function-sections, -fdata-sections, and —gc-sections.

Wouldn’t it work to just not have those? Or is something else going on?
On Tue, Nov 7, 2017 at 5:17 AM Pavel Labath <labath at google.com> wrote:

> On 7 November 2017 at 12:46, Zachary Turner <zturner at google.com> wrote:
> > I just wonder if we should be disabling linker gc across the board for
> all
> > tests unless you explicitly opt in.
> >
> > Seems like something we would want only rarely, if ever
>
> Yes, that might be an option. I don't really have a strong opinion on
> that, either way. FWIW, this is the only test that seems to be
> impacted by this.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20171107/3079ea91/attachment-0001.html>


More information about the lldb-commits mailing list