4 ms·
Forcing your compiler to figure out you're doing something trivial on a rank-n array is silly. So is writing all the overhead and logic (where a typo can break
by scottlocklin 10y ago
Forcing your compiler to figure out you're doing something trivial on a rank-n array is silly. So is writing all the overhead and logic (where a typo can break things) which goes into a for or while loop instead of two characters: +/
I encourage you to try writing an FFT routine in C yourself and compare it to FFTW, where they basically wrote a compiler for doing FFTs. It's also worth doing in an interpreted language in an array-wise fashion versus with a for-loop. You should get something like a factor of 100,000 speed up.
- kazinator 10y ago> Forcing your compiler to figure out you're doing something trivial on a rank-n array is silly. What is the alternative, if there is no canned procedure for it? The procedure has to be written somewhere, somehow, in some language. If compilers are silly, assembly, I guess?
- kd0amg 10y agoThe analysis to recognize whether a "canned procedure" is applicable is nontrivial, to put it lightly.