Path: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Terje Mathisen <terje.mathisen@tmsw.no>
Newsgroups: comp.arch
Subject: Re: Computer architects leaving Intel...
Date: Mon, 2 Sep 2024 10:23:43 +0200
Organization: A noiseless patient Spider
Lines: 48
Message-ID: <vb3smg$1ta6s$1@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>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Injection-Date: Mon, 02 Sep 2024 10:23:44 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="e590032ea996c491aa4ac9fda7926e71";
	logging-data="2009308"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19o5aDhvBYzSNSVDNuL+14WH0W1NJ2cvqzwe4WwNsYkLQ=="
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Firefox/91.0 SeaMonkey/2.53.18.2
Cancel-Lock: sha1:1vim7DRm3t0I+gjGAiEUqmoEamg=
In-Reply-To: <vb0kh2$12ukk$1@dont-email.me>
Bytes: 3381

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 et=
c.,
>>> while compiler writers are free in their search for optimization tric=
ks
>>> that let them shine at SPEC benchmarks.
>>
>> A pressure vessel may actually be able to contain 2=C3=83=E2=80=94 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...
>=20
> Perhaps an analogy is code written in assembler, versus coed written in=
=20
> C versus code written in something like Ada or Rust.=C2=A0 Backing away=
 now .=20
> . . :-)

IMNSHO, code written in asm is generally more safe than code written in=20
C, because the author knows exactly what each line of code is going to do=
=2E

The problem is of course that it is harder to get 10x lines of correct=20
asm than to get 1x lines of correct C.

BTW, I am also solidly in the grey hair group here, writing C code that=20
is very low-level, using explicit local variables for any loop=20
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=20
programming now. :-)

Terje

--=20
- <Terje.Mathisen at tmsw.no>
"almost all programming can be viewed as an exercise in caching"