public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ensadc at mailnesia dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/99682] New: [modules] Module implementation unit is unable to indirectly import its corresponding interface unit Date: Sat, 20 Mar 2021 15:00:56 +0000 [thread overview] Message-ID: <bug-99682-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99682 Bug ID: 99682 Summary: [modules] Module implementation unit is unable to indirectly import its corresponding interface unit Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ensadc at mailnesia dot com Target Milestone: --- $ cat src/foo.cpp export module foo; $ cat src/bar.cpp export module bar; import foo; $ cat src/foo-impl.cpp module foo; import bar; $ g++ -fmodules-ts -c src/foo.cpp $ g++ -fmodules-ts -c src/bar.cpp $ g++ -fmodules-ts -c src/foo-impl.cpp In module imported at src/foo-impl.cpp:2:1: bar: error: cannot import module in its own purview In module imported at src/foo-impl.cpp:1:1: foo: note: module ‘foo’ declared here In module imported at src/foo-impl.cpp:2:1: bar: error: failed to read compiled module: Bad import dependency bar: note: compiled module file is ‘gcm.cache/bar.gcm’ bar: fatal error: returning to the gate for a mechanical issue compilation terminated. ==== AFAIK, although a module implementation unit cannot *directly* imports its module interface unit (http://eel.is/c++draft/module.import#9 ), *indirect* import should not be prohibited (and should probably be a no-op, because the primary module interface unit has been imported by `module foo;`). MSVC compiles this test case without any errors.
reply other threads:[~2021-03-20 15:00 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-99682-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: 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).