From: Paul Smith <paul@mad-scientist.net>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Hei Chan <structurechart@yahoo.com>,
Andrew Haley <aph@redhat.com>,
"gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: is portable aliasing possible in C++?
Date: Mon, 15 Sep 2014 12:09:00 -0000 [thread overview]
Message-ID: <1410783001.10011.70.camel@homebase> (raw)
In-Reply-To: <CAH6eHdR4074ni68szw14Qq43mXUG590mVkwkvxzUWFfjipEtbg@mail.gmail.com>
On Mon, 2014-09-15 at 12:27 +0100, Jonathan Wakely wrote:
> On 15 September 2014 12:07, Hei Chan wrote:
> > Your statement that the trick "is now hallowed by the standard"
> > makes it sounds like at some point GCC won't guarantee it work
> > anymore.
>
> If GCC supports a feature, and that feature is now standardised, why
> would GCC stop supporting it?
Perhaps a language barrier issue? Using a less-common term like
"hallowed" may be throwing Hei off the mark?
"Hallowed" means "enshrined" or "blessed"; in other words, the standard
has adopted the behavior as part of the standard. Therefore GCC will
definitely not abandon it.
Hei; it would help us greatly if you could configure your mail software
to include some sort of quoting to the original text when you reply to
email. Your responses and the text you are replying to look exactly the
same and it's very confusing.
Cheers!
next prev parent reply other threads:[~2014-09-15 12:09 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 23:03 haynberg
2014-09-11 8:11 ` Andrew Haley
2014-09-11 23:25 ` haynberg
2014-09-12 8:32 ` Andrew Haley
2014-09-12 22:58 ` haynberg
2014-09-13 7:23 ` Andrew Haley
2014-09-13 11:45 ` Oleg Endo
2014-09-15 2:37 ` Hei Chan
2014-09-15 8:35 ` Andrew Haley
2014-09-15 11:07 ` Hei Chan
2014-09-15 11:21 ` Andrew Haley
2014-09-15 11:29 ` Hei Chan
2014-09-15 11:32 ` Andrew Haley
2014-09-15 11:57 ` Hei Chan
2014-09-15 13:21 ` Andrew Haley
2014-09-15 13:31 ` Hei Chan
2014-09-15 14:11 ` Andrew Haley
2014-09-15 11:27 ` Jonathan Wakely
2014-09-15 12:09 ` Paul Smith [this message]
2014-11-02 23:55 ` Hei Chan
2014-11-03 9:34 ` Andrew Haley
-- strict thread matches above, loose matches on Subject: below --
2014-09-09 23:13 haynberg
2014-09-10 8:17 ` Andrew Haley
[not found] <A76FB9DDEDFA994BAF6B77704A4AF465BC2464@xchmbbal502.ds.susq.com>
2014-09-04 16:11 ` Andy Webber
2014-09-04 16:51 ` Andrew Haley
2014-09-04 17:18 ` Andy Webber
2014-09-04 17:23 ` Andrew Haley
2014-09-04 17:44 ` Andy Webber
2014-09-04 17:47 ` Andy Webber
2014-09-04 17:48 ` Andrew Haley
2014-09-04 23:11 ` Jonathan Wakely
2014-09-05 7:16 ` Andrew Haley
2014-09-05 14:19 ` Jason Merrill
2014-09-08 9:33 ` Richard Biener
2014-09-10 14:31 ` Jason Merrill
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=1410783001.10011.70.camel@homebase \
--to=paul@mad-scientist.net \
--cc=aph@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=structurechart@yahoo.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).