public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ysrumyan at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/66142] Loop is not vectorized because not sufficient support for GOMP_SIMD_LANE Date: Thu, 14 May 2015 14:19:00 -0000 [thread overview] Message-ID: <bug-66142-4-6TSK9dkr0S@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66142-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66142 --- Comment #1 from Yuri Rumyantsev <ysrumyan at gmail dot com> --- Created attachment 35541 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35541&action=edit test-case to reproduce Must be compiled with -Ofast -fopenmp -march=core-avx2 options.
next prev parent reply other threads:[~2015-05-14 14:19 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-14 14:18 [Bug tree-optimization/66142] New: " ysrumyan at gmail dot com 2015-05-14 14:19 ` ysrumyan at gmail dot com [this message] 2015-05-22 10:09 ` [Bug tree-optimization/66142] " jakub at gcc dot gnu.org 2015-05-22 11:12 ` jakub at gcc dot gnu.org 2015-05-22 11:40 ` jakub at gcc dot gnu.org 2015-05-22 11:54 ` jakub at gcc dot gnu.org 2015-05-22 14:51 ` jakub at gcc dot gnu.org 2015-05-25 9:35 ` jakub at gcc dot gnu.org 2015-05-25 12:48 ` jakub at gcc dot gnu.org 2015-05-26 8:28 ` rguenther at suse dot de 2015-05-26 8:42 ` rguenth at gcc dot gnu.org 2015-05-26 13:56 ` rguenth at gcc dot gnu.org 2015-05-26 14:43 ` rguenth at gcc dot gnu.org 2015-05-27 7:56 ` rguenth at gcc dot gnu.org 2015-05-28 13:25 ` rguenth at gcc dot gnu.org 2015-05-29 13:07 ` jakub at gcc dot gnu.org 2015-06-02 13:18 ` rguenth at gcc dot gnu.org 2015-06-02 13:34 ` rguenth at gcc dot gnu.org 2015-06-03 8:03 ` rguenth at gcc dot gnu.org 2015-09-14 14:10 ` rguenth at gcc dot gnu.org 2015-09-17 12:36 ` rguenth at gcc dot gnu.org 2015-09-18 7:57 ` rguenth at gcc dot gnu.org 2021-05-04 13:17 ` 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-66142-4-6TSK9dkr0S@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).