From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: dje@transmeta.com
Cc: hans-peter.nilsson@axis.com, cgen@sources.redhat.com
Subject: Re: play.cpu or parallel semantics broken
Date: Wed, 20 Mar 2002 16:31:00 -0000 [thread overview]
Message-ID: <200203210030.BAA18089@ignucius.axis.se> (raw)
In-Reply-To: <15513.9725.366196.648073@casey.transmeta.com> (message from Doug Evans on Wed, 20 Mar 2002 16:14:53 -0800 (PST))
> From: Doug Evans <dje@transmeta.com>
> Date: Wed, 20 Mar 2002 16:14:53 -0800 (PST)
> Hans-Peter Nilsson writes:
> > Processing semantic switch case for "add $dr,$sr" ...
> > [ Note that this is actually addv2; they confusingly have the
> > same "syntax". ]
>
> NOTE: play.cpu was only ever a sandbox for playing in.
I'm using it exactly as such. Or trying to. :-)
See next message.
> If someone wants to put in the time to clean it up, go for it.
So, ok to clean it up by removing addv2? That seems all that's
needed.
brgds, H-P
prev parent reply other threads:[~2002-03-21 0:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-20 15:56 Hans-Peter Nilsson
2002-03-20 16:15 ` Doug Evans
2002-03-20 16:31 ` Hans-Peter Nilsson [this message]
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=200203210030.BAA18089@ignucius.axis.se \
--to=hans-peter.nilsson@axis.com \
--cc=cgen@sources.redhat.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).