Re: Add __GNUC_PATCHLEVEL__

[Jeffrey A Law <law@cygnus.com>]

  In message <37557364.F9AA007D@cygnus.co.uk>you write:
  > This is a multi-part message in MIME format.
  > --------------3E307D92F875B35F0C14BB47
  > Content-Type: text/plain; charset=us-ascii
  > Content-Transfer-Encoding: 7bit
  > 
  > The granularity of __GNUC__ and __GNUC_MINOR__ is not fine enough. Here is 
  > a
  > patch that will add support for an additional macro __GNUC_PATCHLEVEL__
  > which is simply the next appropriate number in the version string, if
  > present. I have made it default to "0" if it isn't present.
  > 
  > So e.g. 2.95 would have __GNUC__==2, __GNUC_MINOR__==95 and
  > __GNUC_PATCHLEVEL__==0
  > 2.95.1 would have __GNUC__==2, __GNUC_MINOR__==95 and __GNUC_PATCHLEVEL__==
  > 1
  > 
  > Is this reasonable? If so, I'd be grateful if someone could check it in.
  > 
  > Jifl
  > 
  > Wed Jun  2 17:34:42 1999  Jonathan Larmour  <jlarmour@cygnus.co.uk>
  > 
  >         * gcc.c (default_compilers): Add new __GNUC_PATCHLEVEL__ define to
  >         default cpp spec
  >         * gcc.c (do_spec_1): Add support for %v3 spec used by
  >         __GNUC_PATCHLEVEL__
I believe this change has been overtaken by events.  We no longer spin the
patchlevel number, except when we make minor releases and we're going to be
trying hard to avoid any new features, incompatible changes in minor releass.

jeff