This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: c++/8417: g++ 3.2 generating different (and incorrect?) code from g++ 2.95.4
- From: bangerth at dealii dot org
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, germain at cs dot utah dot edu, nobody at gcc dot gnu dot org
- Date: 2 Nov 2002 01:50:02 -0000
- Subject: Re: c++/8417: g++ 3.2 generating different (and incorrect?) code from g++ 2.95.4
- Reply-to: bangerth at dealii dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, germain at cs dot utah dot edu, nobody at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org
Synopsis: g++ 3.2 generating different (and incorrect?) code from g++ 2.95.4
State-Changed-From-To: open->closed
State-Changed-By: bangerth
State-Changed-When: Fri Nov 1 17:50:01 2002
State-Changed-Why:
What you try is calling for trouble: you should not assume
anything about where member variables are located relative
to "this". Also, "this" may change from sub- to superclass,
depending on the layout of vtables, etc. You should only
try to zero out data pointed to by "this" if you absolutely
know what you do, and stick to the ABI that is relevant to
your platform.
This said, the ABI gcc uses on Linux has changed between
2.95 and 3.2, so the inconsistent behavior is not surprising.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8417