From: Diego Novillo <dnovillo@redhat.com>
To: James E Wilson <wilson@specifixinc.com>
Cc: Jeroen Dobbelaere <jeroen.dobbelaere@gmail.com>, gcc@gcc.gnu.org
Subject: Re: restrict and char pointers
Date: Thu, 05 May 2005 01:10:00 -0000 [thread overview]
Message-ID: <20050505004120.GA12726@topo.toronto.redhat.com> (raw)
In-Reply-To: <1115251703.5426.169.camel@aretha.corp.specifixinc.com>
On Wed, May 04, 2005 at 05:08:23PM -0700, James E Wilson wrote:
> We can perhaps handle this well in the tree-aliasing code (if
> it handled restrict at all), but it would be difficult to
> handle this well in the RTL aliasing code.
>
It doesn't. Mostly for similar reasons.
Perhaps we could be more aggressive with the new aliasing changes
coming down the line, but it's certainly non-trivial to take
advantage of restrict. A shame, really.
Diego.
next prev parent reply other threads:[~2005-05-05 0:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 10:18 Jeroen Dobbelaere
2005-05-04 20:47 ` James E Wilson
2005-05-04 21:31 ` Jeroen Dobbelaere
2005-05-04 23:24 ` James E Wilson
2005-05-05 0:04 ` Jeroen Dobbelaere
2005-05-05 0:22 ` James E Wilson
2005-05-05 1:10 ` Diego Novillo [this message]
2005-05-05 21:53 ` Daniel Berlin
2005-05-07 3:16 ` Michael Matz
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=20050505004120.GA12726@topo.toronto.redhat.com \
--to=dnovillo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jeroen.dobbelaere@gmail.com \
--cc=wilson@specifixinc.com \
/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).