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

[Barry Smith]

   You should never get yourself in a position where you “have to” use a particular compiler. Strive to have portable makefiles that don’t depend on the compiler (with PETSc makefiles this is easy) and to have portable code that doesn’t depend on the compiler. Then switching between compilers takes literally a couple minutes. It is extremely counter productive to do nothing for days because the compiler you are using doesn’t work under a particular circumstance. It really isn’t hard to set things up so changing compilers is easy.

   Barry


On Apr 8, 2014, at 6:39 AM, Jed Brown <jed at jedbrown.org> wrote:

> TAY wee-beng <zonexo at gmail.com> writes:
>> My impression was intel is mostly faster. However, does it apply to 
>> gfortran too? Is it also faster for a lot of code than Intel fortran? 
>> I'll give it a go if it's so. However, I remember changing a no. of 
>> options to build and in the end, it was slower. that's a few yrs ago though.
> 
> It varies, but usually not by a large factor and a broken compiler takes
> infinitely long to produce correct answers.  Report the bug to Intel,
> use gfortran (latest version), and get on with your business.  If/when
> Intel fixes the bug, if you still have a license, try ifort again.