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/52483] SH Target: Loads from volatile memory leave redundant sign/zero extensions
Date: Sat, 26 Oct 2013 22:07:00 -0000	[thread overview]
Message-ID: <bug-52483-4-C8OnoeZhGJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52483-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52483

--- Comment #5 from Oleg Endo <olegendo at gcc dot gnu.org> ---
Author: olegendo
Date: Sat Oct 26 22:07:37 2013
New Revision: 204097

URL: http://gcc.gnu.org/viewcvs?rev=204097&root=gcc&view=rev
Log:
    PR target/52483
    * config/sh/predicates.md (general_movdst_operand): Allow reg+reg
    addressing, do not use general_operand for memory operands.

    PR target/52483
    * gcc.target/sh/pr52483-1.c: Add tests for memory stores.
    * gcc.target/sh/pr52483-2.c: Likewise.
    * gcc.target/sh/pr52483-3.c: Likewise.
    * gcc.target/sh/pr52483-4.c: Likewise.


Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/config/sh/predicates.md
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/gcc.target/sh/pr52483-1.c
    trunk/gcc/testsuite/gcc.target/sh/pr52483-2.c
    trunk/gcc/testsuite/gcc.target/sh/pr52483-3.c
    trunk/gcc/testsuite/gcc.target/sh/pr52483-4.c


  parent reply	other threads:[~2013-10-26 22:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-04 18:18 [Bug target/52483] New: " olegendo at gcc dot gnu.org
2012-03-05  5:35 ` [Bug target/52483] " kkojima at gcc dot gnu.org
2012-09-17 23:06 ` olegendo at gcc dot gnu.org
2012-09-18 12:26 ` kkojima at gcc dot gnu.org
2013-06-23  8:44 ` olegendo at gcc dot gnu.org
2013-10-26 22:07 ` olegendo at gcc dot gnu.org [this message]
2013-10-26 22:09 ` 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-52483-4-C8OnoeZhGJ@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).