This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/81733] stage1 libgcc_s.dylib fails to link on Darwin 11/x86_64
- From: "iains at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 18 Sep 2017 13:22:04 +0000
- Subject: [Bug target/81733] stage1 libgcc_s.dylib fails to link on Darwin 11/x86_64
- Auto-submitted: auto-generated
- References: <bug-81733-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81733
--- Comment #7 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Iain Sandoe from comment #6)
> (In reply to Iain Sandoe from comment #5)
> > (In reply to Iain Sandoe from comment #4)
> > > (In reply to ro@CeBiTec.Uni-Bielefeld.DE from comment #3)
> > > > > --- Comment #1 from Iain Sandoe <iains at gcc dot gnu.org> ---
> > > > > Is this still current?
> > > >
> > > > It is: just tried with a vanilla tree at r252892.
> >
> > So with Eric's fix for 81361, and jamming reorder_and_partition = 0, most of
> > the dwarfdump --verify fails go away, but not all (and the unwinder is still
> > broken). Will take a look at them later.
>
> some of the verify fails seem to be caused by the ancient dwarfdump not
> being smart enough; ld64 and BINUTILS objdump seem to be happy that the FDEs
> are well-formed (more checking to be done)
however (on 10.11.6), a trivial c++ try catch, succeeds -static-libgcc with 7.2
but not with trunk.. and the c++ code is essentially unchanged.