public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <dje@transmeta.com>
To: Greg McGary <greg@mcgary.org>
Cc: cgen@sourceware.cygnus.com
Subject: Re: how to implement general macro-insn expansion?
Date: Wed, 20 Dec 2000 07:39:00 -0000	[thread overview]
Message-ID: <14912.53918.827200.424561@casey.transmeta.com> (raw)
In-Reply-To: <msy9xb5vhp.fsf@mcgary.org>

Greg McGary writes:
 > I stared at the code some more, and I think I understand it better
 > now.  rtl-c.scm is a toolkit for making builders.  Having a "builder
 > for each real insn" is what I want to do.

I _think_ that's the way to go.
As you get into it feel free to change your mind. :-)

 > Here's another comment from minsn.scm:
 > 
 > ; Expansion:
 > ; If the macro expands to a string, arguments in the input string
 > ; are refered to with %N.
 > 
 > By %N, do you mean that %0, %1, %2 stand for first, second and third
 > operands in the macro-insn's syntax string?

Yes.  That was some playing around I did _really_ early on.
Ignore it unless there's a seed of something useful there.

 > ; Multiple insns are separated with '\n'.
 > ; String expansion is a special case of the normal form which is a Scheme
 > ; expression that controls the expansion.
 > 
 > Do you still want to support this?  I'd rather just support the
 > general scheme expansion.

Dunno.  Feel free to ignore it for now.

  reply	other threads:[~2000-12-20  7:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-18 12:02 multi-insn expansions for macro insns? Greg McGary
2000-12-18 13:09 ` Doug Evans
2000-12-18 13:17   ` Greg McGary
2000-12-18 13:41     ` Doug Evans
2000-12-19 22:54   ` how to implement general macro-insn expansion? Greg McGary
2000-12-20  0:48     ` Greg McGary
2000-12-20  7:39       ` Doug Evans [this message]
2000-12-26 17:43         ` Greg McGary
2000-12-27 11:28           ` Doug Evans
2000-12-27 12:09             ` Greg McGary
2000-12-27 14:21               ` Doug Evans
2001-01-09 15:23                 ` Greg McGary
2000-12-27 10:39 Nick Clifton

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=14912.53918.827200.424561@casey.transmeta.com \
    --to=dje@transmeta.com \
    --cc=cgen@sourceware.cygnus.com \
    --cc=greg@mcgary.org \
    /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).