public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marc@nieper-wisskirchen.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/89479] __restrict on a pointer ignored when disambiguating against a call
Date: Wed, 16 Feb 2022 21:56:35 +0000	[thread overview]
Message-ID: <bug-89479-4-r9r0wr1yC8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-89479-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89479

--- Comment #11 from Marc Nieper-Wißkirchen <marc@nieper-wisskirchen.de> ---
(In reply to Richard Biener from comment #1 of bug 94416)
> I think there's a duplicate somewhere.  We currently cannot encode "restrict"
> into the "accesses" implied by a call.
> 
> Note there's slight complication when g (b) eventually recurses into 'f'
> passing this 'b' as 'a'.  Recursion makes the interpretation of the
> lexically defined restrict concept a bit weird.
> 
> So I think this bug can be closed as duplicate of the "restrict and calls"
> bug.
> 
> *** This bug has been marked as a duplicate of bug 89479 ***

What do you mean by that the restrict concept is lexically defined? If I read
the standard correctly, restrict makes an assumption about the dynamic extent
of an executed block. This seems obvious from section 6.7.3.1 (of ISO C18)
which speaks of the block of main in paragraph 2 and the lifetime of objects in
paragraph 5.

  parent reply	other threads:[~2022-02-16 21:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-89479-4@http.gcc.gnu.org/bugzilla/>
2020-03-31  7:49 ` rguenth at gcc dot gnu.org
2022-02-16 21:37 ` pinskia at gcc dot gnu.org
2022-02-16 21:56 ` marc@nieper-wisskirchen.de [this message]
2023-07-07 17:49 ` pinskia at gcc dot gnu.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=bug-89479-4-r9r0wr1yC8@http.gcc.gnu.org/bugzilla/ \
    --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).