public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: rearnsha@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/8896: '-mcpu=xscale -fno-strict-aliasing -O2' generates wrong code
Date: Thu, 15 May 2003 18:46:00 -0000	[thread overview]
Message-ID: <20030515184601.20193.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/8896; it has been noted by GNATS.

From: Daniel Jacobowitz <drow@mvista.com>
To: Richard Earnshaw <rearnsha@arm.com>
Cc: gcc-gnats@gcc.gnu.org, enrico.scholz@informatik.tu-chemnitz.de,
	gcc-bugs@gcc.gnu.org
Subject: Re: optimization/8896: '-mcpu=xscale -fno-strict-aliasing -O2' generates wrong code
Date: Thu, 15 May 2003 14:36:28 -0400

 On Thu, Dec 12, 2002 at 03:14:52PM +0000, Richard Earnshaw wrote:
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8896
 > 
 > I've attached what I believe to be the fix to the above PR.  It would be 
 > helpful if you could give it a whirl.
 
 I've added an updated testcase (produced after much labor by Russell
 King) which shows the problem in 3.2.3.  The testcase is extremely
 delicate.  It doesn't show the problem in 3.3 or HEAD, but I wouldn't
 be at all surprised if the problem was still there.  Making a
 testcase to show it is beyond me though.
 
 For the curious, here's a diff of the first differing dump with and
 without Richard's patch, using the 3.2 CVS branch.  It fails using
 only "-march=armv4 -O2".
 
 --- 32.s.22.postreload	2003-05-15 14:29:58.000000000 -0400
 +++ 32p.s.22.postreload	2003-05-15 14:29:59.000000000 -0400
 @@ -155,18 +155,25 @@
  (note 79 843 95 NOTE_INSN_DELETED)
  
  (insn 95 79 107 (set (reg/v:SI 11 fp [47])
 -        (const_int 2 [0x2])) 175 {*arm_movsi_insn} (insn_list:REG_DEP_ANTI 79 (nil))
 -    (nil))
 +        (const_int 1 [0x1])) 175 {*arm_movsi_insn} (insn_list:REG_DEP_ANTI 79 (nil))
 +    (expr_list:REG_EQUAL (const_int 1 [0x1])
 +        (nil)))
 +
 +(note 107 95 117 NOTE_INSN_DELETED)
  
 -(note 107 95 129 NOTE_INSN_DELETED)
 +(insn 117 107 129 (set (reg/v:SI 11 fp [47])
 +        (plus:SI (reg/v:SI 11 fp [47])
 +            (reg/f:SI 11 fp))) 4 {*arm_addsi3} (insn_list:REG_DEP_ANTI 107 (insn_list 95 (nil)))
 +    (expr_list:REG_EQUAL (const_int 2 [0x2])
 +        (nil)))
  
 -(note 129 107 135 NOTE_INSN_DELETED)
 +(note 129 117 135 NOTE_INSN_DELETED)
  
  (note 135 129 137 NOTE_INSN_DELETED)
  
  (insn 137 135 141 (set (reg/v:SI 11 fp [47])
          (plus:SI (reg/v:SI 11 fp [47])
 -            (reg/f:SI 11 fp))) 4 {*arm_addsi3} (insn_list:REG_DEP_ANTI 129 (insn_list 117 (nil)))
 +            (const_int 1 [0x1]))) 4 {*arm_addsi3} (insn_list:REG_DEP_ANTI 129 (insn_list 117 (nil)))
      (expr_list:REG_EQUAL (const_int 3 [0x3])
          (nil)))
  
 @@ -177,7 +184,7 @@
  
  (insn 197 141 221 (set (reg/v:SI 11 fp [47])
          (plus:SI (reg/v:SI 11 fp [47])
 -            (const_int 2 [0x2]))) 4 {*arm_addsi3} (insn_list:REG_DEP_ANTI 141 (insn_list:REG_DEP_OUTPUT 137 (insn_list 135 (nil))))
 +            (const_int 3 [0x3]))) 4 {*arm_addsi3} (insn_list:REG_DEP_ANTI 141 (insn_list:REG_DEP_OUTPUT 137 (insn_list 135 (nil))))
      (expr_list:REG_EQUAL (const_int 6 [0x6])
          (nil)))
  
 
 
 -- 
 Daniel Jacobowitz
 MontaVista Software                         Debian GNU/Linux Developer


             reply	other threads:[~2003-05-15 18:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-15 18:46 Daniel Jacobowitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-14 17:46 Dara Hazeghi
2003-03-22 13:54 steven
2003-03-22 13:36 Richard Earnshaw
2003-03-22 13:36 Steven Bosscher
2003-03-22 10:05 steven
2002-12-16 10:06 Enrico Scholz
2002-12-12  7:16 Richard Earnshaw
2002-12-12  7:03 rearnsha
2002-12-11  9:57 rearnsha
2002-12-10 15:46 enrico.scholz

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=20030515184601.20193.qmail@sources.redhat.com \
    --to=drow@mvista.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=rearnsha@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).