Re: [PATCH v2] RISC-V: Fix a typo in zce to zcf implication

2025-03-01 Thread Jeff Law
On 2/24/25 3:22 AM, Yuriy Kolerov wrote: zce must imply zcf but this rule was corrupted after refactoring in 9e12010b5e724277ea. This may be observed ater generating an .s file from any source code file with -mriscv-attribute -march=rv32if_zce -mabi=ilp32 -S options. A full march will be prese

Re: [PATCH v2] RISC-V: Fix a typo in zce to zcf implication

2025-03-01 Thread Jeff Law
On 2/25/25 12:05 PM, Yuriy Kolerov wrote: Hi Jeff, That check is performed in a lambda function: {"zce", "zcf", [] (const riscv_subset_list *subset_list) -> bool { return subset_list->xlen () == 32 && subset_list->lookup ("f"); }}, The typo was in a rule itself: {"zcf"

Re: [PATCH v2] RISC-V: Fix a typo in zce to zcf implication

2025-02-26 Thread Kito Cheng
;f") != NULL > && subset_list->lookup ("zcf") == NULL) > subset_list->add ("zcf", false); > > But it was accidentally refactored in a wrong way. > > Regards, > Yuriy Kolerov > > -Original Message- > From: Jeff Law

RE: [PATCH v2] RISC-V: Fix a typo in zce to zcf implication

2025-02-25 Thread Yuriy Kolerov
uriy Kolerov -----Original Message----- From: Jeff Law Sent: Tuesday, February 25, 2025 4:46 PM To: Yuriy Kolerov ; gcc-patches@gcc.gnu.org Cc: Artemiy Volkov Subject: Re: [PATCH v2] RISC-V: Fix a typo in zce to zcf implication On 2/24/25 3:22 AM, Yuriy Kolerov wrote: > zce must imply zc

Re: [PATCH v2] RISC-V: Fix a typo in zce to zcf implication

2025-02-25 Thread Jeff Law
On 2/24/25 3:22 AM, Yuriy Kolerov wrote: zce must imply zcf but this rule was corrupted after refactoring in 9e12010b5e724277ea. This may be observed ater generating an .s file from any source code file with -mriscv-attribute -march=rv32if_zce -mabi=ilp32 -S options. A full march will be prese