From: Randolph Chung <randolph@tausq.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] interesting linker behaviour :)
Date: Tue, 21 Sep 2004 12:49:39 -0700 [thread overview]
Message-ID: <20040921194939.GT22642@tausq.org> (raw)
In-Reply-To: <200409211851.i8LIpT1Z009455@hiauly1.hia.nrc.ca>
> Good catch! I've hit this problem before but under HP-UX. GAS doesn't
> support the alternate entry point fixup needed to support multiple
> entry points to a function. I don't think anyone has tried to support
> this with the ELF tools. There could be some nasty interactions with
> the HP unwind data when you start adding multiple entry points to a
> function.
yeah, it will break unwinding :(
> I haven't looked at this in detail but possibly you can change the
> fixup table to contain pc-relative offsets. I looked at this
> when I reworked the casesi pattern in GCC a few months ago. This
> makes the table smaller and in many cases the number of instructions
> is less than that with branches in the table (particularly for the
> PIC case).
well, this is what we used to do, but we don't do this now because it
requires us to be able to do a pc-relative calculation between code in
two different sections (text and fixup), and GAS doesn't allow that
either.
for now i'm using the solution we are using for 64-bit code, which is to
use a manually created long-branch stub (ldil/ldo/bv). since this is
anyway in a slow-path the performance hit is probably negligible.
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2004-09-21 19:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-21 17:22 [parisc-linux] interesting linker behaviour :) Randolph Chung
2004-09-21 17:43 ` Carlos O'Donell
2004-09-21 17:46 ` Carlos O'Donell
2004-09-21 18:51 ` John David Anglin
2004-09-21 19:49 ` Randolph Chung [this message]
2004-09-21 20:06 ` John David Anglin
2004-09-21 20:20 ` John David Anglin
2004-09-21 20:36 ` Randolph Chung
2004-09-21 22:04 ` Carlos O'Donell
2004-09-21 22:19 ` Carlos O'Donell
2004-09-21 22:21 ` John David Anglin
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=20040921194939.GT22642@tausq.org \
--to=randolph@tausq.org \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=parisc-linux@lists.parisc-linux.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