From: Nemo Nusquam <cym224@gmail.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] OT: compiler back-end bug
Date: Thu, 3 Oct 2019 16:03:47 -0400 [thread overview]
Message-ID: <31d29b9b-9810-7731-cfd7-326acb9e2844@gmail.com> (raw)
In-Reply-To: <6696fb88a31a97eeae2c0f9970476ff6aa55e9d4@webmail.yaccman.com>
On 10/03/19 16:03, Steve Johnson wrote (in part):
> Once you know what you want, then you figure out the first instruction
> that isn't right and hit it with everything you have...
+42
N.
(And sorry, Warren, I haven't written iapx assembler in over a decade.)
prev parent reply other threads:[~2019-10-03 20:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-29 9:21 Warren Toomey
2019-09-29 9:47 ` Ralph Corderoy
2019-09-29 10:03 ` Warren Toomey
2019-09-29 10:50 ` Ralph Corderoy
2019-10-03 20:03 ` Steve Johnson
2019-10-03 20:03 ` Nemo Nusquam [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=31d29b9b-9810-7731-cfd7-326acb9e2844@gmail.com \
--to=cym224@gmail.com \
--cc=tuhs@minnie.tuhs.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 NNTP newsgroup(s).