From f45592874280feb8515bfdc75e532ed94e5faf5e Mon Sep 17 00:00:00 2001 From: Ben Elliston Date: Mon, 20 Dec 2004 09:50:21 +0000 Subject: [PATCH] md.texi (Expander Definitions): Use @emph instead of @strong around Note... * doc/md.texi (Expander Definitions): Use @emph instead of @strong around Note: text to workaround a limitation of the Info format. * doc/cpp.texi (Invocation): Likewise. * doc/cppopts.texi: Likewise. From-SVN: r92411 --- gcc/ChangeLog | 7 +++++++ gcc/doc/cpp.texi | 2 +- gcc/doc/cppopts.texi | 4 ++-- gcc/doc/md.texi | 2 +- 4 files changed, 11 insertions(+), 4 deletions(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 243363bf497..427aa21b06e 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,10 @@ +2004-12-20 Ben Elliston + + * doc/md.texi (Expander Definitions): Use @emph instead of @strong + around Note: text to workaround a limitation of the Info format. + * doc/cpp.texi (Invocation): Likewise. + * doc/cppopts.texi: Likewise. + 2004-12-19 Dale Johannesen * tree-ssa-loop-ivopts.c (contains_abnormal_ssa_name_p): Don't diff --git a/gcc/doc/cpp.texi b/gcc/doc/cpp.texi index 66f92818e8d..fa94f48d77d 100644 --- a/gcc/doc/cpp.texi +++ b/gcc/doc/cpp.texi @@ -4133,7 +4133,7 @@ here are also acceptable to the C compiler and have the same meaning, except that the C compiler has different rules for specifying the output file. -@strong{Note:} Whether you use the preprocessor by way of @command{gcc} +@emph{Note:} Whether you use the preprocessor by way of @command{gcc} or @command{cpp}, the @dfn{compiler driver} is run first. This program's purpose is to translate your command into invocations of the programs that do the actual work. Their command line interfaces are diff --git a/gcc/doc/cppopts.texi b/gcc/doc/cppopts.texi index edd446a9fdd..872cffcd501 100644 --- a/gcc/doc/cppopts.texi +++ b/gcc/doc/cppopts.texi @@ -133,7 +133,7 @@ time it is redefined or undefined. Built-in macros, macros defined on the command line, and macros defined in include files are not warned about. -@strong{Note:} If a macro is actually used, but only used in skipped +@emph{Note:} If a macro is actually used, but only used in skipped conditional blocks, then CPP will report it as unused. To avoid the warning in such a case, you might improve the scope of the macro's definition by, for example, moving it into the first skipped block. @@ -359,7 +359,7 @@ extensions for C++ and assembly are also recognized. If cpp does not recognize the extension, it will treat the file as C; this is the most generic mode. -@strong{Note:} Previous versions of cpp accepted a @option{-lang} option +@emph{Note:} Previous versions of cpp accepted a @option{-lang} option which selected both the language and the standards conformance level. This option has been removed, because it conflicts with the @option{-l} option. diff --git a/gcc/doc/md.texi b/gcc/doc/md.texi index 9e11e44fd50..36c73a19392 100644 --- a/gcc/doc/md.texi +++ b/gcc/doc/md.texi @@ -4511,7 +4511,7 @@ on this machine. So it must be copied into a register with = force_reg (SImode, GEN_INT (65535)); ") @end smallexample -@strong{Note:} If the @code{define_expand} is used to serve a +@emph{Note:} If the @code{define_expand} is used to serve a standard binary or unary arithmetic operation or a bit-field operation, then the last insn it generates must not be a @code{code_label}, @code{barrier} or @code{note}. It must be an @code{insn}, -- 2.30.2