IIUC this text is not true (maybe it was back in 2018?)
OK for trunk?
Which branches should it be on too, all of them?
-- >8 --
The choice of ieee or ibm long double format is orthogonal to multilibs,
as the two sets of symbols co-exist and don't need a separate multilib.
gcc/ChangeLog:
* doc/install.texi (Configuration): Remove misleading text
around LE PowerPC Linux multilibs.
---
gcc/doc/install.texi | 11 -----------
1 file changed, 11 deletions(-)
diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index 3192824bdc4..10bfceffceb 100644
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -2139,17 +2139,6 @@ Until all of the libraries are converted to use IEEE
128-bit floating
point, it is not recommended to use
@option{--with-long-double-format=ieee}.
-On little endian PowerPC Linux systems, if you explicitly set the
-@code{long double} type, it will build multilibs to allow you to
-select either @code{long double} format, unless you disable multilibs
-with the @code{--disable-multilib} option. At present,
-@code{long double} multilibs are not built on big endian PowerPC Linux
-systems. If you are building multilibs, you will need to configure
-the compiler using the @option{--with-system-zlib} option.
-
-If you do not set the @code{long double} type explicitly, no multilibs
-will be generated.
-
@item --enable-fdpic
On SH Linux systems, generate ELF FDPIC code.
--
2.34.1
