All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: PARISC list <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] Panic on boot in 64 bit 2.6.6-rc1-pa0
Date: 23 Apr 2004 15:43:42 -0400	[thread overview]
Message-ID: <1082749422.1913.54.camel@mulgrave> (raw)
In-Reply-To: <200404231927.i3NJR33f016630@hiauly1.hia.nrc.ca>

On Fri, 2004-04-23 at 15:27, John David Anglin wrote:
> I think I know why.  The 64-bit linker only supports a single stub
> table.  Things go bad when a branch can't reach its stub.  I hit this
> when I was trying to implement tail calls.

That's a bit, um, unfortunate, given the current kernel predisposition
for adding a new section for almost every new feature...

How hard would it be to fix this?  Surely all we really need is one stub
table per text section in the final executable (linux still has only
about five executable sections in the vmlinux.lds.S map).

James

  reply	other threads:[~2004-04-23 19:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-22 22:32 [parisc-linux] Panic on boot in 64 bit 2.6.6-rc1-pa0 James Bottomley
2004-04-22 22:50 ` John David Anglin
2004-04-22 22:54   ` James Bottomley
2004-04-22 23:13     ` John David Anglin
2004-04-23 12:46       ` James Bottomley
2004-04-23 13:40         ` John David Anglin
2004-04-23 13:51           ` James Bottomley
2004-04-23 16:57             ` John David Anglin
2004-04-23 17:09               ` James Bottomley
2004-04-23 17:50                 ` John David Anglin
2004-04-23 19:01                   ` James Bottomley
2004-04-23 19:27                     ` John David Anglin
2004-04-23 19:43                       ` James Bottomley [this message]
2004-04-23 20:13                         ` 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=1082749422.1913.54.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --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 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.