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] New: NSDMI deferred parse
Date: Fri, 03 Apr 2020 17:36:52 +0000	[thread overview]
Message-ID: <bug-94476-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94476

            Bug ID: 94476
           Summary: NSDMI deferred parse
           Product: gcc
           Version: 10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: nathan at gcc dot gnu.org
  Target Milestone: ---

This code, extracted from <filesystem> leaves an unparsed NSDMI for _M_type. 
That kills the module streamer, which doesn't expect to meet such things. 
Bizarrely, removing either the 'signed char' underlying type, the ctor
declaration, or the _M_path field removes the problem.  Not sure if the
non-module compiler copes?

enum class file_type : signed char { none = 0 };

class directory_entry
{
public:
  directory_entry(int);

  int _M_path;

  file_type _M_type = file_type::none;
};

             reply	other threads:[~2020-04-03 17:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03 17:36 nathan at gcc dot gnu.org [this message]
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
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@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).