public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/18401] [4.0.0 Regression] Bootstrap failure on all ARM targets due to incorrect GCSE
Date: Wed, 05 Jan 2005 19:00:00 -0000	[thread overview]
Message-ID: <20050105190019.18575.qmail@sourceware.org> (raw)
In-Reply-To: <20041109150721.18401.rearnsha@gcc.gnu.org>


------- Additional Comments From rearnsha at gcc dot gnu dot org  2005-01-05 19:00 -------
It went away after this patch:

2004-11-10  Zdenek Dvorak  <dvorakz@suse.cz>

        * tree-ssa-loop-ivopts.c (get_address_cost): Add address elements in
        right order.
        (force_var_cost): Determine cost of addition and multiplication more
        precisely.
        (get_computation_cost_at): Add cost for computing address elements to
        the final cost.

        * fold-const.c (fold): Attempt to use ptr_difference_const whenever
        one of the arguments of MINUS_EXPR is an address.
        (split_address_to_core_and_offset): New function.
        (ptr_difference_const): Handle case when one of the operands is a
        pointer.
        * tree-ssa-loop-ivopts.c (determine_base_object): Fold &*addr.
        (ptr_difference_cost): Pass addresses instead of objects to
        ptr_difference_const.

So I suspect it might have gone latent again, but it might be that it was fixed
by the canonicalization change to get_address_cost and that the problem can only
occur with RTL that is not in correct canonical form.

For reference here are the links to the two patch proposals:

http://gcc.gnu.org/ml/gcc-patches/2004-11/msg00610.html
http://gcc.gnu.org/ml/gcc-patches/2004-11/msg00715.html

-- 


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


  parent reply	other threads:[~2005-01-05 19:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-09 15:08 [Bug bootstrap/18401] New: " rearnsha at gcc dot gnu dot org
2004-11-09 15:09 ` [Bug bootstrap/18401] " rearnsha at gcc dot gnu dot org
2004-11-09 15:10 ` pinskia at gcc dot gnu dot org
2004-11-09 15:47 ` rearnsha at gcc dot gnu dot org
2004-11-09 17:55 ` [Bug rtl-optimization/18401] " pinskia at gcc dot gnu dot org
2004-12-12 22:10 ` pinskia at gcc dot gnu dot org
2004-12-13  9:54 ` rearnsha at gcc dot gnu dot org
2004-12-22 13:03 ` steven at gcc dot gnu dot org
2005-01-05 19:00 ` rearnsha at gcc dot gnu dot org [this message]
2005-01-05 19:05 ` [Bug rtl-optimization/18401] " 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=20050105190019.18575.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).