Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 02 Jun 2010 09:04:22 -0600 (MDT)
From:      "M. Warner Losh" <imp@bsdimp.com>
To:        c.jayachandran@gmail.com
Cc:        freebsd-mips@freebsd.org
Subject:   Re: HEADS UP: Toolchain changes coming soon. (Octeon, n32, n64)
Message-ID:  <20100602.090422.862433495782007974.imp@bsdimp.com>
In-Reply-To: <AANLkTiksE5HAN9gz_4FVRUYYtGWHG7jmLOWVSoLAC_U-@mail.gmail.com>
References:  <AANLkTilYyTZRFvkly897pFgnISE9npT9BM1yuOiQr3rx@mail.gmail.com> <20100602.073644.695112013731480233.imp@bsdimp.com> <AANLkTiksE5HAN9gz_4FVRUYYtGWHG7jmLOWVSoLAC_U-@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
In message: <AANLkTiksE5HAN9gz_4FVRUYYtGWHG7jmLOWVSoLAC_U-@mail.gmail.c=
om>
            "C. Jayachandran" <c.jayachandran@gmail.com> writes:
: On Wed, Jun 2, 2010 at 7:06 PM, M. Warner Losh <imp@bsdimp.com> wrote=
:
: > In message: <AANLkTilYyTZRFvkly897pFgnISE9npT9BM1yuOiQr3rx@mail.gma=
il.com>
: > =A0 =A0 =A0 =A0 =A0 =A0"C. Jayachandran" <c.jayachandran@gmail.com>=
 writes:
: > : On Tue, Jun 1, 2010 at 2:53 PM, Juli Mallett <jmallett@freebsd.or=
g> wrote:
: > : > On Tue, Jun 1, 2010 at 02:17, C. Jayachandran <c.jayachandran@g=
mail.com> wrote:
: > : >> That clears it up, thanks. =A0Looking at the patch, most of th=
e 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 =
toolchain
: > : >> is synchronized across architectures - are all architectures a=
t the
: > : >> same version of binutils, or can each architecture decide to u=
pdate
: > : >> its part of the tool-chain.
: > : >
: > : > I pulled some files from a slightly more modern version of binu=
tils
: > : > from a Cavium SDK than ours and reduced differences to make the=

: > : > relevant parts of code match the older binutils API we provide,=
 while
: > : > still providing the newer opcode interface and a couple of near=
by
: > : > things.
: > : >
: > : >>> Is there specific functionality you need in GCC?
: > : >>
: > : >> Netlogic has some updates for GCC and binutils in its SDK. But=
 they
: > : >> are not critical, and we have not merged these into the FreeBS=
D. =A0I
: > : >> was not sure if I can get these changes into FreeBSD directly.=

: > : >
: > : > If Netlogic can GPLv2 their specific changes or reimplement the=
m
: > : > relative to FreeBSD's toolchain, I think we would want to coord=
inate
: > : > to get them into the tree. =A0Our goal is generally to produce =
a
: > : > fully-working self-hosting system out of the box. =A0That may c=
hange at
: > : > some point, especially if Warner's work on supporting external
: > : > toolchains better pans out well, but I think for now it's a rea=
sonable
: > : > 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. =A0=
Our
: > : patch for GCC is for adding 'xlr' machine description and march/m=
tune
: > : options. The binutils patch is for a few XLR specific instruction=
s for
: > : which we currently '.word' in assembly for. =A0So both of these a=
re not
: > : really needed.
: > :
: > : Also licensing should not be an issue here - =A0I'll have a go at=
 this
: > : 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 differe=
nces
: > : > required for mips64r2 and Octeon substantially-smaller and I wo=
uld
: > : > 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. =A0Bas=
ed 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.  How will there not be license
issues?

Warner



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100602.090422.862433495782007974.imp>