public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/114210] Potential bug wrt __restrict on member function decl/def Date: Sun, 31 Mar 2024 00:18:12 +0000 [thread overview] Message-ID: <bug-114210-4-Hp8WjzzB4w@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114210-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114210 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Exactly like the following standard C23 code: ``` void nonrestirct(); void restirctcall(); void foo (int* a, int* __restrict b, int n); void foo (int* a, int* b, int n) { typeof(b) c = b; _Generic (&c , int * __restrict*: restirctcall(), int **: nonrestirct() ); // calls nonrestirct } void foo1 (int* a, int* b, int n); void foo1 (int* a, int* __restrict b, int n) { typeof(b) c = b; _Generic (&c , int * __restrict*: restirctcall(), int **: nonrestirct() ); // calls restirctcall } ```
next prev parent reply other threads:[~2024-03-31 0:18 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-02 17:41 [Bug c++/114210] New: " rl.alt.accnt at gmail dot com 2024-03-31 0:08 ` [Bug c++/114210] " pinskia at gcc dot gnu.org 2024-03-31 0:18 ` pinskia at gcc dot gnu.org [this message] 2024-03-31 0:25 ` rl.alt.accnt at gmail dot com
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-114210-4-Hp8WjzzB4w@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: linkBe 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).