aboutsummaryrefslogtreecommitdiff
path: root/gcc/f
diff options
context:
space:
mode:
authorDave Love <fx@gcc.gnu.org>1998-11-19 10:41:20 +0000
committerDave Love <fx@gcc.gnu.org>1998-11-19 10:41:20 +0000
commit10a51b218ffe05c48d43143bd676830191a72efa (patch)
tree2c41adf087bb1115db5a88dbe3a98386d1c9dbce /gcc/f
parente9831ca0d0ca81e4fdbae886e046a232c2e92d36 (diff)
downloadgcc-10a51b218ffe05c48d43143bd676830191a72efa.zip
gcc-10a51b218ffe05c48d43143bd676830191a72efa.tar.gz
gcc-10a51b218ffe05c48d43143bd676830191a72efa.tar.bz2
Formatting changes from Craig.
From-SVN: r23713
Diffstat (limited to 'gcc/f')
-rw-r--r--gcc/f/bugs.texi4
1 files changed, 2 insertions, 2 deletions
diff --git a/gcc/f/bugs.texi b/gcc/f/bugs.texi
index af18d80c..b591cfc 100644
--- a/gcc/f/bugs.texi
+++ b/gcc/f/bugs.texi
@@ -219,7 +219,7 @@ Version 0.6 should solve most or all remaining problems
@cindex COMPLEX support
@cindex support, COMPLEX
@item
-Maintainers of gcc report that the back end definitely has ``broken''
+Maintainers of @code{gcc} report that the back end definitely has ``broken''
support for @code{COMPLEX} types.
Based on their input, it seems many of
the problems affect only the more-general facilities for gcc's
@@ -242,7 +242,7 @@ by versions of @code{g77} prior to 0.5.20.
when using the @samp{-fPIC} option (such as compiling for ELF targets)
on the Intel x86 architecture target.
The symptom is that the assembler complains about invalid opcodes.
-This bug is in the gcc back end.
+This bug is in the @code{gcc} back end.
Fixed in @code{egcs} version 1.0.2.