• Reviewer Coverage for LLDB RISC-V PRs First I need to make folks aware that while I was previously assigned to Linaro, I am now back at Arm. • To you in the community that is just a change of email address but for me it changes how I have to approach LLDB changes for non-Arm architectures. • Put simply, I have to be more careful, for obvious reasons. • I am still an LLDB maintainer and a good experience using LLDB with RISC-V is important for the health and reputation of the project on all platforms. • So from that perspective, RISC-V deserves as much attention as anything else. • What I can continue to do is the first pass, high level review: “where are the tests” “this needs a release note” Appropriate use of APIs Effect on other architectures, and so on What I cannot be doing is: Checking architecture or ABI details for RISC-V (even if I tried, it’s not familiar to me).
Article Summaries:
- Arm engineer mchoo7, formerly with Linaro, has returned to Arm and will continue as an LLDB maintainer. He notes that his new role requires greater caution when reviewing RISC‑V pull requests, as he lacks deep familiarity with the architecture’s ABI and feature design. mchoo7 will perform high‑level checks-ensuring tests exist, release notes are added, APIs are used correctly, and cross‑architecture impacts are considered-but will not verify low‑level RISC‑V details. He invites community members to collaborate on RISC‑V PRs, possibly designating an architecture‑specific maintainer, and seeks volunteers to be added to the CODEOWNERS file. Potential stakeholders include @JDevlieghere, @tedwoodward, @lenary, and a Syntacore representative.
Sources: