From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: brobecker@adacore.com, gdb-patches@sources.redhat.com
Subject: Re: Question regarding storing/restoring data during inferior function call
Date: Tue, 18 Oct 2005 20:00:00 -0000 [thread overview]
Message-ID: <200510181959.j9IJxJn2022154@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20051018191208.GA19167@nevyn.them.org> (message from Daniel Jacobowitz on Tue, 18 Oct 2005 15:12:08 -0400)
> Date: Tue, 18 Oct 2005 15:12:08 -0400
> From: Daniel Jacobowitz <drow@false.org>
> > 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?
>
> Maybe, maybe not. Might be the easiest answer. I'd suspect ia64
> dislikes executable stacks, though. Can you (ew) poke the necessary
> code into the entry point, assuming it is small enough? If it's just a
> jump to register...
On PA-RISC the C startup code provided some help here by providing
some of the code to do the branch with setting up the registers
correctly. I think libgcc also had some code to deal with it.
Perhaps there is some magic help on ia64 too?
Mark
prev parent reply other threads:[~2005-10-18 20:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-18 18:46 Joel Brobecker
2005-10-18 19:12 ` Daniel Jacobowitz
2005-10-18 20:00 ` Mark Kettenis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200510181959.j9IJxJn2022154@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=brobecker@adacore.com \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox