Ondřej Čertík

@rouson, thanks for the feedback. I think your concerns can be alleviated: * Idiomatic vs most performing: I would like to have both. I expect to have 10 different Fortran...

Regarding your comment at https://github.com/fortran-lang/benchmarks/issues/10#issuecomment-869787773, what you described should absolutely be one version of a Fortran code that solves a given problem. Depending on the problem, I might agree or...

@rouson yes, I am thinking the initial set of languages could be Fortran, C++, Python/NumPy, Julia and Matlab/Octave.

I opened #22 just for the name change. Thanks @rouson for all the feedback. I feel good about this. I also opened tons of new issues (#12 - #21) for...

@arunningcroc I personally like fixed size arrays as well, as they are also automatically deallocated (just like allocatable arrays) and for a simple example like you did I think they...

It's a chicken and egg problem: we can't design and show what we are trying to do without first having a few benchmarks in, but we can't get the few...

Thanks @milancurcic, good points. Yes, if we can constructively figure out criteria, then by all means let's do that. I like what you started with the question. My comment would...

I think we have to run on all hardware that people are interested in. From typical HPC cpus, to typical workstations and laptops, to servers. X86 and ARM. And GPU!...

Yes, I would start with x86-64 and AVX2 instructions.

Furthermore, we also need to run other languages, at least C++, Julia and probably Python/NumPy (possibly via NumBa or other Python accelerator frameworks). It should be done so that it's...