public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/24609] [4.0/4.1/4.2/4.3 regression] Same value duplicated in two different registers
Date: Wed, 04 Jul 2007 22:11:00 -0000	[thread overview]
Message-ID: <20070704221138.22467.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24609-1313@http.gcc.gnu.org/bugzilla/>



------- Comment #15 from pinskia at gcc dot gnu dot org  2007-07-04 22:11 -------
For foo4.c
> SCCVN says j_3 value numbers to i_2 (VH.3)
But that is really PR 28868.

The orginal issue here I think is fixed because we now use unsigned int for the
addition.
The IR looks like:

<bb 4>:
  d = 2;
  prephitmp.39 = 1;
  goto <bb 6>;

<bb 5>:
  d = 1;
  prephitmp.39 = 0;

<bb 6>:
  MEM[base: a, index: ivtmp.49, step: 4, offset: 4294967292] = d;
  D.2029 = bar ((short int *) ivtmp.52, (int) (short int) *(pretmp.36 +
prephitmp.39), d);

Which looks good as there is no duplicated value.  Note the offset of -4 is a
different and already known issue.

Ian do you think this should no longer be a 4.3 Regression or should we even
not PRE "PHI<1,2> - 1" ?


-- 


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


  parent reply	other threads:[~2007-07-04 22:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-01  5:33 [Bug tree-optimization/24609] New: " ian at airs dot com
2005-11-01  6:02 ` [Bug tree-optimization/24609] " ian at airs dot com
2005-11-01 14:54 ` pinskia at gcc dot gnu dot org
2005-11-01 16:09 ` ian at airs dot com
2005-11-01 16:17 ` pinskia at gcc dot gnu dot org
2005-11-01 18:06 ` ian at airs dot com
2005-11-01 18:46 ` ian at airs dot com
2005-11-01 18:47 ` [Bug tree-optimization/24609] [4.1 regression] " ian at airs dot com
2005-11-02  0:58 ` ian at airs dot com
2005-11-03  6:28 ` ian at airs dot com
2006-03-08 16:03 ` [Bug tree-optimization/24609] [4.1/4.2 " pinskia at gcc dot gnu dot org
2006-04-12 18:36 ` mmitchel at gcc dot gnu dot org
2006-04-27 12:36 ` rguenth at gcc dot gnu dot org
2006-05-25  2:40 ` mmitchel at gcc dot gnu dot org
2006-07-10 13:01 ` [Bug tree-optimization/24609] [4.0/4.1/4.2 " rguenth at gcc dot gnu dot org
2006-08-25  7:47 ` bonzini at gnu dot org
2006-08-25  7:48 ` bonzini at gnu dot org
2007-02-14  9:08 ` [Bug tree-optimization/24609] [4.0/4.1/4.2/4.3 " mmitchel at gcc dot gnu dot org
2007-07-04 22:11 ` pinskia at gcc dot gnu dot org [this message]
2008-01-21 17:26 ` steven at gcc dot gnu dot org
2008-01-23  6:49 ` ian at airs dot com

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=20070704221138.22467.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).