public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/20290] [4.0/4.1 Regression] Miscompilation on ppc with -Os
Date: Wed, 02 Mar 2005 23:09:00 -0000	[thread overview]
Message-ID: <20050302230907.22982.qmail@sourceware.org> (raw)
In-Reply-To: <20050302203320.20290.jakub@gcc.gnu.org>


------- Additional Comments From jakub at gcc dot gnu dot org  2005-03-02 23:09 -------
The bug goes away with -Os -floop-optimize2, it is just the old loop optimizer
that doesn't handle this properly.  It seems to me that loop.c really can't
do its job correctly if it doesn't detect where the loop header and latch
are and if a BIV increments are done in header, latch or body.

Zdenek, any ideas what to do with this?

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rakdver at gcc dot gnu dot
                   |                            |org
         AssignedTo|jakub at gcc dot gnu dot org|unassigned at gcc dot gnu
                   |                            |dot org
             Status|ASSIGNED                    |NEW


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


  parent reply	other threads:[~2005-03-02 23:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-02 20:33 [Bug rtl-optimization/20290] New: " jakub at gcc dot gnu dot org
2005-03-02 20:40 ` [Bug rtl-optimization/20290] [4.0 Regression] " pinskia at gcc dot gnu dot org
2005-03-02 20:44 ` [Bug middle-end/20290] [4.0/4.1 " pinskia at gcc dot gnu dot org
2005-03-02 21:17 ` jakub at gcc dot gnu dot org
2005-03-02 23:09 ` jakub at gcc dot gnu dot org [this message]
2005-03-02 23:12 ` jakub at gcc dot gnu dot org
2005-03-02 23:15 ` rakdver at gcc dot gnu dot org
2005-03-04 14:58 ` [Bug middle-end/20290] [4.0/4.1 Regression] Miscompilation on ppc/arm " pinskia at gcc dot gnu dot org
2005-03-20 18:34 ` [Bug rtl-optimization/20290] " aoliva at redhat dot com
2005-03-31 21:46 ` rth at gcc dot gnu dot org
2005-04-02 16:54 ` cvs-commit at gcc dot gnu dot org
2005-04-02 16:54 ` cvs-commit at gcc dot gnu dot org
2005-04-02 17:02 ` aoliva 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=20050302230907.22982.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).