On Sun, 23 Sep 2018, Fredrik Noring wrote: > > Patch 4 will break bisect on clang builds. The reason for this is that > > clang treats unused functions as errors. Therefore, patch 4 must be merged > > with some of subsequent patches that contain first invocation of the > > function currently defined in patch 4. I know this is in some way > > illogical, but not breaking the bisect takes precedence. > > Right. GCC accepts it since static inline functions are exempted.
How does clang handle static inline function definitions in header files then? Such cases are pretty common, also in system headers, and all those functions are not necessarily used by every program including the relevant header. Maciej
