public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/20165] Pointer does not really escape with write
Date: Thu, 02 Jul 2009 15:47:00 -0000 [thread overview]
Message-ID: <20090702154656.30792.qmail@sourceware.org> (raw)
In-Reply-To: <bug-20165-6528@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from rguenther at suse dot de 2009-07-02 15:46 -------
Subject: Re: Pointer does not really escape
with write
On Thu, 2 Jul 2009, steven at gcc dot gnu dot org wrote:
> ------- Comment #6 from steven at gcc dot gnu dot org 2009-07-02 15:40 -------
> Dan, you mentioned a "pointer_no_escape" attribute. What was that about? I've
> never seen that mentioned before (or a patch to implement it). Sounds like a
> cool attribute to have (and not just for Fortran, too).
There are several useful things to specify per pointer argument:
1) whether it escapes
2) whether pointed-to memory is read
3) whether pointed-to memory is written to
4) whether memory reachable from it is read
5) whether memory reachable form it is written to
6) whether addresses to pointed-to memory may be returned
7) whether addresses to reachable memory may be returned
in addition to, of course, if the function reads from / writes to
global memory.
Zdenek hat a patch with some fancy attribute at some point, and
implementation-wise I'd like to have something that shares
representation with IPA-PTA results.
We do have tasks to do both IPA-PTA and the above attribute btw.
Richard.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20165
next prev parent reply other threads:[~2009-07-02 15:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-20165-6528@http.gcc.gnu.org/bugzilla/>
2007-04-16 21:54 ` pinskia at gcc dot gnu dot org
2009-06-08 18:12 ` tkoenig at gcc dot gnu dot org
2009-07-02 15:40 ` steven at gcc dot gnu dot org
2009-07-02 15:47 ` rguenther at suse dot de [this message]
2009-09-26 15:33 ` rguenth at gcc dot gnu dot org
[not found] <bug-20165-4@http.gcc.gnu.org/bugzilla/>
2010-10-16 16:06 ` tkoenig at gcc dot gnu.org
2010-10-16 18:53 ` tkoenig at gcc dot gnu.org
2005-02-23 18:21 [Bug tree-optimization/20165] New: " pinskia at gcc dot gnu dot org
2005-02-23 23:29 ` [Bug tree-optimization/20165] " pinskia at gcc dot gnu dot org
2005-03-01 18:12 ` pinskia at gcc dot gnu dot org
2005-08-31 15:09 ` dberlin at gcc dot gnu dot 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=20090702154656.30792.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).