public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nathan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/94476] NSDMI deferred parse
Date: Fri, 03 Apr 2020 19:41:10 +0000 [thread overview]
Message-ID: <bug-94476-4-ORkEq5cByC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94476-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94476
Nathan Sidwell <nathan at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P4
Status|ASSIGNED |SUSPENDED
--- Comment #1 from Nathan Sidwell <nathan at gcc dot gnu.org> ---
this caused by the as_base creation code copying the field_decl, deferred NSDMI
and all. That doesn't affect trunk's behaviour so is harmless. But we should
get it right. Fixed on modules 2c6b4bd9ab0
Can push to trunk once stage 1 opens up.
PR c++/94476
gcc/cp/
* class.c (layout_class_type): Zap NSDMI of as_base fields.
gcc/testsuite/
* g++.dg/modules/nsdmi-2.C: New.
next prev parent reply other threads:[~2020-04-03 19:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 17:36 [Bug c++/94476] New: " nathan at gcc dot gnu.org
2020-04-03 17:37 ` [Bug c++/94476] " nathan at gcc dot gnu.org
2020-04-03 19:41 ` nathan at gcc dot gnu.org [this message]
2024-03-07 19:56 ` ppalka at gcc dot gnu.org
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=bug-94476-4-ORkEq5cByC@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).