On Thu, 1 Dec 2011, Steven Bosscher wrote: > Is it valid in dialects older than C99 to declare a function static > inline after calling it? Should the warnings be brought back in the > compiler?
Older dialects didn't have inline. > One reason to bring the warnings back could be that there is now no > way for anyone bootstrapping GCC to detect this warning. If it is > still a goal that recently modern GCC's should be able to build the > latest GCC, then it would be good if the latest GCC warns about the > same things in a given C dialect as older GCC versions do. Building with older GCC should not use -Werror; only later bootstrap stages, or --enable-werror-always, should do so, and --enable-werror-always is meant to be used for building a cross-compiler using the same version of GCC. In general GCC is only clean for warnings with the same version of GCC; building with 4.3 will give plenty of warnings relating to changes in GCC's internal diagnostic format as well. -- Joseph S. Myers jos...@codesourcery.com
