public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/48636] Enable more inlining with -O2 and higher Date: Tue, 21 Aug 2012 08:15:00 -0000 [thread overview] Message-ID: <bug-48636-4-IfRnXDhKwz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48636-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48636 --- Comment #18 from Jan Hubicka <hubicka at gcc dot gnu.org> 2012-08-21 08:14:33 UTC --- With loop_iterations hint, we should now hint the bar function of testcase in comment #4, but we don't because the value is used conditionally: # iftmp.11_3 = PHI <_12(3), 1(2)> a.0_16 = a_11(D)->data; _17 = a_11(D)->dim[0].ubound; _18 = a_11(D)->dim[0].lbound; _19 = _17 - _18; ubound.0_20 = _19 + 1; stride.3_21 = a_11(D)->dim[1].stride; _22 = a_11(D)->dim[1].ubound; _23 = a_11(D)->dim[1].lbound; _24 = _22 - _23; ubound.2_25 = _24 + 1; _27 = -iftmp.11_3; offset.4_28 = _27 - stride.3_21; *x_35(D) = 0.0; _53 = stride.3_21 >= 0; _56 = ubound.2_25 > 0; _57 = _53 & _56; _59 = stride.3_21 < 0; _60 = _57 | _59; _66 = _59 | _60; if (_66 != 0) goto <bb 5>; else goto <bb 6>; <bb 5>: iftmp.13_68 = (integer(kind=4)) ubound.2_25; <bb 6>: # iftmp.13_4 = PHI <iftmp.13_68(5), 0(4)> if (iftmp.13_4 > 0) goto <bb 7>; else goto <bb 14>; Martin, does this work with your PHI patch? (i.e. do you get "loop iterations" in -fdump-ipa-inline?) Next step will be to teach inliner to inline into functions called once when callee is important and some propagation happens. Honza
next prev parent reply other threads:[~2012-08-21 8:15 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-15 21:05 [Bug fortran/48636] New: " tkoenig at gcc dot gnu.org 2011-04-16 11:22 ` [Bug fortran/48636] " rguenth at gcc dot gnu.org 2011-04-17 10:23 ` dominiq at lps dot ens.fr 2011-04-17 10:44 ` hubicka at gcc dot gnu.org 2011-04-17 13:32 ` tkoenig at gcc dot gnu.org 2011-04-17 14:12 ` dominiq at lps dot ens.fr 2011-04-20 11:22 ` jb at gcc dot gnu.org 2011-04-20 12:29 ` burnus at gcc dot gnu.org 2011-04-20 13:10 ` jb at gcc dot gnu.org 2011-04-20 15:42 ` burnus at gcc dot gnu.org 2011-04-20 16:41 ` tkoenig at gcc dot gnu.org 2011-04-20 18:15 ` jb at gcc dot gnu.org 2011-05-04 16:23 ` hubicka at gcc dot gnu.org 2011-05-04 17:31 ` burnus at gcc dot gnu.org 2011-06-04 18:08 ` hubicka at gcc dot gnu.org 2012-07-03 17:44 ` jamborm at gcc dot gnu.org 2012-08-11 10:50 ` jamborm at gcc dot gnu.org 2012-08-21 6:54 ` hubicka at gcc dot gnu.org 2012-08-21 8:15 ` hubicka at gcc dot gnu.org [this message] 2012-09-12 21:52 ` hubicka at gcc dot gnu.org 2012-10-16 16:39 ` hubicka at gcc dot gnu.org 2012-10-16 17:58 ` dominiq at lps dot ens.fr 2012-10-16 20:59 ` dominiq at lps dot ens.fr 2012-10-17 12:20 ` jakub at gcc dot gnu.org 2012-10-17 13:13 ` dominiq at lps dot ens.fr 2012-10-17 14:06 ` dominiq at lps dot ens.fr 2012-10-19 8:45 ` vincenzo.innocente at cern dot ch 2012-10-20 10:35 ` hubicka at gcc dot gnu.org 2012-10-20 11:22 ` dominiq at lps dot ens.fr 2012-10-20 12:11 ` tkoenig at gcc dot gnu.org 2012-10-28 10:08 ` hubicka at gcc dot gnu.org 2012-10-28 10:11 ` hubicka at gcc dot gnu.org 2012-10-28 11:27 ` vincenzo.innocente at cern dot ch 2012-11-07 9:34 ` hubicka at gcc dot gnu.org 2012-11-07 11:18 ` hubicka at gcc dot gnu.org 2012-11-08 16:46 ` hubicka at gcc dot gnu.org 2012-11-11 18:15 ` hubicka at gcc dot gnu.org 2012-11-12 12:16 ` hubicka at gcc dot gnu.org 2012-11-12 12:45 ` izamyatin at gmail dot com 2012-11-14 23:22 ` hubicka at gcc dot gnu.org 2012-11-14 23:54 ` Jan Hubicka 2012-11-14 23:55 ` hubicka at ucw dot cz 2012-11-15 2:29 ` hubicka at gcc dot gnu.org 2012-11-16 14:43 ` dominiq at lps dot ens.fr 2013-03-01 17:49 ` wschmidt at gcc dot gnu.org 2013-03-04 17:54 ` wschmidt 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-48636-4-IfRnXDhKwz@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: linkBe 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).