public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kirill.yukhin at intel dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/59617] New: [vectorizer] ICE in vectorizable_mask_load_store with AVX-512F's gathers enabled. Date: Sat, 28 Dec 2013 22:21:00 -0000 [thread overview] Message-ID: <bug-59617-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59617 Bug ID: 59617 Summary: [vectorizer] ICE in vectorizable_mask_load_store with AVX-512F's gathers enabled. Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: kirill.yukhin at intel dot com Created attachment 31529 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31529&action=edit Reproducer Hello, I am going to check in a patch, which will enable AVX-512F new gathers instructions. New gathers are use mask registers (%kN), while vectorizable_mask_load_store asserts mask type to be compatible with operand type. This fails 416.gamess to build with -mavx512f -Ofast. Reproducer attached. Reproduce: $ gfortran -S -Ofast -mavx512f hss2a.fppized.f Back trace: 0xbcfc27 vectorizable_mask_load_store /export/users/kyukhin/gcc/git/gcc/gcc/tree-vect-stmts.c:1901 0xbddf6c vectorizable_call /export/users/kyukhin/gcc/git/gcc/gcc/tree-vect-stmts.c:2172 0xbe1021 vect_transform_stmt(gimple_statement_base*, gimple_stmt_iterator*, bool*, _slp_tree*, _slp_instance*) /export/users/kyukhin/gcc/git/gcc/gcc/tree-vect-stmts.c:7017 0xbe4731 vect_transform_loop(_loop_vec_info*) /export/users/kyukhin/gcc/git/gcc/gcc/tree-vect-loop.c:6046 0xc00838 vectorize_loops() /export/users/kyukhin/gcc/git/gcc/gcc/tree-vectorizer.c:476 I'll check my patch in with disabled gathers, so to enable it - remove `#if 0' in gcc/config/i386/i386.c
next reply other threads:[~2013-12-28 22:21 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-28 22:21 kirill.yukhin at intel dot com [this message] 2014-01-13 19:17 ` [Bug tree-optimization/59617] " jakub at gcc dot gnu.org 2014-01-29 17:35 ` kyukhin at gcc dot gnu.org 2014-03-30 19:06 ` dominiq at lps dot ens.fr 2014-04-02 7:52 ` ubizjak at gmail dot com 2014-04-03 8:50 ` dominiq at lps dot ens.fr 2014-04-03 9:55 ` dominiq at lps dot ens.fr 2014-04-03 11:38 ` dominiq at lps dot ens.fr 2014-04-03 11:42 ` kirill.yukhin at intel dot com 2014-04-03 11:54 ` dominiq at lps dot ens.fr 2014-04-03 12:00 ` dominiq at lps dot ens.fr 2014-04-03 13:19 ` dominiq at lps dot ens.fr 2014-04-03 13:23 ` kirill.yukhin at intel dot com 2014-04-03 13:30 ` dominiq at lps dot ens.fr 2014-04-03 13:31 ` iains at gcc dot gnu.org 2020-09-14 12:48 ` 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-59617-4@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).