Using x86_64-w64-mingw32-gcc-4.7.2-release-win64_rubenvb.7z on Windows 7 x64.
I compile my C++ program with both -Winline and -Werror flags enabled because I highly rely on inlining and want to manually control it. If gcc can't inline some functions, I get a error message, increase various inline related limits and compile again until all functions that I marked as "inline" are actually inlined. But sometimes I get strange error messages. Try this code for example:
As you can see, the class test has no explicitly defined destructor. So I don't care if gcc is unable to inline it. Moreover, if I define the destructor like this
Tried x86_64-w64-mingw32-gcc-4.8-unstable-win64_rubenvb.7z, the warning is not shown there. But I can't compile boost with it, so it's useless for me so far.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Using x86_64-w64-mingw32-gcc-4.7.2-release-win64_rubenvb.7z on Windows 7 x64.
I compile my C++ program with both -Winline and -Werror flags enabled because I highly rely on inlining and want to manually control it. If gcc can't inline some functions, I get a error message, increase various inline related limits and compile again until all functions that I marked as "inline" are actually inlined. But sometimes I get strange error messages. Try this code for example:
As you can see, the class test has no explicitly defined destructor. So I don't care if gcc is unable to inline it. Moreover, if I define the destructor like this
gcc compiles it without any warnings despite the fact that the destructor is still implicitly inline.
I'm not sure if this is a mingw or gcc bug. Maybe std::string is somehow related to it. Any ideas?
Tried x86_64-w64-mingw32-gcc-4.8-unstable-win64_rubenvb.7z, the warning is not shown there. But I can't compile boost with it, so it's useless for me so far.