Sujet : Re: Computer architects leaving Intel...
De : already5chosen (at) *nospam* yahoo.com (Michael S)
Groupes : comp.archDate : 12. Sep 2024, 21:10:16
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <20240912231016.00004048@yahoo.com>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
User-Agent : Claws Mail 4.1.1 (GTK 3.24.34; x86_64-w64-mingw32)
On Tue, 3 Sep 2024 17:46:38 +0200
Terje Mathisen <
terje.mathisen@tmsw.no> wrote:
Q&D programming is still far faster for me in C, but using Rust I
don't have to worry about how well the compiler will be able to
optimize my code, it is pretty much always close to speed of light
since the entire aliasing issue goes away.
I am trying to compare speed of few compiled languages in one benchmark
that I find interesting.
In order to make comparison I have to port a test bench first, because
while most of this languages are able, with various level of
difficulties, to call C routines, none of them can be called from 'C',
at least at my level of knowledge.
Porting test bench from C to Go was quite easy, the only part that I
didn't grasp immediately was related to time measurements.
Today I started Rust port and it is VERY much harder. After several
hours of reading of various tutorials, examples and Stack Overflow
articles I still don't know how to write
switch (argv[1][0]) {
case 't':
case 'T':
x = 42;
break;
}
At this rate, I am not sure that my motivation will last long enough to
finish the porting.
Rust also gets rid of the horrible external library/configure/cmake
mess that kept me from successfully compiling the reference LAStools
lidar code for nearly 10 years.
Using the Rust port I just tell cargo to add it to my project and
that's it.
Terje