public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amker at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/62631] gcc.dg/tree-ssa/ivopts-lt-2.c FAILs
Date: Sun, 08 Feb 2015 14:07:00 -0000	[thread overview]
Message-ID: <bug-62631-4-0G6RTcM553@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62631-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62631

--- Comment #28 from amker at gcc dot gnu.org ---
On hppa 32, the two iv uses are:
use 0
  address
  in statement *p_1 = 0;

  at position *p_1
  type int *
  base p_7
  step 4
  base object (void *) p_7
  related candidates 
use 1
  compare
  in statement if (i_11 <= 99)

  at position 
  type unsigned int
  base i_4(D) + 1
  step 1
  is a biv
  related candidates 
And the BIV/GIV candidates are:
candidate 3 (important)
  original biv
  type int *
  base p_7
  step 4
  base object (void *) p_7
candidate 4 (important)
  ...
candidate 5 (important)
  original biv
  type unsigned int
  base i_4(D)
  step 1

The costs table are:

Candidate costs:
  cand    cost
  0    5
  1    5
  2    5
  3    4
  4    5
  5    4
  6    5
  7    5
Use 0:
  cand    cost    compl.    depends on
  0    1    2    1
  1    1    0    
  2    1    1    1
  3    1    0    
  4    3    2     inv_expr:0
  5    3    2     inv_expr:0
  6    1    1    
  7    19    3     inv_expr:1

Use 1:
  cand    cost    compl.    depends on
  0    4    0     inv_expr:2
  3    3    0     inv_expr:3
  4    0    0    
  5    0    0    
  7    4    1    

It seems cand3 and cand5 have same level cost, but GCC chooses candidate 5 as
below:
Initial set of candidates:
  cost: 9 (complexity 2)
  cand_cost: 4
  cand_use_cost: 3 (complexity 2)
  candidates: 5
   use:0 --> iv_cand:5, cost=(3,2)
   use:1 --> iv_cand:5, cost=(0,0)

While on other targets, cand 3 is selected.


  parent reply	other threads:[~2015-02-08 14:07 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-01 13:52 [Bug tree-optimization/62631] New: " ro at gcc dot gnu.org
2014-09-01 13:53 ` [Bug tree-optimization/62631] " ro at gcc dot gnu.org
2014-09-01 14:06 ` ro at gcc dot gnu.org
2014-09-01 14:26 ` ro at gcc dot gnu.org
2014-09-01 14:27 ` ro at gcc dot gnu.org
2014-09-02  6:00 ` amker.cheng at gmail dot com
2014-09-07 19:37 ` danglin at gcc dot gnu.org
2014-09-11  5:48 ` amker at gcc dot gnu.org
2014-09-11  8:43 ` ro at CeBiTec dot Uni-Bielefeld.DE
2014-09-12 10:58 ` ro at CeBiTec dot Uni-Bielefeld.DE
2015-02-02 23:22 ` [Bug target/62631] " ebotcazou at gcc dot gnu.org
2015-02-03  9:57 ` ebotcazou at gcc dot gnu.org
2015-02-03 10:54 ` amker at gcc dot gnu.org
2015-02-04  4:06 ` amker at gcc dot gnu.org
2015-02-04 11:45 ` ebotcazou at gcc dot gnu.org
2015-02-04 14:43 ` ebotcazou at gcc dot gnu.org
2015-02-06  6:20 ` amker at gcc dot gnu.org
2015-02-06  7:10 ` ebotcazou at gcc dot gnu.org
2015-02-06 11:18 ` ebotcazou at gcc dot gnu.org
2015-02-06 11:26 ` ebotcazou at gcc dot gnu.org
2015-02-06 11:33 ` ebotcazou at gcc dot gnu.org
2015-02-06 15:52 ` dave.anglin at bell dot net
2015-02-07 19:08 ` dave.anglin at bell dot net
2015-02-07 22:24 ` ebotcazou at gcc dot gnu.org
2015-02-07 23:14 ` dave.anglin at bell dot net
2015-02-08 14:07 ` amker at gcc dot gnu.org [this message]
2015-02-08 14:09 ` amker at gcc dot gnu.org
2015-02-08 14:59 ` dave.anglin at bell dot net
2015-02-08 21:44 ` ebotcazou at gcc dot gnu.org
2015-02-09  3:24 ` amker at gcc dot gnu.org
2015-02-09  8:11 ` amker at gcc dot gnu.org
2015-04-22 12:01 ` jakub at gcc dot gnu.org
2015-07-16  9:13 ` rguenth at gcc dot gnu.org
2022-01-09  0:42 ` pinskia at gcc dot gnu.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=bug-62631-4-0G6RTcM553@http.gcc.gnu.org/bugzilla/ \
    --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).