Question regarding storing/restoring data during inferior function call

[Joel Brobecker <brobecker@adacore.com>]

Hello,

I'm working on inferior function calls on ia64-hpux (which I'd like to
eventually contribute), and I've hit a glitch: HPUX does not allow us
to modify the BSP register. So this prevents us from creating a new
RSE frame for the function being called.

One way around this problem that I thought about was to keep the BSP
as is. This meant adjusting a bit the addresses where the arguments
were saved. But more importantly, this meant that we overwrote the
output section of the register frame.

It's pretty easy to add some code in GDB to save this data, either
on the inferior stack frame or perhaps directly in debugger memory.
However, I don't see a clear way for us to do the restoration. Is
there any?

Right now, the inferior function call is made AT_ENTRY_POINT. One
way to solve my problem that might work is to make the call ON_STACK.
Not sure if that's allowed on this chip.  But this way, I can
dynamically create a small piece of code that does the branch to the
target function, which would implicitly cause the BSP update that
we're currently doing ourselves. This does open a whole can of worms,
though, as I think I'll need to revisit the entire dummy frame unwinder,
won't I?

Any suggestion? The simplest for me would probably to add an extra
mechanism to do associate a restore procedure to the popping of the
dummy frame (or something like that), where I believe the registers
are restored.

Thanks,
-- 
Joel