On 11/20/25 9:27 AM, Christoph Müllner wrote:
Hi Zhongyao, Jeff, and Kito,
In the discussion of this feature in the RISC-V C API PR [1], Craig
brought up a compatibility issue:
"Developer writes code for RVA23U64 today.
In the future the code is compiled with RVA30U64 that is superset of RVA23U64.
__riscv_rva23u64 macro is not defined because __riscv_rva30u64.
Code no longer does the correct thing and must be updated to check for
__riscv_rva30u64 OR __riscv_rva23u64."
Zhongyao agreed that this is an issue.
Kito then proposed to define all test macros whose extensions are enabled.
Since then, I haven't seen anything regarding this issue.
Should we revert the patch for now?
I'm not opposed to profile test macros in general, but we probably
want to fix the compatibility issue before GCC releases.
I have no strong opinion here, but that's probably because I'm not using
profile strings yet :-)
I don't mind reverting if we're unsure how we want this to work going
forward, so if that's what Kito, Zhongyao and yourself think is best,
then please submit a patch (and consider it pre-approved).
Jeff
