From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] lisp challenge
Date: Fri, 16 Feb 2018 15:02:33 -0800 [thread overview]
Message-ID: <20180216230233.GD27574@mcvoy.com> (raw)
In-Reply-To: <8a4ac448-9ed2-016a-6440-33597e36915d@kilonet.net>
I suspect that back in the day Fortran may have beat C for scientific
computations (vector stuff would be my guess). But x86 extensions do
vectors as do the GPUs so I don't know of anything that beats C in a
big way.
On Fri, Feb 16, 2018 at 05:56:59PM -0500, Arthur Krewat wrote:
> Has ANY language (except assembler) EVER outperformed C in a big way?
>
> Give or take any optimizations that may be done by either?
>
> On 2/16/2018 5:28 PM, Larry McVoy wrote:
> >I'm no lisp expert, not by any stretch, but I've never seen a lisp
> >program that out performed a well written C program.
--
---
Larry McVoy lm at mcvoy.com http://www.mcvoy.com/lm
next prev parent reply other threads:[~2018-02-16 23:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 21:01 Larry McVoy
2018-02-16 21:03 ` Larry McVoy
2018-02-16 22:05 ` Bakul Shah
2018-02-16 22:28 ` Larry McVoy
2018-02-16 22:53 ` Donald ODona
2018-02-16 23:01 ` Arthur Krewat
2018-02-16 22:56 ` Arthur Krewat
2018-02-16 23:02 ` Larry McVoy [this message]
2018-02-16 23:18 ` Toby Thain
2018-02-16 23:41 ` Larry McVoy
2018-02-16 23:49 ` Bakul Shah
2018-02-16 23:34 ` Andy Kosela
2018-02-16 23:44 Noel Chiappa
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=20180216230233.GD27574@mcvoy.com \
--to=lm@mcvoy.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;
as well as URLs for NNTP newsgroup(s).