Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jason Molenda <jason-swarelist@molenda.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com, jimb@redhat.com,
	kettenis@jive.nl, dpatel@apple.com
Subject: Re: RFA/doc-patch stabs reader:  Recognize language hint in SO stab
Date: Mon, 20 Sep 2004 19:28:00 -0000	[thread overview]
Message-ID: <20040920122812.A43212@molenda.com> (raw)
In-Reply-To: <7137-Fri06Aug2004115131+0300-eliz@gnu.org>; from eliz@gnu.org on Fri, Aug 06, 2004 at 11:51:32AM +0300

[-- Attachment #1: Type: text/plain, Size: 1335 bytes --]

On Fri, Aug 06, 2004 at 11:51:32AM +0300, Eli Zaretskii wrote:
> > From: Jason Molenda <jmolenda@apple.com>
> > Date: Thu, 5 Aug 2004 13:09:08 -0700
> > 
> > Eli, I added a table documenting these values to stabs.texinfo.  Do you 
> > think this is a correct use of a texinfo table?

[...]

> Therefore, if the indentation and the general formatting of @table is
> okay with you, I think the following will look better:
> 
>     +@table @asis
>     +@item @code{N_SO_AS} (0x1)
>     +Assembly language
> 
> etc., you get the point.  


Thanks for the feedback, Eli.  Attached is an updated patch to the
documentation.  The FSF has just accepted the generation of this
code, the original patch posted here:

http://gcc.gnu.org/ml/gcc-patches/2004-08/msg00917.html

And approved here:

http://gcc.gnu.org/ml/gcc-patches/2004-09/msg01572.html

So I'd like to get the documentation checked in to gdb, at least.
Can you approve this?  The patch goes through makeinfo and texi2html
without any warnings; the generated HTML looks fine.

Thanks.

Jason
(sending from my molenda.com acct instead of apple.com because of
irrelevant/uninteresting technical difficulties.)

2004-09-20  Jason Molenda  (jason-cl@molenda.com)

	* stabs.texinfo (Paths and Names of the Source Files): Document the
	meaning of values in the 'desc' field of a SO stab.

[-- Attachment #2: pa.txt --]
[-- Type: text/plain, Size: 1532 bytes --]

Index: stabs.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/stabs.texinfo,v
retrieving revision 1.15
diff -u -p -r1.15 stabs.texinfo
--- stabs.texinfo	14 Jun 2004 22:26:34 -0000	1.15
+++ stabs.texinfo	20 Sep 2004 19:21:10 -0000
@@ -422,9 +422,33 @@ file.  This information is contained in 
 value of the symbol is the start address of the portion of the
 text section corresponding to that file.
 
-With the Sun Solaris2 compiler, the desc field contains a
-source-language code.
-@c Do the debuggers use it?  What are the codes? -djm
+Some compilers use the desc field to indicate the language of the
+source file.  Sun's compilers started this usage, and the first
+constants are derived from their documentation.  Languages added
+by gcc/gdb start at 0x32 to avoid conflict with languages Sun may
+add in the future.  A desc field with a value 0 indicates that no
+language has been specified via this mechanism.
+
+@table @asis
+@item @code{N_SO_AS} (0x1)
+Assembly language
+@item @code{N_SO_C}  (0x2)
+K&R traditional C
+@item @code{N_SO_ANSI_C} (0x3)
+ANSI C
+@item @code{N_SO_CC}  (0x4)
+C++
+@item @code{N_SO_FORTRAN} (0x5)
+Fortran
+@item @code{N_SO_PASCAL} (0x6)
+Pascal
+@item @code{N_SO_FORTRAN90} (0x7)
+Fortran90
+@item @code{N_SO_OBJC} (0x32)
+Objective-C
+@item @code{N_SO_OBJCPLUS} (0x33)
+Objective-C++
+@end table
 
 Some compilers (for example, GCC2 and SunOS4 @file{/bin/cc}) also
 include the directory in which the source was compiled, in a second

  reply	other threads:[~2004-09-20 19:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-05 20:08 RFA/patch " Jason Molenda
2004-08-05 20:17 ` Jason Molenda
2004-08-05 20:55   ` Andrew Cagney
2004-08-24 20:45     ` Andrew Cagney
2004-08-25  1:05       ` Jason Molenda
2004-08-05 21:10   ` Michael Chastain
2004-08-06  8:54 ` Eli Zaretskii
2004-09-20 19:28   ` Jason Molenda [this message]
2004-09-21  3:43     ` RFA/doc-patch " Eli Zaretskii
2004-09-21 21:08       ` COMMITTED/doc-patch " Jason Molenda

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=20040920122812.A43212@molenda.com \
    --to=jason-swarelist@molenda.com \
    --cc=dpatel@apple.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@redhat.com \
    --cc=kettenis@jive.nl \
    /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