public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/114600] [14 Regression] [modules] redefinition errors when using certain std headers in GMF Date: Fri, 05 Apr 2024 13:33:34 +0000 [thread overview] Message-ID: <bug-114600-4-M2V6b9CIUD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114600-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114600 --- Comment #5 from Patrick Palka <ppalka at gcc dot gnu.org> --- (In reply to Nathaniel Shead from comment #4) > In general we don't yet implement merging of textual redefinitions; I guess > this ultimately falls under that, but I'm not sure we have a dedicated bug > report for that yet? Maybe PR99000. Makes sense. > I'm not yet sure exactly why my patch caused this to start failing though; > it sounds like it's exporting some using-decls even though they aren't > directly exported, which I suppose is still a bug in its own right. Hmm, should the check added to add_binding_entity flags & (WMB_Using | WMB_Export) instead be (flags & WMB_Using) && (flags & WMB_Export) ?
next prev parent reply other threads:[~2024-04-05 13:33 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-05 10:07 [Bug c++/114600] New: " m.cencora at gmail dot com 2024-04-05 10:07 ` [Bug c++/114600] " m.cencora at gmail dot com 2024-04-05 12:55 ` [Bug c++/114600] [14 Regression] " ppalka at gcc dot gnu.org 2024-04-05 12:58 ` ppalka at gcc dot gnu.org 2024-04-05 13:10 ` nshead at gcc dot gnu.org 2024-04-05 13:33 ` ppalka at gcc dot gnu.org [this message] 2024-04-10 13:24 ` nshead at gcc dot gnu.org 2024-04-10 14:27 ` m.cencora at gmail dot com 2024-04-10 15:41 ` redi at gcc dot gnu.org 2024-04-10 20:55 ` m.cencora at gmail dot com 2024-04-10 21:03 ` m.cencora at gmail dot com 2024-04-15 8:26 ` cvs-commit at gcc dot gnu.org 2024-04-24 13:46 ` ppalka at gcc dot gnu.org 2024-04-24 13:50 ` 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-114600-4-M2V6b9CIUD@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).