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/59343] miscompiled for loop in sh4 target (-Os)
Date: Fri, 06 Dec 2013 10:47:00 -0000	[thread overview]
Message-ID: <bug-59343-4-Vv3OLD3sEl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59343-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Oleg Endo <olegendo at gcc dot gnu.org> ---
Author: olegendo
Date: Fri Dec  6 10:46:53 2013
New Revision: 205734

URL: http://gcc.gnu.org/viewcvs?rev=205734&root=gcc&view=rev
Log:
    PR target/51244
    PR target/59343
    * config/sh/sh.md (*cbranch_t): Check that there are no labels between
    the s1 insn and the testing insn.  Remove REG_DEAD note    from s1 insn.

    PR target/51244
    PR target/59343
    * gcc.target/sh/pr51244-19.c: Adjust test case.


Modified:
    branches/gcc-4_8-branch/gcc/ChangeLog
    branches/gcc-4_8-branch/gcc/config/sh/sh.md
    branches/gcc-4_8-branch/gcc/testsuite/ChangeLog
    branches/gcc-4_8-branch/gcc/testsuite/gcc.target/sh/pr51244-19.c


  parent reply	other threads:[~2013-12-06 10:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-29 13:52 [Bug target/59343] New: " gcc-bugzilla-f5d8 at theblacksun dot eu
2013-11-29 13:55 ` [Bug target/59343] " gcc-bugzilla-f5d8 at theblacksun dot eu
2013-11-29 13:55 ` gcc-bugzilla-f5d8 at theblacksun dot eu
2013-12-02 12:57 ` gcc-bugzilla-f5d8 at theblacksun dot eu
2013-12-02 13:02 ` gcc-bugzilla-f5d8 at theblacksun dot eu
2013-12-03 12:52 ` chrbr at gcc dot gnu.org
2013-12-03 14:55 ` gcc-bugzilla-f5d8 at theblacksun dot eu
2013-12-03 22:22 ` olegendo at gcc dot gnu.org
2013-12-06 10:47 ` olegendo at gcc dot gnu.org [this message]
2013-12-06 12:52 ` 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-59343-4-Vv3OLD3sEl@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).