public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tom de Vries <vries@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-7582] [nvptx] Add multilib mptx=3.1
Date: Thu, 10 Mar 2022 11:22:35 +0000 (GMT)	[thread overview]
Message-ID: <20220310112235.A0D443857C44@sourceware.org> (raw)

https://gcc.gnu.org/g:975e7ade35095839b4dd2cc0f2b303bd63950db9

commit r12-7582-g975e7ade35095839b4dd2cc0f2b303bd63950db9
Author: Tom de Vries <tdevries@suse.de>
Date:   Tue Mar 8 09:25:39 2022 +0100

    [nvptx] Add multilib mptx=3.1
    
    With commit 5b5e456f018 ("[nvptx] Build libraries with mptx=3.1") the
    intention was that the ptx isa version for all libraries was switched back to
    3.1 using MULTILIB_EXTRA_OPTS, without changing the default 6.0.
    
    Further testing revealed that this is not the case, and some libs were still
    build with 6.0.
    
    Fix this by introducing an mptx=3.1 multilib.
    
    Adding a multilib should be avoided if possible, because it adds build time.
    But I think it's a reasonable trade-off.  With --disable-multilib, the default
    lib with misa=sm_30 and mptx=6.0 should be usable in most scenarios.  With
    --enable-multilib, we can enable older drivers, as well as generate code
    similar to how that was done in previous gcc releases, which is very useful.
    
    Tested on nvptx.
    
    gcc/ChangeLog:
    
    2022-03-07  Tom de Vries  <tdevries@suse.de>
    
            * config/nvptx/t-nvptx (MULTILIB_EXTRA_OPTS): Move mptx=3.1 ...
            (MULTILIB_OPTIONS): ... here.

Diff:
---
 gcc/config/nvptx/t-nvptx | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/gcc/config/nvptx/t-nvptx b/gcc/config/nvptx/t-nvptx
index a4a5341bb24..b63c4a5a39d 100644
--- a/gcc/config/nvptx/t-nvptx
+++ b/gcc/config/nvptx/t-nvptx
@@ -30,6 +30,4 @@ s-nvptx-gen-opt: $(srcdir)/config/nvptx/nvptx-sm.def
 	  tmp-nvptx-gen.opt $(srcdir)/config/nvptx/nvptx-gen.opt
 	$(STAMP) s-nvptx-gen-opt
 
-MULTILIB_OPTIONS = mgomp
-
-MULTILIB_EXTRA_OPTS = mptx=3.1
+MULTILIB_OPTIONS = mgomp mptx=3.1


                 reply	other threads:[~2022-03-10 11:22 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=20220310112235.A0D443857C44@sourceware.org \
    --to=vries@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).