From: Jakub Jelinek <jakub@redhat.com>
To: rupp@gnat.com
Cc: gcc-patches@gcc.gnu.org
Subject: [PATCH] Fix a typo
Date: Tue, 13 Nov 2001 15:03:00 -0000 [thread overview]
Message-ID: <20011119233923.I543@sunsite.ms.mff.cuni.cz> (raw)
Hi!
Commited as obvious bugfix.
2001-11-19 Jakub Jelinek <jakub@redhat.com>
* doc/hostconfig.texi (DUMPFILE_FORMAT): Move into the table.
--- gcc/doc/hostconfig.texi.jj Tue Nov 20 00:31:41 2001
+++ gcc/doc/hostconfig.texi Tue Nov 20 00:43:22 2001
@@ -230,7 +230,6 @@ preprocessor is canonicalized. @var{pat
canonicalized. If the C statement does canonicalize @var{path} into a
different buffer, the old path should be freed and the new buffer should
have been allocated with malloc.
-@end table
@findex DUMPFILE_FORMAT
@item DUMPFILE_FORMAT
@@ -240,6 +239,7 @@ If you do not define this macro, GCC wil
filename will be the prefix of the assembler file name concatenated with
the string resulting from applying this format concatenated with a string
unique to each dump file kind, e.g. @samp{rtl}.
+@end table
@findex bzero
@findex bcmp
Jakub
next reply other threads:[~2001-11-19 22:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 15:03 Jakub Jelinek [this message]
2023-07-21 7:46 Haochen Jiang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011119233923.I543@sunsite.ms.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rupp@gnat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).