From: Eli Zaretskii <eliz@gnu.org>
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:01:00 -0000 [thread overview]
Message-ID: <uy7779epj.fsf@gnu.org> (raw)
In-Reply-To: <20080421153008.GV23852@calimero.vinschen.de>
> 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.
next prev parent reply other threads:[~2008-04-21 19:43 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 [this message]
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=uy7779epj.fsf@gnu.org \
--to=eliz@gnu.org \
--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