search for: r201729

On Mon, May 5, 2014 at 10:47 AM, Chandler Carruth <chandlerc at google.com>wrote: > On Mon, May 5, 2014 at 8:11 AM, Alp Toker <alp at nuanti.com> wrote: > >> I suspect that pulling in clang header fixes r201729, r202911 and r207606 >> to 3.4.1 will resolve libstdc++ / glibc compatibility issues people have >> been having with 3.4: >> >> r201729: Teach Clang to provide ::max_align_t in C11 and C++11 modes) >> r202911: Headers: Provide an ABI compatible max_align_t when _MS...

...e branch works with 4.9 is a good idea because it will be a standard configuration in coming months. > > Has anyone tried the 3.4 release with gcc 4.9? I doubt this was tested > much since LLVM 3.4 was released several months before gcc 4.9. I suspect that pulling in clang header fixes r201729, r202911 and r207606 to 3.4.1 will resolve libstdc++ / glibc compatibility issues people have been having with 3.4: r201729: Teach Clang to provide ::max_align_t in C11 and C++11 modes) r202911: Headers: Provide an ABI compatible max_align_t when _MSC_VER is defined) r207606: Let stdde...

...t; <chandlerc at google.com <mailto:chandlerc at google.com>> wrote: > > > > On Mon, May 5, 2014 at 8:11 AM, Alp Toker <alp at nuanti.com > > <mailto:alp at nuanti.com>> wrote: > > > > I suspect that pulling in clang header fixes r201729, r202911 > > and r207606 to 3.4.1 will resolve libstdc++ / glibc > > compatibility issues people have been having with 3.4: > > > > r201729: Teach Clang to provide ::max_align_t in C11 and > > C++11 modes) > > r202911:...

On 02/05/2014 20:45, Tuncer Ayaz wrote: > Bump. > > Is it really unsupported to build llvm from scratch with gcc 4.9 and > libstdc++ 4.9? Should I file a bugzilla ticket instead? Obviously LLVM/clang should compile out of the box using the current stable GCC version, and failure to do so would be a potential release blocker. Please file a PR Tom, do you know about this issue? Alp.