From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com
Cc: gdb@sources.redhat.com
Subject: Re: Another "ptype B" validity question
Date: Tue, 03 Dec 2002 08:41:00 -0000 [thread overview]
Message-ID: <200212031641.gB3Gfax31066@duracef.shout.net> (raw)
Daniel J writes:
> It is _not_ acceptable. I thought I'd gotten most of these but
> obviously I've missed some. Please do file a bug.
Okay, I will do that.
With gdb HEAD and binutils 2.13.1 and stabs+:
gcc 3.2.1 48 FAIL, 81 XFAIL
gcc HEAD 114 FAIL, 80 XFAIL
It's going to be a couple of bug reports. :(
gcc HEAD with dwarf-2 is fine compared to gcc 3.2.1 with dwarf-2.
Here is a good table for you:
http://www.shout.net/~mec/sunday/2002-11-25/difference/compare-by-gcc-17.html
Michael C
next reply other threads:[~2002-12-03 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 8:41 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-04 10:20 Michael Elizabeth Chastain
2002-12-03 7:57 Michael Elizabeth Chastain
2002-12-03 8:08 ` Gabriel Dos Reis
2002-12-03 8:27 ` Daniel Jacobowitz
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=200212031641.gB3Gfax31066@duracef.shout.net \
--to=mec@shout.net \
--cc=drow@mvista.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