public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/105469] [10/11/12/13 Regression] "execution reached an unreachable program point" with -flto since r5-7027-g0b986c6ac777aa4e Date: Wed, 18 Jan 2023 16:46:02 +0000 [thread overview] Message-ID: <bug-105469-4-38G5pGYFAF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105469-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105469 --- Comment #16 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Can't reproduce the __builtin_unreachable on the trunk. Bisection shows that cc1plus -quiet -fsanitize=undefined -O3 -fwhole-program -fdump-tree-optimized pr105469.C; grep unreachable pr105469.C.* stopped printing anything with r13-4686-g095a13eda2caf6842096a3ab78b2081c50fe8799 Martin, is that a real fix for this or it just went latent?
next prev parent reply other threads:[~2023-01-18 16:46 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-03 19:58 [Bug c++/105469] New: "execution reached an unreachable program point" with -flto remi.coulom at gmail dot com 2022-05-04 6:28 ` [Bug middle-end/105469] " rguenth at gcc dot gnu.org 2022-05-04 7:15 ` remi.coulom at gmail dot com 2022-05-04 8:54 ` marxin at gcc dot gnu.org 2022-05-04 9:28 ` jakub at gcc dot gnu.org 2022-05-04 10:30 ` marxin at gcc dot gnu.org 2022-05-04 10:33 ` marxin at gcc dot gnu.org 2022-05-04 10:34 ` marxin at gcc dot gnu.org 2022-05-04 10:44 ` rguenth at gcc dot gnu.org 2022-05-04 10:50 ` marxin at gcc dot gnu.org 2022-05-04 10:53 ` marxin at gcc dot gnu.org 2022-05-04 11:01 ` [Bug middle-end/105469] "execution reached an unreachable program point" with -flto since r5-7027-g0b986c6ac777aa4e marxin at gcc dot gnu.org 2022-05-04 11:01 ` jakub at gcc dot gnu.org 2022-05-05 4:50 ` pinskia at gcc dot gnu.org 2022-05-11 12:47 ` remi.coulom at gmail dot com 2022-09-14 13:08 ` [Bug middle-end/105469] [10/11/12/13 Regression] " rguenth at gcc dot gnu.org 2023-01-18 16:46 ` jakub at gcc dot gnu.org [this message] 2023-01-18 16:47 ` jakub at gcc dot gnu.org 2023-01-18 21:30 ` hubicka at gcc dot gnu.org 2023-01-19 13:25 ` jamborm at gcc dot gnu.org 2023-07-07 10:43 ` [Bug middle-end/105469] [11/12/13/14 " 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-105469-4-38G5pGYFAF@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).