public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "acahalan at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/26372] opposite of may_alias attribute
Date: Mon, 20 Feb 2006 03:29:00 -0000	[thread overview]
Message-ID: <20060220032953.17918.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26372-12219@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from acahalan at gmail dot com  2006-02-20 03:29 -------
There have been times when I could not prove to myself that __restrict would be
safe (it may have been), yet I knew that the char pointer would not alias with
non-char pointers.

(sorry to not have a nice chunk of code handy -- I just discovered where to
report gcc bugs and missing features, so I had a backlog of things that have
bothered me over the years)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26372


  parent reply	other threads:[~2006-02-20  3:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-19 21:29 [Bug c/26372] New: " acahalan at gmail dot com
2006-02-19 21:31 ` [Bug c/26372] " pinskia at gcc dot gnu dot org
2006-02-19 21:40 ` acahalan at gmail dot com
2006-02-20  2:04 ` pinskia at gcc dot gnu dot org
2006-02-20  3:29 ` acahalan at gmail dot com [this message]
2006-02-21 10:18 ` rguenth at gcc dot gnu dot org
2006-02-22  3:28 ` acahalan at gmail dot com
2006-07-19  3:48 ` pinskia at gcc dot gnu dot 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=20060220032953.17918.qmail@sourceware.org \
    --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).