public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/102345] [modules] Cannot define a module interface unit for anything in <new> Date: Wed, 15 Sep 2021 11:22:17 +0000 [thread overview] Message-ID: <bug-102345-4-ZR345xPRqL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102345-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102345 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2021-09-15 Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> --- The first problem is demonstrated by: export module newdel; namespace std { using size_t = decltype(sizeof(0)); enum class align_val_t : size_t; } new.cc:5:28: error: cannot define ‘enum class std::align_val_t’ in different module 5 | enum class align_val_t : size_t; | ^~~~~~ <built-in>: note: declared here new.cc:5: confused by earlier errors, bailing out Preprocessed source stored into /tmp/cc4qIyxE.out file, please attach this to your bugreport. This is fixed by Jason's patch in PR 48396 comment 4.
next prev parent reply other threads:[~2021-09-15 11:22 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-15 11:21 [Bug c++/102345] New: " redi at gcc dot gnu.org 2021-09-15 11:22 ` redi at gcc dot gnu.org [this message] 2021-09-15 11:24 ` [Bug c++/102345] " redi at gcc dot gnu.org 2021-09-15 11:24 ` redi at gcc dot gnu.org 2024-03-13 18:26 ` ppalka at gcc dot gnu.org 2024-05-25 0:32 ` cvs-commit at gcc dot gnu.org 2024-05-25 0:34 ` nshead 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-102345-4-ZR345xPRqL@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: linkBe 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).