public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107261] ICE: in classify_argument, at config/i386/i386.cc:2523 on __bf16 vect argument or return value
Date: Thu, 20 Oct 2022 03:28:03 +0000 [thread overview]
Message-ID: <bug-107261-4-4KD9O48jQh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107261-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107261
--- Comment #3 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Jakub Jelinek from comment #2)
> I think:
> --- gcc/config/i386/i386.cc.jj 2022-10-14 09:35:56.158990825 +0200
> +++ gcc/config/i386/i386.cc 2022-10-19 19:49:07.883101047 +0200
> @@ -2507,6 +2507,7 @@ classify_argument (machine_mode mode, co
> case E_V2SImode:
> case E_V4HImode:
> case E_V4HFmode:
> + case E_V4BFmode:
> case E_V2HFmode:
> case E_V8QImode:
> classes[0] = X86_64_SSE_CLASS;
> ought to fix this.
We haven't support V4BFmode yet, why there's V4BFmode coming in.
We'll take a look.
next prev parent reply other threads:[~2022-10-20 3:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 11:00 [Bug c++/107261] New: ICE: in classify_argument, at config/i386/i386.cc:2523 on C++ __bf16 vect argument zsojka at seznam dot cz
2022-10-14 11:10 ` [Bug c++/107261] " marxin at gcc dot gnu.org
2022-10-19 14:34 ` [Bug target/107261] ICE: in classify_argument, at config/i386/i386.cc:2523 on __bf16 vect argument or return value zsojka at seznam dot cz
2022-10-19 17:55 ` jakub at gcc dot gnu.org
2022-10-20 3:28 ` crazylht at gmail dot com [this message]
2022-10-20 3:30 ` crazylht at gmail dot com
2022-10-31 1:50 ` cvs-commit at gcc dot gnu.org
2022-10-31 1:52 ` crazylht at gmail dot com
2023-11-30 8:57 ` liuhongt 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-107261-4-4KD9O48jQh@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).