From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Rewrite "structs" testcase
Date: Thu, 06 Nov 2003 17:33:00 -0000 [thread overview]
Message-ID: <200311061733.hA6HXSWA004161@duracef.shout.net> (raw)
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 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.
Not proofread yet because of so many FAIL results.
Michael C
2003-11-05 Andrew Cagney <cagney@redhat.com>
* gdb.base/structs.exp: Update copyright. Rewrite.
* gdb.base/structs.c: Update copyright. Rewrite.
next reply other threads:[~2003-11-06 17:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-06 17:33 Michael Elizabeth Chastain [this message]
2003-11-06 18:49 ` Andrew Cagney
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=200311061733.hA6HXSWA004161@duracef.shout.net \
--to=mec@shout.net \
--cc=ac131313@redhat.com \
--cc=gdb-patches@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