From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60314) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xyn8h-0002Un-Jk for qemu-devel@nongnu.org; Wed, 10 Dec 2014 14:41:40 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xyn8c-0004TH-Kr for qemu-devel@nongnu.org; Wed, 10 Dec 2014 14:41:35 -0500 Received: from mail-lb0-f177.google.com ([209.85.217.177]:51726) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xyn8c-0004TB-DT for qemu-devel@nongnu.org; Wed, 10 Dec 2014 14:41:30 -0500 Received: by mail-lb0-f177.google.com with SMTP id b6so2858640lbj.22 for ; Wed, 10 Dec 2014 11:41:29 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: From: Peter Maydell Date: Wed, 10 Dec 2014 19:41:09 +0000 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [PATCH 1/3] target-mips: Add n32/n64 configuration files List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Maciej W. Rozycki" Cc: Leon Alrae , QEMU Developers , Aurelien Jarno On 10 December 2014 at 18:53, Maciej W. Rozycki wrote: > Mechanically add new n32/n64 configuration files copying the relevant > preexisting ones, fixing the system emulation configuration build, that > breaks due to the lack of the respective configuration files, for the > `mipsn32' and `mipsn32el' targets on this occasion as well. > > Signed-off-by: Maciej W. Rozycki > --- > To be applied first so as not to break the build and consequently > bisection with the configuration changes posted next. > > Maciej > > qemu-mips-configs.diff > Index: qemu-git-trunk/default-configs/mipsn32-softmmu.mak > Index: qemu-git-trunk/default-configs/mipsn32el-softmmu.mak > Index: qemu-git-trunk/default-configs/mipsn64el-linux-user.mak > Index: qemu-git-trunk/default-configs/mipsn64el-softmmu.mak Some of these look weird. n32 and n64 are ABIs, right? We shouldn't have extra -softmmu configs for different ABIs, the guest can deal with those. The MIPS config name variants that are only ABI related should only result in new -linux-user binaries (where we need a binary per Linux syscall ABI). thanks -- PMM