From: "Magnus Fromreide" <magfr56@hotmail.com>
To: gcc@gcc.gnu.org
Subject: Broken vtable-thunks
Date: Fri, 15 Sep 2000 02:14:00 -0000 [thread overview]
Message-ID: <F112SOlbpH71yEXUIEA00012175@hotmail.com> (raw)
Have anybody looked into the broken vtable-thunks that are present
in 2.95.2 as well as 2.96 20000904? What could be done to circumvent the
problem when it hits me?
When I tried the patch from
http://gcc.gnu.org/ml/gcc-patches/2000-02/msg00934.html
applied on 2.95.2 it did me no good, on a simple test program it fixed the
bug in nonoptimized mode but in optimized mode then an instantiation of the
second leaf failed. On the target program it moved the crash from one of our
destructors to the constructor of fstream, where the call constructing went
bad.
Do anyone have any ideas to share?
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com .
Share information about yourself, create your own public profile at
http://profiles.msn.com .
reply other threads:[~2000-09-15 2:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=F112SOlbpH71yEXUIEA00012175@hotmail.com \
--to=magfr56@hotmail.com \
--cc=gcc@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).