ifort versus gfortran: binary produced by INTEL compilers runs 2 time slower than binary produced by GNU compilers
I'm working with ARPREC package downloaded from David H. Bailey's web page:http://crd.lbl.gov/~dhbailey/mpdist/
I have experimenting with ISO_C_BINDING. There are some cases where a pure routine is useful, but something as trivial as C_LOC() is not pure in Intel Fortan.
I have been experimenting with building Fortran interfaces to C library functions. Here are some of my ideas. It would be good to hear what other people think.
i made a source file... so i am trying to compile but when i use on the command bar ifort XXX.f90 i recived "command ifort not found".
My code compiles. It is an MPI job compiled with Intel 10.1.
However, I am getting the following message when I run my job.
This might really be a questioon for a C forum, but maybe someone working on ISO_C_BINDING has already considered this.
The following code crashes the compiler. Of course, the code has a bug, but the compiler apparently too.
I am trouble finding the Intel Compiler Suite Pro boxed/complete edition of the software. I can find license only, but not the boxed edition. I can find C++ and Fortran boxed separately.
I read the F2008 committee responses to public comments. One comment was on the difficulties of establishing the equivalence of sequence derived types defined in different source code files.
1) please, is anything potentially wrong with this code?
program aa call tisk( (/0,0/) ) end program aa