public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jamborm 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, 03 Jul 2012 17:44:00 -0000 [thread overview] Message-ID: <bug-48636-4-qAklyjhMIU@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 #15 from Martin Jambor <jamborm at gcc dot gnu.org> 2012-07-03 17:43:35 UTC --- Hi, (In reply to comment #12) > Hi, > I discussed some of the issues today with Martin. For the array descriptor > testcase, we really want ipa-cp to be propagate the constant array bounds > instead of making Inliner to blindly inline enough in all cases. > For that we need > > 1) Make ipa-prop to work on aggregates. For aggregates passed by value we > can have jump functions that define known constants at known offsets I have posted a patch implementing this yesterday: http://gcc.gnu.org/ml/gcc-patches/2012-07/msg00039.html > 2) Make ipa-inline-analysis to produce predicates on constantness of > aggregate fields in the same format I have posted a patch implementing this yesterday too: http://gcc.gnu.org/ml/gcc-patches/2012-07/msg00041.html With this patch, the test case from comment #4 is inlined at -O3 without any parameter tweaking. It is in fact a testcase in that patch. However, functions in real benchmarks are bigger. We will see to what extent IPA-CP can help with them. > 3) Array descriptors are passed by reference, rather than by value. This > need further work, since need to be sure that the value passed does not change > by aliasing. IPA-SRA would help here if it was really SRA and we had > -fwhole-program, but that is weak. We would need IPA-PTA to solve this in > general. Perhaps frontend could help us here since the descriptors are probably > constant after they are initialized, or is there way to change existing > descriptor? At the moment I'm relying on a slightly sophisticated intra-PTA and TBAA. I'll try to investigate where this does not work in Fortran and perhaps will have some suggestions afterwards. > 4) Make ipa-inline-analysis to understand that determining loop bounds is > very cool to do. Yep, knowing what constants should get a profitability "boost" would be indeed very beneficial. Meanwhile, the following patch also helps ipa-inline-analysis.c with cases like fatigue2: http://gcc.gnu.org/ml/gcc-patches/2012-07/msg00052.html
next prev parent reply other threads:[~2012-07-03 17:44 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 [this message] 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 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-qAklyjhMIU@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).