GCC 3.0 release criteria - __GNUC_MINOR__

[Joseph S. Myers]

I presume that GCC 3.0 will change __GNUC__ to 3 and __GNUC_MINOR__ to
0.  There is software out there (including Linux 2.2.14, listed as one of
the test packages for GCC 3.0) which has broken tests assuming that
__GNUC__ remains 2 and __GNUC_MINOR does not fall back to 0, such as

include/linux/init.h:#if __GNUC__ >= 2 && __GNUC_MINOR__ >= 8
include/asm-alpha/byteorder.h:#if defined(__GNUC__) && __GNUC_MINOR__ < 91

While in most cases this may not break the software involved but simply
reduce efficiency, it would probably be a good idea before the release for
someone to grep large source trees (e.g. Linux distributions, BSDs) for
incorrect use of __GNUC_MINOR__, so patches can be distributed.

-- 
Joseph S. Myers
jsm28@cam.ac.uk