On Sun, 15 Sep 2024, Pali Rohár wrote:
When compiling any application with flags under gcc 7+ with flags
-D__MINGW_INTRIN_INLINE -Wall -Wextra, it throws about 300 lines of
If I try to build a test program, which only contains "#include
<intrin.h>", nothing else, with GCC 10, with those flags, I get a lot of
errors like "<command-line>: error: expected identifier or ‘(’ before
numeric constant". __MINGW_INTRIN_INLINE should be defined to something
like "extern __inline__
__attribute__((__always_inline__,__gnu_inline__))" anyway - and isn't it
always defined?
So I can't reproduce this situation - did you mean some other define?
Btw, when dealing with headers, Clang has a behaviour where it normally
silences all warnings from headers that are in the general toolchain
sysroot, considered system headers. So normally we don't see any warnings
from code in headers at all - which is a bit problematic when you want to
investigate issues like these... Does GCC do something like that, or does
GCC normally print all warnings for things in system headers too, in
regular installs?
// Martin
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
