public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zhroma at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/98533] [11/12/13/14 Regression] ICE: 'verify_type' failed
Date: Sat, 14 Oct 2023 07:16:03 +0000	[thread overview]
Message-ID: <bug-98533-4-VhfqKXSMyJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98533-4@http.gcc.gnu.org/bugzilla/>

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

Roman Zhuykov <zhroma at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |zhroma at gcc dot gnu.org

--- Comment #9 from Roman Zhuykov <zhroma at gcc dot gnu.org> ---
Just adding another example where I caught the same error:

$ cat test.cc 
class IR;
class Pass {
public:
    explicit Pass(IR *ir) : ir_(ir) {}
    virtual ~Pass() = default;
    IR *ir_ {nullptr};
};
class PassManager {
public:
    template <typename T> void RunPass() { T pass(ir_); }
    IR *ir_ {nullptr};
};
class IR final {
public:                            
    template <typename T> void RunPass() { pass_manager_.RunPass<T>(); }
    PassManager pass_manager_;
};
class ThePass : Pass {
public:
    explicit ThePass(IR *ir) : Pass(ir) {}
    ThePass(const ThePass &) = delete;
    template <typename Func = bool (*)(void *)> void Bar(void *inst, Func func
= [](void *) {});
};

void foo(IR *ir) { ir->RunPass<ThePass>(); }

$ g++ -fchecking -g -c test.cc  # any g++ from 8 to 13
test.cc:18:7: error: type variant has different ‘TYPE_FIELDS’
   18 | class ThePass : Pass {
      |       ^~~~~~~
 <record_type 0x7f44b1bbd738 ThePass ...

  parent reply	other threads:[~2023-10-14  7:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-05 14:25 [Bug other/98533] New: [11 " doko at debian dot org
2021-01-05 14:34 ` [Bug other/98533] " jakub at gcc dot gnu.org
2021-01-05 14:39 ` jakub at gcc dot gnu.org
2021-01-05 20:16 ` marxin at gcc dot gnu.org
2021-01-06  8:43 ` rguenth at gcc dot gnu.org
2021-01-14 11:18 ` [Bug other/98533] [8/9/10/11 " rguenth at gcc dot gnu.org
2021-02-26 12:27 ` rguenth at gcc dot gnu.org
2021-03-07  9:59 ` doko at debian dot org
2021-05-14  9:54 ` [Bug other/98533] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01  8:19 ` rguenth at gcc dot gnu.org
2022-05-27  9:44 ` [Bug c++/98533] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:43 ` jakub at gcc dot gnu.org
2023-07-07 10:38 ` [Bug c++/98533] [11/12/13/14 " rguenth at gcc dot gnu.org
2023-10-14  7:16 ` zhroma at gcc dot gnu.org [this message]
2024-01-02 22:15 ` 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-98533-4-VhfqKXSMyJ@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).