public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/53787] Possible IPA-SRA / IPA-CP improvement
Date: Thu, 28 Jun 2012 10:08:00 -0000 [thread overview]
Message-ID: <bug-53787-4-Gzzq7UlfQB@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
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
CC| |jamborm at gcc dot gnu.org
Component|lto |tree-optimization
Summary|Possible lto improvement |Possible IPA-SRA / IPA-CP
| |improvement
--- Comment #6 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-06-28 10:08:13 UTC ---
This has nothing to do with LTO - with a single compilation unit you can
use -fwhole-program. The issue is that Fortran passes parameters by reference
and our interprocedural constant-propagation pass does not know how to deal
with that. The IPA SRA pass which is supposed to "fix" that decides that
init cannot have its signature changed. Martin, can you check why?
I think we ought to optimize this with -O3 -fwhole-program -fno-inline.
next prev parent reply other threads:[~2012-06-28 10:08 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 ` rguenth at gcc dot gnu.org [this message]
2012-07-19 19:10 ` [Bug tree-optimization/53787] Possible IPA-SRA / IPA-CP improvement 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
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-Gzzq7UlfQB@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).