similar to: [LLVMdev] Use -D_GLIBCXX_DEBUG

On Thu, 7 Jun 2007, David A. Greene wrote: > I just made a patch to our local llvm build here to pass -D_GLIBCXX_DEBUG when > building llvm. This switch turns on debug code in libstdc++ that checks for > various violations. We've already discovered several llvm bugs with it. > Should I commit a change back to the official sources? It will almost > certainly cause tests to

I'm continuing my quest to integrate _GLIBCXX_DEBUG into the config system. I now have things at a point where I can configure llvm to build with -D_GLIBCXX_DEBUG and the llvm-gcc will pick up the correct CPPFLAGS automatically. One thing I noticed in the llvm Makefile.rules is this: # If DISABLE_ASSERTIONS=1 is specified (make command line or configured), # then disable assertions by

> 3. Any comments on the patch itself? > > The one major thing to be aware of is that it isn't safe to use &V[0] when V > is an empty std::vector Oh dear. That's a bit of a flaw in the plan. I suppose the solution is to switch to SmallVector whenever this might be a problem. I'm a bit concerned that any new &empty[0] problems that are introduced will go unnoticed.

Inviting Paul to the party (he wrote the libstdc++ sort checker <https://gcc.gnu.org/svn/gcc/branches/google/gcc-4_9/libstdc++-v3/include/bits/stl_algo.h> ). On Tue, Jan 12, 2016 at 11:09 PM, Yury Gribov <y.gribov at samsung.com> wrote: > On 01/13/2016 10:08 AM, Yury Gribov wrote: > >> On 01/13/2016 09:57 AM, Kostya Serebryany wrote: >> >>> On Tue, Jan 12,

Thank Ismail for quick reply. I read that Linux, we need to build... (1) libcxx (without libcxxabi) ==> done (2) build libcxxabi ==> failing with following error (3) and then re-build libcxx By the way I am building libcxx and libcxxabi Out-of-tree llvm build. Please correct me if I am missing something. Thank you. -Hiral -----Original Message----- From: İsmail Dönmez [mailto:ismail

[Sorry about the crosspost. Since this is a clang build question but the build is invoked from the top-level LLVM directory I'm not sure where the question should go.] I've got a clang build against libstdc++ on Linux but I would really like one built against libc++/libc++abi. In other words I'd like to rebuild clang/llvm with clang using libc++ and libc++abi on Linux. I looked at

2009/4/1 Chris Lattner <clattner at apple.com>: > As far API design goes, we're in a mixed state.  I'd strongly prefer > to get rid of std::vector from the various interfaces, f.e. creating a > constant array currently requires passing in an std::vector.  For > these sorts of interfaces, we should migrate to passing in a "Constant > *const* / unsigned" pair.

On May 14, 2009, at 4:56 AM, Jay Foad wrote: > 2009/4/1 Chris Lattner <clattner at apple.com>: >> As far API design goes, we're in a mixed state. I'd strongly prefer >> to get rid of std::vector from the various interfaces, f.e. >> creating a >> constant array currently requires passing in an std::vector. For >> these sorts of interfaces, we

On 01/13/2016 09:57 AM, Kostya Serebryany wrote: > On Tue, Jan 12, 2016 at 10:28 PM, Yury Gribov <y.gribov at samsung.com> wrote: > >> On 01/13/2016 03:10 AM, Kostya Serebryany wrote: >> >>> FTR, here is one way to implement this in the library: >>> >>> https://gcc.gnu.org/svn/gcc/branches/google/gcc-4_9/libstdc++-v3/include/bits/stl_algo.h

I am seeing a whole lot of failures in the tests on trunk. From discussions with Chris and others, I should not be seeing this. Here's a typical case: [x86_64-off-opt]: Core was generated by `Output/simple_throw.cbe'. [x86_64-off-opt]: Program terminated with signal 6, Aborted. [x86_64-off-opt]: #0 0x00002b0620792b95 in raise () from /lib64/libc.so.6 [x86_64-off-opt]: #0

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 01/13/2016 03:10 AM, Kostya Serebryany wrote: > FTR, here is one way to implement this in the library: > https://gcc.gnu.org/svn/gcc/branches/google/gcc-4_9/libstdc++-v3/include/bits/stl_algo.h > Search for "check sort predicate for strict weak ordering" Nice, although this wouldn't catch violations of transitivity (which is probably the most important type of bug).

I just ran into this today. Do we need to update our requirements on libstdc++ version? Jay, did you figure out a way around this? On Wed, Sep 4, 2019 at 5:29 AM David Blaikie via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > It's a bug in libstdc++ - so if you have clang using libstdc++ (which it will by default, I think) then it's the same thing. You could try with

Hey guys, I'm trying to install the latest Kerio and it seems to want an older version of libstdc++ which I cannot find anywhere in RPM land (sorry, but I just know gmail is going to mangle this on its way out ) [root at localhost ~]# rpm --install /home/amckay/kerio-kms-6.7.3-7892.linux.i386.rpm error: Failed dependencies: libstdc++.so.5 is needed by kerio-kms-6.7.3-7892.linux.i386

while doing a yum update today, I noticed a few errors being reported that seemed strange to me... /sbin/ldconfig: /usr/lib/libxml2.so.2 is not a symbolic link /sbin/ldconfig: /usr/lib/libstdc++.so.6 is not a symbolic link # ls -l /usr/lib/libstdc++.so.* lrwxrwxrwx 1 root root 18 Oct 13 18:38 /usr/lib/libstdc++.so.5 -> libstdc++.so.5.0.7 -rwxr-xr-x 1 root root 733168 Jan 8 2007

Hi, i have compile and built the llvm-gcc4 and llvm 1.8a in my machine, but there is some problem about llvm-gcc4. It can not compile a cpp code like this: #include <iostream> using std::cout; using std::endl; int main() { cout << "Hello" << endl; } $llvm-g++ hello.cc -o hello /developer/zsth/llvm-gcc/install/bin/../lib/gcc/i686-pc-linux-gnu/4.0.1/../../..

On Wed, Jun 04, 2014 at 06:32:35PM -0400, Rafael Espíndola wrote: > I think the difference is actually in the c++ library. It looks like > libstdc++ changed to always use strcmp of the typeinfo names: > > https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=149964 > > Should we do the same with libc++? No. It pessimizes correctly behaving code to work around code that

Hi, when building the llvm cfe (3.4 derivative), for the mingw platform, I get this error: 'error: there are no arguments to `lrand48' that depend on a template parameter, so a declaration of `lrand48' must be available'. ------------------------ make[3]: Entering directory `/C/projects/build/MinGW/llvm-gcc-1-1/i686-pc-mingw32/libstdc++-v3/testsuite'

On Fri, 14 Jan 2005, Henrik Bach wrote: > when building the llvm cfe (3.4 derivative), for the mingw platform, I get > this error: 'error: there are no arguments to `lrand48' that depend on a > template parameter, so a declaration of `lrand48' must be available'. Hi Henrik, We haven't modified the GCC configure script or build system, so I don't know what

On Thu, 2015-07-09 at 06:56 +0000, William Kennington wrote: > Does fedora have gcc5 patches? I believe they applied some of the 5.2 > changes. I'm not an expert on the gcc package, but looking at the changelog it appears to be be following the upstream 5.x branch: * Thu Jun 18 2015 Jakub Jelinek <jakub at redhat.com> 5.1.1-4 - update from the 5 branch - fix C++ ICE in