From: Joseph Myers <josmyers@redhat.com>
To: Ties Klappe <tg.klappe@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Nested restrict pointers: missed optimization & client with UB?
Date: Tue, 13 Feb 2024 14:29:11 +0000 (UTC) [thread overview]
Message-ID: <4b5ab0fa-7f70-4617-379-a80c94b1dc6@redhat.com> (raw)
In-Reply-To: <CAHSOcvAOb5df_R3hF3k7p-57BG5r=VArM8Ybqs6=bP7RDYarSg@mail.gmail.com>
On Tue, 13 Feb 2024, Ties Klappe via Gcc wrote:
> int foo2(int *restrict *p, int *restrict *q)
> {
> **p = 10;
> **q = 11;
> return **p;
> }
In this case, *p and *q might be the same restricted pointer object. See
the more detailed explanation at
<https://gcc.gnu.org/bugzilla/show_bug.cgi?id=14192#c8>.
--
Joseph S. Myers
josmyers@redhat.com
next prev parent reply other threads:[~2024-02-13 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 13:00 Ties Klappe
2024-02-13 14:15 ` Richard Biener
2024-02-13 14:29 ` Joseph Myers [this message]
2024-02-13 15:25 ` Ties Klappe
2024-02-13 15:33 ` Joseph Myers
2024-02-13 16:06 ` Richard Biener
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=4b5ab0fa-7f70-4617-379-a80c94b1dc6@redhat.com \
--to=josmyers@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=tg.klappe@gmail.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).