From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 50089138247 for ; Sun, 29 Dec 2013 21:49:26 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D4BCAE0ABB; Sun, 29 Dec 2013 21:49:25 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 5E606E0ABB for ; Sun, 29 Dec 2013 21:49:25 +0000 (UTC) Received: from [192.168.1.2] (unknown [176.253.32.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: hwoarang) by smtp.gentoo.org (Postfix) with ESMTPSA id 5215833F73D for ; Sun, 29 Dec 2013 21:49:24 +0000 (UTC) Message-ID: <52C098C8.4000601@gentoo.org> Date: Sun, 29 Dec 2013 21:48:56 +0000 From: Markos Chandras User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-mips@lists.gentoo.org Reply-to: gentoo-mips@lists.gentoo.org MIME-Version: 1.0 To: gentoo-mips@lists.gentoo.org Subject: Re: [gentoo-mips] Re: On MIPS using the same CHOST for all multilib ABIs References: <20131228235839.5bb0305a@gentoo.org> <52C096B8.1020302@gentoo.org> <20131229224806.66137df9@gentoo.org> In-Reply-To: <20131229224806.66137df9@gentoo.org> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Archives-Salt: 9d44c077-2499-4b72-961e-a50a4423d27d X-Archives-Hash: 8f8a0435e18f9c5a0841e0a19dbe7527 On 12/29/2013 09:48 PM, Michał Górny wrote: > Dnia 2013-12-29, o godz. 16:40:08 > Joshua Kinard napisał(a): > >> On 12/28/2013 5:58 PM, Michał Górny wrote: >>> I've noticed today that mips uses the same CHOST value for all three >>> ABIs it supports: >>> >>> arch/mips/mips64/multilib/make.defaults:CHOST_o32="${CHOST}" >>> arch/mips/mips64/multilib/make.defaults:CHOST_n32=${CHOST} >>> arch/mips/mips64/multilib/make.defaults:CHOST_n64=${CHOST} >>> arch/mips/mipsel/mips64el/multilib/make.defaults:CHOST_o32="${CHOST}" >>> arch/mips/mipsel/mips64el/multilib/make.defaults:CHOST_n32="${CHOST}" >>> arch/mips/mipsel/mips64el/multilib/make.defaults:CHOST_n64="${CHOST}" >>> >>> [...] >> >> Matt can probably vouch for this better, but the only two ABIs affected by >> this are n32 and n64. mips[el]-unknown-linux-gnu implies a 32-bit >> big/little endian CHOST, which means the o32 ABI. >> mips64[el]-unknown-linux-gnu means either n32 or n64. So no change should >> be needed for o32-based installs. > > Just to be clear: > > profiles/arch/mips/mipsel/mips64el/multilib/make.defaults: > > CHOST="mips64el-unknown-linux-gnu" > > [...] > > CFLAGS_o32="-mabi=32" > CHOST_o32="${CHOST}" > > CFLAGS_n32="-mabi=n32" > CHOST_n32="${CHOST}" > > CFLAGS_n64="-mabi=64" > CHOST_n64="${CHOST}" > > So in this case, o32 actually uses mips64el-unknown-linux-gnu, unless > I'm missing something. > Yes all 3 ABIs use the same tuple. -- Regards, Markos Chandras