--- Comment #6 from kargl at gcc dot gnu dot org 2009-10-02 16:25 ---
Works for me.
--
kargl at gcc dot gnu dot org changed:
What|Removed |Added
Status|WAITIN
--- Comment #5 from lanceb at ksu dot edu 2009-10-02 15:29 ---
Subject: Re: Segmentation fault calling DGETRF from gfortran
I have not figured out what is going on. I've been using G95 because it
works correctly with G95. When I have more time (things are very busy
right now) I will
--- Comment #4 from kargl at gcc dot gnu dot org 2009-10-01 17:30 ---
(In reply to comment #2)
> Subject: Re: Segmentation fault calling DGETRF from
> gfortran
>
> Well, that's an embarrassing mistake. My apologies. For some reason the
> example
> code does run correctly for G95.
>
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2009-09-19 15:01
---
Lets keep this bug open while you are hunting so we don't forget. Waiting
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
--
--- Comment #2 from lanceb at k-state dot edu 2009-09-19 14:48 ---
Subject: Re: Segmentation fault calling DGETRF from
gfortran
Well, that's an embarrassing mistake. My apologies. For some reason the example
code does run correctly for G95.
In my (much larger) program I do call DGETR
--- Comment #1 from dominiq at lps dot ens dot fr 2009-09-19 14:01 ---
Have a look at http://linux.die.net/man/l/dgetrf for the calling convention.
The following works for me:
program det_test
implicit none
integer, parameter :: p15=selected_real_kind(15)
integer :: ipiv(2)
real
