Sparc64 support

[Baptiste Daroussin]

On Sun, Aug 09, 2015 at 09:34:33PM -0700, Jordan Hubbard wrote:
> 
> > On Aug 9, 2015, at 8:48 PM, Adrian Chadd <adrian.chadd at gmail.com> wrote:
> > 
> > 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:

Well external toolchain is know to work properly with sparc64 (without patches)
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)).
> 
> # cd /usr/src
> # make buildworld buildkernel USE_EXT_TOOLCHAIN=yes EXT_TOOLCHAIN_PORT=gcc-4.9 (or whatever the suitable incantation is?)
> 
> Does it have to work for multiple values of “external toolchain”?  Is it a safe assumption to just say that “port install FOO” 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’s 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?

me neither :)
> 
> > 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’t 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’t 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 “default toolchain” in base and any other value of GCC (which?) comes from ports?
>
That is the plan

Best regards,
Bapt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20150810/c37a5932/attachment.bin>