public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zadeck at naturalbridge dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/33662] [4.3 Regression] Wrong register allocation on SH
Date: Thu, 11 Oct 2007 21:51:00 -0000 [thread overview]
Message-ID: <20071011215053.25463.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33662-5208@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from zadeck at naturalbridge dot com 2007-10-11 21:50 -------
kazumoto,
there was a set of miscommunications associated with the final patch for
pr33669.
hj had checked in an earlier version of the patch and that testcase and i asked
him to revert it because there were issues with it. He only reverted the code
and left the testcase in. You tested against version 129192 and i checked in
the corrected patch as 129193.
given that, pr33669.c should have failed. seongbae has verified that pr33669.c
and the testcase here no longer fails on the current truck with sh-elf.
I am going to assume that this is closed unless you find some other issue.
Sorry for the mess up.
Kenny
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33662
next prev parent reply other threads:[~2007-10-11 21:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 1:54 [Bug middle-end/33662] New: " kkojima at gcc dot gnu dot org
2007-10-08 2:23 ` [Bug middle-end/33662] " kkojima at gcc dot gnu dot org
2007-10-08 3:53 ` zadeck at naturalbridge dot com
2007-10-10 13:28 ` kkojima at gcc dot gnu dot org
2007-10-10 13:33 ` zadeck at naturalbridge dot com
2007-10-11 0:52 ` spark at gcc dot gnu dot org
2007-10-11 3:07 ` spark at gcc dot gnu dot org
2007-10-11 21:51 ` zadeck at naturalbridge dot com [this message]
2007-10-12 2:06 ` kkojima 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=20071011215053.25463.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).