From: Helge Deller <deller@gmx.de>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: Carlos O'Donell <carlos@systemhalted.org>,
elendil@planet.nl, 539378@bugs.debian.org,
debian-hppa@lists.debian.org, linux-parisc@vger.kernel.org,
randolph@tausq.org, submit@bugs.debian.org
Subject: Re: Bug#539378: [hppa]: fails to load nfs module: Global Offset Table
Date: Fri, 31 Jul 2009 23:09:47 +0200 [thread overview]
Message-ID: <4A735D9B.30200@gmx.de> (raw)
In-Reply-To: <20090731190304.C7BF55161@hiauly1.hia.nrc.ca>
On 07/31/2009 09:03 PM, John David Anglin wrote:
>> Only 32-bit targets have the 14-bit signed immediate offset (0x3fff),
>> which becomes a 13-bit limit when loading positive offsets e.g.
>> +0x1fff or 1023 GOT slots.
>
> Can't we offset the table and double the number of entries?
Dave,
Can you explain this idea a little more?
Helge
next prev parent reply other threads:[~2009-07-31 21:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090731091729.1105.20608.reportbug@aragorn.fjphome.nl>
2009-07-31 18:49 ` Bug#539378: [hppa]: fails to load nfs module: Global Offset Table overflow Carlos O'Donell
2009-07-31 19:03 ` Bug#539378: [hppa]: fails to load nfs module: Global Offset Table John David Anglin
2009-07-31 21:09 ` Helge Deller [this message]
2009-07-31 21:13 ` Carlos O'Donell
2009-07-31 21:14 ` Carlos O'Donell
2009-07-31 21:26 ` John David Anglin
2009-07-31 22:00 ` Carlos O'Donell
2009-07-31 23:38 ` Kyle McMartin
2009-07-31 23:45 ` Helge Deller
2009-07-31 0:37 ` John David Anglin
2009-07-31 1:16 ` John David Anglin
2009-08-01 1:51 ` Carlos O'Donell
2009-08-01 13:53 ` John David Anglin
2009-08-01 19:07 ` John David Anglin
2009-08-01 20:02 ` Carlos O'Donell
2009-08-01 21:17 ` Frans Pop
2009-08-01 8:08 ` Frans Pop
2009-08-01 1:49 ` Carlos O'Donell
2009-07-31 21:08 ` Bug#539378: [hppa]: fails to load nfs module: Global Offset Table overflow Helge Deller
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=4A735D9B.30200@gmx.de \
--to=deller@gmx.de \
--cc=539378@bugs.debian.org \
--cc=carlos@systemhalted.org \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=debian-hppa@lists.debian.org \
--cc=elendil@planet.nl \
--cc=linux-parisc@vger.kernel.org \
--cc=randolph@tausq.org \
--cc=submit@bugs.debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.