You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 17, 2022. It is now read-only.
As the subject says - could/should GDB/MI -data-list-register-names return ABI rather than canonical names for some or all of integer regs. FP regs and CSRs - either automatically or as a configurable option?
Are there situations in which some users want to see "raw" canonical names?
Are there situations in which other ABIs/register naming conventions might be used?
Shouldn't GDB/MI -data-list-register-names and the likes of info registers/info all-registers generate consistent output (they don't right now)?
If ABI names are used then might it also be necessary to cater for targets adhering to different versions of the (draft) priv spec - e.g. 1.9, 1.9.1, 1.10 and provide a command to tell GDB which priv spec should apply?
Are there other issues to consider?
If you need any more info please let me know.
Thanks
Tommy
The text was updated successfully, but these errors were encountered:
See also:
As the subject says - could/should GDB/MI -data-list-register-names return ABI rather than canonical names for some or all of integer regs. FP regs and CSRs - either automatically or as a configurable option?
Are there situations in which some users want to see "raw" canonical names?
Are there situations in which other ABIs/register naming conventions might be used?
Shouldn't GDB/MI -data-list-register-names and the likes of info registers/info all-registers generate consistent output (they don't right now)?
If ABI names are used then might it also be necessary to cater for targets adhering to different versions of the (draft) priv spec - e.g. 1.9, 1.9.1, 1.10 and provide a command to tell GDB which priv spec should apply?
Are there other issues to consider?
If you need any more info please let me know.
Thanks
Tommy
The text was updated successfully, but these errors were encountered: