From: Andrew Cagney <ac131313@cygnus.com>
To: Michael Elizabeth Chastain <chastain@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: C++ FAIL counts and the effect of demangler fix
Date: Wed, 14 Feb 2001 07:31:00 -0000 [thread overview]
Message-ID: <3A8AA3D2.22B3CF9B@cygnus.com> (raw)
In-Reply-To: <200102140806.AAA28150@bosch.cygnus.com>
Michael,
Can you elaborate? The numbers look really intersting however, to me
(someone that has avoided C++ since cfront 1.2) they are meaningless.
Why is there the divergence, for instance - where is it comming from.
> Column #4 is /usr/bin/gcc (gcc 2.96), which uses v2 abi, + FSF CVS gdb
> (2001-02-12). This is the baseline that we have to get back to. [Hmmm,
> ovldbreak.exp was working with v2 abi compilers on 2001-01-28 when I
> checked it in. I have to look into that].
BTW, we don't have to get back to anything. As far as I know, the
failures are being caused by an unlreased version of GCC that has
changed its mangler ABI in some incompatible way. It would be nice if
the problems were resolved, however, they are _NOT_ a 5.1 release
criteria so not especially high on my radar. 5.1 needs to work with
real compilers installed on real machines.
enjoy,
Andrew
next prev parent reply other threads:[~2001-02-14 7:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-14 0:06 Michael Elizabeth Chastain
2001-02-14 7:31 ` Andrew Cagney [this message]
2001-02-14 8:28 ` Daniel Berlin
2001-02-14 8:49 Michael Elizabeth Chastain
2001-02-15 10:27 ` Andrew Cagney
2001-02-15 13:46 ` Per Bothner
2001-02-15 15:06 ` Andrew Cagney
2001-02-15 15:14 ` Per Bothner
2001-02-15 23:35 ` Eli Zaretskii
2001-02-16 0:58 ` Daniel Berlin
2001-02-16 2:32 ` Eli Zaretskii
2001-02-14 8:52 Michael Elizabeth Chastain
2001-02-14 10:06 ` Daniel Berlin
2001-02-14 10:24 Michael Elizabeth Chastain
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=3A8AA3D2.22B3CF9B@cygnus.com \
--to=ac131313@cygnus.com \
--cc=chastain@cygnus.com \
--cc=gdb@sources.redhat.com \
/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