This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [RFC PATCH] Optionally use -mlong-double-128 by default on {powerpc{,64},s390{,x},sparc,alpha}-linux
- From: Mark Mitchell <mark at codesourcery dot com>
- To: Benjamin Kosnik <bkoz at redhat dot com>
- Cc: jakub at redhat dot com, matz at suse dot de, gcc-patches at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org
- Date: Wed, 01 Feb 2006 10:00:36 -0800
- Subject: Re: [RFC PATCH] Optionally use -mlong-double-128 by default on {powerpc{,64},s390{,x},sparc,alpha}-linux
- References: <20060127165807.GV32233@devserv.devel.redhat.com> <Pine.LNX.4.58.0601311640500.627@wotan.suse.de> <20060131172535.GQ32233@devserv.devel.redhat.com> <43E05F19.4000103@codesourcery.com> <20060201114321.06a000f3.bkoz@redhat.com>
Benjamin Kosnik wrote:
>> For
>>libstdc++, my (unexpert) approach would just be to bump the SONAME, in
>>part because I'd have a hard time being sure that anything else was
>>really safe, and in part because the more magic we stuff into the
>>exports file, the harder it is to be sure that everything we do in
>>future will still work.
>
> SONAME 7 has been in progress for some time: there will be no "bumping"
> of the SONAME in mainline, but instead a merge of libstdcxx_so_7-branch.
Sure, I meant in addition to that change, or as part of that change, or
as a traditional multilib. I'm just fearful that making this long
double change will somehow introduce either an incompatibility (in that
old 64-bit long double binaries stop working with the new library), or a
bug (in that new 128-bit long double binaries don't work correctly).
Like I said, an unexpert opinion; I wasn't trying to dictate anything.
--
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713
- References:
- Re: [RFC PATCH] Optionally use -mlong-double-128 by default on {powerpc{,64},s390{,x},sparc,alpha}-linux
- Re: [RFC PATCH] Optionally use -mlong-double-128 by default on {powerpc{,64},s390{,x},sparc,alpha}-linux