From: Michael Snyder <msnyder@redhat.com>
To: Jim Blandy <jimb@redhat.com>
Cc: Elena Zannoni <ezannoni@redhat.com>,
Michael Snyder <msnyder@cygnus.com>,
gdb-patches@sources.redhat.com
Subject: Re: [RFA] Add vector type flag to stabsread.c
Date: Wed, 08 May 2002 13:46:00 -0000 [thread overview]
Message-ID: <3CD98B7A.A6CCBDCD@redhat.com> (raw)
In-Reply-To: <npadrajs0e.fsf@zwingli.cygnus.com>
[-- Attachment #1: Type: text/plain, Size: 167 bytes --]
Jim Blandy wrote:
>
> Elena Zannoni <ezannoni@redhat.com> writes:
> > OK.
> > Should the stabs doc be updated? Who controls that?
>
> Yes. Us. :)
OK, how's this?
[-- Attachment #2: vector.patch --]
[-- Type: text/plain, Size: 958 bytes --]
2002-05-08 Michael Snyder <msnyder@redhat.com>
* stabs.texinfo (Attributes): Document new "vector" attribute.
Index: stabs.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/stabs.texinfo,v
retrieving revision 1.5
diff -p -r1.5 stabs.texinfo
*** stabs.texinfo 30 Dec 2001 06:25:16 -0000 1.5
--- stabs.texinfo 8 May 2002 20:36:35 -0000
*************** Indicate that this type is a string inst
*** 287,292 ****
--- 287,298 ----
or a bitstring instead of a set. It doesn't change the layout of the
data being represented, but does enable the debugger to know which type
it is.
+
+ @item V
+ Indicate that this type is a vector instead of an array. The only
+ major difference between vectors and arrays is that vectors are
+ passed by value instead of by reference (vector coprocessor extension).
+
@end table
All of this can make the string field quite long. All versions of GDB,
next prev parent reply other threads:[~2002-05-08 20:46 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
2002-05-07 19:19 ` Michael Snyder
2002-05-08 13:37 ` Jim Blandy
2002-05-08 13:46 ` Michael Snyder [this message]
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=3CD98B7A.A6CCBDCD@redhat.com \
--to=msnyder@redhat.com \
--cc=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