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 tree-optimization/95001] std::terminate() and abort() do not have __builtin_unreachable() semantics Date: Fri, 08 May 2020 12:24:31 +0000 [thread overview] Message-ID: <bug-95001-4-E4Jg8VfcQz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95001-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95001 --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- The on-demand VRP (or if it can do non-zero bits too, even better), ought to handle this kind of things, but it isn't something we can store in the SSA_NAMEs unless we create the ASSERT_EXPRs (which means during VRP only).
next prev parent reply other threads:[~2020-05-08 12:24 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-08 9:07 [Bug c++/95001] New: " s_gccbugzilla at nedprod dot com 2020-05-08 9:44 ` [Bug tree-optimization/95001] " pinskia at gcc dot gnu.org 2020-05-08 11:26 ` rguenth at gcc dot gnu.org 2020-05-08 11:43 ` jakub at gcc dot gnu.org 2020-05-08 12:16 ` glisse at gcc dot gnu.org 2020-05-08 12:24 ` jakub at gcc dot gnu.org [this message] 2020-05-08 12:42 ` s_gccbugzilla at nedprod dot com
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-95001-4-E4Jg8VfcQz@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).