From: Ian Lance Taylor <iant@google.com>
To: Alexey Salmin <alexey.salmin@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Question about restrict pointers
Date: Sat, 24 Apr 2010 11:37:00 -0000 [thread overview]
Message-ID: <mcrtyr1slpo.fsf@dhcp-172-17-9-151.mtv.corp.google.com> (raw)
In-Reply-To: <o2q87a8dc11004212348odde40fdcn2f444d26d3c82bd4@mail.gmail.com> (Alexey Salmin's message of "Thu\, 22 Apr 2010 13\:48\:13 +0700")
Alexey Salmin <alexey.salmin@gmail.com> writes:
> However if we add a "restrict" keyword to the definition of b like
> that it affects nothing:
> As far as I understand the "restrict" concept "const int *restrict b"
> guarantee that "*b" will not be modified by "*a++ = *b + 1;".
I believe you are correct, and that this is an unimplemented
optimization.
Ian
next prev parent reply other threads:[~2010-04-24 1:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 11:01 Alexey Salmin
2010-04-24 11:37 ` Ian Lance Taylor [this message]
2010-04-24 18:32 ` Manuel López-Ibáñez
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=mcrtyr1slpo.fsf@dhcp-172-17-9-151.mtv.corp.google.com \
--to=iant@google.com \
--cc=alexey.salmin@gmail.com \
--cc=gcc-help@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).