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/19703] [4.0 Regression] Poor optimisation of loop test, DOM causing unsigned to int and missing combine compares
Date: Sun, 30 Jan 2005 05:25:00 -0000	[thread overview]
Message-ID: <20050130052548.4100.qmail@sourceware.org> (raw)
In-Reply-To: <20050130025905.19703.andrewhutchinson@cox.net>


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-01-30 05:25 -------
Confirmed (sorry about that I was thinking of something different at the time).
Here is a better example for normal targets (PPC and x86 too):
extern void foo6(int);
void testloop6 (void)
{
  int i;
  i = 100;
  do {
      foo6 ( i);
    i-=10;
  } while (i != 0);
}

The tree dump for the loop on x86:
<L0>:;
  foo6 (i);
  D.1592 = (unsigned int) i + 0fffffff6;
  i = (int) D.1592;
  if (D.1592 != 0) goto <L0>; else goto <L1>;

Note this is not IV-OPTS messing up but DOM changing the if statement.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1
 GCC target triplet|avr                         |
   Last reconfirmed|0000-00-00 00:00:00         |2005-01-30 05:25:46
               date|                            |
            Summary|Poor optimisation of loop   |[4.0 Regression] Poor
                   |test                        |optimisation of loop test,
                   |                            |DOM causing unsigned to int
                   |                            |and missing combine compares
   Target Milestone|---                         |4.0.0


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


  parent reply	other threads:[~2005-01-30  5:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-30  2:59 [Bug c/19703] New: Poor optimisation of loop test andrewhutchinson at cox dot net
2005-01-30  3:17 ` [Bug tree-optimization/19703] " pinskia at gcc dot gnu dot org
2005-01-30  3:17 ` pinskia at gcc dot gnu dot org
2005-01-30  4:58 ` andrewhutchinson at cox dot net
2005-01-30  5:25 ` pinskia at gcc dot gnu dot org [this message]
2005-01-30 19:20 ` [Bug tree-optimization/19703] [4.0 Regression] Poor optimisation of loop test, DOM causing unsigned to int and missing combine compares pinskia at gcc dot gnu dot org
2005-02-10 23:46 ` pinskia at gcc dot gnu dot org
2005-04-21  5:05 ` [Bug tree-optimization/19703] [4.0/4.1 " mmitchel at gcc dot gnu dot org
2005-06-26 18:03 ` pinskia at gcc dot gnu dot org
2005-07-08  1:43 ` mmitchel at gcc dot gnu dot org
2005-08-17 12:43 ` [Bug tree-optimization/19703] [4.0 " pinskia at gcc dot gnu dot org
2005-09-27 16:12 ` mmitchel at gcc dot gnu dot org
     [not found] <bug-19703-7648@http.gcc.gnu.org/bugzilla/>
2005-11-04 15:36 ` pinskia at gcc dot gnu 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=20050130052548.4100.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).