public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Stubbs <ams@codesourcery.com>
To: Paul-Antoine Arras <pa@codesourcery.com>,
	Kwok Cheung Yeung <kcyeung77@gmail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][OG12] amdgcn: Support AMD-specific 'isa' and 'arch' traits in OpenMP context selectors
Date: Thu, 1 Dec 2022 12:45:45 +0000	[thread overview]
Message-ID: <0600a1e2-d877-6522-15a9-0e5d0219a76b@codesourcery.com> (raw)
In-Reply-To: <82a884ed-ea1d-5116-fedf-42de6e22e730@codesourcery.com>

On 01/12/2022 11:10, Paul-Antoine Arras wrote:
> +      if (TARGET_FIJI)                                                         \
> +	builtin_define ("__FIJI__");                                           \
> +      else if (TARGET_VEGA10)                                                  \
> +	builtin_define ("__VEGA10__");                                         \
> +      else if (TARGET_VEGA20)                                                  \
> +	builtin_define ("__VEGA20__");                                         \
> +      else if (TARGET_GFX908)                                                  \
> +	builtin_define ("__GFX908__");                                         \
> +      else if (TARGET_GFX90a)                                                  \
> +	builtin_define ("__GFX90a__");                                         \
> +  } while (0)
>  

I don't think it makes sense to say __VEGA10__ when the user asked for 
-march=gfx900.

This whole naming thing is a bit of a mess already, so I think we'd do 
better to either keep the same names throughout or match what LLVM does 
(since it got to these first).

Please use "__gfx900__" etc. (lower case).

I'm half tempted to do a global search and replace on the internal 
names, but since they're not externally visible that would probably just 
be making merge conflicts for the sake of it.

Thanks

Andrew

P.S. If you want to split the patch into the GCN bits and the bits that 
depend on metadirectives then we can apply the first part to mainline 
right away.

  reply	other threads:[~2022-12-01 12:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30 15:32 Paul-Antoine Arras
2022-11-30 18:50 ` Kwok Cheung Yeung
2022-12-01 11:10   ` Paul-Antoine Arras
2022-12-01 12:45     ` Andrew Stubbs [this message]
2022-12-01 14:35       ` [PATCH] amdgcn: Add preprocessor builtins for every processor type Paul-Antoine Arras
2022-12-01 14:42         ` Andrew Stubbs
2022-12-01 15:48       ` [PATCH][OG12] amdgcn: Support AMD-specific 'isa' and 'arch' traits in OpenMP context selectors Paul-Antoine Arras
2022-12-02 16:51         ` Kwok Cheung Yeung

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=0600a1e2-d877-6522-15a9-0e5d0219a76b@codesourcery.com \
    --to=ams@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kcyeung77@gmail.com \
    --cc=pa@codesourcery.com \
    /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).