how long to keep support for gcc on x86?

[Warner Losh]

On Jan 12, 2013, at 8:30 PM, Adrian Chadd wrote:

> IMHO gcc shuld be available until all of the platforms that we
> currently ship FreeBSD on gets clang support.
> 
> This includes MIPS (which is there, but I don't think the default MIPS
> build uses clang at the moment) and ia64, which Marcel has been
> dutifully working on.
> 
> Please also note that people can and will compile FreeBSD on a
> non-default-system compiler ; so deprecating gcc (either support or
> framework) should be considered carefully.


When this was talked about at the clang summit, the overwhelming opinion expressed was "better with clang". If you can make things better with clang, great. However, gcc still must work.

So no. You can't break gcc build of the kernel. You can make it better with clang, but you must still support gcc, especially for something like this.

Warner

> 
> Adrian
> 
> 
> On 12 January 2013 17:42, Steve Kargl <sgk at troutmask.apl.washington.edu> wrote:
>> On Sat, Jan 12, 2013 at 03:31:47PM -0800, John-Mark Gurney wrote:
>>> So, now that -current x86 is defaulting to clang, how much longer do we
>>> need to support gcc on platforms that default to clang?
>> 
>> IMHO, gcc should be available until after 10.0 is branched.
>> 
>>> I'm asking because clang support AES-NI, but gcc does not...
>> 
>> The last and only time I had for testing clang's handling
>> of floating point revealed that clang had a few bugs and
>> performance issues.
>> 
>> --
>> Steve
>> _______________________________________________
>> freebsd-arch at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-arch
>> To unsubscribe, send any mail to "freebsd-arch-unsubscribe at freebsd.org"
> _______________________________________________
> freebsd-arch at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-arch
> To unsubscribe, send any mail to "freebsd-arch-unsubscribe at freebsd.org"