On Thu, Jun 21, 2018 at 12:58:06PM -0400, Michael Meissner wrote: > On Wed, Jun 20, 2018 at 07:31:31PM -0500, Segher Boessenkool wrote: > > 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? > > The main advantge is that it makes it a little easier for me to test things, > since I only have to build one compiler instead of two. But that is fairly > minor. > > Here is the alternate patch to eliminate the multilib support for IEEE/IBM > long > double. > > [gcc] > 2018-06-21 Michael Meissner <meiss...@linux.ibm.com> > > * config.gcc (powerpc64le*): Remove multilib support for IEEE and > IBM long double. > * config/rs6000/rs6000.c (rs6000_option_override_internal): > Likewise. > * config/rs6000/rs6000.h (TARGET_IEEEQUAD_MULTILIB): Likewise. > * config/rs6000/t-ldouble-linux64le-ibm: Delete, IEEE/IBM long > double multilib no longer supported. > * config/rs6000/t-ldouble-linux64le-ieee: Likewise. > * doc/install.texi (PowerPC options): Delete information about > IEEE/IBM long double multilibs.
This reverts r256775 (the commit message should say), except the linux64.h parts, and it seems you just missed those? Segher
