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++/99000] [modules] declaration std::__copy_move_a2 conflicts with import
Date: Mon, 08 Feb 2021 20:24:47 +0000 [thread overview]
Message-ID: <bug-99000-4-3wEeN3OBfZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99000-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99000
Nathan Sidwell <nathan at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |SUSPENDED
Last reconfirmed| |2021-02-08
Ever confirmed|0 |1
--- Comment #1 from Nathan Sidwell <nathan at gcc dot gnu.org> ---
You're hitting this:
@emph{G++'s modules support is not complete.} Other than bugs, the
known missing pieces are:
....
@item Textual merging of reachable GM entities
Entities may be multiply defined across different header-units.
These must be de-duplicated, and this is implemented across imports,
or when an import redefines a textually-defined entity. However the
reverse is not implemented---textually redefining an entity that has
been defined in an imported header-unit. A redefinition error is
emitted.
next prev parent reply other threads:[~2021-02-08 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 11:08 [Bug c++/99000] New: " boris at kolpackov dot net
2021-02-08 20:24 ` nathan at gcc dot gnu.org [this message]
2021-02-09 14:27 ` [Bug c++/99000] " boris at kolpackov dot net
2024-03-13 17:53 ` 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-99000-4-3wEeN3OBfZ@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).