This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
gcc/tm.texi,v is corrupt
- To: gcc at gcc dot gnu dot org
- Subject: gcc/tm.texi,v is corrupt
- From: Greg McGary <greg at mcgary dot org>
- Date: Tue, 15 Aug 2000 00:29:53 -0700
I made the diff below by touching an unmodified tm.texi from a tree
checked-out from the trunk a few days ago.
The `mode_for_size' code snippet shows up in other branches as well.
Time to break out the backup tapes.
Greg
Index: tm.texi
===================================================================
RCS file: /cvs/gcc/egcs/gcc/tm.texi,v
retrieving revision 1.138
diff -u -p -r1.138 tm.texi
--- tm.texi 2000/08/08 08:27:59 1.138
+++ tm.texi 2000/08/15 07:24:46
@@ -6669,17 +6669,13 @@ This works only if @code{ASM_OUTPUT_MAX_
@findex ASM_OUTPUT_SKIP
@item ASM_OUTPUT_SKIP (@var{stream}, @var{nbytes})
A C statement to output to the stdio stream @var{stream} an assembler
-instruction to advance the lod have exactly that many bits.
- If LIMIT is nonzero, modes of wider than MAX_FIXED_MODE_SIZE will not
- be used. */
+instruction to advance the location counter by @var{nbytes} bytes.
+Those bytes should be zero when loaded. @var{nbytes} will be a C
+expression of type @code{int}.
-enum machine_mode
-mode_for_size (size, class, limit)
- unsigned int size;
- enum mode_class class;
- int limit;
-{
-ld not be used in the
+@findex ASM_NO_SKIP_IN_TEXT
+@item ASM_NO_SKIP_IN_TEXT
+Define this macro if @code{ASM_OUTPUT_SKIP} should not be used in the
text section because it fails to put zeros in the bytes that are skipped.
This is true on many Unix systems, where the pseudo--op to skip bytes
produces no-op instructions rather than zeros when used in the text