public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: cgen@sources.redhat.com
Subject: [RFA:] Improve cgen/doc/rtl.texi wrt. timing and PROFILE.
Date: Sat, 30 Nov 2002 00:25:00 -0000	[thread overview]
Message-ID: <200211300824.gAU8Ov5t011425@ignucius.axis.se> (raw)

Slight improvements to the documentation, I hope.

By the way, it seems toplevel configury does not create a
cgen/Makefile, necessary for "make info" to take effect, even
though nothing else is created object-wise.  Needs fixing.

Ok to commit?

	* doc/rtl.texi (Model variants): Mention current limitations for
	unit inputs and outputs.
	(Hardware elements) <attribute PROFILE>: Be slightly more
	verbose.
	(Instructions) <timing>: input/output overrides have a direction
	operand.

Index: rtl.texi
===================================================================
RCS file: /cvs/src/src/cgen/doc/rtl.texi,v
retrieving revision 1.15
diff -c -p -r1.15 rtl.texi
*** rtl.texi	29 Jan 2002 22:51:52 -0000	1.15
--- rtl.texi	30 Nov 2002 08:13:20 -0000
*************** function unit called @samp{u-cmp} is def
*** 755,761 ****
  This handles instructions that use src1 and src2 as operands.  The
  organization of units is arbitrary.  On the M32R, src1/src2 instructions
  are typically compare instructions so a separate function unit was
! created for them.
  
  @node Hardware elements
  @section Hardware Elements
--- 755,763 ----
  This handles instructions that use src1 and src2 as operands.  The
  organization of units is arbitrary.  On the M32R, src1/src2 instructions
  are typically compare instructions so a separate function unit was
! created for them.  Current limitations require that each hardware item
! behind the operands must be marked with the attribute @code{PROFILE} and
! the hardware item must not be scalar.
  
  @node Hardware elements
  @section Hardware Elements
*************** with @code{VIRTUAL} (??? revisit).
*** 813,820 ****
  
  @item PROFILE
  
! Ignore.  This is a work-in-progress to define how to profile references
! to hardware elements.
  
  @item VIRTUAL
  
--- 815,823 ----
  
  @item PROFILE
  
! This attribute must be present for hardware elements to which references
! are profiled.  Beware, this is work-in-progress.  If you use this
! attribute it is likely you have to hack CGEN.  (Please submit patches.)
  
  @item VIRTUAL
  
*************** that supports the instruction.  The defa
*** 1866,1879 ****
  The syntax is:
  
  @example
! (mach-name (unit name (unit-var-name1 insn-operand-name1)
!                       (unit-var-name2 insn-operand-name2)
                        ...
                        (cycles cycle-count))
  @end example
  
! unit-var-name/insn-operand-name mappings are optional.
! They map unit inputs/outputs to semantic elements.
  
  @code{cycles} overrides the @code{done} value (latency) of the function
  unit and is optional.
--- 1869,1885 ----
  The syntax is:
  
  @example
! (mach-name (unit name (direction unit-var-name1 insn-operand-name1)
!                       (direction unit-var-name2 insn-operand-name2)
                        ...
                        (cycles cycle-count))
  @end example
  
! direction/unit-var-name/insn-operand-name mappings are optional.
! They map unit inputs/outputs to semantic elements.  The
! direction specifier can be @code{in} or @code{out} mapping the
! name of a unit input or output, respectively, to an insn
! operand.
  
  @code{cycles} overrides the @code{done} value (latency) of the function
  unit and is optional.

brgds, H-P

             reply	other threads:[~2002-11-30  8:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-30  0:25 Hans-Peter Nilsson [this message]
2002-11-30  3:18 ` Ben Elliston
2002-11-30  3:18 ` Ben Elliston

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=200211300824.gAU8Ov5t011425@ignucius.axis.se \
    --to=hans-peter.nilsson@axis.com \
    --cc=cgen@sources.redhat.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).