Re: [Mingw-w64-public] clang on Windows

2014-01-05 Thread Jonathan Liu
On 25/12/2013 7:31 AM, niXman wrote: > Ivan Garramona 2013-12-25 00:19: >> I'm even planning to move my projects from the buggy VC++ 2013 >> to Clang. > Why Clang? Why not GCC/MinGW-W64? > > As far as I know, Clang optimizes much worse than GCC. Small plus Clang > in that it compiles a little bit f

Re: [Mingw-w64-public] clang on Windows

2013-12-27 Thread Óscar Fuentes
Hello Kai, Kai Tietz writes: > Sounds interesting. But honestly, llvm (Clang) is for Windows right > now pretty unusable. Major basic features of compiler are missing. LLVM is one thing and Clang another. LLVM works fine on Windows. Lacks some features compared to *nix, but it is useful since

Re: [Mingw-w64-public] clang on Windows

2013-12-27 Thread Kai Tietz
Regards, >> >> Jose >> -Original Message----- >> From: Ruben Van Boxem >> Date: Fri, 27 Dec 2013 12:18:03 >> To: >> mingw-w64-public@lists.sourceforge.net >> Reply-To: mingw-w64-public@lists.sourceforge.net >> Subject: Re: [Mingw-w64-p

Re: [Mingw-w64-public] clang on Windows

2013-12-27 Thread niXman
Ruben Van Boxem 2013-12-27 16:54: > I was busy setting up some new build scripts, and hoped to > get a new Clang build out with a newer GCC's libstdc++, but haven't > finished that little project yet. Wish me luck on that :-) Why yet another build scripts? Our scripts can build CLang. Maybe with o

Re: [Mingw-w64-public] clang on Windows

2013-12-27 Thread Ruben Van Boxem
oxem > Date: Fri, 27 Dec 2013 12:18:03 > To: mingw-w64-public@lists.sourceforge.net< > mingw-w64-public@lists.sourceforge.net> > Reply-To: mingw-w64-public@lists.sourceforge.net > Subject: Re: [Mingw-w64-public] clang on Windows > > > -

Re: [Mingw-w64-public] clang on Windows

2013-12-27 Thread josealf
t's use both gcc and clang. It's about choice. The more tools, the better. Regards, Jose -Original Message- From: Ruben Van Boxem Date: Fri, 27 Dec 2013 12:18:03 To: mingw-w64-public@lists.sourceforge.net Reply-To: mingw-w64-public@lists.sourceforge.net Subject: Re: [Ming

Re: [Mingw-w64-public] clang on Windows

2013-12-27 Thread Ruben Van Boxem
2013/12/27 niXman > Óscar Fuentes 2013-12-25 00:51: > > In my projects, programs compiled with Clang (since 3.2) run about 5% > > faster than with g++ (4.8.1). That's on Linux x86_64. > My tests indicate the opposite. > > > Diagnostics are much better than any other C++ compiler, > What are you t

Re: [Mingw-w64-public] clang on Windows

2013-12-26 Thread niXman
Óscar Fuentes 2013-12-25 00:51: > In my projects, programs compiled with Clang (since 3.2) run about 5% > faster than with g++ (4.8.1). That's on Linux x86_64. My tests indicate the opposite. > Diagnostics are much better than any other C++ compiler, What are you talking? > Standards compliance i

Re: [Mingw-w64-public] clang on Windows

2013-12-24 Thread Óscar Fuentes
Ivan Garramona writes: > Clang+MinGW-w64 is working pretty well for me. For me the inability of creating C++ DLLs (exporting classes and template instantiations) is a show stopper. I had problems with some Boost libraries (boost::thread, IIRC) but that could be fixable. I'm glad that it works f

Re: [Mingw-w64-public] clang on Windows

2013-12-24 Thread Óscar Fuentes
niXman writes: > Ivan Garramona 2013-12-25 00:19: >> I'm even planning to move my projects from the buggy VC++ 2013 >> to Clang. > Why Clang? Why not GCC/MinGW-W64? > > As far as I know, Clang optimizes much worse than GCC. In my projects, programs compiled with Clang (since 3.2) run about 5% fa

Re: [Mingw-w64-public] clang on Windows

2013-12-24 Thread Óscar Fuentes
Alexpux writes: > This topic about removing dependency from GCC libs - libstdc++ and libgcc as > I understand. Why shall users interested on Clang worry about replacing libstdc++ and libgcc when there are core features missing, such as C++ DLLs? > There are two projects that can replace them:

Re: [Mingw-w64-public] clang on Windows

2013-12-24 Thread niXman
Ivan Garramona 2013-12-25 00:19: > I'm even planning to move my projects from the buggy VC++ 2013 > to Clang. Why Clang? Why not GCC/MinGW-W64? As far as I know, Clang optimizes much worse than GCC. Small plus Clang in that it compiles a little bit faster than GCC. I really do not understand the

Re: [Mingw-w64-public] clang on Windows

2013-12-24 Thread Ivan Garramona
2013/12/24 Óscar Fuentes > Ivan Garramona > writes: > > > I think Clang svn uses its integrated assembler. > > IIRC Clang uses the integrated assembler since a few releases ago. > > > But it still needs GCC for linking though. > > On Windows, Clang needs MinGW or VS for linking and for the runti

Re: [Mingw-w64-public] clang on Windows

2013-12-24 Thread Alexpux
25 дек. 2013 г., в 0:08, Óscar Fuentes написал(а): > Alexpux writes: > >> My 50 cents to this topic. There are some interesting discussion about >> porting clang to self-hosting on windows >> http://clang-developers.42468.n3.nabble.com/Porting-libcxxabi-Unwind-to-Windows-MingW-32-bit-td403539

Re: [Mingw-w64-public] clang on Windows

2013-12-24 Thread Óscar Fuentes
Alexpux writes: > My 50 cents to this topic. There are some interesting discussion about > porting clang to self-hosting on windows > http://clang-developers.42468.n3.nabble.com/Porting-libcxxabi-Unwind-to-Windows-MingW-32-bit-td4035390.html AFAIK Clang could use (actually uses?) GCC exception

Re: [Mingw-w64-public] clang on Windows

2013-12-24 Thread Alexpux
24 дек. 2013 г., в 23:13, Óscar Fuentes написал(а): > Ivan Garramona > writes: > >> I think Clang svn uses its integrated assembler. > > IIRC Clang uses the integrated assembler since a few releases ago. > >> But it still needs GCC for linking though. > > On Windows, Clang needs MinGW or VS

Re: [Mingw-w64-public] clang on Windows

2013-12-24 Thread Óscar Fuentes
Ivan Garramona writes: > I think Clang svn uses its integrated assembler. IIRC Clang uses the integrated assembler since a few releases ago. > But it still needs GCC for linking though. On Windows, Clang needs MinGW or VS for linking and for the runtime libraries and headers (SDK, standard C/C

Re: [Mingw-w64-public] clang on Windows

2013-12-24 Thread Ivan Garramona
I think Clang svn uses its integrated assembler. But it still needs GCC for linking though. 2013/12/24 Óscar Fuentes > Baruch Burstein > writes: > > > And if I compile it with MinGW then it uses MinGW's toolchain, no? > > Correct. > > > Does Clang not have it's own toolchain (specifically link

Re: [Mingw-w64-public] clang on Windows

2013-12-24 Thread Óscar Fuentes
Baruch Burstein writes: > And if I compile it with MinGW then it uses MinGW's toolchain, no? Correct. > Does Clang not have it's own toolchain (specifically linker)? They are creating one ( http://lld.llvm.org ) but it is not production-ready yet. llvm-link is for manipulating LLVM IR files.

Re: [Mingw-w64-public] clang on Windows

2013-12-24 Thread Baruch Burstein
And if I compile it with MinGW then it uses MinGW's toolchain, no? Does Clang not have it's own toolchain (specifically linker)? On Mon, Dec 23, 2013 at 9:45 PM, Ivan Garramona wrote: > You have to compile Clang with MinGW, otherwise Clang will use VS's > toolchain. > > > 2013/12/23 Baruch Burst

Re: [Mingw-w64-public] clang on Windows

2013-12-23 Thread Ivan Garramona
You have to compile Clang with MinGW, otherwise Clang will use VS's toolchain. 2013/12/23 Baruch Burstein > I apologize if this is not the right place for this. If so, letme know and > I will not post more questions about clang to here. > > This question is really targeted towards Ruben and oth

[Mingw-w64-public] clang on Windows

2013-12-23 Thread Baruch Burstein
I apologize if this is not the right place for this. If so, letme know and I will not post more questions about clang to here. This question is really targeted towards Ruben and others on this list who have built clang toolchains for Windows. I just tried building clang myself (nothing fancy, just