public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org, Martin Jambor <mjambor@suse.de>
Subject: Re: [PATCH] Fix bootstrap with older and non-GCC host compilers
Date: Tue, 19 Jan 2016 14:33:00 -0000	[thread overview]
Message-ID: <20160119143314.GO3017@tucnak.redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1601191518100.31122@t29.fhfr.qr>

On Tue, Jan 19, 2016 at 03:19:17PM +0100, Richard Biener wrote:
> 
> It also seems we're wrongly using values defined for the host while
> looking at GIMPLE IL for the target.
> 
> Bootstrap / regtest running on x86_64-unknown-linux-gnu.
> 
> Ok?
> 
> Richard.
> 
> 2016-01-19  Richard Biener  <rguenther@suse.de>
> 
> 	* hsa-gen.c (get_memory_order_name): Use MEMMODEL_ constants
> 	and name.
> 	(get_memory_order): Likewise.
> 
> Index: gcc/hsa-gen.c
> ===================================================================
> --- gcc/hsa-gen.c	(revision 232561)
> +++ gcc/hsa-gen.c	(working copy)
> @@ -4417,18 +4417,18 @@ get_memory_order_name (unsigned memmodel
>  {
>    switch (memmodel)
>      {
> -    case __ATOMIC_RELAXED:
> -      return "__ATOMIC_RELAXED";
> -    case __ATOMIC_CONSUME:
> -      return "__ATOMIC_CONSUME";
> -    case __ATOMIC_ACQUIRE:
> -      return "__ATOMIC_ACQUIRE";
> -    case __ATOMIC_RELEASE:
> -      return "__ATOMIC_RELEASE";
> -    case __ATOMIC_ACQ_REL:
> -      return "__ATOMIC_ACQ_REL";
> -    case __ATOMIC_SEQ_CST:
> -      return "__ATOMIC_SEQ_CST";
> +    case MEMMODEL_RELAXED:
> +      return "MEMMODEL_RELAXED";
> +    case MEMMODEL_CONSUME:
> +      return "MEMMODEL_CONSUME";
> +    case MEMMODEL_ACQUIRE:
> +      return "MEMMODEL_ACQUIRE";
> +    case MEMMODEL_RELEASE:
> +      return "MEMMODEL_RELEASE";
> +    case MEMMODEL_ACQ_REL:
> +      return "MEMMODEL_ACQ_REL";
> +    case MEMMODEL_SEQ_CST:
> +      return "MEMMODEL_SEQ_CST";

The case changes are ok, though it is not handling various
other memory models (MEMMOVED_SYNC_{ACQUIRE,RELEASE,SEQ_CST}).
For the returned strings, that is used in user visible context (warning),
so I think neither is ok, better use "relaxed", "consume", "acquire",
"release", "acq_rel", "seq_cst" (and the rest are internals for __sync_
builtins).

>      default:
>        return NULL;
>      }
> @@ -4442,13 +4442,13 @@ get_memory_order (unsigned memmodel, loc
>  {
>    switch (memmodel)
>      {
> -    case __ATOMIC_RELAXED:
> +    case MEMMODEL_RELAXED:
>        return BRIG_MEMORY_ORDER_RELAXED;
> -    case __ATOMIC_ACQUIRE:
> +    case MEMMODEL_ACQUIRE:
>        return BRIG_MEMORY_ORDER_SC_ACQUIRE;
> -    case __ATOMIC_RELEASE:
> +    case MEMMODEL_RELEASE:
>        return BRIG_MEMORY_ORDER_SC_RELEASE;
> -    case __ATOMIC_ACQ_REL:
> +    case MEMMODEL_ACQ_REL:
>        return BRIG_MEMORY_ORDER_SC_ACQUIRE_RELEASE;
>      default:
>        HSA_SORRY_ATV (location,

This LGTM (though I'm really surprised it doesn't have seq_cst,
e.g. OpenMP #pragma omp atomic will be either relaxed, or seq_cst.

	Jakub

  reply	other threads:[~2016-01-19 14:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-19 14:19 Richard Biener
2016-01-19 14:33 ` Jakub Jelinek [this message]
2016-01-19 15:08   ` Richard Biener

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=20160119143314.GO3017@tucnak.redhat.com \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mjambor@suse.de \
    --cc=rguenther@suse.de \
    /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).