Re: Minimum gcc and clang supported to generate FreeBSD binaries

On Jun 19, 2024, at 6:01 PM, Warner Losh <imp@bsdimp.com> wrote:
> 
> Ah, but what do you say about tcc and pcc which are't gcc? Well, tcc lies, and says it supports gcc (version 9 I think, but it's been a while since I checked). tcc can't work today because we have qsort.h using versioned symbols unconditionally, and it doesn't support versioned symbols.... And patches to do that have been stalled for reasons unrelated to this desire. pcc doesn't support gnuc symbols at all last I checked. But it has real issues building some things in the tree, so I'll not gate things by it unless somebody steps up to actually do the work to make it work. The pcc upstream has been weird lately too.

Why are versioned symbols required for qsort.h?

Can we maintain freebsd specific hack in tcc port?

Compiling with tcc is sooo much faster. That is more important to me than the speed of the running code - at least during development. tcc does require more work than just support for versioned symbols....

Just as the build is ideally portable to more platforms (linux, macos) it should be portable to more compilers & to resist temptation to rely on compiler specific features. 

Personally I'd prefer if clang+llvm was picked up from a port and not part of the freebsd sources -- to keep them somewhat more portable  and to cut down on buildworld time. Ok by me if only specific version(s) are supported for a given compiler.

Thanks for all the cleanup in any case.