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:01:09 -0400 [thread overview]
Message-ID: <1082746870.1913.48.camel@mulgrave> (raw)
In-Reply-To: <200404231750.i3NHouD9019650@hiauly1.hia.nrc.ca>
On Fri, 2004-04-23 at 13:50, John David Anglin wrote:
> Yes, that's what gcc generates for PA 2.0.
>
> Regarding the assembler, I'm wondering if we want the keep "bl" for
> generating 17-bit branches. It's rather confusing and inconsistent
> with the mnemonic mapping given in the 2.0 manual. On the otherhand,
> gas has been this way for 4-5 years.
Yes, I think our current pressing problem is to discover why hppa64-ld
is generating out of range PCREL17F branches instead of stubbing them.
That's definitely what's causing the boot failure in 2.6.6-rc1-pa0.
It's so strange. Since the init section is quite a way away, it should
already be stubbing jumps to the init section. I can't work out why the
addition of yet another section (this time covering scheduler functions)
suddenly causes it to fail.
James
next prev parent reply other threads:[~2004-04-23 19:01 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 [this message]
2004-04-23 19:27 ` John David Anglin
2004-04-23 19:43 ` James Bottomley
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=1082746870.1913.48.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.