public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-8300] doc: Remove misleading text about multilibs for IEEE long double Date: Thu, 28 Apr 2022 10:29:11 +0000 (GMT) [thread overview] Message-ID: <20220428102911.404EE3858C2C@sourceware.org> (raw) https://gcc.gnu.org/g:8094526109034c6c6af44de47612e97319b2c7c5 commit r12-8300-g8094526109034c6c6af44de47612e97319b2c7c5 Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Apr 28 10:30:58 2022 +0100 doc: Remove misleading text about multilibs for IEEE long double 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. Diff: --- 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.
reply other threads:[~2022-04-28 10:29 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20220428102911.404EE3858C2C@sourceware.org \ --to=redi@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).