From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] kenc vlong <asop> double
Date: Mon, 14 Sep 2015 14:18:46 +0100 [thread overview]
Message-ID: <CAOw7k5hZv5SQi=3x1MGCj1qTYu_4OwrcQ0UNUEGN24DCRHVP6Q@mail.gmail.com> (raw)
In-Reply-To: <ae2ef0bf128acb32cabedca74e752cac@felloff.net>
[-- Attachment #1: Type: text/plain, Size: 779 bytes --]
On 14 September 2015 at 13:59, <cinap_lenrek@felloff.net> wrote:
> is there any reason to handle the <asop> as single operations instead
> of breaking it down into separate <as> and <op> operations? that is,
> is (a <op>= b) always equivalent to (a = a <op> b)?
>
you then have to fuss whether the evaluation of a has side-effects, and
if so, add an assignment to a temporary. it turns out that the existing
code needs only a little more care about which type is used to allocate
registers, and on the RISCy machines it will then work. 8c is a little more
involved because of the 387's architecture. there probably won't be much
code,
but it's fiddly. it would be nice finally to switch
to SSE but i suppose there might still be some SSE-less x86/32 processors.
[-- Attachment #2: Type: text/html, Size: 1344 bytes --]
next prev parent reply other threads:[~2015-09-14 13:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-13 8:09 cinap_lenrek
2015-09-13 13:45 ` erik quanstrom
2015-09-13 14:23 ` cinap_lenrek
2015-09-13 15:54 ` Charles Forsyth
2015-09-13 17:10 ` Charles Forsyth
2015-09-13 18:01 ` cinap_lenrek
2015-09-13 18:21 ` erik quanstrom
2015-09-13 18:31 ` Charles Forsyth
2015-09-13 18:28 ` erik quanstrom
2015-09-13 18:33 ` Charles Forsyth
2015-09-13 18:46 ` cinap_lenrek
2015-09-13 18:55 ` Charles Forsyth
2015-09-14 12:32 ` Charles Forsyth
2015-09-14 12:59 ` cinap_lenrek
2015-09-14 13:18 ` Charles Forsyth [this message]
2015-09-14 13:59 ` Charles Forsyth
2015-09-14 14:50 ` cinap_lenrek
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='CAOw7k5hZv5SQi=3x1MGCj1qTYu_4OwrcQ0UNUEGN24DCRHVP6Q@mail.gmail.com' \
--to=charles.forsyth@gmail.com \
--cc=9fans@9fans.net \
/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).