It's likely harder than a typical "simple hack of the week" as those
often end up being target patterns or match.pd patterns -- so limited
in how many APIs you need to understand, much less RTL or gimple IL
parsing, etc. But there's folks here that can help.
That is true: it has been a little harder than I expected!
Since I am modifying cleanup_cfg, and it is called so many times,
I am getting a lot of weird interactions leading to infinite loops or
other errors. Or getting different behavior when it is called in CFGRTL vs.
CFGLAYOUT
mode (I spent last evening trying to grok the difference).
Maybe this is just something to tag onto the end of bbro rather than adding it
to a core function instead?
I've requested a bugzilla account and I will file one once that is thru.
Sounds good. Thanks. Feel free to add me on CC once the bug is
open. I track all RISC-V bugs for the weekly patchwork meeting
(Tuesday mornings US time, happy to get you an invite if you want). We
focus on making sure submitted patches have someone assigned for
review, state of the CI systems, usually a handful of bugs to make
sure get proper attention, and any general discussion that we need for
RISC-V issues. We often also touch on glibc or binutils issues,
particularly as those projects approach releases.
I appreciate it -- I do want to work towards engaging more with the toolchain +
RISC-V
but I am probably not free during usual US ET work hours.
BTW, I haven't gotten a response from gcc-bugzilla-account-request (not sure if
that is typical,
I'm sure there is a lot of spam sadly) but I have not forgotten about it.
Best,
Robert
