From: Greg McGary <greg@mcgary.org>
To: Doug Evans <dje@transmeta.com>
Cc: cgen@sourceware.cygnus.com
Subject: Re: how to implement general macro-insn expansion?
Date: Wed, 20 Dec 2000 00:48:00 -0000 [thread overview]
Message-ID: <msy9xb5vhp.fsf@mcgary.org> (raw)
In-Reply-To: <ms1yv37fcw.fsf_-_@mcgary.org>
Greg McGary <greg@mcgary.org> writes:
> ; Another thing to do is have a builder for each real insn so instead of
> ; expanding to text, the macro-expansion could invoke the builder for each
> ; expanded-to insn.
>
> I don't understand this statement. Could you elaborate?
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.
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?
; 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.
Greg
next prev parent reply other threads:[~2000-12-20 0:48 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 [this message]
2000-12-20 7:39 ` Doug Evans
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=msy9xb5vhp.fsf@mcgary.org \
--to=greg@mcgary.org \
--cc=cgen@sourceware.cygnus.com \
--cc=dje@transmeta.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).