Re: 2.29.1 Release Imminent

[Alan Modra <amodra at gmail dot com>]

On Wed, Sep 13, 2017 at 05:43:05PM +0200, Matthias Klose wrote:
> On 13.09.2017 16:16, Alan Modra wrote:
> > On Mon, Sep 11, 2017 at 06:36:36PM +0200, Matthias Klose wrote:
> >> this weekend I got https://bugs.debian.org/874674, which might be a regression
> >> compared to 2.28. I don't have further information on this yet.
> > 
> > Hmm, aborting at ../../bfd/merge.c:908.  llvm built with gcc-7 using
> > -g.  So you'll have a very likely huge .debug_str in total for the
> > merge code to handle.  I wonder if you are getting a memory alloc
> > failure, with binutils somewhere not checking malloc return status?
> 
> that might be related to another issue I'm seeing with llvm builds on aarch64
> and ppc64le, where the size of the debug info explodes by a factor of five, but
> the linker doesn't crash. It's llvm building with
> -DCMAKE_BUILD_TYPE=RelWithDebInfo, and it's going away with
> -DCMAKE_CXX_FLAGS_RELWITHDEBINFO="-g1 -O2".  So the original problem might be a
> GCC 7 issue.

Another possibility occurs to me.  We've seen the merge.c abort before
when ld read an object file before it had been completely written.  So
the llvm build may have a dependency problem.

-- 
Alan Modra
Australia Development Lab, IBM