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

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 writes: Thanks for the advice. It took me a while to compile and build successfully with gfortran due to the stricter rules and entirely differe

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

> From: TAY wee-beng To: Barry Smith > , Jed Brown Cc: PETSc list > Subject: Re: [petsc-users] Intel Internal > compiler error: segmentation violation signal raised > > Hi Barry, ... > > Also, can anyone recommend options to get optimized results in > gfortran

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

On 9/4/2014 12:31 AM, Dharmendar Reddy wrote: Hello wee-beng, What is the version of intel compiler you are using ? I use 13.1.0.146 Build 20130121, i have no issues using petsc.h90 in my fortran code. Reddy Hi Reddy, Thanks for the help. I was also using petsc.h9

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

Hello wee-beng, What is the version of intel compiler you are using ? I use 13.1.0.146 Build 20130121, i have no issues using petsc.h90 in my fortran code. Reddy On Tue, Apr 8, 2014 at 7:15 AM, TAY wee-beng wrote: > Hi Barry, > > Thanks for the advice. It took me a wh

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

TAY wee-beng 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 wit

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

Hi Barry, 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. 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

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

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 t

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

On 8/4/2014 7:39 PM, Jed Brown wrote: TAY wee-beng 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 en

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

TAY wee-beng 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

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

On Tue, Apr 8, 2014 at 6:26 AM, TAY wee-beng wrote: > On 8/4/2014 7:58 AM, Matthew Knepley wrote: > > On Mon, Apr 7, 2014 at 6:46 PM, TAY wee-beng wrote: > >> On 8/4/2014 12:40 AM, Matthew Knepley wrote: >> >> How about just including petsc.h90 so you get everything. >> >>Thanks, >> >>

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

On 8/4/2014 7:58 AM, Matthew Knepley wrote: On Mon, Apr 7, 2014 at 6:46 PM, TAY wee-beng > wrote: On 8/4/2014 12:40 AM, Matthew Knepley wrote: How about just including petsc.h90 so you get everything. Thanks, Matt Sorry this is my 2nd emai

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

Did you submit an Intel "Software Problem Report” as they requested? Perhaps they already have updates that fix the problem. Barry On Apr 7, 2014, at 6:58 PM, Matthew Knepley wrote: > On Mon, Apr 7, 2014 at 6:46 PM, TAY wee-beng wrote: > On 8/4/2014 12:40 AM, Matthew Knepley wrote: >> H

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

On Mon, Apr 7, 2014 at 6:46 PM, TAY wee-beng wrote: > On 8/4/2014 12:40 AM, Matthew Knepley wrote: > > How about just including petsc.h90 so you get everything. > >Thanks, > > Matt > > Sorry this is my 2nd email. See below for the 1st email. Using petsc.h90 > gave the error "... segme

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

On 8/4/2014 12:40 AM, Matthew Knepley wrote: How about just including petsc.h90 so you get everything. Thanks, Matt Sorry this is my 2nd email. See below for the 1st email. Using petsc.h90 gave the error "... segmentation violation signal raised " On Mon, Apr 7, 2014 at 5:19 AM,

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

How about just including petsc.h90 so you get everything. Thanks, Matt On Mon, Apr 7, 2014 at 5:19 AM, TAY wee-beng wrote: > Sorry I realised that > > *#include "finclude/petscdmda.h90"* > *#include "finclude/petscksp.h90"* > > also gave errors: > > */home/wtay/Lib/petsc-3.4.4_shared_

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

Sorry I realised that *#include "finclude/petscdmda.h90"* *#include "finclude/petscksp.h90"* also gave errors: *//home/wtay/Lib/petsc-3.4.4_shared_rel/include/finclude/ftn-custom/petscdmda.h90(10): error #5082: Syntax error, found ',' when expecting one of: ( % [ : . = =>/**/ /**/ P

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

Hi, I encountered the error below when compiling my code using intel fortran: /tmp/ifortlPEDlK.i90: catastrophic error: **Internal compiler error: segmentation violation signal raised** Please report this error along with the circumstances in which it occurred in a Software Problem Report. N