Re: patch to add AES intrinsics to gcc
On Fri, Aug 23, 2013 at 2:12 PM, Volodymyr Kostyrko wrote: > 23.08.2013 12:58, Bernhard Fröhlich 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. > > > I object. Many ports that compiles perfectly on gcc 4.2.1 can't be compiled > with lang/gcc. I checked this once and the number of ports that require > strictly gcc 4.2.1 was bigger for me then number of ports that can't be > compiled with clang but fill fine on lang/gcc. > > I'll gonna recheck whether lang/gcc42 is sufficient for them. But I have > that bad feeling... lang/gcc42 is on the list of ports that have USE_GCC=any. So you would need to fix it first to be able to compile it with clang 3.3 from base. We are not trying to build everything with lang/gcc but just the ports that have USE_GCC=any in their Makefile. Per default all ports are still build with cc from base so clang 3.3 on HEAD. -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-toolchain@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
Re: patch to add AES intrinsics to gcc
On Fri, Aug 23, 2013 at 12:35 PM, David Chisnall wrote: > On 23 Aug 2013, at 10:58, Bernhard Fröhlich 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). I have asked the question of "when will gcc be removed from base" multiple times over the last year and I got varying results back with the majority saying "after 10". I'm just trying to say that It looks like some people in src also don't expect it to be removed in 10. Anyway bapt already did some testing without gcc in base on HEAD and the results were bad but not totally awful. We will see if we can fix the most important ones in time before 10 but we can't promise anything. If someone wants to have a look at the failures with no gcc in base on HEAD: http://pb2.nyi.freebsd.org/bulk/nogcc-default/2013-08-04_01h01m20s/ (this also includes HEAD failures caused by clang) -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-toolchain@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
Re: patch to add AES intrinsics to gcc
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. -- Bernhard Froehlich http://www.bluelife.at/ On Fri, Aug 23, 2013 at 11:16 AM, David Chisnall wrote: > I have a patch that I intend to commit before the 10.0 code slush that > removes GCC and libstdc++ from the default build on platforms where clang is > the system compiler. We definitely don't want to be supporting our > 6-year-old versions of these for the lifetime of the 10.x branch. > > David > > On 22 Aug 2013, at 21:09, John-Mark Gurney wrote: > >> In my work to get AES-NI performance in a better state and the fact >> that we haven't deprecated gcc yet, I have developed another patch to >> add the appropriate AES intrinstic headers to gcc. >> >> The patch is available at: >> https://people.freebsd.org/~jmg/gcc.aes.intrin.patch >> >> I did have to change the opth-gen.awk script, since it wouldn't let >> me use bit 31, and recent changes to gcc used up all the remaining >> bits. I also was unable to add the -mpclmul option because of running >> out of these bits. >> >> Thanks. >> >> -- >> John-Mark Gurney Voice: +1 415 225 5579 >> >> "All that I will do, has been done, All that I have, has not." >> ___ >> freebsd-toolchain@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-toolchain >> To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org" ___ freebsd-toolchain@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
