[libcxx] r260570 - Work around regression in glibc 2.22: request that glibc provides the correct

2016-02-11 Thread Richard Smith via cfe-commits
Author: rsmith Date: Thu Feb 11 13:40:06 2016 New Revision: 260570 URL: http://llvm.org/viewvc/llvm-project?rev=260570&view=rev Log: Work around regression in glibc 2.22: request that glibc provides the correct prototypes for functions that are converted into overload sets in C++. This matches th

Re: [libcxx] r260570 - Work around regression in glibc 2.22: request that glibc provides the correct

2016-02-11 Thread Alexey Samsonov via cfe-commits
I see bogus boostrap build failures when we're trying to use just-built Clang to build libc++: http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux/builds/22540/steps/bootstrap%20clang/logs/stdio Do you think it can be related to one of your changes? I'm pretty sure the contents of /usr/inclu

Re: [libcxx] r260570 - Work around regression in glibc 2.22: request that glibc provides the correct

2016-02-11 Thread Richard Smith via cfe-commits
The problem here is that your version of glibc has broken clang support -- see https://sourceware.org/ml/glibc-cvs/2014-q4/msg00215.html It looks like we may need Clang to start claiming to be GCC 4.4 or later to work around these glibc issues. On Thu, Feb 11, 2016 at 2:58 PM, Alexey Samsonov wr

Re: [libcxx] r260570 - Work around regression in glibc 2.22: request that glibc provides the correct

2016-02-11 Thread Richard Smith via cfe-commits
This should be less broken in r260622. We no longer assume that glibc provides non-broken declarations of the functions. =( On Thu, Feb 11, 2016 at 3:50 PM, Richard Smith wrote: > The problem here is that your version of glibc has broken clang > support -- see https://sourceware.org/ml/glibc-cvs