public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/43665] INTENT(IN) etc. optimization of calls: function annotations for noclobber/noescape arguments
Date: Wed, 21 Jul 2010 08:27:00 -0000 [thread overview]
Message-ID: <20100721082709.7586.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43665-13404@http.gcc.gnu.org/bugzilla/>
------- Comment #13 from jamborm at gcc dot gnu dot org 2010-07-21 08:27 -------
(In reply to comment #12)
> So I wonder what code removes the arguments then.
>
IPA-CP can do that for quite some time please try with -fno-ipa-cp.
(I don't have a trunk built with enabled fortran at hand and I am a
bit overwhelmed with bugs and other stuff recently so I can have a
look at this but it will take at least a few days before I get to it.)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43665
next prev parent reply other threads:[~2010-07-21 8:27 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 13:30 [Bug fortran/43665] New: Optimization of libgfortran " burnus at gcc dot gnu dot org
2010-04-06 13:51 ` [Bug fortran/43665] " burnus at gcc dot gnu dot org
2010-05-10 10:11 ` burnus at gcc dot gnu dot org
2010-05-13 10:31 ` dfranke at gcc dot gnu dot org
2010-07-13 13:21 ` burnus at gcc dot gnu dot org
2010-07-13 17:26 ` burnus at gcc dot gnu dot org
2010-07-13 17:32 ` [Bug fortran/43665] INTENT(IN) etc. optimization of " burnus at gcc dot gnu dot org
2010-07-20 15:06 ` burnus at gcc dot gnu dot org
2010-07-20 15:26 ` burnus at gcc dot gnu dot org
2010-07-20 15:58 ` burnus at gcc dot gnu dot org
2010-07-20 16:01 ` rguenth at gcc dot gnu dot org
2010-07-20 16:12 ` burnus at gcc dot gnu dot org
2010-07-21 8:09 ` rguenther at suse dot de
2010-07-21 8:27 ` jamborm at gcc dot gnu dot org [this message]
2010-07-22 15:36 ` burnus at gcc dot gnu dot org
2010-09-06 14:14 ` jamborm at gcc dot gnu dot org
2010-09-06 18:26 ` jamborm at gcc dot gnu dot org
2010-09-06 18:44 ` burnus at gcc dot gnu dot org
2010-09-07 17:01 ` jamborm at gcc dot gnu dot org
2010-09-08 6:25 ` burnus at gcc dot gnu dot org
2010-09-09 8:43 ` burnus at gcc dot gnu dot org
2010-09-10 12:09 ` burnus at gcc dot gnu dot org
2010-09-10 12:12 ` burnus at gcc dot gnu dot org
2010-09-11 15:13 ` dominiq at lps dot ens dot fr
2010-09-12 9:32 ` burnus at gcc dot gnu dot org
2010-09-12 10:14 ` dominiq at lps dot ens dot fr
2010-09-16 21:30 ` burnus at gcc dot gnu dot org
[not found] <bug-43665-4@http.gcc.gnu.org/bugzilla/>
2010-10-16 16:06 ` tkoenig at gcc dot gnu.org
2012-06-29 17:32 ` mikael at gcc dot gnu.org
2013-06-25 9:02 ` dominiq at lps dot ens.fr
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=20100721082709.7586.qmail@sourceware.org \
--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).