public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Olivier Hainque <hainque@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-5948] Drop the fpic multilib for powerpc*-vxworks*
Date: Tue, 14 Dec 2021 12:28:22 +0000 (GMT)	[thread overview]
Message-ID: <20211214122822.0E2273858D28@sourceware.org> (raw)

https://gcc.gnu.org/g:dff8ae8e839a5102aff266c8246864b610c066c9

commit r12-5948-gdff8ae8e839a5102aff266c8246864b610c066c9
Author: Frederic Konrad <konrad@adacore.com>
Date:   Thu Nov 12 12:39:25 2020 +0100

    Drop the fpic multilib for powerpc*-vxworks*
    
    The addition of fPIC for shared libraries is performed
    independently from multilibs and the fpic multilibs have
    no other particular purpose. They incur extra build time,
    complexify the install tree and are a bit tricky because
    -fpic is not supported for kernel mode.
    
    2020-11-06  Fred Konrad  <konrad@adacore.com>
    
    gcc/
            * config/rs6000/t-vxworks: Drop the fPIC multilib.

Diff:
---
 gcc/config/rs6000/t-vxworks | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/gcc/config/rs6000/t-vxworks b/gcc/config/rs6000/t-vxworks
index 68b241523e3..6da829d40b7 100644
--- a/gcc/config/rs6000/t-vxworks
+++ b/gcc/config/rs6000/t-vxworks
@@ -19,7 +19,7 @@
 # <http://www.gnu.org/licenses/>.
 
 # The base multilib is -mhard-float.
-MULTILIB_OPTIONS = mrtp fPIC msoft-float
+MULTILIB_OPTIONS = mrtp msoft-float
 MULTILIB_DIRNAMES =
-MULTILIB_MATCHES = fPIC=fpic
-MULTILIB_EXCEPTIONS = fPIC*
+MULTILIB_MATCHES =
+MULTILIB_EXCEPTIONS =


                 reply	other threads:[~2021-12-14 12:28 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=20211214122822.0E2273858D28@sourceware.org \
    --to=hainque@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: link
Be 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).