public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
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:41:00 -0000	[thread overview]
Message-ID: <15067.22740.508672.419317@casey.transmeta.com> (raw)
In-Reply-To: <msy9t0pozo.fsf@mcgary.org>

Greg McGary writes:
 > Doug Evans <dje@transmeta.com> writes:
 > 
 > > 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.
 > 
 > Intercepts are one use, whereas what I have implemented is a
 > "fallback" to be used only when a real insn won't match.  Both are
 > valid, IMO.  What needs to be done differently is to allow the
 > programmer to specify whether they want to intercept or if they want
 > to offer fallback.  Sounds like the least disruptive way to go is to
 > retain intercept semantics as the default, and allow an attribute to
 > specify fallback semantics.

I don't have a problem with the attribute (well, I do, but
not a big enough of one to care).
I just wonder whether that's the best way to go.

  reply	other threads:[~2001-04-16 13:41 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
2001-04-16 13:29       ` Greg McGary
2001-04-16 13:41         ` Doug Evans [this message]
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.22740.508672.419317@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).