Date: Fri, 23 Aug 2013 06:54:44 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Slawa Olhovchenkov <slw@zxy.spb.ru> Cc: "re@FreeBSD.org Engineering Team" <re@freebsd.org>, "current@freebsd.org" <current@freebsd.org>, John-Mark Gurney <jmg@funkthat.com>, toolchain@freebsd.org, Julian Elischer <julian@freebsd.org> Subject: Re: patch to add AES intrinsics to gcc Message-ID: <CAJ-Vmom3pn06Wcmj6oHPaH8PPWj8sACk4qj2YXT8L_v0Jy=YMg@mail.gmail.com> In-Reply-To: <20130823114635.GB64913@zxy.spb.ru> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <CAE-m3X324rbdP_C=az4eO-EkMcR-yFAeRG7S4q%2BMUsnMezGddw@mail.gmail.com> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> <52173C8D.20608@freebsd.org> <20130823114635.GB64913@zxy.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! If firewire code doesn't build on clang correctly, have you filed a bug so it gets looked at before 10.0 is released? that's pretty broken code/behaviour. -adrian On 23 August 2013 04:46, Slawa Olhovchenkov <slw@zxy.spb.ru> wrote: > On Fri, Aug 23, 2013 at 06:42:21PM +0800, Julian Elischer wrote: > > > On 8/23/13 6:35 PM, David Chisnall wrote: > > > On 23 Aug 2013, at 10:58, Bernhard Fr?hlich <decke@freebsd.org> wrote: > > > > > >> I don't know if you are aware that IF you really do that we will have > serious > > >> problems to ship packages for 10. USE_GCC=any is the fallback in the > > >> portstree for all ports that are unable to build with clang which was > introduced > > >> when HEAD switched to clang as default cc. Right now there are 150 > ports in > > >> the tree that use this fallback and quite a few of them are high > profile ports: > > >> > > >> the highlights: > > >> audio/nas devel/mingw32-binutils emulators/qemu > emulators/virtualbox-ose > > >> emulators/wine lang/go lang/v8 mail/courier math/fftw3 > multimedia/libxine > > >> multimedia/gstreamer multimedia/gstreamer-plugins multimedia/x264 > > >> security/clamav > > >> > > >> the full list: > > >> http://dpaste.com/1354075/ > > >> > > >> A possible hack could be to add a check for USE_GCC=any to behave like > > >> a USE_GCC=yes on HEAD on the affected platforms. This pulls in > lang/gcc > > >> from ports for a lot of people on HEAD I suppose. > > >> > > >> We certainly need to do that switch to remove the ancient gcc from > base > > >> some time but with my portmgr hat on I can only say we don't plan to > do that > > >> before 10.0 especially not if we are only talking about a few weeks > time window. > > > That is unfortunate. We have said for over a year that 10.0 should > not ship with gcc. I can delay committing the patch to flip the switch > until later in the code slush, if re approves, but ports that require gcc > should be building with gcc from ports (which will also improve code > quality, as gcc 4.6/7 produce significantly better code than 4.2.1). > > no, I believe we have said that 10 would ship with clang by default. > > 10 from this winner have broken firewire code when building by clang > -- cannot resume from sleep. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmom3pn06Wcmj6oHPaH8PPWj8sACk4qj2YXT8L_v0Jy=YMg>