public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "liuhongt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/114471] [14 regression] ICE when building liblc3-1.0.4 with -fno-vect-cost-model -march=x86-64-v4 Date: Tue, 26 Mar 2024 03:58:17 +0000 [thread overview] Message-ID: <bug-114471-4-G1F4pNWyzc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114471-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114471 Hongtao Liu <liuhongt at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |liuhongt at gcc dot gnu.org --- Comment #5 from Hongtao Liu <liuhongt at gcc dot gnu.org> --- Maybe we should always use kmask under AVX512, currently only >= 128-bits vector of vector _Float16 use kmask, < 128 bits vector still use vector mask. 24628 /* Scalar mask case. */ 24629 if ((TARGET_AVX512F && TARGET_EVEX512 && vector_size == 64) 24630 || (TARGET_AVX512VL && (vector_size == 32 || vector_size == 16)) 24631 /* AVX512FP16 only supports vector comparison 24632 to kmask for _Float16. */ 24633 || (TARGET_AVX512VL && TARGET_AVX512FP16 24634 && GET_MODE_INNER (data_mode) == E_HFmode)) 24635 { 24636 if (elem_size == 4 24637 || elem_size == 8 24638 || (TARGET_AVX512BW && (elem_size == 1 || elem_size == 2))) 24639 return smallest_int_mode_for_size (nunits); 24640 } 24641 24642 scalar_int_mode elem_mode 24643 = smallest_int_mode_for_size (elem_size * BITS_PER_UNIT); 24644 24645 gcc_assert (elem_size * nunits == vector_size); 24646 24647 return mode_for_vector (elem_mode, nunits);
next prev parent reply other threads:[~2024-03-26 3:58 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-25 17:18 [Bug tree-optimization/114471] New: [14 regression] ICE when building liblc3-1.0.4 sjames at gcc dot gnu.org 2024-03-25 17:20 ` [Bug tree-optimization/114471] [14 regression] ICE when building liblc3-1.0.4 with -fno-vect-cost-model -march=x86-64-v4 sjames at gcc dot gnu.org 2024-03-25 17:21 ` sjames at gcc dot gnu.org 2024-03-25 18:02 ` sjames at gcc dot gnu.org 2024-03-25 22:51 ` pinskia at gcc dot gnu.org 2024-03-26 3:58 ` liuhongt at gcc dot gnu.org [this message] 2024-03-26 4:09 ` liuhongt at gcc dot gnu.org 2024-03-26 7:58 ` rguenth at gcc dot gnu.org 2024-03-26 10:06 ` cvs-commit at gcc dot gnu.org 2024-03-26 10:07 ` 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-114471-4-G1F4pNWyzc@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).