From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id D5E09B6EEE for ; Wed, 9 Mar 2011 15:40:22 +1100 (EST) Message-ID: <62749.94.211.195.167.1299645589.squirrel@gate.crashing.org> In-Reply-To: References: <4D6E8932.1010405@zytor.com> <4D6EB07C.5040004@zytor.com> <4D6ECBDB.6090307@zytor.com> <20110303083035.GB14854@elte.hu> <1299619716.22236.32.camel@pasglop> Date: Wed, 9 Mar 2011 05:39:49 +0100 (CET) Subject: Re: RFC: x86: kill binutils 2.16.x? From: "Segher Boessenkool" To: "Kyle Moffett" MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Cc: Andrew Morton , linux-kbuild , Kumar Gala , Linux Kernel Mailing List , Kyle Moffett , "H. Peter Anvin" , Ingo Molnar , linuxppc-dev@lists.ozlabs.org, Thomas Gleixner List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , > 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