From: Dan Nicolaescu <dann@godzilla.ICS.UCI.EDU>
To: mike stump <mrs@windriver.com>
Cc: jason@redhat.com, gcc@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: C++ aliasing rules
Date: Fri, 17 May 2002 13:09:00 -0000 [thread overview]
Message-ID: <200205171201.aa25976@gremlin-relay.ics.uci.edu> (raw)
In-Reply-To: <200204260027.RAA00692@kankakee.wrs.com>
Now that 3.1 is out of the way we can reopen this discussion...
For reference the start of this thread is at:
http://gcc.gnu.org/ml/libstdc++/2002-04/msg00049.html
mike stump <mrs@windriver.com> writes:
> > To: Dan Nicolaescu <dann@godzilla.ICS.UCI.EDU>
> > Cc: mike stump <mrs@windriver.com>, gcc@gcc.gnu.org, libstdc++@gcc.gnu.org
> > From: Jason Merrill <jason@redhat.com>
> > Date: Thu, 25 Apr 2002 18:44:05 +0100
>
> > I don't see how Mike's statement answers my question.
>
> Yes, I agree, I don't think it does.
>
> > I would probably support writing that into the standard. But I
> > don't think that's what it says now.
>
> A hard line would be we should be conservative, and get it written
> into the standard first. I think it would be reasonable for the
> standard to say they don't alias.
>
> If we want to lead the standard, I think we can. Because the standard
> isn't perfectly clear, it would be good to document what we did.
If we decide to lead the standard, I volunteer the write the patch and
the associated GCC documentation.
Somebody else will have to take care about the standardization
process...
Who can make a decision about this?
--dan
prev parent reply other threads:[~2002-05-17 19:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200204031103.aa15838@gremlin-relay.ics.uci.edu>
2002-04-23 13:59 ` Jason Merrill
2002-04-23 19:52 ` mike stump
2002-04-24 6:43 ` Andreas Schwab
2002-04-24 13:32 ` Dan Nicolaescu
2002-04-25 1:11 ` Nathan Sidwell
2002-04-25 10:57 ` Jason Merrill
2002-04-25 17:44 ` mike stump
2002-05-17 13:09 ` Dan Nicolaescu [this message]
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=200205171201.aa25976@gremlin-relay.ics.uci.edu \
--to=dann@godzilla.ics.uci.edu \
--cc=gcc@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=mrs@windriver.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).