On 5/15/25 8:35 PM, Kito Cheng wrote:
Hmmmmm, it really doesn't make too much sense to get that warning, but
I can reproduce that when I compile with gcc 13 (and newer)...and
seems like a known issue [1][2]...
I still hadn't managed to convince myself the code was wrong. It looked
more like the change was papering over a bug in the warning itself.
The referenced bug is closed as fixed, but there was a link (from the
stack overflow discussion) to a testcase in godbolt that was still failing.
However I don't really like that approach, could you change the
argument type of get_riscv_ext_info to `const char *` to suppress that
warning instead?
If that works, it'd be better IMHO.
jeff
