https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68358
Iain Sandoe <iains at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
--- Comment #18 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Nenad Vukicevic from comment #15)
> Just updated Xcode to 7.2. Still the same issue, even though dsymutil
> changed.
>
> On 12/7/2015 1:19 AM, iains at gcc dot gnu.org wrote:
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68358
> >
> > --- Comment #14 from Iain Sandoe <iains at gcc dot gnu.org> ---
> > (In reply to Nenad Vukicevic from comment #13)
> >> For what is worth I filed two bug reports:
> >
> > Thanks!
> >
> >> LLVM:
> >> https://llvm.org/bugs/show_bug.cgi?id=25757
> >>
> >> APPLE:
> >> Bug 23778972 (not sure how to get URL for this bug)
The actual issue seems to be that ld64 only issues the OSO for the first use
of a source file seen when linking an exe. Therefore, in cases where
conditional
compilation (or LTO) causes multiple objects to be created from one source,
there's
no OSO for some of the .o files.
dsymutil complains - but its complaint is correct.
FWIW; I have a fix for the ld64 bug here:
https://github.com/iains/darwin-xtools/commit/c2b58c3328cb002459fba9b312949c9fd9f0165e
> > It's on my TODO to deal with problem #1 (shouldn't be calling dsymutil
> > unconditionally), but I'll attach that to PR 61352.
lto-wrapper and friends have has some TLC in the 9 timeframe, and for at least
9.x and 10, I think that dsymutil is only now being called when it's needed.
LTO debug for Darwin does require some more work (and a change to dsymutil to
deal with it) - but that's tracked in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82005 so don't let's duplicate
here.
(so ... I don't expect all aspects of this to be fixed yet - but running some
checks with revised ld64).
