Dave Martin <dave.mar...@linaro.org> wrote: > c) Create a new note type specially for this, and dump the > VFP/NEON regs in there. This is closest to the model followed > by ptrace, where PTRACE_GETREGS, PTRACE_GETFPREGS and > PTRAGE_GETVFPREGS are all distinct.
>From a GDB perspective, I'd consider this the preferred solution; there are precedents for this on other platforms (e.g. PowerPC), and there is existing GDB/BFD infrastructure to check for presence/ absence of such notes. However, we also need to be able to distinguish the various cases: VFPv2 vs. VFPv3-D16 vs. VFPv3-D32 vs. VFPv32-D32+NEON These cause GDB to display/interact with the register set in different ways ... To distinguish 16 vs. 32 registers, we can of course simply look at the size of the note. But how to detect support for NEON as opposed to plain VFPv32-D32? I could think of two ways: 1) Have *two* new note types, one for VFP, and one for NEON 2) Have GDB look into the AT_HWCAP setting in the NT_AUXV note Option 2) seems preferable to me, since NT_AUXV is already there, and it can also be used to detect the integer-only NEON case. Thoughts? Mit freundlichen Gruessen / Best Regards Ulrich Weigand -- Dr. Ulrich Weigand | Phone: +49-7031/16-3727 STSM, GNU compiler and toolchain for Linux on System z and Cell/B.E. IBM Deutschland Research & Development GmbH Vorsitzender des Aufsichtsrats: Martin Jetter | Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen | Registergericht: Amtsgericht Stuttgart, HRB 243294 _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
