search for: platform_c

...g for their entire project. This > is especially crucial in HPC applications, where you may want to use LLVM > to compile a domain-specific language and the compiler is part of a larger > project that you want to compile using a vendor compiler for performance > reasons. > In LLVM+platform_C++_compiler scenario the safest way would be to use no C++11 features in LLVM at all and just keep the status quo. > >> >> Clang is good enough to bootstrap itself on practically >> any platform I can think of or it can be cross-bootstrapped >> if needed. >> >...

...> is especially crucial in HPC applications, where you may want to use LLVM > > to compile a domain-specific language and the compiler is part of a > larger > > project that you want to compile using a vendor compiler for performance > > reasons. > > > > In LLVM+platform_C++_compiler scenario the safest way would be to use > no C++11 features in LLVM at all and just keep the status quo. > That's exactly the point of this discussion. What C++11 features could be feasibly allow without alienating too many users with diverse requirements. > > > &g...

On Thu, Jan 10, 2013 at 1:11 AM, Pawel Wodnicki <root at 32bitmicro.com> wrote: > Hello, > > I have been following this discussion for a while and I think the > question we should be asking is: > > Why do we want to even bother with all these other broken C++ > compilers in a first place? > Because not everyone that uses LLVM also uses Clang for every C++ compile.

Hello, I have been following this discussion for a while and I think the question we should be asking is: Why do we want to even bother with all these other broken C++ compilers in a first place? Clang is good enough to bootstrap itself on practically any platform I can think of or it can be cross-bootstrapped if needed. I think usage of any language features should be decided based on