From cbe414361810b588e8dddefb1bd0c3c4ccb49008 Mon Sep 17 00:00:00 2001 From: jsm28 Date: Mon, 11 Jun 2001 20:52:30 +0000 Subject: [PATCH] * doc/md.texi: Use TeX dashes and quotes. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@43219 138bc75d-0d04-0410-961f-82ee72b054a4 --- gcc/ChangeLog | 4 ++++ gcc/doc/md.texi | 10 +++++----- 2 files changed, 9 insertions(+), 5 deletions(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 0c6f22b36af..340322fe4e6 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,5 +1,9 @@ 2001-06-11 Joseph S. Myers + * doc/md.texi: Use TeX dashes and quotes. + +2001-06-11 Joseph S. Myers + * doc/rtl.texi: Reference manual chapter about trees. 2001-06-11 Rainer Orth diff --git a/gcc/doc/md.texi b/gcc/doc/md.texi index a3ec9ef90de..6ec28e6e937 100644 --- a/gcc/doc/md.texi +++ b/gcc/doc/md.texi @@ -71,7 +71,7 @@ named @code{define_insn} or a @code{define_expand}. The compiler will choose the pattern with the right name and apply the operands according to the documentation later in this chapter, without regard for the RTL template or operand constraints. Note that the names the compiler looks -for are hard-coded in the compiler - it will ignore unnamed patterns and +for are hard-coded in the compiler---it will ignore unnamed patterns and patterns with names it doesn't know about, but if you don't provide a named pattern it needs, it will abort. @@ -1413,10 +1413,10 @@ Registers from r16 to r31 Registers from r24 to r31. These registers can be used in @samp{adiw} command @item e -Pointer register (r26 - r31) +Pointer register (r26--r31) @item b -Base pointer register (r28 - r31) +Base pointer register (r28--r31) @item q Stack pointer register (SPH:SPL) @@ -1548,7 +1548,7 @@ do not use upper halves) that do use upper halves) @item R -Legacy register --- equivalent to @code{r} class in i386 mode. +Legacy register---equivalent to @code{r} class in i386 mode. (for non-8-bit registers used together with 8-bit upper halves in a single instruction) @@ -3786,7 +3786,7 @@ this: in a @code{define_split}. The @var{split-condition} is also used as in @code{define_split}, with the additional behavior that if the condition starts with @samp{&&}, the condition used for the split will be the constructed as a -logical "and" of the split condition with the insn condition. For example, +logical ``and'' of the split condition with the insn condition. For example, from i386.md: @smallexample -- 2.11.4.GIT