Re: GCC withdraw

2013-08-25 Thread Slawa Olhovchenkov
On Sun, Aug 25, 2013 at 12:13:15AM -0700, Rui Paulo wrote: On 24 Aug 2013, at 16:06, Steve Kargl s...@troutmask.apl.washington.edu wrote: On Sat, Aug 24, 2013 at 11:44:38PM +0100, David Chisnall wrote: On 24 Aug 2013, at 23:42, Slawa Olhovchenkov s...@zxy.spb.ru wrote: And i found

Re: GCC withdraw

2013-08-25 Thread Scot Hetzel
On Sat, Aug 24, 2013 at 5:42 PM, Slawa Olhovchenkov s...@zxy.spb.ru wrote: On Sat, Aug 24, 2013 at 07:42:17PM +0400, Slawa Olhovchenkov wrote: On Sat, Aug 24, 2013 at 01:10:46PM +0100, David Chisnall wrote: On 24 Aug 2013, at 12:51, Slawa Olhovchenkov s...@zxy.spb.ru wrote: Oh, I

Re: GCC withdraw

2013-08-25 Thread Slawa Olhovchenkov
On Sun, Aug 25, 2013 at 02:23:54AM -0500, Scot Hetzel wrote: On Sat, Aug 24, 2013 at 5:42 PM, Slawa Olhovchenkov s...@zxy.spb.ru wrote: On Sat, Aug 24, 2013 at 07:42:17PM +0400, Slawa Olhovchenkov wrote: On Sat, Aug 24, 2013 at 01:10:46PM +0100, David Chisnall wrote: On 24 Aug 2013,

Re: GCC withdraw

2013-08-25 Thread Slawa Olhovchenkov
On Sun, Aug 25, 2013 at 12:23:45AM -0700, Rui Paulo wrote: On 25 Aug 2013, at 00:24, Slawa Olhovchenkov s...@zxy.spb.ru wrote: On Sun, Aug 25, 2013 at 12:13:15AM -0700, Rui Paulo wrote: On 24 Aug 2013, at 16:06, Steve Kargl s...@troutmask.apl.washington.edu wrote: On Sat, Aug

Re: GCC withdraw

2013-08-25 Thread David Chisnall
On 25 Aug 2013, at 00:06, Steve Kargl s...@troutmask.apl.washington.edu wrote: On Sat, Aug 24, 2013 at 11:44:38PM +0100, David Chisnall wrote: On 24 Aug 2013, at 23:42, Slawa Olhovchenkov s...@zxy.spb.ru wrote: And i found PR about clang and mplayer: ports/176272 This PR contains log with

Re: GCC withdraw

2013-08-25 Thread Ian Lepore
On Sat, 2013-08-24 at 23:44 +0100, David Chisnall wrote: On 24 Aug 2013, at 23:42, Slawa Olhovchenkov s...@zxy.spb.ru wrote: And i found PR about clang and mplayer: ports/176272 This PR contains log with build error log. Please file clang bugs at http://llvm.org/bugs/ David And

Re: GCC withdraw

2013-08-25 Thread Slawa Olhovchenkov
On Sun, Aug 25, 2013 at 05:24:23PM +0200, Erik Cederstrand wrote: Expecting FreeBSD Clang maintainers to respond to compilation issues in FreeBSD base seems perfectly reasonable. Expecting them to respond to random issues in the ~24.000 ports is not. OK, how FreeBSD Clang maintainers can

Re: GCC withdraw

2013-08-25 Thread Steve Kargl
On Sun, Aug 25, 2013 at 11:08:57AM +0100, David Chisnall wrote: On 25 Aug 2013, at 00:06, Steve Kargl s...@troutmask.apl.washington.edu wrote: On Sat, Aug 24, 2013 at 11:44:38PM +0100, David Chisnall wrote: On 24 Aug 2013, at 23:42, Slawa Olhovchenkov s...@zxy.spb.ru wrote: And i

Re: GCC withdraw

2013-08-25 Thread Ed Schouten
2013/8/25 David Chisnall thera...@freebsd.org: Oh, and it's worth noting that clang, as an extension, supports using initialiser lists to create complex values and so this particular case is trivial to avoid if you use this feature, which you will if you create complex numbers using the

Re: patch to add AES intrinsics to gcc

2013-08-25 Thread Gerald Pfeifer
On Fri, 23 Aug 2013, Bernhard Fröhlich wrote: 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 am planning to work on this a bit more once the two

Re: patch to add AES intrinsics to gcc

2013-08-25 Thread Gerald Pfeifer
On Sat, 24 Aug 2013, Warner Losh wrote: If you push gcc out to a port, and you have the 'external compiler' toolchain support working correctly enough to build with this, why don't we just push clang out to a port, and be done with it? This is a stupid idea. It kills the tightly integrated

Re: patch to add AES intrinsics to gcc

2013-08-25 Thread Warner Losh
On Aug 25, 2013, at 7:12 PM, Gerald Pfeifer wrote: On Sat, 24 Aug 2013, Warner Losh wrote: If you push gcc out to a port, and you have the 'external compiler' toolchain support working correctly enough to build with this, why don't we just push clang out to a port, and be done with it?

Re: patch to add AES intrinsics to gcc

2013-08-25 Thread Gerald Pfeifer
On Fri, 23 Aug 2013, Bernhard Fröhlich wrote: 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. I don't think so. :-) You can install lang/gcc which builds just fine with clang, and then use lang/gcc

Re: patch to add AES intrinsics to gcc

2013-08-25 Thread Gerald Pfeifer
On Fri, 23 Aug 2013, Volodymyr Kostyrko wrote: 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

Re: patch to add AES intrinsics to gcc

2013-08-25 Thread Warner Losh
Can all such ports be identified with a ports build run in a special chroot without FreeBSD's FCC installed? Sent from my iPad On Aug 25, 2013, at 7:41 PM, Gerald Pfeifer ger...@pfeifer.com wrote: On Fri, 23 Aug 2013, Volodymyr Kostyrko wrote: I object. Many ports that compiles perfectly on