From: Greg McGary <greg@mcgary.org>
To: Doug Evans <dje@transmeta.com>
Cc: cgen@sourceware.cygnus.com
Subject: Re: multi-insn expansions for macro insns?
Date: Mon, 18 Dec 2000 13:17:00 -0000 [thread overview]
Message-ID: <msitoha0oy.fsf@mcgary.org> (raw)
In-Reply-To: <14910.31997.701815.400981@casey.transmeta.com>
Doug Evans <dje@transmeta.com> writes:
> On the other hand, simple expansions are completely reasonable IMO.
> ...
> > (sequence () (emit ...) (emit ...))
>
> That's the plan. Note that the intent here is to also allow
> specification of runtime determination of what gets emitted.
> e.g. (sequence () (if (foo) (emit this) (emit that)))
Cool. If no one else is actively working on this, I'll proceed.
next prev parent reply other threads:[~2000-12-18 13:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-18 12:02 Greg McGary
2000-12-18 13:09 ` Doug Evans
2000-12-18 13:17 ` Greg McGary [this message]
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
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
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=msitoha0oy.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).