The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Winalski <paul.winalski@gmail.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Multiflow Compiler
Date: Tue, 2 Apr 2024 12:37:22 -0400	[thread overview]
Message-ID: <CABH=_VSBpXmxLnwbSDYkGv7ed5C-SrAZDRE8SOFbQdqoATwD=w@mail.gmail.com> (raw)
In-Reply-To: <CABH=_VTMM38ii=k58KC2gYp2jYjSSE7_G0FDADiXN0H93JphCA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 672 bytes --]

On Tue, Apr 2, 2024 at 11:53 AM Paul Winalski <paul.winalski@gmail.com>
wrote:

> The back end (optimizer and code generator) for Intel's current C/C++ and
> Fortran compilers uses a modified version of Multiflow IL0 as its
> intermediate language.
>
> Clem Cole reminds me that the situation has changed since I retired from
Intel in 2016.  Intel has switched to a LLVM-based compiler back end.  The
migration to LLVM was just getting started when I retired.  Intel has been
contributing to LLVM, particularly in the areas of parallelization, loop
transformation, and interprocedural optimization.  Some of this technology
has Multiflow roots.

-Paul W.

[-- Attachment #2: Type: text/html, Size: 1007 bytes --]

  reply	other threads:[~2024-04-02 16:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-01 18:44 [TUHS] " Henry Bent
2024-04-01 18:53 ` [TUHS] " Jon Steinhart
2024-04-01 19:12   ` Luther Johnson
2024-04-02  3:46 ` Lawrence Stewart
2024-04-02 15:53 ` Paul Winalski
2024-04-02 16:37   ` Paul Winalski [this message]
     [not found] <171209236009.1214089.9696983396368447310@minnie.tuhs.org>
2024-04-02 22:55 ` Paul McJones
2024-04-02 23:46   ` Luther Johnson

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='CABH=_VSBpXmxLnwbSDYkGv7ed5C-SrAZDRE8SOFbQdqoATwD=w@mail.gmail.com' \
    --to=paul.winalski@gmail.com \
    --cc=tuhs@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).