public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pan2.li at intel dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114639] [riscv] ICE in create_pre_exit, at mode-switching.cc:451
Date: Tue, 09 Apr 2024 11:55:46 +0000 [thread overview]
Message-ID: <bug-114639-4-Z3UoufIhTn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114639-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114639
--- Comment #11 from Li Pan <pan2.li at intel dot com> ---
(In reply to Li Pan from comment #10)
> The #define FUNCTION_VALUE_REGNO_P(N) ((N) == GP_RETURN || (N) == FP_RETURN)
> of the riscv backend doesn't honor vector mode. Then the below part
>
> 370 ................ if (!targetm.calls.function_value_regno_p
> (copy_start))
>
> 371 ................ copy_num = 0;
>
> 372 ................ else
> 373 ................ copy_num = hard_regno_nregs (copy_start,
> 374 ................................................ GET_MODE (copy_reg));
>
> will have copy_num == 0 and then went to a different code path.
>
> Let me run fully riscv regression test for this fix first.
Maybe misunderstand here, need to double-check the vector ABI for return
values.
next prev parent reply other threads:[~2024-04-09 11:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 12:29 [Bug target/114639] New: " schwab@linux-m68k.org
2024-04-08 14:08 ` [Bug target/114639] " kito at gcc dot gnu.org
2024-04-08 18:13 ` pinskia at gcc dot gnu.org
2024-04-09 1:26 ` pan2.li at intel dot com
2024-04-09 1:28 ` kito at gcc dot gnu.org
2024-04-09 1:33 ` pan2.li at intel dot com
2024-04-09 1:37 ` juzhe.zhong at rivai dot ai
2024-04-09 3:45 ` pan2.li at intel dot com
2024-04-09 7:22 ` pan2.li at intel dot com
2024-04-09 8:05 ` ubizjak at gmail dot com
2024-04-09 8:32 ` pan2.li at intel dot com
2024-04-09 11:55 ` pan2.li at intel dot com [this message]
2024-04-09 15:30 ` pan2.li at intel dot com
2024-04-10 3:20 ` pan2.li at intel dot com
2024-04-11 3:02 ` cvs-commit at gcc dot gnu.org
2024-04-16 8:47 ` schwab@linux-m68k.org
2024-04-22 22:53 ` juzhe.zhong at rivai dot ai
2024-04-28 6:02 ` pan2.li at intel dot com
2024-04-28 6:22 ` juzhe.zhong at rivai dot ai
2024-04-28 6:51 ` pan2.li 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-114639-4-Z3UoufIhTn@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).