From 586964a732aabb2c48a76a73f8994a9adb78d811 Mon Sep 17 00:00:00 2001 From: Andres Felipe Vargas Date: Mon, 22 Jan 2001 15:41:04 -0500 Subject: [PATCH] * cpp.texi: Fix typos. From-SVN: r39186 --- gcc/ChangeLog | 4 ++++ gcc/cpp.texi | 4 ++-- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 421766e1c61..27d7978202b 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,7 @@ +2001-01-22 Andres Felipe Vargas + + * cpp.texi: Correct typos. + Mon Jan 22 13:59:09 2001 Richard Kenner * explow.c (probe_stack_range): Ensure value passed to diff --git a/gcc/cpp.texi b/gcc/cpp.texi index 02b6253c535..253d6ee6cba 100644 --- a/gcc/cpp.texi +++ b/gcc/cpp.texi @@ -1127,7 +1127,7 @@ version 1, which is now obsolete, and @samp{2} for version 2). @findex __GNUC_MINOR__ The macro contains the minor version number of the compiler. This can be used to work around differences between different releases of the -compiler (for example, if GCC 2.6.3 is known to support a feature, you +compiler (for example, if GCC 2.6.x is known to support a feature, you can test for @code{__GNUC__ > 2 || (__GNUC__ == 2 && __GNUC_MINOR__ >= 6)}). @item __GNUC_PATCHLEVEL__ @@ -1138,7 +1138,7 @@ of the compiler (for example, if GCC 2.6.2 is known to contain a bug, whereas GCC 2.6.3 contains a fix, and you have code which can workaround the problem depending on whether the bug is fixed or not, you can test for @code{__GNUC__ > 2 || (__GNUC__ == 2 && __GNUC_MINOR__ > 6) || -(__GNUC__ == 2 && __GNUC_MINOR__ == 6 && __GNUC_PATCHLEVEL__ > 3)}). +(__GNUC__ == 2 && __GNUC_MINOR__ == 6 && __GNUC_PATCHLEVEL__ >= 3)}). @item __GNUG__ @findex __GNUG__ -- 2.30.2