public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/67705] incorrect restrict interpretation Date: Thu, 24 Sep 2015 16:28:00 -0000 [thread overview] Message-ID: <bug-67705-4-TD0LVaEHeN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67705-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67705 --- Comment #4 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- Regarding multiple levels of restricted pointers, please see my annotations of the C99 wording at <https://gcc.gnu.org/ml/gcc-bugs/2005-01/msg03394.html>, in particular as regards the wording "Every access that modifies X shall be considered also to modify P, for the purposes of this subclause.".
next prev parent reply other threads:[~2015-09-24 16:28 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-09-24 8:09 [Bug tree-optimization/67705] New: " vries at gcc dot gnu.org 2015-09-24 9:07 ` [Bug tree-optimization/67705] " glisse at gcc dot gnu.org 2015-09-24 11:25 ` rguenth at gcc dot gnu.org 2015-09-24 14:20 ` vries at gcc dot gnu.org 2015-09-24 16:28 ` joseph at codesourcery dot com [this message] 2015-09-25 5:46 ` vries 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-67705-4-TD0LVaEHeN@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).