From: Jeroen Dobbelaere <jeroen.dobbelaere@gmail.com>
To: James E Wilson <wilson@specifixinc.com>
Cc: gcc@gcc.gnu.org
Subject: Re: restrict and char pointers
Date: Thu, 05 May 2005 00:04:00 -0000 [thread overview]
Message-ID: <325e93670505041624262d6e2c@mail.gmail.com> (raw)
In-Reply-To: <1115247081.5426.144.camel@aretha.corp.specifixinc.com>
On 5/4/05, James E Wilson wrote:
[..]
> The standard says "A translator is free to ignore any or all aliasing
> implications of restrict". So there is no conflict with the standard
> here. We are free to do as little optimization as we want, and in the
> case of a restricted char pointer, we do none.
I'm aware of that. The reason are asked for more clarity is that I
think gcc should
do better (as in the example I gave), but I want to be sure that this
is still allowed
by the standard.
[..]
> /* No two restricted pointers can point at the same thing.
> However, a restricted pointer can point at the same thing
> as an unrestricted pointer, if that unrestricted pointer
> is based on the restricted pointer. So, we make the
> alias set for the restricted pointer a subset of the
> alias set for the type pointed to by the type of the
> decl. */
[..]
From what I found on these pages I refered to, this could be made more strict :
accesses through restricted pointers would not interfere with other accesses,
which would allow some more aggressive optimizations.
Greetings,
--
Jeroen Dobbelaere
next prev parent reply other threads:[~2005-05-04 23:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 10:18 Jeroen Dobbelaere
2005-05-04 20:47 ` James E Wilson
2005-05-04 21:31 ` Jeroen Dobbelaere
2005-05-04 23:24 ` James E Wilson
2005-05-05 0:04 ` Jeroen Dobbelaere [this message]
2005-05-05 0:22 ` James E Wilson
2005-05-05 1:10 ` Diego Novillo
2005-05-05 21:53 ` Daniel Berlin
2005-05-07 3:16 ` Michael Matz
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=325e93670505041624262d6e2c@mail.gmail.com \
--to=jeroen.dobbelaere@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=wilson@specifixinc.com \
/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).