Re: RFA: New port: ia64-hp-openvms - the stub

[Pedro Alves <palves@redhat.com>]

On 02/24/2012 08:34 AM, Tristan Gingold wrote:
> 
> On Feb 22, 2012, at 8:52 PM, Pedro Alves wrote:
> 
>> On 02/21/2012 04:30 PM, Tristan Gingold wrote:
>>>
>>> On Feb 14, 2012, at 7:08 PM, Pedro Alves wrote:
>>
>>>> I couldn't really tell, but you may want to consider looking into xml target
>>>> descriptions.  At least reporting a description with the openvms osabi would
>>>> be good.
>>>
>>> I plan to fix the register issue soon, just be patient !
>>
>> I am.  :-)  A description with at least the osabi is good so that gdb
>> knows the target's osabi even if the user doesn't supply an executable.
> 
> Ok, shouldn't be hard to do.  Just to implement qXfer:features:read, IIUC.

Yeah.

>>>>> +#if 1
>>>>> +      /* What a mess.  Gdb and linux expects bsp to point after the current
>>>>> +         register frame.  Adjust.  */
>>>>
>>>> What does this mean?  Are we committing to a hack that will make our
>>>> lives hard when we want to fix it?
>>>
>>> I have updated the comment.  Currently, ia64-tdep.c follows the Linux convention, and we don't want to change that.  So the BSP has to be adjusted.
>>
>> Why don't we want to change it?
> 
> I think it's too late.  That would be a change in gdbserver and other stubs, so it would break compatibility.  

We have ways to make it happen without breaking other stubs.  The question is what is the
right thing to do.  Is this really Linux specific?  We have ia64 hpux support as well.
I take it libunwind must follow the same convention as well, and I hope a libunwind
built on a Linux host doesn't behave different from a libunwind built on a
different host.

The adjustment in the VMS stubs isn't that complex.

Hopefully it'll still be simple with infcalls in the game.  :-)  afaics, you're
not undoing the adjustment on writes.

-- 
Pedro Alves