public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, germain@cs.utah.edu,
	nobody@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 17:50:00 -0000	[thread overview]
Message-ID: <20021102015002.25145.qmail@sources.redhat.com> (raw)

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


             reply	other threads:[~2002-11-02  1:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-01 17:50 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-01  0:46 Giovanni Bajo
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=20021102015002.25145.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=germain@cs.utah.edu \
    --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).