public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r10-10985] nvptx: Define (dummy) 'TARGET_PTX_6_0'
Date: Wed, 14 Sep 2022 10:09:11 +0000 (GMT)	[thread overview]
Message-ID: <20220914100911.38A3F3858016@sourceware.org> (raw)

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

commit r10-10985-gddeca5944408edfac28b3d90b02b2d0b4cfe73d1
Author: Thomas Schwinge <thomas@codesourcery.com>
Date:   Tue Sep 13 17:26:33 2022 +0200

    nvptx: Define (dummy) 'TARGET_PTX_6_0'
    
    'TARGET_PTX_*' not applicable before GCC 12, but makes it easier to cherry-pick
    patches.
    
            gcc/
            * config/nvptx/nvptx.h (TARGET_PTX_6_0): '#define' to 'false'.

Diff:
---
 gcc/config/nvptx/nvptx.h | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/gcc/config/nvptx/nvptx.h b/gcc/config/nvptx/nvptx.h
index 6ebcc760771..ca1aa11d852 100644
--- a/gcc/config/nvptx/nvptx.h
+++ b/gcc/config/nvptx/nvptx.h
@@ -95,6 +95,9 @@
 
 #define TARGET_SM35 (ptx_isa_option >= PTX_ISA_SM35)
 
+/* 'TARGET_PTX_*' not applicable before GCC 12.  */
+#define TARGET_PTX_6_0 false
+
 /* Registers.  Since ptx is a virtual target, we just define a few
    hard registers for special purposes and leave pseudos unallocated.
    We have to have some available hard registers, to keep gcc setup

                 reply	other threads:[~2022-09-14 10:09 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=20220914100911.38A3F3858016@sourceware.org \
    --to=tschwinge@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).