Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Michael Snyder <msnyder@cygnus.com>
Cc: gdb-patches@sources.redhat.com, jimb@redhat.com
Subject: Re: [RFA] Add vector type flag to stabsread.c
Date: Tue, 07 May 2002 19:09:00 -0000	[thread overview]
Message-ID: <15576.35004.495092.847403@localhost.redhat.com> (raw)
In-Reply-To: <200205062331.g46NV4k26237@reddwarf.sfbay.redhat.com>

Michael Snyder writes:
 > 


OK.
Should the stabs doc be updated? Who controls that?

Elena


 > This patch does to stabs what Elena has recently done for dwarf --
 > add an attribute extension that allows an array type to be tagged
 > as a vector.  Knowing that it is a vector, GDB can then modify the
 > way the object is passed as a function argument.
 > 
 > The syntax for stabs will be to add the string "@V;" in front of
 > the "ar" declaration.  The "@" attribute extension already exists
 > in stabs -- we're just adding a new instance of it.
 > 
 > The GCC patch for this extension should be coming out today.
 > 
 > 2002-05-06  Michael Snyder  <msnyder@redhat.com>
 > 
 > 	* stabsread.c (read_type): Add recognition for new attribute:
 > 	"@V;" means that an array type is actually a vector.
 > 	This is analogous to the vector flag that's been added to dwarf2.
 > 
 > Index: stabsread.c
 > ===================================================================
 > RCS file: /cvs/src/src/gdb/stabsread.c,v
 > retrieving revision 1.32
 > diff -p -r1.32 stabsread.c
 > *** stabsread.c	4 May 2002 00:21:09 -0000	1.32
 > --- stabsread.c	6 May 2002 23:39:00 -0000
 > *************** define_symbol (CORE_ADDR valu, char *str
 > *** 1904,1909 ****
 > --- 1904,1910 ----
 >         break;
 >   
 >       case 't':
 > +       /* Typedef */
 >         SYMBOL_TYPE (sym) = read_type (&p, objfile);
 >   
 >         /* For a nameless type, we don't want a create a symbol, thus we
 > *************** read_type (register char **pp, struct ob
 > *** 2359,2364 ****
 > --- 2360,2368 ----
 >     /* Used to distinguish string and bitstring from char-array and set. */
 >     int is_string = 0;
 >   
 > +   /* Used to distinguish vector from array. */
 > +   int is_vector = 0;
 > + 
 >     /* Read type number if present.  The type number may be omitted.
 >        for instance in a two-dimensional array declared with type
 >        "ar1;1;10;ar1;1;10;4".  */
 > *************** again:
 > *** 2574,2580 ****
 >            forward-referenced), and we must change it to a pointer, function,
 >            reference, or whatever, *in-place*.  */
 >   
 > !     case '*':
 >         type1 = read_type (pp, objfile);
 >         type = make_pointer_type (type1, dbx_lookup_type (typenums));
 >         break;
 > --- 2578,2584 ----
 >            forward-referenced), and we must change it to a pointer, function,
 >            reference, or whatever, *in-place*.  */
 >   
 > !     case '*':			/* Pointer to another type */
 >         type1 = read_type (pp, objfile);
 >         type = make_pointer_type (type1, dbx_lookup_type (typenums));
 >         break;
 > *************** again:
 > *** 2732,2747 ****
 >   
 >   	  switch (*attr)
 >   	    {
 > ! 	    case 's':
 >   	      type_size = atoi (attr + 1);
 >   	      if (type_size <= 0)
 >   		type_size = -1;
 >   	      break;
 >   
 > ! 	    case 'S':
 >   	      is_string = 1;
 >   	      break;
 >   
 >   	    default:
 >   	      /* Ignore unrecognized type attributes, so future compilers
 >   	         can invent new ones.  */
 > --- 2736,2757 ----
 >   
 >   	  switch (*attr)
 >   	    {
 > ! 	    case 's':		/* Size attribute */
 >   	      type_size = atoi (attr + 1);
 >   	      if (type_size <= 0)
 >   		type_size = -1;
 >   	      break;
 >   
 > ! 	    case 'S':		/* String attribute */
 > ! 	      /* FIXME: check to see if following type is array? */
 >   	      is_string = 1;
 >   	      break;
 >   
 > + 	    case 'V':		/* Vector attribute */
 > + 	      /* FIXME: check to see if following type is array? */
 > + 	      is_vector = 1;
 > + 	      break;
 > + 
 >   	    default:
 >   	      /* Ignore unrecognized type attributes, so future compilers
 >   	         can invent new ones.  */
 > *************** again:
 > *** 2844,2852 ****
 >         type = read_array_type (pp, type, objfile);
 >         if (is_string)
 >   	TYPE_CODE (type) = TYPE_CODE_STRING;
 >         break;
 >   
 > !     case 'S':
 >         type1 = read_type (pp, objfile);
 >         type = create_set_type ((struct type *) NULL, type1);
 >         if (is_string)
 > --- 2854,2864 ----
 >         type = read_array_type (pp, type, objfile);
 >         if (is_string)
 >   	TYPE_CODE (type) = TYPE_CODE_STRING;
 > +       if (is_vector)
 > + 	TYPE_FLAGS (type) |= TYPE_FLAG_VECTOR;
 >         break;
 >   
 > !     case 'S':			/* Set or bitstring  type */
 >         type1 = read_type (pp, objfile);
 >         type = create_set_type ((struct type *) NULL, type1);
 >         if (is_string)


  reply	other threads:[~2002-05-08  2:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-06 16:44 Michael Snyder
2002-05-07 19:09 ` Elena Zannoni [this message]
2002-05-07 19:19   ` Michael Snyder
2002-05-08 13:37   ` Jim Blandy
2002-05-08 13:46     ` Michael Snyder
2002-05-08 21:44       ` Eli Zaretskii
2002-05-09 11:13         ` Michael Snyder
2002-05-09 11:12   ` Michael Snyder

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=15576.35004.495092.847403@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@redhat.com \
    --cc=msnyder@cygnus.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