Summary: | z13 vector register support for vgdb gdbserver | ||
---|---|---|---|
Product: | [Developer tools] valgrind | Reporter: | Mark Wielaard <mark> |
Component: | general | Assignee: | Andreas Arnez <arnez> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | arnez, jseward |
Priority: | NOR | ||
Version: | 3.14 SVN | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Add vector register support for vgdb |
Description
Mark Wielaard
2018-08-05 18:36:31 UTC
Created attachment 115734 [details]
Add vector register support for vgdb
This provides the missing vector register support for Valgrind's gdbserver.
(In reply to Andreas Arnez from comment #1) > Created attachment 115734 [details] > Add vector register support for vgdb Is this OK? Please let me know if I may have missed anything. (In reply to Andreas Arnez from comment #2) > Is this OK? Please let me know if I may have missed anything. Looks OK. +1 to land provided you're sure that the various magic numbers are correct, in particular the "case 52:" etc in transfer_register and the offset numbers, eg "{ "v23", 4704, 128 }", in tatic struct reg regs[]. (In reply to Julian Seward from comment #3) > Looks OK. +1 to land provided you're sure that the various magic numbers are > correct, in particular the "case 52:" etc in transfer_register and the offset > numbers, eg "{ "v23", 4704, 128 }", in tatic struct reg regs[]. Thanks. Yes, I'm fairly positive that these magic numbers are correct. (I didn't change to a less magic way because this would affect the existing code as well.) Pushed as git commit 50bd2282b. |