Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb-patches@sources.redhat.com
Subject: [rfa/testsuite] ptype.exp: fix FAILs for unused types
Date: Wed, 26 Mar 2003 18:04:00 -0000	[thread overview]
Message-ID: <200303261804.h2QI4cG17022@duracef.shout.net> (raw)

This patch fixes two FAILs in gdb.base/ptype.exp with gcc HEAD
-gdwarf-2.

  gdb.base/ptype.exp: ptype t_char_array
  gdb.base/ptype.exp: ptype func_type

gdb.base/ptype.c typedef's some types but then does not actually use
them.  Recent versions of gcc HEAD with -gdwarf-2 optimize away the type
information.  So this patch simply uses the types.

Tested on my usual testbed: native i686-pc-linux-gnu with gcc v2 and v3,
-gdward-2 and -gstabs+.  I specifically checked that it fixes the
FAILs associated with gcc HEAD.

OK to commit?

Michael C

2003-03-26  Michael Chastain  <mec@shout.net>

	* gdb.base/ptype.exp: Actually use some typedef'd types.

Index: ptype.c
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/ptype.c,v
retrieving revision 1.2
diff -u -r1.2 ptype.c
--- ptype.c	21 Feb 2002 20:34:16 -0000	1.2
+++ ptype.c	26 Mar 2003 17:39:21 -0000
@@ -59,6 +59,7 @@
 
 /* PR 3742 */
 typedef char t_char_array[];
+t_char_array *pv_char_array;
 
 /**** pointers *******/
 
@@ -236,6 +237,8 @@
 int (*xptr) (int (*) (), int (*) (void), int);
 int (*(*ffptr) (char)) (short);
 int (*(*(*fffptr) (char)) (short)) (long);
+
+func_type v_func_type;
 
 /* Here are the sort of stabs we expect to see for the above:
 


             reply	other threads:[~2003-03-26 18:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-26 18:04 Michael Elizabeth Chastain [this message]
2003-03-26 20:14 ` Daniel Jacobowitz
2003-03-26 22:11 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=200303261804.h2QI4cG17022@duracef.shout.net \
    --to=mec@shout.net \
    --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