Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Is Scheme/LISP faster than C/C++

Path: g2news1.google.com!news1.google.com!border1.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!nx02.iad01.newshosting.com!newshosting.com!69.16.185.11.MISMATCH!npeer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!nntp.club.cc.cmu.edu!feeder.erje.net!eternal-september.org!.POSTED!not-for-mail
From: Raymond Toy <toy.raym...@gmail.com>
Newsgroups: sci.math,comp.lang.lisp,comp.lang.scheme,comp.lang.c++,comp.lang.python
Subject: Re: Is Scheme/LISP faster than C/C++
Date: Mon, 14 Jun 2010 15:34:42 -0400
Organization: A noiseless patient Spider
Lines: 13
Message-ID: <hv608j$qsq$1@news.eternal-september.org>
References: <6dea1f91-7685-4337-8854-d8001c678c8b@s9g2000yqd.googlegroups.com> 	<1aee779e-766c-4b9c-b7f2-0d8e388c593b@w12g2000yqj.googlegroups.com> <8728b782-1b4e-46a4-b8fc-d7f17fcb4371@j8g2000yqd.googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Injection-Date: Mon, 14 Jun 2010 19:34:43 +0000 (UTC)
Injection-Info: mx02.eternal-september.org; posting-host="vrDEos3M8RTr6wDgbYvNyw";
	logging-data="27546"; mail-complaints-to="ab...@eternal-september.org";	posting-account="U2FsdGVkX1+1KhohwfcsknH63aofcbbAk6P2VP5ledbbJuhuueU8rA=="
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4
In-Reply-To: <8728b782-1b4e-46a4-b8fc-d7f17fcb4371@j8g2000yqd.googlegroups.com>
Cancel-Lock: sha1:LYVz5NZJkqc8ctbNRO2CckWaI/s=
X-Original-Bytes: 2000

On 6/14/10 1:53 PM, fortunatus wrote:
> For crying out loud, the best any compiler can do is make optimal
> machine language.  Many C compilers can do that over most inputs.  So

Is that why I had to use assembly code instead of C for some parts of my
previous projects?

There was even one example where the C compiler made spectacularly bad
code.  I only needed 6 pointer registers (the arch has 8), but the
compiler decided to use only one or two and spilled and reloaded them
from the stack for each use.  Yay!

Ray