public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seongbae dot park at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/33669] [4.3 Regression]  Revision 128957 miscompiles 481.wrf
Date: Mon, 08 Oct 2007 20:18:00 -0000	[thread overview]
Message-ID: <20071008201816.21282.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33669-682@http.gcc.gnu.org/bugzilla/>



------- Comment #12 from seongbae dot park at gmail dot com  2007-10-08 20:18 -------
Subject: Re:  [4.3 Regression] Revision 128957 miscompiles 481.wrf

Please remove the extra blank line above the line 984 (in new file).
This patch is OK.

Seongbae

On 10/7/07, Kenneth Zadeck <zadeck@naturalbridge.com> wrote:
> This patch fixes pr33669.
>
> The failure only happens if you have a block with 2 or more uses of a
> multiword pseudo register that is local to this block and has been
> allocated by local_alloc.  The uses must be in a particular form: the
> last use must be a subreg use that only used some of the hard registers and
> a previous non subreg use of the multiword register.
>
> When all of this happens, the code did not properly expand this to a
> whole multiregister when the second to last use is encountered in the
> backwards scan.
>
> I.e. a lot of things have to happen to get this to fail.
>
> I have tested this patch on ia-64, x86-{64,32} and ppc-32.
>
> Ok for commit?
>
> Kenny
>
> 2007-10-07  Kenneth Zadeck <zadeck@naturalbridge.com>
>
>     PR middle-end/33669
>     * ra-conflict.c (record_one_conflict_between_regnos,
>     set_conflicts_for_earlyclobber, global_conflicts): Improved logging.
>     (global_conflicts): Removed incorrect check.
>
> 2007-10-07  Kenneth Zadeck <zadeck@naturalbridge.com>
>
>     PR middle-end/33669
>     * gcc.c-torture/execute/pr33669.c: New.
>
>
>
>


-- 


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


  parent reply	other threads:[~2007-10-08 20:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-05 14:49 [Bug rtl-optimization/33669] New: " hjl at lucon dot org
2007-10-05 15:00 ` [Bug rtl-optimization/33669] " rguenth at gcc dot gnu dot org
2007-10-05 21:17 ` hjl at lucon dot org
2007-10-05 21:49 ` hjl at lucon dot org
2007-10-05 21:52 ` hjl at lucon dot org
2007-10-05 23:14 ` hjl at lucon dot org
2007-10-06  2:07 ` hjl at lucon dot org
2007-10-06  2:31 ` hjl at lucon dot org
2007-10-06  4:12 ` zadeck at naturalbridge dot com
2007-10-06 16:17 ` hjl at lucon dot org
2007-10-07  3:18 ` zadeck at naturalbridge dot com
2007-10-07  9:41 ` steven at gcc dot gnu dot org
2007-10-07 11:36 ` zadeck at naturalbridge dot com
2007-10-07 21:57 ` zadeck at naturalbridge dot com
2007-10-08  3:53 ` zadeck at naturalbridge dot com
2007-10-08 20:18 ` seongbae dot park at gmail dot com [this message]
2007-10-09 14:00 ` hjl at gcc dot gnu dot org
2007-10-09 15:33 ` zadeck at naturalbridge dot com
2007-10-09 15:41 ` zadeck at naturalbridge dot com
2007-10-09 16:19 ` hjl at lucon dot org
2007-10-10  3:33 ` zadeck at gcc dot gnu dot org
2007-10-10  3:40 ` zadeck at naturalbridge dot com
2007-10-10  3:41 ` zadeck at naturalbridge dot com
2007-10-10  3:47 ` hjl at lucon 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=20071008201816.21282.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).