This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Minor bug in GCC manual: description of "-fsigned-char".
- To: Julian Foad <julian_foad at hotmail dot com>
- Subject: Re: Minor bug in GCC manual: description of "-fsigned-char".
- From: Neil Booth <neil at daikokuya dot demon dot co dot uk>
- Date: Sat, 9 Jun 2001 14:24:21 +0100
- Cc: gcc at gcc dot gnu dot org
Julian Foad wrote:-
> In the GCC Manual (current version as well as previous versions), under the
> description of compiler option "-fsigned-char", there are four paragraphs.
> The first two paragraphs belong here but the last two are duplicated from
> the description of "-ftraditional" and I believe they are inappropriate and
> should be deleted from here.
Thank you. I'll apply this to 3.0 and mainline.
Neil.
2001-06-09 Julian Foad <julian_foad@hotmail.com>
* invoke.texi: Remove superfluous text.
Index: invoke.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/invoke.texi,v
retrieving revision 1.4
diff -u -p -r1.4 invoke.texi
--- invoke.texi 2001/06/08 19:42:28 1.4
+++ invoke.texi 2001/06/09 13:23:16
@@ -1169,15 +1169,6 @@ Note that this is equivalent to @samp{-f
the negative form of @samp{-funsigned-char}. Likewise, the option
@samp{-fno-signed-char} is equivalent to @samp{-funsigned-char}.
-You may wish to use @samp{-fno-builtin} as well as @samp{-traditional}
-if your program uses names that are normally GNU C builtin functions for
-other purposes of its own.
-
-You cannot use @samp{-traditional} if you include any header files that
-rely on ISO C features. Some vendors are starting to ship systems with
-ISO C header files and you cannot use @samp{-traditional} on such
-systems to compile files that include any system headers.
-
@item -fsigned-bitfields
@itemx -funsigned-bitfields
@itemx -fno-signed-bitfields