similar to: [LLVMdev] New libc++ LLVM Subproject

On Tuesday 11 May 2010 15:43:21 Chris Lattner wrote: > Hi All, > > LLVM now includes a C++ standard library, written by Howard Hinnant. You > can read about it here: > http://blog.llvm.org/2010/05/new-libc-c-standard-library.html > > Or get the code here: > svn co http://llvm.org/svn/llvm-project/libcxx/trunk libcxx > > If you have questions or comments, please

On May 11, 2010, at 7:26 PM, David Greene wrote: > On Tuesday 11 May 2010 15:43:21 Chris Lattner wrote: >> Hi All, >> >> LLVM now includes a C++ standard library, written by Howard Hinnant. You >> can read about it here: >> http://blog.llvm.org/2010/05/new-libc-c-standard-library.html >> >> Or get the code here: >> svn co

On Tue, May 11, 2010 at 5:40 PM, Andrew Sutton <andrew.n.sutton at gmail.com>wrote: > > What's driving libc++? >> >> The possibility of being a superior solution. >> > > I thought "to support Apple applications" from the previous post was > sufficient motivation :) Either way, I'm excited about a new library. Plus, > it looks a little

On 5/11/10 4:43 PM, Chris Lattner wrote: > Hi All, > > LLVM now includes a C++ standard library, written by Howard Hinnant. You can read about it here: > http://blog.llvm.org/2010/05/new-libc-c-standard-library.html > > Or get the code here: > svn co http://llvm.org/svn/llvm-project/libcxx/trunk libcxx > > If you have questions or comments, please direct them to one of

On May 11, 2010, at 9:32 PM, David Leimbach wrote: > > libc++: > > 5 seconds > > libstdc++: > > 22 seconds > > (smaller is better) > > Is this libstdc++ with or without rvalue references? > > How about compile times? Having used Go a bit, I've been quite fond of how short the code, compile, test loop ends up being. Tonight compile times

On May 11, 2010, at 8:40 PM, Andrew Sutton wrote: > > What's driving libc++? > > The possibility of being a superior solution. > > I thought "to support Apple applications" from the previous post was sufficient motivation :) Either way, I'm excited about a new library. Plus, it looks a little easier to read (from the tiny amount of code that I've looked

On Feb 14, 2014, at 1:09 PM, Howard Hinnant <hhinnant at apple.com> wrote: > Author: hhinnant > Date: Fri Feb 14 15:09:01 2014 > New Revision: 201432 > > URL: http://llvm.org/viewvc/llvm-project?rev=201432&view=rev > Log: Remove myself as owner of libc++ > > Modified: > llvm/trunk/CODE_OWNERS.TXT > > Modified: llvm/trunk/CODE_OWNERS.TXT > URL:

On Fri, Feb 14, 2014 at 1:29 PM, Howard Hinnant <hhinnant at apple.com> wrote: > On Feb 14, 2014, at 4:23 PM, Marshall Clow <mclow.lists at gmail.com> wrote: > >> On Feb 14, 2014, at 1:09 PM, Howard Hinnant <hhinnant at apple.com> wrote: >> >>> Author: hhinnant >>> Date: Fri Feb 14 15:09:01 2014 >>> New Revision: 201432 >>>

> > This was compiled with g++-4.-2 -O3 (without rvalue references, which would have no effect on sorting ints anyway). Errr, that is a pretty old version at this point. Also this was before significant performance improvements were target at libstdc++ *and* g++. It seems a bit strange to compare something from today to something that is now 3 release versions old.

On Tuesday 11 May 2010 19:07:50 Howard Hinnant wrote: > > This looks cool, but I can't help wondering about the motivation. > > libstdc++ has a ton of useful functionality (debug mode, profile mode, > > etc.). Does libc++ plan to reproduce that? > > debug mode yes. It isn't there yet. And I would like to limit it to being > ABI compatible with release

On Aug 10, 2018, at 9:35 PM, Eric Fiselier <eric at efcs.ca> wrote: > > Part of me is still concerned with the future, and the filesystems which are yet to exist. > Me too. But it is best to target modern systems when targeting future systems adds an unnecessary cost. When future systems come into being, it is likely because future hardware is making those future systems

Hi community, In CentOS 7 there is such rpm (libcxx-devel - it seems from EPEL repository), but in CentOS 8 it isn't. How is it possible to have it there as RPM? because alternative to build it (libc++) from sources is a big headache (I need it in order to build v9 and plv8 projects) Thanks

On 04/12/2019 06:31 PM, Tom Stellard via llvm-dev wrote: > On 04/12/2019 04:28 PM, AiChi via llvm-dev wrote: >> Hi, >> >> I'm currently working on one of my team's project to build LLVM full clang toolchain (Clang, libcxx, libcxxabi) on a CentOS machine. >> >> Previously we compiled our codebase with llvm-toolset-7/clang++, which by default takes stdlibc++

I've completed a survey of llvm for unnecessary dependencies on libstdc++, and on conflicts with the upcoming C++0X standard, and am recommending several changes in the enclosed patch (created with svn diff). Here is a summary of the patch: --- #include <cstdlib> added to LinkAllVMCore.h and LinkAllCodegenComponents.h to declare std::getenv. Changed next(...) to llvm::next(...) in

Hi, I'm currently working on one of my team's project to build LLVM full clang toolchain (Clang, libcxx, libcxxabi) on a CentOS machine. Previously we compiled our codebase with llvm-toolset-7/clang++, which by default takes stdlibc++ to compile and link. And now we'd like to switch to use LLVM clang with libc++. I have built libc++ and libc++abi from source (5.0.1 release) and set

On Mon, 12 Oct 2020, Alexandru Lazarev wrote: > Hi community, > In CentOS 7 there is such rpm (libcxx-devel - it seems from EPEL > repository), but in CentOS 8 it isn't. > > How is it possible to have it there as RPM? because alternative to build it > (libc++) from sources is a big headache (I need it in order to build v9 and > plv8 projects) Do you mean the

Hello everybody, I am very new to llvm and I am struggling to install it on my 15.10 Xubuntu with kernel 4.2.0-34-generic #39-Ubuntu SMP x86_64 GNU/Linux. I essentially intend to use the clang static analyzer, but it seems that I have to build it on top of llvm and clang. Unfortunately I run into the following problem. CXX shared library ../../../lib/libc++.so at around 52% of the procedure

Hi Dimitry, I do not particularly need to build libc++ from the package. Is the name of the package's libc++, libcxx, because this is where the installation starts finding undefined references, during linking CXX shared library ../../../lib/libc++.so. Please check below the first part of the log when the first error appear, I omited repeating results. Furthermore, the undefined references are

Hi Ioannis, If you only want the clang static analyzer, there is no need to check out and build libc++ as part of the process. The rest of the build can just use the system C++ library, which will be libstdc++ on Xubuntu. That said, without the full build log, it is hard to say what went wrong. Specifically, which references were undefined? -Dimitry > On 26 Mar 2016, at 16:04, Ioannis

> -  std::string string(isl_printer_get_str(p)); > +  char *char_str = isl_printer_get_str(p); > +  std::string string(char_str); > +  free(char_str); This got me wondering: If this were compiled with exceptions it wouldn't be safe (std::string's ctor could throw & then the free wouldn't be called), but I know LLVM doesn't use exceptions in its codebase. Are