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 15:42:00 -0000 [thread overview]
Message-ID: <20080421153008.GV23852@calimero.vinschen.de> (raw)
In-Reply-To: <20080417162802.GI17488@caradoc.them.org>
On Apr 17 12:28, Daniel Jacobowitz wrote:
> On Tue, Apr 15, 2008 at 01:58:42PM +0200, Corinna Vinschen wrote:
> > Ok to apply?
>
> This is OK with two changes. One is that Renesas should always be
> capitalized in comments. The other is that each new CLI command
> needs to be added to the manual, probably in the "Super-H" node.
> And it should probably get a NEWS entry too.
Is the following documentation patch ok?
Thanks,
Corinna
Index: doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.483
diff -u -p -r1.483 gdb.texinfo
--- doc/gdb.texinfo 20 Apr 2008 09:06:43 -0000 1.483
+++ doc/gdb.texinfo 21 Apr 2008 15:29:53 -0000
@@ -15649,6 +15649,24 @@ commands:
@item regs
@kindex regs@r{, Super-H}
Show the values of all Super-H registers.
+
+@item 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}.
+In the @samp{gcc} setting, functions are called using the gcc calling
+convention. If the DWARF-2 information of the called function specifies
+that the function is following 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
+@cindex Show SH Calling convention
+Show the current calling convention setting.
+
@end table
--
Corinna Vinschen
Cygwin Project Co-Leader
Red Hat
next prev parent reply other threads:[~2008-04-21 15:30 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 [this message]
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
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=20080421153008.GV23852@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