From: Doug Evans <dje@transmeta.com>
To: Greg McGary <greg@mcgary.org>
Cc: fche@redhat.com (Frank Ch. Eigler), cgen@sourceware.cygnus.com
Subject: Re: PATCH: string-expansion macros
Date: Mon, 16 Apr 2001 13:18:00 -0000 [thread overview]
Message-ID: <15067.21393.766115.222329@casey.transmeta.com> (raw)
In-Reply-To: <ms8zl0r4zs.fsf@mcgary.org>
Greg McGary writes:
> fche@redhat.com (Frank Ch. Eigler) writes:
>
> > : I'd like to know why the old code tried to match macros before hard
> > : insns? The reason I need to try hard insns before macros is that for
> > : my MIPS-like port, string macros catch cases that can't be handled by
> > : one insn, and implement a "virtual insn" that do things in 2 or 3 hard
> > : insns. [...]
> >
> > Yes, this makes sense in most cases, but methinks there are other
> > opposite cases also.
>
> Can you think of an example?
One way I think of macro insns is as being intercepts/wrappers
for real insns. If you don't do the intercepts first, you ain't
gonna get the effect you want.
I think that's the way things should work,
and I wonder if needing to reverse it reveals a problem that
is best solved differently.
Note that macros were originally intended to support emitting
code rather than doing text transformation.
next prev parent reply other threads:[~2001-04-16 13:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200103022358.QAA31874.cygnus.local.cgen@kayak.mcgary.org>
2001-04-16 12:37 ` Frank Ch. Eigler
2001-04-16 12:58 ` Greg McGary
2001-04-16 13:18 ` Doug Evans [this message]
2001-04-16 13:29 ` Greg McGary
2001-04-16 13:41 ` Doug Evans
2001-03-02 15:59 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=15067.21393.766115.222329@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=cgen@sourceware.cygnus.com \
--cc=fche@redhat.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).