[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <62749.94.211.195.167.1299645589.squirrel@gate.crashing.org>
Date: Wed, 9 Mar 2011 05:39:49 +0100 (CET)
From: "Segher Boessenkool" <segher@...nel.crashing.org>
To: "Kyle Moffett" <kyle@...fetthome.net>
Cc: "Benjamin Herrenschmidt" <benh@...nel.crashing.org>,
"Ingo Molnar" <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
"Thomas Gleixner" <tglx@...utronix.de>,
"linux-kbuild" <linux-kbuild@...r.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
"Andrew Morton" <akpm@...ux-foundation.org>,
linuxppc-dev@...ts.ozlabs.org,
"Kyle Moffett" <kyle.d.moffett@...ing.com>,
"Kumar Gala" <kumar.gala@...escale.com>
Subject: Re: RFC: x86: kill binutils 2.16.x?
> The problem is not with the kernel compile itself, but with the 2.12
> "dssall" binutils test. Basically, recent binutils treats e500 as
> effectively a separate architecture that happens to share *most* of
> the opcodes with regular PowerPC. Any opcode which is not understood
> by the e500 chip is either convert to an equivalent opcode which is
> understood (IE: lwsync => sync), or failed with an error. This means
> that the kernel compile aborts early telling me to upgrade to a newer
> version of binutils.
$ echo dssall | powerpc-linux-as -many -me500
$ powerpc-linux-objdump -d a.out | grep 0:
0: 7e 00 06 6c dssall
$ powerpc-linux-as --version | head -1
GNU assembler (GNU Binutils) 2.21.51.20110309
What version of binutils does not work? (I also checked with
-me500x2, -me500mc, -mspe, and various combinations. lwsync
is indeed converted to a regular sync (well, "msync") for e500
and e500x2).
Segher
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists