Deutsch   English   Français   Italiano  
<vhv3pc$8ve1$2@paganini.bofh.team>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!feeds.phibee-telecom.net!2.eu.feeder.erje.net!feeder.erje.net!newsfeed.bofh.team!paganini.bofh.team!not-for-mail
From: antispam@fricas.org (Waldek Hebisch)
Newsgroups: comp.lang.c
Subject: Re: else ladders practice
Date: Sun, 24 Nov 2024 11:47:58 -0000 (UTC)
Organization: To protect and to server
Message-ID: <vhv3pc$8ve1$2@paganini.bofh.team>
References: <3deb64c5b0ee344acd9fbaea1002baf7302c1e8f@i2pn2.org>   <vhic66$1thk0$1@dont-email.me> <vhins8$1vuvp$1@dont-email.me> <vhj7nc$2svjh$1@paganini.bofh.team> <vhje8l$2412p$1@dont-email.me> <WGl%O.42744$LlWc.33050@fx42.iad> <vhkr9e$4bje$1@dont-email.me> <vhptmn$3mlgf$1@paganini.bofh.team> <vhq6b4$17hkq$1@dont-email.me> <vhqm3l$3ntp7$1@paganini.bofh.team> <vhso61$1o2of$1@dont-email.me> <vhtrns$71ic$1@paganini.bofh.team> <vhtvvc$1ukc7$1@dont-email.me> <vhu0ft$1ukc7$2@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Sun, 24 Nov 2024 11:47:58 -0000 (UTC)
Injection-Info: paganini.bofh.team; logging-data="294337"; posting-host="WwiNTD3IIceGeoS5hCc4+A.user.paganini.bofh.team"; mail-complaints-to="usenet@bofh.team"; posting-account="9dIQLXBM7WM9KzA+yjdR4A";
User-Agent: tin/2.6.2-20221225 ("Pittyvaich") (Linux/6.1.0-9-amd64 (x86_64))
X-Notice: Filtered by postfilter v. 0.9.3
Bytes: 2793
Lines: 37

Bart <bc@freeuk.com> wrote:
> On 24/11/2024 01:36, Bart wrote:
>> On 24/11/2024 00:24, Waldek Hebisch wrote:
>>> Bart <bc@freeuk.com> wrote:
> 
>>> And of course, there is a question why program with runtime that
>>> does not matter is written in a low level language?
>> 
>> I mean it doesn't matter if it's half the speed. It might matter if it 
>> was 40 times slower.
>> 
>> There's quite a gulf between even unoptimised native code and even a 
>> fast dynamic language interpreter.
>> 
>> People seem to think that the only choices are the fastest possible C 
>> code at one end, and slow CPython at the other:
>> 
>>    gcc/O3-tcc-----------------------------------------------------CPython
>> 
>> On this scale, gcc/O3 code and tcc code are practically the same!
> 
> (I wasn't able to post results earlier because CPython hadn't finished. 
> But for a JPEG decoder test on an 85Mpixel image, all using the same 
> algorithm:
> 
>   gcc-O3    2.2 seconds
>   mm6-opt   3.3 seconds  (My older compiler with the register optim.)
>   mm7       5.7 seconds  (My unoptimising new one)
>   cc        6.0 seconds  (Unoptimising)
>   tcc       8.1 seconds
>   PyPy     43   seconds  (Uses JIT to optimise hot loops to native code)
>   CPython 386   seconds)

That looks like example of a program that should use optimizing
compiler.

-- 
                              Waldek Hebisch