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/59591] [4.9 Regression] ICE in vect_get_vec_def_for_stmt_copy, at tree-vect-stmts.c:156 for -march=core-avx2 Date: Fri, 27 Dec 2013 12:07:00 -0000 [thread overview] Message-ID: <bug-59591-4-CgffIVdjyL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59591-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59591 --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Slightly reduced fortran testcase for -O3 -mavx2: subroutine foo (m, n, o, p, q, e, a, b, x, f) integer, intent (in) :: n, o, p, q, m, f integer, dimension (n:o) :: e, a, b integer, dimension (n:o, p:q) :: x integer :: j, i do j = 1, m do i = n, f if (e(i) .eq. 0) then a(i) = x(i, b(i)) endif enddo enddo end subroutine foo and C testcase for -O3 -mavx2 -fopenmp-simd: int p[256], q[256], r[256], t[256]; void foo (void) { int i; #pragma omp simd safelen(64) for (i = 0; i < 256; i++) if (r[i] > 32) t[i] = p[q[i] * 3L + 2L]; }
next prev parent reply other threads:[~2013-12-27 12:07 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-24 8:47 [Bug tree-optimization/59591] New: " izamyatin at gmail dot com 2013-12-24 8:48 ` [Bug tree-optimization/59591] " izamyatin at gmail dot com 2013-12-24 12:26 ` [Bug tree-optimization/59591] [4.9 Regression] " hjl.tools at gmail dot com 2013-12-24 12:38 ` dominiq at lps dot ens.fr 2013-12-27 12:07 ` jakub at gcc dot gnu.org [this message] 2013-12-27 19:16 ` jakub at gcc dot gnu.org 2013-12-30 12:19 ` jakub at gcc dot gnu.org 2013-12-30 17:05 ` jakub at gcc dot gnu.org 2013-12-30 17:08 ` jakub 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-59591-4-CgffIVdjyL@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).