public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/45051] [4.6 Regression]: gcc.c-torture/execute/builtins/abs-2.c and abs-3.c due to "track subwords of DImode allocnos"
Date: Sat, 24 Jul 2010 03:03:00 -0000	[thread overview]
Message-ID: <20100724030258.32246.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45051-507@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from hp at gcc dot gnu dot org  2010-07-24 03:02 -------
--- good:r162417/abs-2.s        Sat Jul 24 03:13:36 2010
+++ bad:r162418/abs-2.s Sat Jul 24 03:15:53 2010
@@ -9,27 +9,27 @@ _main_test:
        move $srp,[$sp]
        subu.b 84,$sp
        movem $r8,[$sp]
-       clear.d $r4
-       clear.d $r5
-       move.b 1,$r4
-       move.d $r4,[$sp+76]
-       move.d $r5,[$sp+80]
+       clear.d $r0      ; (set (reg:SI r0) (const_int 0))
+       clear.d $r1
+       move.b 1,$r0     ; (set (strict_low_part:QI (reg:SI r0)) (const_int 1))
+       move.d $r0,[$sp+76]
+       move.d $r1,[$sp+80]
        moveq -1,$r12
        move.d $r12,[$sp+68]
        move.d $r12,[$sp+72]
-       clear.d $r10
-       move.d $r4,$r11
-       move.d $r11,$r8
-       move.d -2147483648,$r0
-       move.d $r11,[$sp+60]
-       move.d $r10,[$sp+64]
-       move.d 2147483647,$r11
+       move.d $r0,$r10
+       move.d -2147483648,$r11
+       move.d $r10,[$sp+60]
+       move.d $r11,[$sp+64]
+       clear.b $r0     ; (set (strict_low_part:QI (reg:SI r9)) (const_int 0))
+       move.d $r0,$r9  ; (set (reg:SI r9) (reg:SI r0))
+       move.d 2147483647,$r0
        move.d $r12,[$sp+52]
-       move.d $r11,[$sp+56]
-       move.d $r8,[$sp+44]
-       move.d $r0,[$sp+48]
+       move.d $r9,[$sp+56]     ; stored here
+       move.d $r10,[$sp+44]
+       move.d $r11,[$sp+48]
        move.d $r12,[$sp+36]
-       move.d $r11,[$sp+40]
+       move.d $r0,[$sp+40]
        move.d [$sp+52],$r12
        move.d [$sp+56],$r13    ; loaded here
        test.d $r12 ; fatally tested below; containing 0, expected 0x7fffffff


-- 

hp at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2010-07-24 03:02:58
               date|                            |


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


  parent reply	other threads:[~2010-07-24  3:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-24  2:43 [Bug rtl-optimization/45051] New: " hp at gcc dot gnu dot org
2010-07-24  2:46 ` [Bug rtl-optimization/45051] " hp at gcc dot gnu dot org
2010-07-24  2:51 ` hp at gcc dot gnu dot org
2010-07-24  3:03 ` hp at gcc dot gnu dot org [this message]
2010-07-27  9:35 ` bernds at gcc dot gnu dot org
2010-07-27 21:49 ` bernds at gcc dot gnu dot org
2010-09-21 21:26 ` hp at gcc dot gnu dot org
     [not found] <bug-45051-4@http.gcc.gnu.org/bugzilla/>
2010-12-22 16:23 ` ibolton at gcc dot gnu.org
2010-12-23  1:56 ` hp at gcc dot gnu.org
2010-12-23 14:29 ` hp at gcc dot gnu.org
2011-01-03 19:58 ` rguenth at gcc dot gnu.org
2011-01-03 20:01 ` rguenth 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=20100724030258.32246.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).