Re: [PATCH] RISC-V: Don't unconditionally add m, a, f, d in arch-canonicalize

Back ported to releases/gcc-11 and releases/gcc-12 branch :) On Thu, May 26, 2022 at 5:33 AM Palmer Dabbelt wrote: > > On Wed, 25 May 2022 07:00:11 PDT (-0700), gcc-patches@gcc.gnu.org wrote: > > Committed, Thanks for fixing my stupid bug :P > > IMO this is a good candidate for a backport. > > >

Re: [PATCH] RISC-V: Don't unconditionally add m, a, f, d in arch-canonicalize

On Wed, 25 May 2022 07:00:11 PDT (-0700), gcc-patches@gcc.gnu.org wrote: Committed, Thanks for fixing my stupid bug :P IMO this is a good candidate for a backport. On Wed, May 25, 2022 at 9:26 PM Simon Cook wrote: This solves an issue where rv32i, etc. are canonicalized to rv32imafd since

Re: [PATCH] RISC-V: Don't unconditionally add m, a, f, d in arch-canonicalize

Committed, Thanks for fixing my stupid bug :P On Wed, May 25, 2022 at 9:26 PM Simon Cook wrote: > > This solves an issue where rv32i, etc. are canonicalized to rv32imafd > since the g->i addition of 'm', 'a', 'f', 'd' is not actually gated by > whether the input was rv32g/rv64g. > > gcc/ChangeLo

[PATCH] RISC-V: Don't unconditionally add m,a,f,d in arch-canonicalize

This solves an issue where rv32i, etc. are canonicalized to rv32imafd since the g->i addition of 'm', 'a', 'f', 'd' is not actually gated by whether the input was rv32g/rv64g. gcc/ChangeLog: * config/riscv/arch-canonicalize: Only add mafd extension if base was rv32/rv64g. --- gcc