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/62218] gcc produces invalid SH instruction (stc r2,sr) when building libgcc
Date: Thu, 25 Sep 2014 16:01:00 -0000	[thread overview]
Message-ID: <bug-62218-4-I2bO8nbWMy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62218-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from Oleg Endo <olegendo at gcc dot gnu.org> ---
Author: olegendo
Date: Thu Sep 25 16:00:58 2014
New Revision: 215609

URL: https://gcc.gnu.org/viewcvs?rev=215609&root=gcc&view=rev
Log:
gcc/
2014-09-25  Oleg Endo  <olegendo@gcc.gnu.org>

    Backport from mainline
    2014-09-25  Nick Clifton  <nickc@redhat.com>
    2014-09-25  Oleg Endo  <olegendo@gcc.gnu.org>

    PR target/62218
    * config/sh/sync.md (atomic_fetch_nand<mode>_soft_imask,
    atomic_test_and_set_soft_imask): Fix typo in instruction sequence.

Modified:
    branches/gcc-4_8-branch/gcc/ChangeLog
    branches/gcc-4_8-branch/gcc/config/sh/sync.md


  parent reply	other threads:[~2014-09-25 16:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-21 14:52 [Bug target/62218] New: " dhowells at redhat dot com
2014-08-21 15:09 ` [Bug target/62218] " dhowells at redhat dot com
2014-08-21 15:11 ` dhowells at redhat dot com
2014-08-21 15:23 ` dhowells at redhat dot com
2014-08-21 15:25 ` dhowells at redhat dot com
2014-09-25 14:46 ` nickc at redhat dot com
2014-09-25 15:02 ` nickc at gcc dot gnu.org
2014-09-25 15:24 ` olegendo at gcc dot gnu.org
2014-09-25 15:51 ` olegendo at gcc dot gnu.org
2014-09-25 15:54 ` olegendo at gcc dot gnu.org
2014-09-25 16:01 ` olegendo at gcc dot gnu.org [this message]
2014-09-25 16:13 ` 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-62218-4-I2bO8nbWMy@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).