Path: csiph.com!weretis.net!feeder9.news.weretis.net!border-3.nntp.ord.giganews.com!nntp.giganews.com!local-3.nntp.ord.giganews.com!Xl.tags.giganews.com!local-1.nntp.ord.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Tue, 30 Jun 2026 00:58:02 +0000
From: steve g <Sgonedes1977@gmail.com>
Newsgroups: comp.lang.lisp
Subject: Re: Resources to learn common lisp?
References: <874ina49v1.fsf@mariorosell.es> <87pl21m1i6.fsf@gmail.com> <1107n17$3k6ea$5@dont-email.me> <jwv5x3rg80j.fsf-monnier+comp.lang.lisp@gnu.org> <110a9pp$ckmk$6@dont-email.me> <jwvqzmetvqw.fsf-monnier+comp.lang.lisp@gnu.org> <110cv4b$13kte$7@dont-email.me> <110njmu$2810q$1@paganini.bofh.team> <110o3cs$4okg$1@dont-email.me> <110on3c$2gi2l$1@paganini.bofh.team> <110q4nu$o45a$6@dont-email.me> <110qfq5$2q2b6$1@paganini.bofh.team> <110vgkb$292a0$4@dont-email.me> <1110uhe$3jmcm$3@paganini.bofh.team> <111tfrk$8psn$1@dont-email.me>
Date: Mon, 29 Jun 2026 20:58:02 -0400
Message-ID: <875x30yhd1.fsf@gmail.com>
User-Agent: Gnus/5.13 (Gnus v5.13)
Cancel-Lock: sha1:Zte3wacVaBEOBsj+uZpPe2X5eeE=
MIME-Version: 1.0
Content-Type: text/plain
Lines: 21
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-NZlo4CbqZJ7r8+PsPhphkI6cAJgeaT4Ta53aQ/aBiRLgEq1HpGJ07qHuFWfEiqENctzEVX3IE4Nbuac!f8H+oKmimI55Bkr58sXtVA/jJYYlCawS1OY5Q6IgdlMZU+U=
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
Xref: csiph.com comp.lang.lisp:61091

tfb <tfb@work.it.out> writes:

> Waldek Hebisch <antispam@fricas.org> wrote:
>> Lisp is not exactly there, but not far: rather
>> typical figure for sbcl is half of speed of comparable C.  It is
>> worse when dealing with multidimensional arrays or if C compiler
>> manages to usefuly autovectorize the code.  OTOH memory access
>> time may effectively decrease differences.
>> 
>
> FWIW for float-array intensive code SBCL is about 80% of C (specifically
> the LLVM-based C compiler that ships with macOS and a fairly recent SBCL). 
> Obviously C will do better if the compiler can vectorize things.  But then
> so would SBCL if its compiler could.
>
> I should run these benchmarks again.


sbcl does have a package for simd. I personally use GCC; it is not
having any problems with these simd instructions. they are super fast;
complicated to use though.