public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64659] New: [SH] Immedate values not used for atomic ops
Date: Sun, 18 Jan 2015 21:37:00 -0000	[thread overview]
Message-ID: <bug-64659-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64659

            Bug ID: 64659
           Summary: [SH] Immedate values not used for atomic ops
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: olegendo at gcc dot gnu.org
            Target: sh*-*-*

Compiling the following example:

void test4 (volatile int* mem)
{
  __atomic_or_fetch (mem, 1, __ATOMIC_ACQ_REL);
}

with -O2 -m4a -m{l|b} -matomic-model=soft-gusa results in:

        mov    #1,r1

0:      movli.l    @r4,r0  ! 7  atomic_or_fetchsi_hard  [length = 8]
        or    r1,r0
        movco.l    r0,@r4
        bf    0b
        rts
        nop

For some reason, the predicates 'atomic_arith_operand' and
'atomic_logical_operand' don't allow immediate values, although they are
supposed to do so.


             reply	other threads:[~2015-01-18 21:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-18 21:37 olegendo at gcc dot gnu.org [this message]
2015-01-18 22:22 ` [Bug target/64659] " olegendo at gcc dot gnu.org
2015-01-18 22:40 ` olegendo at gcc dot gnu.org
2015-01-28 21:12 ` olegendo at gcc dot gnu.org
2015-02-01 10:47 ` olegendo at gcc dot gnu.org

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=bug-64659-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).