From owner-freebsd-hackers@freebsd.org Mon Aug 10 09:00:59 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 97BB699D4BA for ; Mon, 10 Aug 2015 09:00:59 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 269B0217; Mon, 10 Aug 2015 09:00:59 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: by wibhh20 with SMTP id hh20so141062781wib.0; Mon, 10 Aug 2015 02:00:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=WgfFADROFBL8MLqSzgoLWesxPsBrDDQ95/rcVTdvcxM=; b=z4WDiDOIFCZVGEfcSKVr2wgZDgZ1cswsuWWfGILMDB01rhoOwJSwlB4QKSIvVwTzJ1 WSI/7zqSEemQuPQTuFPUshiU/ptYF9FfNwj8Zlmegem9mVxG/z+lGelEiW6IBuzj8Wia 3yCT+CQUV2hHGpYS8/Tm1cAE8Qc2Ux12K6JWiSLqZ3Iwk0XqwMeCWo6bfYEuR9lClkxD 5oFe8482ocytYYPOrTvanaB4jWZI38mQzqqc1stqo+0cJKJxy9TLNOBJJCPnl/QjxA1U Z8N2jmUkb7meheZa/Vo4UP1sGzIBGkLQUS8Faqr48tePn12juz4S/I3uxWKdOyYzJsIf N8yQ== X-Received: by 10.194.61.10 with SMTP id l10mr41554779wjr.138.1439197257551; Mon, 10 Aug 2015 02:00:57 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by smtp.gmail.com with ESMTPSA id fb3sm12649983wib.21.2015.08.10.02.00.55 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 Aug 2015 02:00:56 -0700 (PDT) Sender: Baptiste Daroussin Date: Mon, 10 Aug 2015 11:00:54 +0200 From: Baptiste Daroussin To: Jordan Hubbard Cc: Adrian Chadd , "freebsd-hackers@freebsd.org" , "K. Macy" , Kevin Bowling , Bill Sorenson Subject: Re: Sparc64 support Message-ID: <20150810090054.GF96980@ivaldir.etoilebsd.net> References: <20150809215403.GC20238@server.rulingia.com> <6C12EBFE-EAA9-4C12-9F03-1CB2C28C4A6E@me.com> <51EEBC6E-5D85-439D-874D-D223EE045515@me.com> <926DDA42-8883-4AB4-B229-D44387FF5C6B@me.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="w3uUfsyyY1Pqa/ej" Content-Disposition: inline In-Reply-To: <926DDA42-8883-4AB4-B229-D44387FF5C6B@me.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2015 09:00:59 -0000 --w3uUfsyyY1Pqa/ej Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 09, 2015 at 09:34:33PM -0700, Jordan Hubbard wrote: >=20 > > On Aug 9, 2015, at 8:48 PM, Adrian Chadd wrote: > >=20 > > What's missing is someone funding / finishing the push to external > > toolchain support for all platforms. >=20 > Does someone have that condensed down to a set of bullet points? Which p= latforms are mandatory and which are optional? Is the task considered done= when one can do: Well external toolchain is know to work properly with sparc64 (without patc= hes) with mips with patches, I used to work with powerpc64 (haven't tried others= ). This was based on gcc 4.9 and has been updated to 5.2 recently. What is missing so far is the chicken egg problem that happen once you have= boot your newly built FreeBSD because you do not have a compiler, one would need= to work on a mechanism to be able to provide at least all the set of packages = until having a working compiler so one can pkg install gcc. (there is work in that direction but not that much, at least now installworld is installing stuff = this is usable as a sysroot (in 99% of the cases)). >=20 > # cd /usr/src > # make buildworld buildkernel USE_EXT_TOOLCHAIN=3Dyes EXT_TOOLCHAIN_PORT= =3Dgcc-4.9 (or whatever the suitable incantation is?) >=20 > Does it have to work for multiple values of =E2=80=9Cexternal toolchain= =E2=80=9D? Is it a safe assumption to just say that =E2=80=9Cport install = FOO=E2=80=9D will be a sufficient prerequisite and /usr/local/bin/cc is all= one needs to reference as the right compiler driver (for the C stuff obvio= usly). >=20 > If anyone is going to fund anything, they will want a very specific set o= f deliverables to fund, since it=E2=80=99s otherwise kind of a blank check = with a completely arbitrary outcome. >=20 > > What's also missing a little bit here is the tier-1-ness of the > > external toolchain support by the people using/developing other > > toolchains. >=20 > Not sure what that means? me neither :) >=20 > > It's basically there. There are some rough edges, but since the > > compiler-developer people aren't using it and the non-x86-building > > people aren't being forced to use it, the development inches along > > very slowly. >=20 > Again, maybe you could qualify just what that means. I don=E2=80=99t kno= w what moving parts are even really being described here. My life is clang= / LLVM and has been for a very long time - I don=E2=80=99t even know what = gcc is anymore. :) >=20 > > If you'd like to erm, "rush" this along, we should actively start the > > "deorbit gcc-4.2 by freebsd-11" and "disconnect gcc-4.2 from the -head > > build" movement now, get those bits done, and start arm-twisting to > > get the last bits finished. >=20 > If gcc 4.2 de-orbits then that means that clang / LLVM can take its place= as the =E2=80=9Cdefault toolchain=E2=80=9D in base and any other value of = GCC (which?) comes from ports? > That is the plan Best regards, Bapt --w3uUfsyyY1Pqa/ej Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlXIaEYACgkQ8kTtMUmk6EyuXACeOVt268VducpnlIBmcbxC9EoB kvAAni5lX+HlnM2FeEGUqCPqGVD5JY9y =dJkE -----END PGP SIGNATURE----- --w3uUfsyyY1Pqa/ej--