public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wickmarkus86 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/114992] New: ICE during IPA pass: targetclone in add_to_same_comdat_group, at symtab.cc:492 Date: Wed, 08 May 2024 18:06:31 +0000 [thread overview] Message-ID: <bug-114992-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114992 Bug ID: 114992 Summary: ICE during IPA pass: targetclone in add_to_same_comdat_group, at symtab.cc:492 Product: gcc Version: 14.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: wickmarkus86 at gmail dot com Target Milestone: --- Created attachment 58133 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58133&action=edit outcome of -freport-bug Since GCC 13.1, my minimal reproducible example triggers an ICE, reproducable here: https://gcc.godbolt.org/z/vYK3TvE6j Thanks a lot for looking at this issue! ------------------------------------------------------------------ template <typename Callable> void helper_func(Callable) {} template <typename Callable> __attribute__((target_clones("avx2", "default"))) void handler(Callable outer_callback) { outer_callback(); } class InnerClass { public: template <typename Callable> void inner_callback(Callable){}; void func() { helper_func([&](int) {}); auto outer_callback = [this]() { inner_callback([]() {}); }; handler(outer_callback); } }; class OuterClass { public: void func(); InnerClass inner; }; void OuterClass::func() { inner.func(); }
next reply other threads:[~2024-05-08 18:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-08 18:06 wickmarkus86 at gmail dot com [this message] 2024-05-08 22:15 ` [Bug c++/114992] [13/14/15 Regression] ICE during IPA pass: targetclone in add_to_same_comdat_group with calling a target clone with a lamdba in a comdat function pinskia at gcc dot gnu.org 2024-05-21 9:20 ` jakub 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-114992-4@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).