public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/101839] [9/10/11/12 Regression] Hang in C++ code with -fdevirtualize Date: Tue, 10 Aug 2021 07:13:17 +0000 [thread overview] Message-ID: <bug-101839-4-esvVuN7brc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101839-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101839 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[9/10/11/12 Regression] |[9/10/11/12 Regression] |Hand in C++ code with |Hang in C++ code with |-fdevirtualize |-fdevirtualize Known to fail| |10.3.0, 11.2.1, 7.5.0, | |9.4.0 Target Milestone|--- |9.5 Priority|P3 |P2 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- BA::fill can be declared virtual without any change (it is implicitely so as stated by the C++ standard it seems). With GCC 11 and -O -fdevirtualize the program crashes and we see void {anonymous}::BA::fill (struct BA * const this, struct Buf & buf) { <bb 2> [count: 0]: __builtin_unreachable (); which is from a-t.C.083i.inline:t.C:16:14: optimized: folding virtual function call to __builtin_unreachable a-t.C.083i.inline:Introduced new external node (void __builtin_unreachable()/1356). a-t.C.083i.inline:t.C:17:14: optimized: folding virtual function call to __builtin_unreachable
next prev parent reply other threads:[~2021-08-10 7:13 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-10 7:02 [Bug ipa/101839] New: [9/10/11/12 Regression] Hand " marxin at gcc dot gnu.org 2021-08-10 7:04 ` [Bug ipa/101839] " marxin at gcc dot gnu.org 2021-08-10 7:09 ` marxin at gcc dot gnu.org 2021-08-10 7:13 ` rguenth at gcc dot gnu.org [this message] 2021-08-10 7:33 ` [Bug ipa/101839] [9/10/11/12 Regression] Hang " redi at gcc dot gnu.org 2022-05-27 9:45 ` [Bug ipa/101839] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:45 ` jakub at gcc dot gnu.org 2022-07-29 12:24 ` rguenth at gcc dot gnu.org 2022-08-10 3:53 ` yinyuefengyi at gmail dot com 2022-08-10 13:19 ` hubicka at gcc dot gnu.org 2022-08-10 13:44 ` hubicka at gcc dot gnu.org 2022-08-12 14:27 ` hubicka at gcc dot gnu.org 2022-08-15 13:57 ` [Bug ipa/101839] [10/11/12 " marxin at gcc dot gnu.org 2023-04-27 13:21 ` [Bug ipa/101839] [10/11 " rguenth at gcc dot gnu.org 2023-07-07 10:40 ` [Bug ipa/101839] [11 " rguenth 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-101839-4-esvVuN7brc@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).