From: Palmer Dabbelt <palmer@dabbelt.com>
To: gcc-patches@gcc.gnu.org
Cc: shihua@iscas.ac.cn, gcc-patches@gcc.gnu.org,
lazyparser@gmail.com, jiawei@iscas.ac.cn,
Kito Cheng <kito.cheng@gmail.com>
Subject: Re: [RFC]RISC-V: Support RV64-ILP32
Date: Tue, 27 Dec 2022 10:25:19 -0800 (PST) [thread overview]
Message-ID: <mhng-cf82d4c1-146a-4d16-9601-3078172e48a3@palmer-ri-x1c9a> (raw)
In-Reply-To: <3c96be88-9289-641c-0fe2-91b45392bfb2@gmail.com>
On Tue, 27 Dec 2022 10:24:10 PST (-0800), gcc-patches@gcc.gnu.org wrote:
>
>
> On 12/12/22 23:49, shihua@iscas.ac.cn wrote:
>> From: Liao Shihua <shihua@iscas.ac.cn>
>>
>> This patch support rv64 insn in ilp32 ABI. It was inspired by aarch64 both
>> support 64-bit and 32-bit ABI with the same set of instructions.
>>
>>
>> gcc/ChangeLog:
>>
>> * config.gcc: Implememt ilp32* with rv64*.
>> * config/riscv/riscv.cc (riscv_option_override): Remove the constraint between RV64 and ILP32.
>> * config/riscv/riscv.h (TARGET_ILP32): Define TARGET_ILP32 with riscv_abi.
>> (POINTER_SIZE):POINTER_SIZE will change with TARGET_ILP32.
>> (Pmode):Likewise.
>> * config/riscv/riscv.md: Convert split mode with Pmode and change mode form Xmode to Pmode in stack_tie.
> This is a new feature and thus I think we should defer to gcc-14 unless
> there is a compelling need.
I agree. This is a pretty big one with a lot of ABI-related
complications, so let's just play it safe.
next prev parent reply other threads:[~2022-12-27 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 6:49 shihua
2022-12-27 18:24 ` Jeff Law
2022-12-27 18:25 ` Palmer Dabbelt [this message]
2022-12-28 1:40 ` Kito Cheng
2022-12-28 4:10 ` Liao Shihua
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=mhng-cf82d4c1-146a-4d16-9601-3078172e48a3@palmer-ri-x1c9a \
--to=palmer@dabbelt.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jiawei@iscas.ac.cn \
--cc=kito.cheng@gmail.com \
--cc=lazyparser@gmail.com \
--cc=shihua@iscas.ac.cn \
/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).