From: David Woodhouse <dwmw2@infradead.org>
To: Chris Friesen <cfriesen@nortel.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: new binutils breaks "tlbie" instruction in kernel?
Date: Fri, 04 Feb 2005 10:11:30 +0000 [thread overview]
Message-ID: <1107511891.18239.48.camel@baythorne.infradead.org> (raw)
In-Reply-To: <42023D23.6020406@nortel.com>
On Thu, 2005-02-03 at 09:02 -0600, Chris Friesen wrote:
> > Wasn't it fixed ?
>
> Not sure what "it" you mean. The current kernel code does not have the
> third parm. I'm not sure about the latest binutils, but 2.15.92.0.2 is
> what a vendor wants to build on.
Binutils was changed in early September last year to require the extra
argument. We objected, and it was fixed again about a month later to
_not_ require the argument. If you're using 2.15.92.0.2, then apply this
patch to it:
2004-10-09 Alan Modra <amodra@bigpond.net.au>
* ppc-opc.c: Revert 2004-09-09 change.
--- opcodes/ppc-opc.c 7 Oct 2004 15:34:08 -0000 1.76
+++ opcodes/ppc-opc.c 9 Oct 2004 01:21:03 -0000 1.77
@@ -300,7 +300,7 @@ const struct powerpc_operand powerpc_ope
/* The L field in a D or X form instruction. */
#define L FXM4 + 1
- { 1, 21, 0, 0, 0 },
+ { 1, 21, 0, 0, PPC_OPERAND_OPTIONAL },
/* The LEV field in a POWER SC form instruction. */
#define LEV L + 1
--
dwmw2
next prev parent reply other threads:[~2005-02-04 10:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 18:39 new binutils breaks "tlbie" instruction in kernel? Chris Friesen
2005-02-03 5:13 ` Benjamin Herrenschmidt
2005-02-03 5:55 ` Kumar Gala
2005-02-03 15:02 ` Chris Friesen
2005-02-04 10:11 ` David Woodhouse [this message]
2005-02-04 0:55 ` Segher Boessenkool
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=1107511891.18239.48.camel@baythorne.infradead.org \
--to=dwmw2@infradead.org \
--cc=cfriesen@nortel.com \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).