From: Randolph Chung <randolph@tausq.org>
To: mark Kettenis <kettenis@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/RFA/hppa] Make the stub identification code smarter
Date: Thu, 18 Nov 2004 17:11:00 -0000 [thread overview]
Message-ID: <20041118171109.GN15714@tausq.org> (raw)
In-Reply-To: <200411181701.iAIH1RPE026059@juw15.nfra.nl>
> AFAIK the BSD's don't use a segmented memory model, and therefore
> don't use stubs, but I'm not completely sure about that.
neither does hppa-linux. The stubs are not for that... they are for
calling shlib functions and to handle long branches (since for pa11 the
branch target for a b,l insn is only 17 bits)
> Now that I think of it, OpenBSD/hppa didn't have shared libraries
> until very recently.
ok, anyway, just a heads up in case the code is useful for hppabsd too
:)
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
prev parent reply other threads:[~2004-11-18 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 1:23 Randolph Chung
2004-11-18 17:01 ` mark Kettenis
2004-11-18 17:11 ` Randolph Chung [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=20041118171109.GN15714@tausq.org \
--to=randolph@tausq.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@gnu.org \
/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