From: Jakub Jelinek <jakub@redhat.com>
To: Nathan Sidwell <nathan@acm.org>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [C++ PATCH] lang_decl selector & decomposition
Date: Wed, 31 May 2017 17:36:00 -0000 [thread overview]
Message-ID: <20170531171836.GD24023@tucnak> (raw)
In-Reply-To: <1dae7652-350f-fdc1-fa12-270c83644dac@acm.org>
On Wed, May 31, 2017 at 01:16:36PM -0400, Nathan Sidwell wrote:
> On 05/31/2017 01:05 PM, Jakub Jelinek wrote:
>
> > That is weird, that sounds like a bug somewhere? Which testcase is it on?
>
> I think decomp25 & decomp7 & 8 (sorry, can't recall full name).
> I discovered them because my first attempt had an assert that the incoming
> base was the same as the stored one, for the already-converted case.
>
> It wasn't the case of turning a NULL into non-NULL.
Even that shouldn't happen. NULL should be only for the base declaration,
i.e. the underlying artificial var, non-NULL should be set on the VAR_DECLs
for the user identifiers and should point to the underlying artificial var.
Jakub
next prev parent reply other threads:[~2017-05-31 17:18 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 [this message]
2017-06-05 11:13 ` Jakub Jelinek
2017-06-05 11:22 ` Nathan Sidwell
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=20170531171836.GD24023@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nathan@acm.org \
/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).