From: "Christopher Oliver" <oliver@fritz.traverse.com>
To: caml-list@inria.fr
Subject: Re: VLIW & caml: how?
Date: Sat, 29 Aug 1998 13:36:28 -0400 (EDT) [thread overview]
Message-ID: <E0zCovM-00006a-00@fritz.traverse.net> (raw)
Todd Lewis writes:
> I've been reading that VLIW as implemented on the IA-64/Merced will post
> problems for conventional compilers such as gcc which don't have a very
> expansive view of the code they're compiling. How well will o'caml deal
> with optimizing for this sort of architecture? Any thoughts?
Well... since no one in the free software community knows much
about Merced, and Intel is not talking, this chip isn't yet real
as far as authors of compiler back ends for free languages. I
think we should make sure Intel doesn't play Appendix H games
again before wasting much time speculating on how any compiler
handles optimization on this architecture.
--
Christopher Oliver Traverse Internet
Systems Coordinator 223 Grandview Pkwy, Suite 108
oliver@traverse.net Traverse City, Michigan, 49684
let magic f = fun x -> x and more_magic n f = fun x -> f ((n f) x);;
next reply other threads:[~1998-08-31 11:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-29 17:36 Christopher Oliver [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-08-28 5:18 Todd Graham Lewis
1998-09-01 11:33 ` Ping Hu
1998-09-02 17:23 ` Xavier Leroy
1998-09-03 19:29 ` Joel Jones
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=E0zCovM-00006a-00@fritz.traverse.net \
--to=oliver@fritz.traverse.com \
--cc=caml-list@inria.fr \
/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