From: James E Wilson <wilson@tuliptree.org>
To: linux-ia64@vger.kernel.org
Subject: Re: PATCH: Fix 2.6 kernel for the new ia64 assembler
Date: Fri, 07 Oct 2005 18:19:51 +0000 [thread overview]
Message-ID: <1128709191.375.5.camel@aretha.corp.specifix.com> (raw)
In-Reply-To: <20051007180119.GA11645@lucon.org>
On Fri, 2005-10-07 at 11:01, H. J. Lu wrote:
> The new ia64 assembler uses slot 1 for the offset of a long (2-slot)
> instruction and the old assembler uses slot 2. The 2.6 kernel assumes
> slot 2 and won't boot when the new assembler is used:
Specifically, this is in reference to tags occurring immediately before
a long instruction.
Given something like
.text
nop
[L1:]
movl
The value of L1 should be .text+1 but it was incorrectly .text+2 until
about 2 weeks ago. Unfortunately, there is code in the kernel that
relies on the incorrect value, and needs to be fixed. H.J.'s patch
fixes this.
next prev parent reply other threads:[~2005-10-07 18:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 18:01 PATCH: Fix 2.6 kernel for the new ia64 assembler H. J. Lu
2005-10-07 18:05 ` David Mosberger-Tang
2005-10-07 18:19 ` James E Wilson [this message]
2005-10-07 19:27 ` Magenheimer, Dan (HP Labs Fort Collins)
2005-10-07 19:56 ` James E Wilson
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=1128709191.375.5.camel@aretha.corp.specifix.com \
--to=wilson@tuliptree.org \
--cc=linux-ia64@vger.kernel.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