[petsc-users] Intel Internal compiler error: segmentation violation signal raised

[TAY wee-beng]

Hi all,

Thank you for the gfortran options. I will try them out!

Yours sincerely,

TAY wee-beng

On 8/4/2014 8:33 PM, Jed Brown wrote:
> TAY wee-beng <zonexo at gmail.com> writes:
>
>> Thanks for the advice. It took me a while to compile and build
>> successfully with gfortran due to the stricter rules and entirely
>> different options.
> Writing portable standards-compliant code pays off.
>
>> But the most problematic thing was that most clusters I work with use
>> old versions of gcc/gfortran. With the gcc/gfortran tied to the MPI, it
>> seems that I can't just update myself to use the new version, or can I?
> They often have modules to access more recent versions.  You can also
> request it.  Paying to upgrade commercial compilers while leaving open
> source compilers at an old version is not good machine maintenance.
>
>> Also, can anyone recommend options to get optimized results in gfortran?
>>
>> I'm using :
>>
>> -fno-signed-zeros  -fno-trapping-math -ffast-math -march=native
>> -funroll-loops -ffree-line-length-none -O3
> I usually use this, with or without -ffast-math depending on requirements:
>
>    -O3 -march=native -ftree-vectorize