search for: clang_compile

Hello, It looks like compiler-rt CMake scripts don't take CMAKE_CXX_FLAGS into account. This is because clang_compile and clang_link_shared functions call the newly-built compiler directly, and they don't add those flags. Using CMAKE_CXX_FLAGS is necessary on systems where the C++11-enabled libstdc++ is installed not in the default location. For example, the CentOS buildbot uses: -DCMAKE_CXX_FLAGS=--gcc-too...

...lt;samsonov at google.com>wrote: > Hi Dmitri, > > On Sat, Mar 22, 2014 at 11:50 PM, Dmitri Gribenko <gribozavr at gmail.com>wrote: > >> Hello, >> >> It looks like compiler-rt CMake scripts don't take CMAKE_CXX_FLAGS >> into account. This is because clang_compile and clang_link_shared >> functions call the newly-built compiler directly, and they don't add >> those flags. >> > > Indeed. > > >> >> Using CMAKE_CXX_FLAGS is necessary on systems where the C++11-enabled >> libstdc++ is installed not in the defau...

...Note that it is against LLVM svn revision 170375. 2.* contention.txt*: Perf report with existing LLVM code - shows contention in llvm::PassRegistry::getPassInfo() 3. *no_contention.txt*: Perf report of LLVM built with our change. 4. *segfault.txt*: Segfault we are encountering after our change. 5. *clang_compile.cpp*: Snippet of code we use to compile code using LLVM. Thanks a lot, Nipun -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150224/47a0c9d5/attachment.html> -------------- next part -------------- Sampl...

...us to be very specific about command-line flags. Of course "just-built Clang" will still need to use system headers and (for unit tests) even system libraries, so _some_ flags must remain configurable by the user. But I'd rather work on the bright future than fix the existing and ugly clang_compile, clang_link etc. set of rules :) Let me know if you're OK with this, or you are in desperate need of the short-term fix (it prevents you from setting up a buildbot, or smth. like that). > > 1) Different compilers. Is bulding llvm with gcc still supported? Is there > a chance llvm (in...

...LVM svn revision 170375. > 2.* contention.txt*: Perf report with existing LLVM code - shows > contention in llvm::PassRegistry::getPassInfo() > 3. *no_contention.txt*: Perf report of LLVM built with our change. > 4. *segfault.txt*: Segfault we are encountering after our change. > 5. *clang_compile.cpp*: Snippet of code we use to compile code using LLVM. > > > Thanks a lot, > Nipun > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150226/b7aa95c6/attachment.html>

...ic about command-line flags. Of course > "just-built Clang" will still need to use system headers and (for unit > tests) even system libraries, so _some_ flags must remain configurable by > the user. But I'd rather work on the bright future than fix the existing > and ugly clang_compile, clang_link etc. set of rules :) Let me know if > you're OK with this, or you are in desperate need of the short-term fix (it > prevents you from setting up a buildbot, or smth. like that). > > > (Ed Maste added to CC.) > > Well, since the buildbot is running v9.2: > &gt...