From: Nathan Sidwell <nathan@acm.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [C++ PATCH] lang_decl selector & decomposition
Date: Mon, 05 Jun 2017 11:22:00 -0000 [thread overview]
Message-ID: <8506e680-f06d-d906-1917-65ba3ab13326@acm.org> (raw)
In-Reply-To: <20170605102826.GC2154@tucnak>
On 06/05/2017 06:28 AM, Jakub Jelinek wrote:
> So unless cxx_dup_lang_specific_decl or copy_decl or tsubst_decl
> clears the DECL_DECOMP_BASE for the short time before cp_finish_decomp
> is called, DECL_DECOMP_BASE will be "wrong" for a short time, but it
> shouldn't matter, nothing should be querying it in between. Setting
> it to NULL wouldn't be correct either anyway.
Ok, thanks for checking. That also explains why we can meet VAR_DECLs
that already have a decomp_lang_decl extension.
nathan
--
Nathan Sidwell
prev parent reply other threads:[~2017-06-05 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 17:05 Nathan Sidwell
2017-05-31 17:11 ` Jakub Jelinek
2017-05-31 17:18 ` Nathan Sidwell
2017-05-31 17:36 ` Jakub Jelinek
2017-06-05 11:13 ` Jakub Jelinek
2017-06-05 11:22 ` Nathan Sidwell [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=8506e680-f06d-d906-1917-65ba3ab13326@acm.org \
--to=nathan@acm.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@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).