This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH], PowerPC long double transition patches, v2, Patch #1 (disable long double multilib)
- From: Segher Boessenkool <segher at kernel dot crashing dot org>
- To: Michael Meissner <meissner at linux dot ibm dot com>, GCC Patches <gcc-patches at gcc dot gnu dot org>, David Edelsohn <dje dot gcc at gmail dot com>, Bill Schmidt <wschmidt at linux dot vnet dot ibm dot com>
- Date: Wed, 20 Jun 2018 19:31:31 -0500
- Subject: Re: [PATCH], PowerPC long double transition patches, v2, Patch #1 (disable long double multilib)
- References: <20180620141505.GA30942@ibm-toto.the-meissners.org> <20180620142536.GA945@ibm-toto.the-meissners.org>
On Wed, Jun 20, 2018 at 10:25:36AM -0400, Michael Meissner wrote:
> This code disables the automatic multilib creation unless you use the
> --with-advance-toolchain=<xxx> option and the Advance Toolchain directoy has
> been modified to have the lib64/ieee128 and/or lib64/ibm128 directories for
> multilib support. This allows the multilib to still be created, but it is not
> enabled by default.
>
> Alternatively, I have a patch that disables the IEEE/IBM long double multilib
> support completely.
So what are the advantages and the disadvantages of both approaches?
And, why do you think this one is preferable?
Segher