Seeking clarification on 2023 RISC-V vector patch from Sourceware GDB mailing list #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi Greg,
I’m Jay,
I recently came across a GDB patch you submitted to the Sourceware mailing list in August 2023 related to RISC-V vector support:
https://www.sourceware.org/pipermail/gdb-patches/2023-August/201475.html
Unfortunately, I noticed that the email address listed there ([email protected]) is no longer active. While looking for another way to reach out, I found your GitHub profile and I hope it’s the same Greg Savin from the patch.
I’ve been some work with your patch, and I just had a quick clarification:
Does the patch enable visibility of RISC-V vector register values during standard debugging operations like:
Or is the patch specifically intended to expose vector registers only through commands like:
I came across your comment mentioning interactive use of the patch via these commands, and I want to confirm if that’s the only scope of its functionality or whether vector registers can also be observed in disassembly/debug output.
Thanks for your time, and apologies for reaching out via this unconventional method. I appreciate any clarification you can offer!
Best regards,
Jaykumar Lokhande