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 13:09:39 -0400 [thread overview]
Message-ID: <1082740179.2017.45.camel@mulgrave> (raw)
In-Reply-To: <200404231657.i3NGvBAP004762@hiauly1.hia.nrc.ca>
On Fri, 2004-04-23 at 12:57, John David Anglin wrote:
> The .level 2.0w should come before any actual assembly code. If the
> includes define any assembly code this could be a problem. The assembler
> isn't very smart about changing levels.
Well, yes, there were (just macros, though). However, I moved the level
setting right to the top of the file and it made no difference.
> Yes. The code is using "bl". It looks as if the assembler is
> generating a 17-bit branch (sub-opcode 0) when it sees a "bl"
> even when generating PA 2.0w code. This would appear to be
> wrong although I haven't checked what the HP assembler does.
> Can you use "b,l" for PA 2.0 code?
Well, the 2.0 manual implies b,l can be used whether the execution is in
wide or narrow mode, so yes, it should apply to all 2.0 code.
James
next prev parent reply other threads:[~2004-04-23 17:09 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 [this message]
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
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=1082740179.2017.45.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.