Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 12 Jan 2013 19:30:57 -0800
From:      Adrian Chadd <adrian@freebsd.org>
To:        Steve Kargl <sgk@troutmask.apl.washington.edu>
Cc:        freebsd-arch@freebsd.org
Subject:   Re: how long to keep support for gcc on x86?
Message-ID:  <CAJ-VmomrSFXcZg%2BKj6C2ARhpmjB9hxZATYJyRZB7-eRrcBLprg@mail.gmail.com>
In-Reply-To: <20130113014242.GA61609@troutmask.apl.washington.edu>
References:  <20130112233147.GK1410@funkthat.com> <20130113014242.GA61609@troutmask.apl.washington.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
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.




Adrian


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?
>
> 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@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?CAJ-VmomrSFXcZg%2BKj6C2ARhpmjB9hxZATYJyRZB7-eRrcBLprg>