public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Sandiford <richard.sandiford@arm.com>
To: Hu Jiangping <hujiangping@cn.fujitsu.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] doc: add return type for functions in gimple.texi
Date: Tue, 18 Aug 2020 17:48:11 +0100	[thread overview]
Message-ID: <mpteeo3oq7o.fsf@arm.com> (raw)
In-Reply-To: <20200817024431.2106-1-hujiangping@cn.fujitsu.com> (Hu Jiangping's message of "Mon, 17 Aug 2020 10:44:31 +0800")

Hu Jiangping <hujiangping@cn.fujitsu.com> writes:
> This patch add the return type for some functions in gimple.texi,
> to make the context unified. OK for trunk?

LGTM, thanks.  Pushed to master.

Richard

>
> Tested on x86_64.
>
> Regards!
> Hujp
>
> ---
>  gcc/doc/gimple.texi | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/gcc/doc/gimple.texi b/gcc/doc/gimple.texi
> index 5e0fc2e0dc5..f01c3083835 100644
> --- a/gcc/doc/gimple.texi
> +++ b/gcc/doc/gimple.texi
> @@ -831,17 +831,17 @@ expression to a variable.
>  Return true if g is any of the OpenMP codes.
>  @end deftypefn
>  
> -@deftypefn {GIMPLE function} gimple_debug_begin_stmt_p (gimple g)
> +@deftypefn {GIMPLE function} bool gimple_debug_begin_stmt_p (gimple g)
>  Return true if g is a @code{GIMPLE_DEBUG} that marks the beginning of
>  a source statement.
>  @end deftypefn
>  
> -@deftypefn {GIMPLE function} gimple_debug_inline_entry_p (gimple g)
> +@deftypefn {GIMPLE function} bool gimple_debug_inline_entry_p (gimple g)
>  Return true if g is a @code{GIMPLE_DEBUG} that marks the entry
>  point of an inlined function.
>  @end deftypefn
>  
> -@deftypefn {GIMPLE function} gimple_debug_nonbind_marker_p (gimple g)
> +@deftypefn {GIMPLE function} bool gimple_debug_nonbind_marker_p (gimple g)
>  Return true if g is a @code{GIMPLE_DEBUG} that marks a program location,
>  without any variable binding.
>  @end deftypefn

      reply	other threads:[~2020-08-18 16:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-17  2:44 Hu Jiangping
2020-08-18 16:48 ` Richard Sandiford [this message]

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=mpteeo3oq7o.fsf@arm.com \
    --to=richard.sandiford@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hujiangping@cn.fujitsu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).