ref: 117893a7177b4f7a63ad3bdf367980656f4ba556
parent: 7a245adb18b8237da8bdb9ae5b7217ec047fb34a
author: Ralph Giles <[email protected]>
date: Thu Dec 21 08:48:55 EST 2017
Don't force inlining for msvc targets. INLINE is defined as __forceinline for vs* configs, but is the normal, compiler-discretion inline for gcc/clang configs. This makes many functions very large when building for windows targets, much larger than they are elsewhere. Use '__inline' as a consistent definition to get consistent function sizes. Although Visual Studio documentation says that 'inline' is only available in C+ code. This is probably incorrect, since Visual Studio 2017 accepts C99 'inline' even when passed /TC. Nevertheless, this commit uses the recommended '__inline' for consistency. Thanks to David Major for the diagnosis. Change-Id: Ib0b31a3afcea77822c84fe3c6cd452add66d825a
--- a/configure
+++ b/configure
@@ -665,7 +665,7 @@
gen_vcproj_cmd=${source_path}/build/make/gen_msvs_vcxproj.sh enabled werror && gen_vcproj_cmd="${gen_vcproj_cmd} --enable-werror" all_targets="${all_targets} solution"- INLINE="__forceinline"
+ INLINE="__inline"
;;
esac