public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amylaar at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/27182] [4.1 regression] SH: wrong-code generation
Date: Wed, 19 Apr 2006 19:35:00 -0000	[thread overview]
Message-ID: <20060419193514.25588.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27182-8402@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from amylaar at gcc dot gnu dot org  2006-04-19 19:35 -------
(In reply to comment #2)
> I'd like to add Joern to the CC list.
> 
> I've looked the rtl dumps for the testcase.  It seems that
> the wrong code is generated during the peephole2 optimization.
...
> (reg:SI 1 r1 [656]) and results a wrong r1 value.  Perhaps this
> issue is simply latent in the mainline, though I have no testcases
> for the mainline.

Well, a latent bug can exist even if no test case can currently trigger it.
If could be triggered again after some other optimizer change.

Your patch is OK for 4.1 branch and mainline. (With the addition of a
ChangeLog entry.)


-- 


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


  parent reply	other threads:[~2006-04-19 19:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-17 13:17 [Bug target/27182] New: " sugioka at itonet dot co dot jp
2006-04-17 13:19 ` [Bug target/27182] " sugioka at itonet dot co dot jp
2006-04-19 12:42 ` kkojima at gcc dot gnu dot org
2006-04-19 19:35 ` amylaar at gcc dot gnu dot org [this message]
2006-04-19 22:41 ` kkojima at gcc dot gnu dot org
2006-04-20  1:54 ` kkojima at gcc dot gnu dot org
2006-04-20  2:04 ` kkojima at gcc dot gnu dot org
2006-06-04 19:47 ` jsm28 at gcc dot gnu dot 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=20060419193514.25588.qmail@sourceware.org \
    --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).