gcc5

I need to extend std::basic_string to work over path strings and different operator+ : #include <string> template <class t_elem, class t_traits, class t_alloc> class path_basic_string : public std::basic_string<t_elem, t_traits, t_alloc> { public: using base_type = std::basic_string<t_elem, t_traits, t_alloc>; path_basic_string() = default; path_basic_string(const path_basic_string & ) = default; path_basic_string & operator =(const path_basic_string &) = default; path_basic_string(const base_type & r) : base_type(r) { } path_basic_string(base_type && r) : base_type(std::move(r)) { } }; using

I try to use the ubuntu 15.10 repository version of libmuparser (package libmuparser2v5). Compiling with gcc works fine, but not with clang. I dug deeper into this to come up with the following minimal (not) working example and a few questions. Consider a library with a simple class that takes a string and returns a string . testlib.h : #pragma once #include <string> struct Test { std::string str; void set(std::string s); std::string get(); }; testlib.cpp : #include "testlib.h" void Test::set(std::string s) { str = s; } std::string Test::get() { return str; } This is compiled with gcc 5.2.1 as

So, if you try to use nvcc when the system GCC is version 5 and up, you get an "unsupported version" error. But - I've heard people report that they've just commented this out and that CUDA 7.5 "works for them" with GCC 5.x . When I do the same, however (the check is in $CUDA_DIR/host_config.h ), and compile something, I get the following errors: /usr/lib/gcc/x86_64-redhat-linux/5.3.1/include/mwaitxintrin.h(36): error: identifier "__builtin_ia32_monitorx" is undefined /usr/lib/gcc/x86_64-redhat-linux/5.3.1/include/mwaitxintrin.h(42): error: identifier "__builtin_ia32_mwaitx" is undefined and a

Consider this code: #include <iostream> int main() { int i{10.1}; // narrowing, should not compile std::cout << i << std::endl; } According to the C++11 standard, it should not compile (narrowing in brace initialization is forbidden.) Now, compiling with g++4.9.2 -std=c++11 only emits a warning warning: narrowing conversion of '1.01e+1' from 'double' to 'int' inside { } [-Wnarrowing] Removing the -std=c++11 flag results in a warning regarding the brace init, but not any narrowing: warning: extended initializer lists only available with -std=c++11 or -std=gnu++11 On the other hand, g++5 doesn't

GCC 5.3 has added a new option: -fno-semantic-interposition A new -fno-semantic-interposition option can be used to improve code quality of shared libraries where interposition of exported symbols is not allowed. This sounds like this is something useful for C++ projects where interposition can't be used for whatever reason, but where latency is a concern. However, the description is fairly vague. Is anyone able to clarify how this option works exactly? -fno-semantic-interposition can significantly improve performance of code in shared libraries but may change semantics in some cases. By