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/58359] __builtin_unreachable prevents vectorization Date: Thu, 24 Oct 2013 08:52:00 -0000 [thread overview] Message-ID: <bug-58359-4-vsKAyB8Xym@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58359-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58359 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> --- That is still wrong, __builtin_unreachable is still very much useful even at the RTL level (where we expand it as basic blocks without successors). Perhaps if-conversion (for LOOP_VERSIONED loop only) can just drop the __builtin_unreachable () from the to be vectorized loop?
next prev parent reply other threads:[~2013-10-24 8:52 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-09-08 8:20 [Bug tree-optimization/58359] New: " glisse at gcc dot gnu.org 2013-09-09 8:22 ` [Bug tree-optimization/58359] " rguenth at gcc dot gnu.org 2013-09-17 13:31 ` glisse at gcc dot gnu.org 2013-09-20 14:20 ` a.sinyavin at samsung dot com 2013-09-27 14:46 ` a.sinyavin at samsung dot com 2013-09-27 14:46 ` a.sinyavin at samsung dot com 2013-09-27 14:48 ` a.sinyavin at samsung dot com 2013-10-23 14:56 ` glisse at gcc dot gnu.org 2013-10-23 15:55 ` a.sinyavin at samsung dot com 2013-10-23 15:56 ` a.sinyavin at samsung dot com 2013-10-24 8:52 ` jakub at gcc dot gnu.org [this message] 2013-10-24 12:03 ` glisse at gcc dot gnu.org 2013-12-06 12:22 ` a.sinyavin at samsung dot com 2021-08-24 23:22 ` pinskia at gcc dot gnu.org 2023-04-18 14:48 ` 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-58359-4-vsKAyB8Xym@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).