public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Xi Ruoyao <ryxi@stu.xidian.edu.cn>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 1/5] Move char_type_p prototype into c-common.h
Date: Fri, 28 Apr 2017 20:28:00 -0000	[thread overview]
Message-ID: <8dee2e55-cf9a-e1e1-a144-14654ab01623@redhat.com> (raw)
In-Reply-To: <1487761260.2882.64.camel@stu.xidian.edu.cn>

On 02/22/2017 04:01 AM, Xi Ruoyao wrote:
> This patch moves prototype of char_type_p into c-common.h, so we can
> use it in c-family/*.
> 
> gcc/ChangeLog:
> 
> 2017-02-22  Xi Ruoyao  <ryxi@stu.xidian.edu.cn>
> 
> 	* c-family/c-common.h (char_type_p): New prototype
> 	* c/c-typeck.c (char_type_p): Make the function extern
> 	* cp/cp-tree.h (char_type_p): Remove prototype
> 	* cp/tree.c (char_type_p): Change the return type to bool
This is OK for the trunk once all 5 patches are approved.

jeff

      reply	other threads:[~2017-04-28 20:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22 11:01 Xi Ruoyao
2017-04-28 20:28 ` Jeff Law [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=8dee2e55-cf9a-e1e1-a144-14654ab01623@redhat.com \
    --to=law@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ryxi@stu.xidian.edu.cn \
    /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).