From: Richard Biener <richard.guenther@gmail.com>
To: Qing Zhao <qing.zhao@oracle.com>
Cc: David Malcolm <dmalcolm@redhat.com>,
gcc Patches <gcc-patches@gcc.gnu.org>,
bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
Subject: Re: [PATCH][Preprocessor][Version 3]patch to fix PR 90581
Date: Fri, 07 Jun 2019 08:26:00 -0000 [thread overview]
Message-ID: <CAFiYyc1j=eHGwzQdVE8bPJ=vhCizYJpNzY5+QYDMGxLxuGHT6g@mail.gmail.com> (raw)
In-Reply-To: <361C1CA3-836B-4188-893E-46DB609B654D@oracle.com>
On Mon, Jun 3, 2019 at 6:46 PM Qing Zhao <qing.zhao@oracle.com> wrote:
>
> Hi,
>
> this is the 3rd version of the patch, which fixed the issues Paolo raised in the previous email.
>
> Okay for trunk?
OK.
Thanks,
Richard.
> thanks.
>
> gcc/ChangeLog:
>
> 2019-06-03 qing zhao <qing.zhao@oracle.com>
>
> * doc/cppopts.texi: Add document for -fmax-include-depth.
> * doc/invoke.texi (Preprocessor Options): List -fmax-include-depth.
>
> libcpp/ChangeLog:
>
> 2019-06-03 qing zhao <qing.zhao@oracle.com>
>
> * directives.c (do_include_common): Replace CPP_STACK_MAX with
> CPP_OPTION (pfile, max_include_depth).
> * include/cpplib.h (struct cpp_options): Add new field
> max_include_depth.
> * init.c (cpp_create_reader): Initiate new field max_include_depth.
> * internal.h: Delete CPP_STACK_MAX.
>
> gcc/c-family/ChangeLog:
>
> 2019-06-03 qing zhao <qing.zhao@oracle.com>
>
> * c-opts.c (c_common_handle_option): Handle -fmax-include-depth.
> * c.opt: Add new option -fmax-include-depth.
>
> gcc/testsuite/ChangeLog:
>
> 2019-06-03 qing zhao <qing.zhao@oracle.com>
>
> * c-c++-common/cpp/fmax-include-depth-1a.h: New test.
> * c-c++-common/cpp/fmax-include-depth-1b.h: New test.
> * c-c++-common/cpp/fmax-include-depth.c: New test.
>
>
>
>
prev parent reply other threads:[~2019-06-07 8:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 16:26 [PATCH][Preprocessor]patch " Qing Zhao
2019-05-30 19:20 ` Bernhard Reutner-Fischer
2019-05-30 20:35 ` Qing Zhao
2019-05-30 20:42 ` David Malcolm
2019-05-30 20:46 ` Qing Zhao
2019-05-30 20:49 ` David Malcolm
2019-05-30 21:05 ` Qing Zhao
2019-05-31 9:01 ` Richard Biener
2019-06-03 14:49 ` [PATCH][Preprocessor][Version 2]patch " Qing Zhao
2019-06-03 15:03 ` Paolo Carlini
2019-06-03 16:42 ` [PATCH][Preprocessor][Version 3]patch " Qing Zhao
2019-06-03 16:46 ` Qing Zhao
2019-06-07 8:26 ` Richard Biener [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='CAFiYyc1j=eHGwzQdVE8bPJ=vhCizYJpNzY5+QYDMGxLxuGHT6g@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=qing.zhao@oracle.com \
--cc=rep.dot.nop@gmail.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).