search for: td53319

...tudio, patches for unsymmetric operator < were accepted into > > the LLVM repo, and I believe it's been done several times after that as > > well. > > In the C++11 discussion back in January > (http://llvm.1065342.n5.nabble.com/Using-C-11-language-features-in-LLVM-itself-td53319.html) > there seemed to be some kind of consensus for 2010 being a reasonable > minimum. Perhaps this is a good time to break compatibility > officially. > > Actually, whatever did happen to using C++11? No-one mentioned > anything about it after that thread. Valid points, raised...

There is some historical precedence for fixing the problem with VS lower_bound by changing the LLVM source - when I first got LLVM to compile with Visual Studio, patches for unsymmetric operator < were accepted into the LLVM repo, and I believe it's been done several times after that as well. m. >From: Ahmed Bougacha >Sent: Friday, July 05, 2013 1:43 AM >To: Benoit Perrot

...nsymmetric operator < were accepted into >> > the LLVM repo, and I believe it's been done several times after that as >> > well. >> >> In the C++11 discussion back in January >> (http://llvm.1065342.n5.nabble.com/Using-C-11-language-features-in-LLVM-itself-td53319.html) >> there seemed to be some kind of consensus for 2010 being a reasonable >> minimum. Perhaps this is a good time to break compatibility >> officially. >> >> Actually, whatever did happen to using C++11? No-one mentioned >> anything about it after that threa...

Hello, I have just updated my svn copy of the llvm/clang repositories after quite a long time of inactivity, and found it not compiling on Windows with Visual Studio 2008. The incriminated file is: llvm/lib/MC/MCModule.cpp Where several calls to "std::lower_bound" are made, like: atom_iterator I = std::lower_bound(atom_begin(), atom_end(),