From: Jason Merrill <jason@redhat.com>
To: Patrick Palka <ppalka@redhat.com>, gcc-patches@gcc.gnu.org
Cc: nathan@acm.org
Subject: Re: [PATCH] c++/modules: stream TREE_UNAVAILABLE and LAMBDA_EXPR_REGEN_INFO
Date: Thu, 15 Feb 2024 16:15:33 -0500 [thread overview]
Message-ID: <aa829fb9-13bb-4d6c-b523-6b1eb0df11a7@redhat.com> (raw)
In-Reply-To: <20240215211110.340624-1-ppalka@redhat.com>
On 2/15/24 16:11, Patrick Palka wrote:
> Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look OK for
> trunk?
OK.
> -- >8 --
>
> gcc/cp/ChangeLog:
>
> * module.cc (trees_out::core_bools): Stream TREE_UNAVAILABLE.
> (trees_in::core_bools): Likewise.
> (trees_out::core_vals): Stream LAMBDA_EXPR_REGEN_INFO.
> (trees_in::core_vals): Likewise.
> ---
> gcc/cp/module.cc | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/gcc/cp/module.cc b/gcc/cp/module.cc
> index f769b3737ed..bd7de3f9156 100644
> --- a/gcc/cp/module.cc
> +++ b/gcc/cp/module.cc
> @@ -5370,6 +5370,7 @@ trees_out::core_bools (tree t, bits_out& bits)
> WB (t->base.u.bits.user_align);
> WB (t->base.u.bits.nameless_flag);
> WB (t->base.u.bits.atomic_flag);
> + WB (t->base.u.bits.unavailable_flag);
> break;
> }
>
> @@ -5560,6 +5561,7 @@ trees_in::core_bools (tree t, bits_in& bits)
> RB (t->base.u.bits.user_align);
> RB (t->base.u.bits.nameless_flag);
> RB (t->base.u.bits.atomic_flag);
> + RB (t->base.u.bits.unavailable_flag);
> break;
> }
>
> @@ -6353,6 +6355,7 @@ trees_out::core_vals (tree t)
> WT (((lang_tree_node *)t)->lambda_expression.capture_list);
> WT (((lang_tree_node *)t)->lambda_expression.this_capture);
> WT (((lang_tree_node *)t)->lambda_expression.extra_scope);
> + WT (((lang_tree_node *)t)->lambda_expression.regen_info);
> /* pending_proxies is a parse-time thing. */
> gcc_assert (!((lang_tree_node *)t)->lambda_expression.pending_proxies);
> if (state)
> @@ -6854,6 +6857,7 @@ trees_in::core_vals (tree t)
> RT (((lang_tree_node *)t)->lambda_expression.capture_list);
> RT (((lang_tree_node *)t)->lambda_expression.this_capture);
> RT (((lang_tree_node *)t)->lambda_expression.extra_scope);
> + RT (((lang_tree_node *)t)->lambda_expression.regen_info);
> /* lambda_expression.pending_proxies is NULL */
> ((lang_tree_node *)t)->lambda_expression.locus
> = state->read_location (*this);
prev parent reply other threads:[~2024-02-15 21:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 21:11 Patrick Palka
2024-02-15 21:15 ` Jason Merrill [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=aa829fb9-13bb-4d6c-b523-6b1eb0df11a7@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nathan@acm.org \
--cc=ppalka@redhat.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).