public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "haochen.jiang at intel dot com" <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 07:35:58 +0000 [thread overview]
Message-ID: <bug-113133-4-jhqZiXHYTz@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 #7 from Haochen Jiang <haochen.jiang at intel dot com> ---
(In reply to Uroš Bizjak from comment #1)
> Created attachment 56962 [details]
> Proposed patch
>
> Patch in testing.
>
> lowpart_subreg can't handle:
>
> lowpart_subreg (V4SFmode, operands[0], DFmode);
>
> and
>
> lowpart_subreg (V2DFmode, operands[0], SFmode);
>
> subreg conversions and will return NULL_RTX for these cases.
I suppose the patch here is ok at least from my initial test.
next prev parent reply other threads:[~2023-12-29 7:35 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 [this message]
2023-12-29 8:16 ` ubizjak at gmail dot com
2023-12-29 8:53 ` cvs-commit at gcc dot gnu.org
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-jhqZiXHYTz@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: link
Be 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).