[Bug default/25252] dwz: returns exit status 1, causing FTBFS in deal.ii

["vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=25252

--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Graham Inggs from comment #2)
> > This still exits with 0 on dwz-0.13-branch, so presumably 0.13-3 is
> > just some random recent trunk version.
> 
> 0.13 + cherry-picks from trunk, I believe. Debian's changelog [1] for
> reference.
> 

Actually, looking at the source, it's an _exact_ match for a recent trunk.

> > As for the exit status 1, that's currently the expected result when
> > running into the max-die-limit.
> 
> Ah, thank you for the explanation.  Passing '-L 100000000' to dwz solves my
> problem.  Is there any reason I should not do this?  Or should I try to get
> close to the actual number of DIEs?

Dwz has two limits, which are there for execution time/memory usage reasons.

Anything bigger than the max-die-limit (-L) is not optimized. Increasing that
limit may make things slower, and consume more memory.

Anything bigger than the low-mem-die-limit (-l) is optimized in a slower and
less memory hungry fashion.  Also, anything bigger than that is skipped in the
multifile optimization, so the result will be less optimal.

In summary, bump the limits to where they're not hit (on trunk, we have -lnone
and -Lnone for that), and if that is not a problem in terms of execution time
and memory, you're done. If not, than you can tune the limits to reduce
execution time/memory usage to acceptable levels.

-- 
You are receiving this mail because:
You are on the CC list for the bug.