From: patl AT cag.lcs.mit.edu (Patrick J. LoPresti)
To: gcc AT gcc.cygnus.com
Cc: rms AT gnu.org, jamie.lokier AT cern.ch
Subject: Re: [dax@gurulabs.com: PATCH: `__norestrict' type qualifier (fwd)]
Date: Tue, 14 Sep 1999 08:34:00 -0000 [thread overview]
Message-ID: <s5gwvttwlrx.fsf@egghead.curl.com> (raw)
In-Reply-To: <19990912212818.C26524@pcep-jamie.cern.ch>
As author of that patch, here is my $0.02.
First, as Richard Henderson pointed out when we discussed this before,
`__typealias' is a better name than `__norestrict'. An informal
description of the behavior meshes nicely with Mark Mitchell's
informal description of the alias analysis rules; namely, that this
type qualifier allows access to the same memory through different
types of pointer.
Jamie's precise specification, which amounts to saying that
`__typealias' is shorthand for "the union hack", should also be given
in the documentation and used to resolve any arguments about the
behavior of the extension. Jamie's spec could also be used to propose
this type qualifier to the standards bodies.
I am willing to do whatever work the GCC maintainers want to make my
patch acceptable to them, assuming they are amenable to the idea at
all. Are they?
- Pat
WARNING: multiple messages have this Message-ID
From: patl@cag.lcs.mit.edu (Patrick J. LoPresti)
To: gcc@gcc.cygnus.com
Cc: rms@gnu.org, jamie.lokier@cern.ch
Subject: Re: [dax@gurulabs.com: PATCH: `__norestrict' type qualifier (fwd)]
Date: Thu, 30 Sep 1999 18:02:00 -0000 [thread overview]
Message-ID: <s5gwvttwlrx.fsf@egghead.curl.com> (raw)
Message-ID: <19990930180200.8Txdb2cUnGARjmv7q3UDPbbsmdMjpWxXvlMZ0GDhyms@z> (raw)
In-Reply-To: <19990912212818.C26524@pcep-jamie.cern.ch>
As author of that patch, here is my $0.02.
First, as Richard Henderson pointed out when we discussed this before,
`__typealias' is a better name than `__norestrict'. An informal
description of the behavior meshes nicely with Mark Mitchell's
informal description of the alias analysis rules; namely, that this
type qualifier allows access to the same memory through different
types of pointer.
Jamie's precise specification, which amounts to saying that
`__typealias' is shorthand for "the union hack", should also be given
in the documentation and used to resolve any arguments about the
behavior of the extension. Jamie's spec could also be used to propose
this type qualifier to the standards bodies.
I am willing to do whatever work the GCC maintainers want to make my
patch acceptable to them, assuming they are amenable to the idea at
all. Are they?
- Pat
next prev parent reply other threads:[~1999-09-14 8:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-12 0:51 Richard Stallman
1999-09-12 12:29 ` Jamie Lokier
1999-09-14 8:34 ` patl [this message]
1999-09-14 8:38 ` Jamie Lokier
1999-09-15 2:02 ` Jeffrey A Law
1999-09-30 18:02 ` Jeffrey A Law
1999-09-30 18:02 ` Jamie Lokier
1999-09-30 18:02 ` Patrick J. LoPresti
1999-09-30 18:02 ` Jamie Lokier
1999-09-30 18:02 ` Richard Stallman
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=s5gwvttwlrx.fsf@egghead.curl.com \
--to=gcc@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).