public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/1833
Date: Thu, 03 Apr 2003 17:36:00 -0000 [thread overview]
Message-ID: <20030403173601.29099.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/1833; it has been noted by GNATS.
From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: gcc-gnats@gcc.gnu.org, <nigels@nigels.com>
Cc:
Subject: Re: c++/1833
Date: Thu, 3 Apr 2003 11:31:58 -0600 (CST)
Nigel,
the problem you sent has nothing to do with the problem described in PR
1833. You are violating aliasing rules. The code in the report is legal,
yours is not.
W.
-------------------------------------------------------------------------
Wolfgang Bangerth email: bangerth@ices.utexas.edu
www: http://www.ices.utexas.edu/~bangerth/
next reply other threads:[~2003-04-03 17:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-03 17:36 Wolfgang Bangerth [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-09 7:16 c++/1833 Gabriel Dos Reis
2003-05-08 23:46 c++/1833 Wolfgang Bangerth
2003-04-04 3:06 c++/1833 Nigel Stewart
2001-04-01 0:00 c++/1833 aoliva
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=20030403173601.29099.qmail@sources.redhat.com \
--to=bangerth@ices.utexas.edu \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).