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/53988] [SH] tst Rm,Rn not used for QI/HImode
Date: Mon, 19 Jan 2015 22:36:00 -0000	[thread overview]
Message-ID: <bug-53988-4-eqS0sei8Kc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53988-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Oleg Endo <olegendo at gcc dot gnu.org> ---
Author: olegendo
Date: Mon Jan 19 22:35:53 2015
New Revision: 219864

URL: https://gcc.gnu.org/viewcvs?rev=219864&root=gcc&view=rev
Log:
gcc/
    PR target/53988
    * config/sh/sh-protos.h (sh_find_set_of_reg): Make sure not to return
    nullptr for insn when reaching the first insn.
    * config/sh/sh.c (sh_unspec_insn_p): Rewrite using subrtx_iterator.
    (sh_insn_operands_modified_between_p): Add nullptr check.
    (sh_find_extending_set_of_reg): Fix log message.  Don't accept
    sign extending mem load if the insn contains any UNSPEC or
    UNSPEC_VOLATILE.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/config/sh/sh-protos.h
    trunk/gcc/config/sh/sh.c


  parent reply	other threads:[~2015-01-19 22:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17  0:02 [Bug target/53988] New: " olegendo at gcc dot gnu.org
2012-09-03 10:02 ` [Bug target/53988] " olegendo at gcc dot gnu.org
2012-10-31 22:09 ` olegendo at gcc dot gnu.org
2012-11-05 21:11 ` olegendo at gcc dot gnu.org
2014-12-29 19:03 ` olegendo at gcc dot gnu.org
2015-01-14 23:47 ` olegendo at gcc dot gnu.org
2015-01-19 22:36 ` olegendo at gcc dot gnu.org [this message]
2015-03-10  8:10 ` olegendo at gcc dot gnu.org
2015-03-10  8:18 ` olegendo at gcc dot gnu.org
2015-03-10  8:19 ` 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-53988-4-eqS0sei8Kc@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).