Re: [PATCH 7/8] ia64-hpux: unwinding bsp value from system call

Pedro Alves
2010-12-28T15:46:15Z

On Tuesday 28 December 2010 11:35:41, Joel Brobecker wrote:
> I will use a different object kind. I could create our own object kind,
> but someone it seems possible to have one that can be re-used by all
> targets.
>
> Some proposed names:
>
> TARGET_OBJECT_OSABI_SPECIFIC_DATA
> TARGET_OBJECT_OSABI_DATA
> TARGET_OBJECT_TARGET_SPECIFIC_DATA
> TARGET_OBJECT_TARGET_DATA
>
> Another option is to create feature-specific objects, but then I'm
> afraid the number of objects might steadily grow beyond reasonable
> (I need two, right now).
>
> The last option, is to follow the lead of some targets, and create
> a CPU-specific target object: TARGET_OBJECT_IA64.

What is the underlying object you're getting those values from?
I understood it to be whatever object TT_LWP_RUREGS accesses?
You seem to call it save_state_t? Why not TARGET_OBJECT_HPUX_RUREGS
or TARGET_OBJECT_HPUX_SAVE_STATE, or something along those lines?
Then, the offset, and length passed to target_xfer would the
the offset and length you're currently passing to
ia64_hpux_read_register_from_save_state_t. This would allow
(if useful) exporting this object similarly to the $_siginfo and
$_tlb objects.

--
Pedro Alves