public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ysrumyan at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/53787] Possible IPA-SRA / IPA-CP improvement
Date: Tue, 22 Jan 2013 15:33:00 -0000	[thread overview]
Message-ID: <bug-53787-4-pJZqXq28tr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53787-4@http.gcc.gnu.org/bugzilla/>


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

Yuri Rumyantsev <ysrumyan at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ysrumyan at gmail dot com

--- Comment #15 from Yuri Rumyantsev <ysrumyan at gmail dot com> 2013-01-22 15:33:33 UTC ---
We checked that for the attached simple test-case IPA_CP is done but it does
not work for the real bench UMTmk_1.1 it does not work. In this bench we have
the following chain of stmts:

UMTmk:
        npart = 16
        call driver(Size, Geom, npart, storePsi)

driver:
           call init(Size, Geom, npart, storePsi,  &
             next,omega,abdym,sigvol,qc,   &
             TPSIC,PSIC,PSIB,PSIFP,CUREZ)

and we did not see that value 16 for npart has been propagated (if so the
innermost loops with npart upper bound will be completely unrolled).

If we look at call graph for init we see that it does not have callee in graph:

init_.constprop.2/72 (init_.constprop.2) @0x7f0874ee3b90
  Type: function
  Visibility: used_from_other_partition public visibility_specified
visibility:hidden
  References: 
  Referring: 
  Read from file: /tmp/ccGZySlu.ltrans2.o
  Clone of init_.2535/55
  Function flags: analyzed local finalized
  Called by: 
...
I put into attachment the whole bench for investigation.


  parent reply	other threads:[~2013-01-22 15:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-27 17:26 [Bug lto/53787] New: Possible lto improvement izamyatin at gmail dot com
2012-06-27 17:39 ` [Bug lto/53787] " dominiq at lps dot ens.fr
2012-06-27 17:57 ` izamyatin at gmail dot com
2012-06-27 20:03 ` hjl.tools at gmail dot com
2012-06-28  8:17 ` izamyatin at gmail dot com
2012-06-28  8:22 ` izamyatin at gmail dot com
2012-06-28 10:08 ` [Bug tree-optimization/53787] Possible IPA-SRA / IPA-CP improvement rguenth at gcc dot gnu.org
2012-07-19 19:10 ` izamyatin at gmail dot com
2012-07-20 19:59 ` jamborm at gcc dot gnu.org
2012-07-26 22:49 ` steven at gcc dot gnu.org
2012-07-27  9:35 ` jamborm at gcc dot gnu.org
2012-08-30 15:59 ` jamborm at gcc dot gnu.org
2012-11-07 15:56 ` jamborm at gcc dot gnu.org
2012-11-08 14:43 ` jamborm at gcc dot gnu.org
2013-01-22 15:32 ` ysrumyan at gmail dot com
2013-01-22 15:33 ` ysrumyan at gmail dot com [this message]
2013-01-25 18:33 ` jamborm at gcc dot gnu.org
2014-02-14 17:16 ` jamborm at gcc dot gnu.org
2014-02-28 14:26 ` izamyatin at gmail dot com
2014-05-23 15:52 ` jamborm 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-53787-4-pJZqXq28tr@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).