Date: Sun, 13 Jan 2013 12:30:30 -0700 From: Warner Losh <imp@bsdimp.com> To: Adrian Chadd <adrian@freebsd.org> Cc: Steve Kargl <sgk@troutmask.apl.washington.edu>, freebsd-arch@freebsd.org Subject: Re: how long to keep support for gcc on x86? Message-ID: <D2E054C1-6A95-41A2-8BB5-B6A46ACA1326@bsdimp.com> In-Reply-To: <CAJ-VmomrSFXcZg%2BKj6C2ARhpmjB9hxZATYJyRZB7-eRrcBLprg@mail.gmail.com> References: <20130112233147.GK1410@funkthat.com> <20130113014242.GA61609@troutmask.apl.washington.edu> <CAJ-VmomrSFXcZg%2BKj6C2ARhpmjB9hxZATYJyRZB7-eRrcBLprg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. >=20 > 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. >=20 > 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 >=20 > Adrian >=20 >=20 > On 12 January 2013 17:42, Steve Kargl = <sgk@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? >>=20 >> IMHO, gcc should be available until after 10.0 is branched. >>=20 >>> I'm asking because clang support AES-NI, but gcc does not... >>=20 >> 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. >>=20 >> -- >> Steve >> _______________________________________________ >> freebsd-arch@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-arch >> To unsubscribe, send any mail to = "freebsd-arch-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to = "freebsd-arch-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D2E054C1-6A95-41A2-8BB5-B6A46ACA1326>