From: Andrew Cagney <ac131313@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Rewrite "structs" testcase
Date: Thu, 06 Nov 2003 18:49:00 -0000 [thread overview]
Message-ID: <3FAA97AC.9020704@redhat.com> (raw)
In-Reply-To: <200311061733.hA6HXSWA004161@duracef.shout.net>
> I'm concerned about the use of "long long" in a test program.
> What if someone uses a non-gcc Ansi C compiler?
> But this doesn't look any worse than other tests, so okay.
>
> In structs.exp, line 22:
>
> # This file was written by Jeff Law. (law@cygnus.com)
>
> Add something like:
>
> # And rewritten by Andrew Cagney (cagney@redhat.com)
I'll just drop that.
> I got a lot of FAILS with the new tests.
> native i686-pc-linux-gnu, gdb HEAD, binutils 2.14.
>
> PASS FAIL
> gcc 2.95.3 -gdwarf-2 1086 138
> gcc 2.95.3 -gstabs+ 1122 102
> gcc 3.3.2 -gdwarf-2 1122 102
> gcc 3.3.2 -gstabs+ 1122 102
>
> I have put up a tarball:
>
> ftp://ftp.shout.net/pub/users/mec/gdb/2003-11-06-2.tar.gz
>
> There are a lot of duplicate test names too. It would be good
> to uniquify them.
Yes, working on it. I can't see a way to fix things like "run_to_main"
though.
> Not proofread yet because of so many FAIL results.
Looks like two problems:
(gdb) ptype foo1.a
type = tld
(gdb) FAIL: gdb.base/structs.exp: ptype foo1.a for 1tld
Some debug info prints "long double", some prints "tld". I've changed
whats printed to hopefully be something more robust ...
(gdb) FAIL: gdb.base/structs.exp: ptype foo1.a for 1tld
p/c fun1()
$1 = {a = 0x08044004c400000000000000}
Seems GDB and GCC disagree over how the i386 returns floating-point
values. My "this will always work" test has found a bug in GDB - cool.
Note that the tests do all pass for PPC.
I've also trimmed back the number of tests so that they are more focused.
I'll post a revision later today.
thanks,
Andrew
next prev parent reply other threads:[~2003-11-06 18:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-06 17:33 Michael Elizabeth Chastain
2003-11-06 18:49 ` Andrew Cagney [this message]
2003-11-06 21:38 ` Michael Snyder
-- strict thread matches above, loose matches on Subject: below --
2003-11-12 18:30 Michael Elizabeth Chastain
2003-11-12 18:13 Michael Elizabeth Chastain
2003-11-13 16:11 ` Andrew Cagney
2003-11-17 15:59 ` Andrew Cagney
2003-11-20 17:17 ` Andrew Cagney
2003-11-12 16:51 Michael Elizabeth Chastain
2003-11-08 1:05 Michael Elizabeth Chastain
2003-11-09 1:22 ` Andrew Cagney
2003-11-10 0:32 ` Michael Elizabeth Chastain
2003-11-11 22:28 ` Andrew Cagney
2003-11-06 20:44 Michael Elizabeth Chastain
2003-11-07 20:35 ` Andrew Cagney
2003-11-06 19:10 Michael Elizabeth Chastain
2003-11-06 20:22 ` Andrew Cagney
2003-11-05 22:17 Andrew Cagney
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=3FAA97AC.9020704@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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