Re: clang and static linking?
--sihESFlf63f/fzF3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Nov 09, 2012 at 08:43:04AM -0800, Steve Kargl wrote:
> On Fri, Nov 09, 2012 at 02:00:12PM +0200, Konstantin Belousov wrote:
> > On Thu, Nov 08, 2012 at 03:49:32PM -0800, Steve Kargl wrote:
> > >=20
> > > This appears to fix the problem. Don't know if this is
> > > th right way to handle it.
> > >=20
> > > Index: src/s_isnan.c
> > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > > --- src/s_isnan.c (revision 242701)
> > > +++ src/s_isnan.c (working copy)
> > > @@ -40,7 +40,6 @@
> >
> > Is this patch against src/msun ?
>=20
> Yes.
>=20
> > This is only a workaround, which break ABI and older binaries.
>=20
> Which leads to an interest question. With the major upheavel
> of switching to clang, are there any ABI breaking changes that
> would be desirable to commit? This would entail a major library
> version bump. For starters, libc/gen/isnan.c could be removed.
No, we do not want or allow for the ABI breakage, regardless of the
compiler used or any other reason. ATM, clang breaks ABI on i386, but
this was promised to be fixed.
--sihESFlf63f/fzF3
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)
iEYEARECAAYFAlCdOYQACgkQC3+MBN1Mb4j8gwCfc/eIxSVNsiXVh5mUw6f146vR
ZLQAn1EMd1HJAnsEb2gmotQoDEb/uK8y
=/XzJ
-----END PGP SIGNATURE-----
--sihESFlf63f/fzF3--
討論串 (同標題文章)
完整討論串 (本文為第 12 之 16 篇)：