From: Claudio Bley <bley@cs.uni-magdeburg.de>
To: "Mateusz Kmiec" <mateusz.kmiec@tpg.pl>
Cc: <gcc-help@gcc.gnu.org>
Subject: Re: Problem with gcc 2.96 - wrong virtual function call
Date: Fri, 18 Jan 2002 09:29:00 -0000 [thread overview]
Message-ID: <15432.23443.602752.43671@wh2-19.st.uni-magdeburg.de> (raw)
In-Reply-To: <003701c1a040$e2d84560$8c05a8c0@krakow.tpg.pl>
>>>>> "Mateusz" == Mateusz Kmiec <mateusz.kmiec@tpg.pl> writes:
Mateusz> Hi, I have the following problem with gcc 2.96: I have an
Mateusz> application that is compiled with egcs-2.91.66 and works
Mateusz> on Red Hat 7.2. I am trying to change compiler from egcs
Mateusz> (egcs-2.91.66) to gcc (gcc version 2.96 20000731).
I suggest you use a real gcc release such as gcc 3.0.3 -- gcc 2.96 has
been the code name for the GCC 3.0 development branch; and there are
of course errors which probably are already fixed in the current
release.
Claudio
prev parent reply other threads:[~2002-01-18 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-18 8:55 Mateusz Kmiec
2002-01-18 9:29 ` Claudio Bley [this message]
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=15432.23443.602752.43671@wh2-19.st.uni-magdeburg.de \
--to=bley@cs.uni-magdeburg.de \
--cc=gcc-help@gcc.gnu.org \
--cc=mateusz.kmiec@tpg.pl \
/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).