From owner-freebsd-mips@FreeBSD.ORG Wed Jun 2 15:32:43 2010 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 078EC106568A; Wed, 2 Jun 2010 15:32:43 +0000 (UTC) (envelope-from c.jayachandran@gmail.com) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id C639F8FC17; Wed, 2 Jun 2010 15:32:42 +0000 (UTC) Received: by pwj1 with SMTP id 1so1414075pwj.13 for ; Wed, 02 Jun 2010 08:32:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=tSidn337UvTxDbRgXExOg99Z4lYaT77CwGgc26u1pTg=; b=w+OohQ1D3aMtITN+p4VblSkWMWXu+uBX34V8hmD1k96f4YE7u/LRn6mteivDe2WfJR mEBy6iLhfpQSbEjozudCVCflK8qpITpomtzDo4/LW49ABbiT3pJM1+f8pYzXiDrfq3rN Fb4qwue4jr5CnT5JP2kYj65HHyhavvRN8kyHg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=W0Ljj/uLB8G5v/xNI9ppRtJLudC3KNMsGzx3aYUYYsSe91NpbhkmNpxUcbUjqvrCso iLXn3PuOWzuGzkncVbWUCZwTI6q1iKWLrhUYGJosGHn0codlCDTJXEnuGRPZxkkd7/Cl KtQ/GtU6UU+Xb9VnZN7MvC+IHR7fLCPBPNdn4= MIME-Version: 1.0 Received: by 10.140.56.18 with SMTP id e18mr6610150rva.167.1275492762153; Wed, 02 Jun 2010 08:32:42 -0700 (PDT) Received: by 10.141.4.3 with HTTP; Wed, 2 Jun 2010 08:32:42 -0700 (PDT) In-Reply-To: <20100602.090422.862433495782007974.imp@bsdimp.com> References: <20100602.073644.695112013731480233.imp@bsdimp.com> <20100602.090422.862433495782007974.imp@bsdimp.com> Date: Wed, 2 Jun 2010 21:02:42 +0530 Message-ID: From: "C. Jayachandran" To: "M. Warner Losh" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-mips@freebsd.org Subject: Re: HEADS UP: Toolchain changes coming soon. (Octeon, n32, n64) X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2010 15:32:43 -0000 On Wed, Jun 2, 2010 at 8:34 PM, M. Warner Losh wrote: > In message: > =A0 =A0 =A0 =A0 =A0 =A0"C. Jayachandran" write= s: > : On Wed, Jun 2, 2010 at 7:06 PM, M. Warner Losh wrote: > : > In message: > : > =A0 =A0 =A0 =A0 =A0 =A0"C. Jayachandran" w= rites: > : > : On Tue, Jun 1, 2010 at 2:53 PM, Juli Mallett = wrote: > : > : > On Tue, Jun 1, 2010 at 02:17, C. Jayachandran wrote: > : > : >> That clears it up, thanks. =A0Looking at the patch, most of the = changes > : > : >> seems to be in binutils, are these from a specific version of > : > : >> binutils? =A0I am asking because I'm not sure how the FreeBSD to= olchain > : > : >> is synchronized across architectures - are all architectures at = the > : > : >> same version of binutils, or can each architecture decide to upd= ate > : > : >> its part of the tool-chain. > : > : > > : > : > I pulled some files from a slightly more modern version of binuti= ls > : > : > from a Cavium SDK than ours and reduced differences to make the > : > : > relevant parts of code match the older binutils API we provide, w= hile > : > : > still providing the newer opcode interface and a couple of nearby > : > : > things. > : > : > > : > : >>> Is there specific functionality you need in GCC? > : > : >> > : > : >> Netlogic has some updates for GCC and binutils in its SDK. But t= hey > : > : >> are not critical, and we have not merged these into the FreeBSD.= =A0I > : > : >> was not sure if I can get these changes into FreeBSD directly. > : > : > > : > : > If Netlogic can GPLv2 their specific changes or reimplement them > : > : > relative to FreeBSD's toolchain, I think we would want to coordin= ate > : > : > to get them into the tree. =A0Our goal is generally to produce a > : > : > fully-working self-hosting system out of the box. =A0That may cha= nge at > : > : > some point, especially if Warner's work on supporting external > : > : > toolchains better pans out well, but I think for now it's a reaso= nable > : > : > goal. > : > : > : > : Stock binutils and GCC works fine for XLR (it is mips64 compliant),= so > : > : XLR is self-hosting with the current FreeBSD MIPS tool-chain. =A0Ou= r > : > : patch for GCC is for adding 'xlr' machine description and march/mtu= ne > : > : options. The binutils patch is for a few XLR specific instructions = for > : > : which we currently '.word' in assembly for. =A0So both of these are= not > : > : really needed. > : > : > : > : Also licensing should not be an issue here - =A0I'll have a go at t= his > : > : once the other toolchain changes are in. > : > : > : > : > Note that my understanding is that David O'Brien is working on > : > : > bringing in the last GPLv2 binutils which will make the differenc= es > : > : > required for mips64r2 and Octeon substantially-smaller and I woul= d > : > : > hope for Netlogic processors as well. > : > > : > One thing that I'm told, but haven't verified, is that the binutils > : > from the XLR SDK breaks other mips platforms in subtle ways. =A0Based= on > : > this assertion, I think it would be prudent to carefully review and > : > test any proposed patches from that SDK. > : > : Our gcc and binutils patches are in the latest releases (IIRC - GCC > : went in about 4.4 and binutils patches are in 2.20), so it has gone > : thru some testing. > > On the one hand, that's cool! > > On the other, if they are in those releases, then it is GPLv3 code. > FSF requires ownership assignment. =A0How will there not be license > issues? We have these changes against the older (GPLv2) tool-chains in the SDK. I brought up the later versions just to clarify the testing and review status. JC.