[patch 2/2] Implement gdbarch hook user_register_name on ARM

[Yao Qi]

On 12/22/2010 03:07 AM, Ulrich Weigand wrote:
> Yao Qi wrote:
>> On 12/15/2010 06:22 PM, Yao Qi wrote:
>>> Once this patch is applied, we leave more flexibility to backend to
>>> determine what is the correct register number given a register alias.
>>
>> This patch is to implement user_register_name on ARM.  With this, we can
>> handle alias "fp" according to the current frame's mode (ARM or Thumb).
>>
>> Regression testing is still running on ARM.  Comments are welcome.
> 
> I'm wondering why the ARM back-end actively defines "fp" as user register
> anyway.  If it simply were to *not* do so, GDB would fall back to the
> default implementation of $fp using value_of_builtin_frame_fp_reg, which
> seems to do always the correct thing anyway.  It returns the value of the
> frame base as returned by arm_normal_frame_base, which will have been
> determined from r11 or r7 as appropriate for the mode.

Good catch! set_gdbarch_deprecated_fp_regnum is called in
arm_gdbarch_init since 2003, introduced by this patch "Deprecate
TARGET_READ_FP, read_fp and FP_REGNUM"
http://sourceware.org/ml/gdb-patches/2003-04/msg00471.html

set_gdbarch_deprecated_fp_regnum is no longer used in most of targets,
and I don't see any reason why we have to keep it in ARM, so I draft
this one-line patch.

Any comments/objections to this one-line patch?  [Regression test is
still running.]

-- 
Yao (齐尧)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: remove_deprecated_fp_regnum.patch
Type: text/x-patch
Size: 612 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/gdb-patches/attachments/20101222/21bdd715/attachment.bin>