public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/10287: [3.2/3.4 regression] Loop/conditional store bug (ARM)
Date: Tue, 01 Apr 2003 20:06:00 -0000	[thread overview]
Message-ID: <20030401200601.24843.qmail@sources.redhat.com> (raw)

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

From: Daniel Jacobowitz <drow@mvista.com>
To: gcc-gnats@gcc.gnu.org
Cc: jh@suse.cz
Subject: Re: optimization/10287: [3.2/3.4 regression] Loop/conditional store bug (ARM)
Date: Tue, 1 Apr 2003 14:56:17 -0500

 On Tue, Apr 01, 2003 at 06:36:11PM -0000, drow@mvista.com wrote:
 > 
 > >Number:         10287
 > >Category:       optimization
 > >Synopsis:       [3.2/3.4 regression] Loop/conditional store bug (ARM)
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       medium
 > >Responsible:    unassigned
 > >State:          open
 > >Class:          sw-bug
 > >Submitter-Id:   net
 > >Arrival-Date:   Tue Apr 01 18:46:00 UTC 2003
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     drow@mvista.com
 > >Release:        3.2.2 (release), 3.4 CVS (2003-03-27)
 > >Organization:
 > >Environment:
 > i686-pc-linux-gnu host, arm-linux target (or arm-elf, xscale-elf, et cetera)
 > >Description:
 > The attached test case aborts when compiled with -O2 for
 > an ARM target.
 > 
 > The diff between failing and succeeding binaries is:
 >         cmp     ip, #0
 > -       moveq   r3, r1
 > -       movne   r3, lr
 >         str     r1, [r5], #4
 > +       strne   lr, [r5], #4
 >         subs    ip, ip, #2
 > -       str     r3, [r5], #4
 > 
 > Note that the failing binary has an unconditional store
 > of a conditional value.  My guess is that something is
 > not respecting post-increment when distinguishing between
 > the two stores.
 > 
 > 
 > This is a 3.2 and 3.4 regression; it worked in 2.95 and
 > it works in 3.3.  The bug was fixed in 3.3 and HEAD by:
 > 
 >  2002-09-18  Richard Henderson  <rth@redhat.com>
 >  
 >        * ifcvt.c (noce_process_if_block): Correctly detect X modified
 >        with INSN_B before COND_EARLIEST.  Don't check A and B for 
 >        modification in condition range.  Reorder INSN_B for A==B properly.
 >        (if_convert): Iterate until no matches for a block.
 > 
 > It was then broken again in HEAD by:
 > Wed Jan  8 12:10:57 CET 2003  Jan Hubicka  <jh@suse.cz>
 > 
 >        * i386.md (adddi3_carry_rex64, subdi3_carry_rex64): Name pattern.
 >        (addhi3_carry, addqi3_carry, subhi3_carry, subqi3_carry): New patterns.
 >        (add??cc): New expanders.
 >        * i386.c (expand_int_addcc): New function.
 >        * i386-protos.h (expand_int_addcc): Declare.
 > 
 >        * alias.c (memory_modified_1): New static function.
 >        (memory_modified): New static varaible.
 >        (memory_modified_in_insn_p): New global function.
 >        * rtl.h (memory_modified_in_insn_p): Declare.
 >        * rtlanal.c (modified_between_p, modified_in_p): Be smart about memory
 >        references.
 > 
 >        * expr.h (emit_conditional_add): Declare.
 
 I'm not sure, but I think that modified_between_p and modified_in_p are
 going to have to have POST_INC (POST_DEC, PRE_INC, PRE_DEC) cases in
 them for the above patch from Jan to be safe.
 
 
 -- 
 Daniel Jacobowitz
 MontaVista Software                         Debian GNU/Linux Developer


             reply	other threads:[~2003-04-01 20:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-01 20:06 Daniel Jacobowitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-02  9:16 Jan Hubicka
2003-04-01 18:46 drow

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