public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Giovanni Bajo" <bagio@zh.t2-design.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/8417: g++ 3.2 generating different (and incorrect?) code from g++ 2.95.4
Date: Fri, 01 Nov 2002 00:46:00 -0000 [thread overview]
Message-ID: <20021101084605.28461.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/8417; it has been noted by GNATS.
From: "Giovanni Bajo" <bagio@zh.t2-design.com>
To: <gcc-gnats@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>, <germain@cs.utah.edu>,
<gcc-bugs@gcc.gnu.org>, <nobody@gcc.gnu.org>
Cc:
Subject: Re: c++/8417: g++ 3.2 generating different (and incorrect?) code from g++ 2.95.4
Date: Fri, 1 Nov 2002 16:38:07 +0800
This is a multi-part message in MIME format.
------=_NextPart_000_1771_01C281C5.0E6A1990
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-trail&database=3D=
gcc&pr=3D8417
The value of this can be changed by the compiler at any time, there is =
no guarantee (in the C++ standard) that it remains the same across the =
derived class tree. For example, it is very usual that the value changes =
when you are using multiple inheritance. This is not a bug in the =
compiler.
------=_NextPart_000_1771_01C281C5.0E6A1990
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4916.2300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><A=20
href=3D"http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-trail&a=
mp;database=3Dgcc&pr=3D8417">http://gcc.gnu.org/cgi-bin/gnatsweb.pl?c=
md=3Dview%20audit-trail&database=3Dgcc&pr=3D8417</A></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>The value of this can be changed by the =
compiler at=20
any time, there is no guarantee (in the C++ standard) that it remains =
the same=20
across the derived class tree. For example, it is very usual that the =
value=20
changes when you are using multiple inheritance. This is not a bug in =
the=20
compiler.</FONT></DIV></BODY></HTML>
------=_NextPart_000_1771_01C281C5.0E6A1990--
next reply other threads:[~2002-11-01 8:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-01 0:46 Giovanni Bajo [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-01 17:50 bangerth
2002-10-31 13:36 germain
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=20021101084605.28461.qmail@sources.redhat.com \
--to=bagio@zh.t2-design.com \
--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).