public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/62171] restrict pointer to struct with restrict pointers parm doesn't prevent aliases
Date: Fri, 22 May 2015 11:25:00 -0000	[thread overview]
Message-ID: <bug-62171-4-7YtkxgSloA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62171-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from vries at gcc dot gnu.org ---
(In reply to vries from comment #3)
> (In reply to Richard Biener from comment #2)
> > And maybe set DECL_BY_REFERENCE, a mere REFERENCE_TYPE doesn't prevent
> > you from doing (&param)[2] which we'd miscompile.  Not sure who added
> > that REFERENCE_TYPE code.
>

[correcting copy/past-o]

Submitted here: https://gcc.gnu.org/ml/gcc-patches/2011-09/msg01426.html
OK-ed here: https://gcc.gnu.org/ml/gcc-patches/2011-09/msg01489.html


  parent reply	other threads:[~2015-05-22 11:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-18 14:51 [Bug tree-optimization/62171] New: " vries at gcc dot gnu.org
2014-08-20  9:15 ` [Bug tree-optimization/62171] " rguenth at gcc dot gnu.org
2014-08-20  9:17 ` rguenth at gcc dot gnu.org
2015-05-22 11:23 ` vries at gcc dot gnu.org
2015-05-22 11:25 ` vries at gcc dot gnu.org [this message]
2015-05-22 11:30 ` vries at gcc dot gnu.org
2015-09-21 16:15 ` vries at gcc dot gnu.org
2015-09-22  8:01 ` rguenth at gcc dot gnu.org
2015-09-22  8:58 ` vries at gcc dot gnu.org
2015-09-22 10:51 ` rguenther at suse dot de
2015-09-22 11:23 ` vries at gcc dot gnu.org
2015-09-22 14:09 ` rguenther at suse dot de
2015-09-28  8:51 ` vries at gcc dot gnu.org
2015-09-28  8:55 ` 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-62171-4-7YtkxgSloA@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).