This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: linux-2.5 min()/max() macros generate warnings with gcc-3.0.4and gcc-3.2
On Sun, Nov 10, 2002 at 12:58:27AM +0000, Joseph S. Myers wrote:
> On Sun, 10 Nov 2002, Matthew Wilcox wrote:
>
> > But... this is behaviour which changed between gcc 2.96 and 3.0.
> > Seems to me the "gnu89" definition has been retroactively changed to
> > disallow this feature. And I don't understand why you wouldn't want
> > this feature to be part of gnu89 anyway. Can you elucidate?
>
> That would be a bug in 2.9x that it failed to detect this case. Where a
> typedef is used (with const in the typedefed type and explicitly),
This is reproducible at least with egcs 2.91.66 (RH kgcc), gcc 2.95.2
(caldera-patches), gcc 2.95.3 (SuSE), gcc 2.95.4 (Debian-prerelease) and
various versions of gcc 2.96-rh.
We kernel developers switching to gcc 3.x now would be verry happy if
you could bring it back in line with those compilers for gnu89 mode.