From: Andi Kleen <andi@firstfloor.org>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, RFA]: Properly mask memory model argument with MEMMODEL_MASK
Date: Tue, 15 Jan 2013 20:38:00 -0000 [thread overview]
Message-ID: <m28v7u18te.fsf@firstfloor.org> (raw)
In-Reply-To: <CAFULd4Ze2O0htQD2+8p+7qT7+KcdSAp5uusnR7UroSvK4nCiQg@mail.gmail.com> (Uros Bizjak's message of "Tue, 15 Jan 2013 09:09:32 +0100")
Uros Bizjak <ubizjak@gmail.com> writes:
>
> 2013-01-15 Uros Bizjak <ubizjak@gmail.com>
>
> * emit-rtl.c (need_atomic_barrier_p): Mask memory model argument
> with MEMMODEL_MASK before comparing with MEMMODEL_* memory types.
> * optabs.c (maybe_emit_sync_lock_test_and_set): Ditto.
> (expand_mem_thread_fence): Ditto.
> (expand_mem_signal_fence): Ditto.
> (expand_atomic_load): Ditto.
> (expand_atomic_store): Ditto.
>
> Bootstrapped and regression tested on x86_64-linux-gnu {,-m32}.
>
> OK for mainline?
Looks good to me (but I cannot approve)
-Andi
next prev parent reply other threads:[~2013-01-15 20:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 8:09 Uros Bizjak
2013-01-15 20:38 ` Andi Kleen [this message]
2013-01-15 21:06 ` Richard Henderson
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=m28v7u18te.fsf@firstfloor.org \
--to=andi@firstfloor.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=ubizjak@gmail.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).