public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109679] export using for functions does not work as specified Date: Sun, 07 Jan 2024 10:52:20 +0000 [thread overview] Message-ID: <bug-109679-4-eR4lcUhXjl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109679-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109679 --- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Nathaniel Shead <nshead@gcc.gnu.org>: https://gcc.gnu.org/g:63b531e6f8783e8624502d890dc422379de47a9a commit r14-6978-g63b531e6f8783e8624502d890dc422379de47a9a Author: Nathaniel Shead <nathanieloshead@gmail.com> Date: Wed Jan 3 15:29:51 2024 +1100 c++: Export usings referring to global module fragment [PR109679] This patch stops 'add_binding_entity' from ignoring all names in the global module fragment, since they should still be exported if named in an exported using-declaration. PR c++/109679 gcc/cp/ChangeLog: * module.cc (depset::hash::add_binding_entity): Don't skip names in the GMF if they've been exported with a using declaration. gcc/testsuite/ChangeLog: * g++.dg/modules/using-11.h: New test. * g++.dg/modules/using-11_a.C: New test. * g++.dg/modules/using-11_b.C: New test. Signed-off-by: Nathaniel Shead <nathanieloshead@gmail.com>
next prev parent reply other threads:[~2024-01-07 10:52 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-29 8:37 [Bug c++/109679] New: " nico at josuttis dot de 2023-04-29 21:38 ` [Bug c++/109679] " pinskia at gcc dot gnu.org 2023-05-02 14:33 ` redi at gcc dot gnu.org 2023-12-25 13:12 ` admin at hexadigm dot com 2024-01-07 10:52 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-27 10:21 ` nshead at gcc dot gnu.org 2024-01-27 10:28 ` 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-109679-4-eR4lcUhXjl@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).