From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com, Richard.Earnshaw@arm.com
Cc: gdb@sources.redhat.com
Subject: Re: A brief analysis of the arm-elf failures for gdb
Date: Tue, 25 Mar 2003 17:24:00 -0000 [thread overview]
Message-ID: <200303251724.h2PHOW630148@duracef.shout.net> (raw)
re> FAIL: gdb.base/ptype.exp: ptype t_char_array
re> FAIL: gdb.base/ptype.exp: ptype func_type
re>
re> Neither of the above types are emitted in dwarf2 debug formats by gcc if
re> they are not used. We need some data object with that type to make this
re> test useful.
I saw these as regressions with gcc HEAD. They PASSed with
gcc HEAD on 2003-02-27 and FAILed with gcc HEAD on 2003-03-15.
The tests PASSed with gcc 2.95.3, gcc 3.2.2, gcc gcc-3_2-branch,
and gcc gcc-3_3-branch.
drow> Definitely a test bug.
That's good news. So it looks like gcc HEAD has gotten sharper about
generating type definitions, exposing a latent problem in the test.
Michael C
next reply other threads:[~2003-03-25 17:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 17:24 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-25 16:48 Richard Earnshaw
2003-03-25 16:55 ` Daniel Jacobowitz
2003-03-25 16:55 ` Corinna Vinschen
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=200303251724.h2PHOW630148@duracef.shout.net \
--to=mec@shout.net \
--cc=Richard.Earnshaw@arm.com \
--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