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 rtl-optimization/19705] New: [4.0 Regression] cannot turn off doloop optimization via -fno-branch-count-reg if -fno-ivopts is also supplied
Date: Sun, 30 Jan 2005 05:58:00 -0000	[thread overview]
Message-ID: <20050130055822.19705.pinskia@gcc.gnu.org> (raw)

Hmm, this is werid, why cannot I turn off doloop optimization with the -fno-branch-count-reg when I 
also turn off ivopts?  I should be able to when I want to look at the interaction between those two 
optimizations (options).
Testcase:
int foo (int x)
{
    int i= x;
    do {
        x *= 2;
    } while (--i);
    return x;
}

Compile with -O2 -fno-branch-count-reg -fno-ivopts and see there still is a bdnz in there.
but compile with -O2 -fno-branch-count-reg and you don't get the bdnz.

-- 
           Summary: [4.0 Regression] cannot turn off doloop optimization via
                    -fno-branch-count-reg if -fno-ivopts is also supplied
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: minor
          Priority: P2
         Component: rtl-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: pinskia at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org
GCC target triplet: powerpc-*-darwin*


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


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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-30  5:58 pinskia at gcc dot gnu dot org [this message]
2005-01-30  6:08 ` [Bug rtl-optimization/19705] Cannot " pinskia at gcc dot gnu dot org
2005-02-20 19:32 ` pinskia at gcc dot gnu dot org
2005-09-01 14:05 ` amodra at bigpond dot net dot au

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=20050130055822.19705.pinskia@gcc.gnu.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).