public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113133] [14 Regression] ICE: SIGSEGV in mark_label_nuses(rtx_def*) (emit-rtl.cc:3896) with -O -fno-tree-ter -mavx512f -march=barcelona Date: Fri, 29 Dec 2023 08:53:34 +0000 [thread overview] Message-ID: <bug-113133-4-cKByEhNrfA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113133-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113133 --- Comment #9 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Uros Bizjak <uros@gcc.gnu.org>: https://gcc.gnu.org/g:1e7f9abb892443719c82bb17910caa8fb5eeec15 commit r14-6862-g1e7f9abb892443719c82bb17910caa8fb5eeec15 Author: Uros Bizjak <ubizjak@gmail.com> Date: Fri Dec 29 09:47:43 2023 +0100 i386: Fix TARGET_USE_VECTOR_FP_CONVERTS SF->DF float_extend splitter [PR113133] The post-reload splitter currently allows xmm16+ registers with TARGET_EVEX512. The splitter changes SFmode of the output operand to V4SFmode, but the vector mode is currently unsupported in xmm16+ without TARGET_AVX512VL. lowpart_subreg returns NULL_RTX in this case and the compilation fails with invalid RTX. The patch removes support for x/ymm16+ registers with TARGET_EVEX512. The support should be restored once ix86_hard_regno_mode_ok is fixed to allow 16-byte modes in x/ymm16+ with TARGET_EVEX512. PR target/113133 gcc/ChangeLog: * config/i386/i386.md (TARGET_USE_VECTOR_FP_CONVERTS SF->DF float_extend splitter): Do not handle xmm16+ with TARGET_EVEX512. gcc/testsuite/ChangeLog: * gcc.target/i386/pr113133-1.c: New test. * gcc.target/i386/pr113133-2.c: New test.
next prev parent reply other threads:[~2023-12-29 8:53 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-25 11:09 [Bug target/113133] New: " zsojka at seznam dot cz 2023-12-28 19:36 ` [Bug target/113133] " ubizjak at gmail dot com 2023-12-28 19:37 ` ubizjak at gmail dot com 2023-12-28 20:02 ` ubizjak at gmail dot com 2023-12-28 20:10 ` ubizjak at gmail dot com 2023-12-29 2:08 ` haochen.jiang at intel dot com 2023-12-29 2:31 ` haochen.jiang at intel dot com 2023-12-29 7:35 ` haochen.jiang at intel dot com 2023-12-29 8:16 ` ubizjak at gmail dot com 2023-12-29 8:53 ` cvs-commit at gcc dot gnu.org [this message] 2023-12-29 8:57 ` ubizjak at gmail dot com 2024-01-02 6:39 ` haochen.jiang at intel dot com
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-113133-4-cKByEhNrfA@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).