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++/113038] [14 regression] Excess errors for g++.dg/modules/hello-1_b.C  after r14-6569-gfe54b57728c09a
Date: Fri, 12 Jan 2024 17:16:56 +0000	[thread overview]
Message-ID: <bug-113038-4-xkCt5AMCyo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113038-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113038

--- Comment #3 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Jason Merrill <jason@gcc.gnu.org>:

https://gcc.gnu.org/g:27521a2f4f7b859d5656e5bdd69d3f759ea4c23a

commit r14-7213-g27521a2f4f7b859d5656e5bdd69d3f759ea4c23a
Author: Jason Merrill <jason@redhat.com>
Date:   Mon Dec 18 15:47:10 2023 -0500

    c++: __class_type_info and modules [PR113038]

    Doing a dynamic_cast in both TUs broke because we were declaring a new
    __class_type_info in _b that conflicted with the one imported in the global
    module from _a.  It seems clear to me that any new class declaration in
    the global module should merge with an imported definition, but for GCC 14
    let's just fix this for the specific case of __class_type_info.

            PR c++/113038

    gcc/cp/ChangeLog:

            * name-lookup.cc (lookup_elaborated_type): Look for bindings
            in the global namespace in the ABI namespace.

    gcc/testsuite/ChangeLog:

            * g++.dg/modules/pr106304_b.C: Add dynamic_cast.

  parent reply	other threads:[~2024-01-12 17:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-15 22:58 [Bug other/113038] New: " seurer at gcc dot gnu.org
2023-12-16  9:09 ` [Bug c++/113038] " redi at gcc dot gnu.org
2023-12-16  9:09 ` redi at gcc dot gnu.org
2023-12-18  8:07 ` rguenth at gcc dot gnu.org
2024-01-11 15:10 ` jason at gcc dot gnu.org
2024-01-12 17:16 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-12 17:20 ` jason at gcc dot gnu.org
2024-01-12 17:21 ` jason at gcc dot gnu.org
2024-01-12 17:22 ` jason at gcc dot gnu.org
2024-01-13  1:48 ` hp at gcc dot gnu.org
2024-01-13 18:59 ` danglin at gcc dot gnu.org
2024-01-19  0:55 ` hp at gcc dot gnu.org
2024-01-19  2:32 ` hp at gcc dot gnu.org
2024-01-19 18:36 ` pinskia 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-113038-4-xkCt5AMCyo@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).