Path: ...!feeds.phibee-telecom.net!2.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Stephen Fuld <sfuld@alumni.cmu.edu.invalid>
Newsgroups: comp.arch
Subject: Re: Computer architects leaving Intel...
Date: Mon, 2 Sep 2024 09:46:47 -0700
Organization: A noiseless patient Spider
Lines: 44
Message-ID: <vb4q5o$12ukk$3@dont-email.me>
References: <2024Aug30.161204@mips.complang.tuwien.ac.at>
 <memo.20240830164247.19028y@jgd.cix.co.uk> <vasruo$id3b$1@dont-email.me>
 <2024Aug30.195831@mips.complang.tuwien.ac.at> <vat5ap$jthk$2@dont-email.me>
 <vaunhb$vckc$1@dont-email.me> <vautmu$vr5r$1@dont-email.me>
 <2024Aug31.170347@mips.complang.tuwien.ac.at> <vavpnh$13tj0$2@dont-email.me>
 <vb00c2$150ia$1@dont-email.me>
 <505954890d8461c1f4082b1beecd453c@www.novabbs.org>
 <vb0kh2$12ukk$1@dont-email.me> <vb3smg$1ta6s$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 02 Sep 2024 18:46:48 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="f2fa24f005bb1cc6f28a6c7fbf637e17";
	logging-data="1145492"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18rDTUTYvt3ClQhIUszOg9oN0tV7bGa88w="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:hyXmoS9okHlulxjwrovAHt5L5ao=
Content-Language: en-US
In-Reply-To: <vb3smg$1ta6s$1@dont-email.me>
Bytes: 3457

On 9/2/2024 1:23 AM, Terje Mathisen wrote:
> Stephen Fuld wrote:
>> On 8/31/2024 2:14 PM, MitchAlsup1 wrote:
>>> On Sat, 31 Aug 2024 21:01:54 +0000, Bernd Linsel wrote:
>>>> You compare apples and peaches. Technical specifications for your
>>>> pressure vessel result from the physical abilities of the chosen
>>>> material, by keeping requirements as vessel border width, geometry 
>>>> etc.,
>>>> while compiler writers are free in their search for optimization tricks
>>>> that let them shine at SPEC benchmarks.
>>>
>>> A pressure vessel may actually be able to contain 2× the pressure it
>>> will be able to contain 20 after 20 years of service due to stress
>>> and strain acting on the base materials.
>>>
>>> Then there are 3 kinds of metals {grey, white, yellow} with different
>>> responses to stress and induced strain. There is no analogy in code--
>>> If there were perhaps we would have better code today...
>>
>> Perhaps an analogy is code written in assembler, versus coed written 
>> in C versus code written in something like Ada or Rust.  Backing away 
>> now . . . :-)
> 
> IMNSHO, code written in asm is generally more safe than code written in 
> C, because the author knows exactly what each line of code is going to do.
> 
> The problem is of course that it is harder to get 10x lines of correct 
> asm than to get 1x lines of correct C.
> 
> BTW, I am also solidly in the grey hair group here, writing C code that 
> is very low-level, using explicit local variables for any loop 
> invariant, copying other stuff into temp vars in order to make it really 
> obvious that they cannot alias any globals or input/output parameters.
> 
> Anyway, that is all mostly moot since I'm using Rust for this kind of 
> programming now. :-)

Can you talk about the advantages and disadvantages of Rust versus C?



-- 
  - Stephen Fuld
(e-mail address disguised to prevent spam)