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++/49387] t.cxx:140: error: too many initializers for ‘const __class_type_info_pseudo’ Date: Fri, 29 Apr 2022 03:00:51 +0000 [thread overview] Message-ID: <bug-49387-4-N1SK4IvoED@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49387-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49387 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:97b30a399ef561f6f37a2c08c830fdf3141bb504 commit r13-24-g97b30a399ef561f6f37a2c08c830fdf3141bb504 Author: Jason Merrill <jason@redhat.com> Date: Fri Apr 15 00:11:00 2022 -0400 c++: typeid and instantiation [PR102651] PR49387 was a problem with initially asking for a typeid for a class template specialization before it was complete, and later actually filling in the descriptor when the class was complete, and thus disagreeing on the form of the descriptor. I fixed that by forcing the class to be complete, but this testcase shows why that approach is problematic. So instead let's adjust the type of the descriptor later if needed. PR c++/102651 PR c++/49387 gcc/cp/ChangeLog: * rtti.cc (get_tinfo_decl_direct): Don't complete_type. (emit_tinfo_decl): Update tdesc type if needed. gcc/testsuite/ChangeLog: * g++.dg/rtti/typeid-complete1.C: New test.
next prev parent reply other threads:[~2022-04-29 3:00 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-06-13 7:25 [Bug c++/49387] New: " mathieu.malaterre at gmail dot com 2011-06-13 9:07 ` [Bug c++/49387] " redi at gcc dot gnu.org 2011-06-13 9:09 ` mathieu.malaterre at gmail dot com 2011-06-13 9:46 ` redi at gcc dot gnu.org 2011-06-13 9:50 ` mathieu.malaterre at gmail dot com 2011-06-13 11:54 ` redi at gcc dot gnu.org 2011-06-13 12:40 ` redi at gcc dot gnu.org 2011-06-30 22:51 ` jason at gcc dot gnu.org 2011-07-01 0:53 ` jason at gcc dot gnu.org 2011-07-01 0:54 ` jason at gcc dot gnu.org 2022-04-29 3:00 ` cvs-commit at gcc dot gnu.org [this message] 2022-05-15 16:29 ` cvs-commit 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-49387-4-N1SK4IvoED@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).