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++/98885] [modules] forward declaration of classes prevent them from being exported at the point of actual declaration Date: Fri, 24 Nov 2023 01:31:51 +0000 [thread overview] Message-ID: <bug-98885-4-M0JKI6GMoi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98885-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98885 --- Comment #11 from CVS 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:d89903ff29473e6e64f032ecee5c72d1584546dc commit r14-5808-gd89903ff29473e6e64f032ecee5c72d1584546dc Author: Nathaniel Shead <nathanieloshead@gmail.com> Date: Sun Nov 12 22:49:45 2023 +1100 c++: check mismatching exports for class tags [PR98885] Checks for exporting a declaration that was previously declared as not exported is implemented in 'duplicate_decls', but this doesn't handle declarations of classes. This patch adds these checks and slightly adjusts the associated error messages for clarity. PR c++/98885 gcc/cp/ChangeLog: * decl.cc (duplicate_decls): Adjust error message. (xref_tag): Adjust error message. Check exporting decl that is already declared as non-exporting. gcc/testsuite/ChangeLog: * g++.dg/modules/export-1.C: Adjust error messages. Remove xfails for working case. Add new test case. Signed-off-by: Nathaniel Shead <nathanieloshead@gmail.com>
next prev parent reply other threads:[~2023-11-24 1:31 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-29 11:26 [Bug c++/98885] New: " pilarlatiesa at gmail dot com 2021-01-29 13:08 ` [Bug c++/98885] " nathan at gcc dot gnu.org 2021-01-29 13:45 ` pilarlatiesa at gmail dot com 2021-01-29 13:51 ` nathan at gcc dot gnu.org 2021-01-29 14:21 ` pilarlatiesa at gmail dot com 2021-01-29 15:58 ` nathan at gcc dot gnu.org 2021-01-29 16:11 ` pilarlatiesa at gmail dot com 2021-01-29 16:51 ` nathan at gcc dot gnu.org 2021-01-30 9:34 ` pilarlatiesa at gmail dot com 2021-02-03 18:58 ` nathan at gcc dot gnu.org 2021-09-15 11:50 ` redi at gcc dot gnu.org 2023-11-24 1:31 ` cvs-commit at gcc dot gnu.org [this message] 2024-02-11 14:21 ` nshead at gcc dot gnu.org 2024-02-11 14:21 ` 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-98885-4-M0JKI6GMoi@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).