From: Valdis.Kletnieks@vt.edu
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Fwd: Will Edwards to give Mill talk in Estonia on 12/10/2014
Date: Fri, 05 Dec 2014 14:33:58 -0500 [thread overview]
Message-ID: <14518.1417808038@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 05 Dec 2014 11:18:57 -0800." <CAA93jw7Bd+hvm88==0fcgeB-mS3TDfqrCr0baV2uy7B==3pS5w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 578 bytes --]
On Fri, 05 Dec 2014 11:18:57 -0800, Dave Taht said:
> The Mill is an extremely wide-issue VLIW design, able to issue 30+
> MIMD operations per cycle. The Mill is inherently a vector machine
> and can vectorize and pipeline almost all loops in general purpose
> code.
The big question is whether we know more about writing compilers for VLIW
machines than we did when the Itanium came out. That was hard enough to
get just 3 instructions packed per word (of course, the fact that it wasn't
3 generic instructions, but 2 of one flavor and 1 of another, didn't help).
[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]
next prev parent reply other threads:[~2014-12-05 19:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <daeaa4982a7a1c6b864c6b557d27ac1acc3.20141205184544@mail158.atl21.rsgsv.net>
2014-12-05 19:18 ` Dave Taht
2014-12-05 19:33 ` Valdis.Kletnieks [this message]
2014-12-05 20:15 ` Dave Taht
2014-12-10 6:13 ` [Cerowrt-devel] [Bloat] " Jonathan Morton
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=14518.1417808038@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.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