On Mon, Jun 6, 2022 at 7:53 PM wangpc via Gcc-patches
wrote:
>
> If -mcpu or -march is specified and there is no -mabi, we will calculate
> default ABI from arch string provided by -march or defined in CPU info.
This is 100% wrong and goes against what all other targets do. All
other targets have
).
> But I think we can make it clearer.
> --
> Sender:Palmer Dabbelt
> Sent At:2022 Jun. 8 (Wed.) 02:45
> Recipient:gcc-patches
> Cc:pc.wang
> Subject:Re: [PATCH] RISC-V: Compute default ABI from -mcpu or -march
>
> On Mon, 06 Jun 2022 19:51:20 PDT (-0700), gcc-patches@gcc.gnu.org wr
g (see
> the next section).
But I think we can make it clearer.
--
Sender:Palmer Dabbelt
Sent At:2022 Jun. 8 (Wed.) 02:45
Recipient:gcc-patches
Cc:pc.wang
Subject:Re: [PATCH] RISC-V: Compute default ABI from -mcpu or -march
On Mo
On Mon, 06 Jun 2022 19:51:20 PDT (-0700), gcc-patches@gcc.gnu.org wrote:
If -mcpu or -march is specified and there is no -mabi, we will calculate
default ABI from arch string provided by -march or defined in CPU info.
IMO this is generally a good idea and we've talked about it before, but
just
If -mcpu or -march is specified and there is no -mabi, we will calculate
default ABI from arch string provided by -march or defined in CPU info.
gcc/ChangeLog:
* common/config/riscv/riscv-common.cc (compute_default_abi):
Implementation
to calculate -mabi from arch string.