[llvm-dev] debug build busts memory

[David Blaikie via llvm-dev]

(minor cleanup required: gdb's split dwarf support needs -gdb-index, which
means you need a linker that can do that (gold or lld) & also I think the
LLVM_USE_SPLIT_DWARF is incomplete (because it only enables -gsplit-dwarf
but doesn't add the -Wl,-gdb-index flag to the linker action) & so before
recommending it as a mainstream thing should probably be tidied up a
bit/fleshed out to address thoes issues)

On Tue, Nov 26, 2019 at 10:17 PM Tom Stellard via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> On 11/26/2019 10:41 AM, Reid Kleckner via llvm-dev wrote:
> > On Tue, Nov 26, 2019 at 10:31 AM David Jones via llvm-dev <
> llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
> >
> >     Throw hardware at it.
> >
> >
> > While I agree that this is good advice with the current state of
> affairs, I don't think we should consider the current situation acceptable.
> >
> > LLVM has a lot of knobs that Tim alluded to, but first time users
> shouldn't have to search for them to get a working debug build of LLVM out
> of the box. As a community, we need to raise the bar here, and spend some
> time making first time build setup easier. I seem to recall that there were
> discussions at the dev meeting about simplifying our CMake build, and I
> think this can be part of that effort.
> >
>
> Can we make LLVM_USE_SPLIT_DWARF=ON the default?  This seems like the
> easiest way to solve the memory usage issues, and we are already
> recommending
> this whenever users hit this problem.
>
> -Tom
>
> >
> > _______________________________________________
> > LLVM Developers mailing list
> > llvm-dev at lists.llvm.org
> > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
> >
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://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/20191126/c5e56211/attachment.html>