From: Corinna Vinschen <vinschen@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFA] Support for multiple calling conventions, patch 3/3: Use calling convention information to handle differnt ABIs on sh target
Date: Mon, 21 Apr 2008 20:20:00 -0000 [thread overview]
Message-ID: <20080421200051.GB23852@calimero.vinschen.de> (raw)
In-Reply-To: <uy7779epj.fsf@gnu.org>
On Apr 21 22:43, Eli Zaretskii wrote:
> > Date: Mon, 21 Apr 2008 17:30:08 +0200
> > From: Corinna Vinschen <vinschen@redhat.com>
> >
> > Is the following documentation patch ok?
>
> Yes, with comments:
>
> > +@cindex Set SH Calling convention
>
> All index entries should start with a lower-case letter, for
> consistency.
>
> > +In the @samp{gcc} setting, functions are called using the gcc calling
> ^^
> "With" is better than "in" here.
>
> Also, we use @value{NGCC} instead of literal "gcc" (this doesn't apply
> to @samp{gcc}, of course).
>
> > +convention. If the DWARF-2 information of the called function specifies
> > +that the function is following the Renesas calling convention, the function
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> "the function follows the Renesas calling convention"
>
> > +is called using the renesas calling convention. If the calling convention
> ^^^^^^^
> "renesas" or "Renesas"? we should be consistent.
>
> > +is set to @samp{renesas}, the Renesas calling convention is always used,
> > +regardless of the Dwarf-2 information. This can be used to override the
>
> "DWARF-2" or "Dwarf-2"?
>
> > +@item show sh calling-convention
> > +@cindex Show SH Calling convention
>
> Finally, please index each command (literally) with @kindex, as we do
> for all other commands.
Thanks for the review. Is that better?
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.483
diff -u -p -r1.483 gdb.texinfo
--- gdb.texinfo 20 Apr 2008 09:06:43 -0000 1.483
+++ gdb.texinfo 21 Apr 2008 20:00:14 -0000
@@ -15649,6 +15649,26 @@ commands:
@item regs
@kindex regs@r{, Super-H}
Show the values of all Super-H registers.
+
+@item set sh calling-convention @var{convention}
+@kindex set sh calling-convention @var{convention}
+@cindex set SH Calling convention
+Set the calling-convention used when calling functions from @value{GDBN}.
+Allowed values are @samp{gcc}, which is the default setting, and @samp{renesas}.
+With the @samp{gcc} setting, functions are called using the @value{NGCC} calling
+convention. If the DWARF-2 information of the called function specifies
+that the function follows the Renesas calling convention, the function
+is called using the Renesas calling convention. If the calling convention
+is set to @samp{renesas}, the Renesas calling convention is always used,
+regardless of the DWARF-2 information. This can be used to override the
+default of @samp{gcc} if debug information is missing, or the compiler
+does not emit the DWARF-2 calling convention entry for a function.
+
+@item show sh calling-convention
+@kindex show sh calling-convention
+@cindex show SH Calling convention
+Show the current calling convention setting.
+
@end table
Corinna
--
Corinna Vinschen
Cygwin Project Co-Leader
Red Hat
next prev parent reply other threads:[~2008-04-21 20:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 12:44 Corinna Vinschen
2008-04-17 16:36 ` Daniel Jacobowitz
2008-04-21 15:42 ` Corinna Vinschen
2008-04-21 18:18 ` Corinna Vinschen
2008-04-21 20:01 ` Eli Zaretskii
2008-04-21 20:23 ` Corinna Vinschen
2008-04-22 6:55 ` Eli Zaretskii
2008-04-21 20:01 ` Eli Zaretskii
2008-04-21 20:20 ` Corinna Vinschen [this message]
2008-04-22 6:30 ` Eli Zaretskii
2008-04-22 13:54 ` Corinna Vinschen
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=20080421200051.GB23852@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=gdb-patches@sourceware.org \
/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