Date: Sun, 09 Aug 2015 21:34:33 -0700 From: Jordan Hubbard <jordanhubbard@me.com> To: Adrian Chadd <adrian.chadd@gmail.com> Cc: Bill Sorenson <instructionset@gmail.com>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, Kevin Bowling <kevin.bowling@kev009.com>, "K. Macy" <kmacy@freebsd.org> Subject: Re: Sparc64 support Message-ID: <926DDA42-8883-4AB4-B229-D44387FF5C6B@me.com> In-Reply-To: <CAJ-VmomzV0YKQwenwSZv6fMAOUP8TmPs-oyQaM8KTF7Ndhv_%2Bw@mail.gmail.com> References: <CACcTwYmS1c5uoO-WiJQDwgqYAevX7WZ7ZrP297hnOu7cNET3CA@mail.gmail.com> <mq3sg1$bno$1@ger.gmane.org> <CACcTwYnU=E-6sV3yLh3yKUSPZOg7967XV5ToXoSVPuNfOjF7hQ@mail.gmail.com> <CAHM0Q_NEYWxpHCwEdytfY6i9%2BRO2BebezzmenfQ_1c4u7zGrgg@mail.gmail.com> <CACcTwY=DcUREt5nJWo_eJfrB=3sQXBaS6nc%2B07fpZhxARD0zTQ@mail.gmail.com> <20150809215403.GC20238@server.rulingia.com> <6C12EBFE-EAA9-4C12-9F03-1CB2C28C4A6E@me.com> <CACcTwYktQRTqVSr7PRr5huwbVXVu6oCy26TKiAxzf2NiGAcocA@mail.gmail.com> <51EEBC6E-5D85-439D-874D-D223EE045515@me.com> <CAJ-VmomzV0YKQwenwSZv6fMAOUP8TmPs-oyQaM8KTF7Ndhv_%2Bw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Aug 9, 2015, at 8:48 PM, Adrian Chadd <adrian.chadd@gmail.com> = wrote: >=20 > What's missing is someone funding / finishing the push to external > toolchain support for all platforms. Does someone have that condensed down to a set of bullet points? Which = platforms are mandatory and which are optional? Is the task considered = done when one can do: # cd /usr/src # make buildworld buildkernel USE_EXT_TOOLCHAIN=3Dyes = EXT_TOOLCHAIN_PORT=3Dgcc-4.9 (or whatever the suitable incantation is?) 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=9Cpor= t 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 obviously). If anyone is going to fund anything, they will want a very specific set = of deliverables to fund, since it=E2=80=99s otherwise kind of a blank = check with a completely arbitrary outcome. > 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. Not sure what that means? > 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. Again, maybe you could qualify just what that means. I don=E2=80=99t = know 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. :) > 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. 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? - Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?926DDA42-8883-4AB4-B229-D44387FF5C6B>