[Bug fortran/60774] New: f951: internal compiler error: Segmentation fault: 11
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60774 Bug ID: 60774 Summary: f951: internal compiler error: Segmentation fault: 11 Product: gcc Version: 4.6.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: kevinecahill at gmail dot com Created attachment 32555 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32555&action=edit A fortran program I wrote. gfortran -Wall -O3 -o $1 $2 energy.f95:180.3: 123 1 Warning: Ignoring statement label in empty statement at (1) f951: internal compiler error: Segmentation fault: 11 Please submit a full bug report, with preprocessed source if appropriate.
[Bug fortran/60774] f951: internal compiler error: Segmentation fault: 11
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60774 --- Comment #4 from Kevin Cahill --- Thank you. Best wishes, Kevin Kevin Cahill Professor of Physics & Astronomy Physics Dept. 1919 Lomas NE, MSC 07 4220 University of New Mexico Albuquerque, NM 87131-0001 kevinecah...@gmail.com cah...@unm.edu 505 205 5448 Until 14 July, I am at KIAS in Seoul +82 (0) 10-2930-5448 On Jun 30, 2014, at 11:48 AM, bdavis at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60774 > > Bud Davis changed: > > What|Removed |Added > > CC||bdavis at gcc dot gnu.org > > --- Comment #3 from Bud Davis --- > reduced a bit further. > > > program energy > go to 123 > 123 > contains > function T(i,j,k,l,iu,ju,ku,lu,id,jd,kd,ld) > end function T > end program energy > > > the label is "123" > make it "123 " > > and the segfault does not happen. > > (random strange thing seen when reducing it) > > -- > You are receiving this mail because: > You reported the bug.
[Bug fortran/61928] a fortran90 program compiles on hopper at NERSC but not under gfortran 4.9.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61928 --- Comment #2 from Kevin Cahill --- Nonsense. I included the linpack subroutines explicitly. Look at my fortan code. Best wishes, Kevin Kevin Cahill Professor of Physics & Astronomy Physics Dept. 1919 Lomas NE, MSC 07 4220 University of New Mexico Albuquerque, NM 87131-0001 kevinecah...@gmail.com cah...@unm.edu 505 205 5448 On Jul 27, 2014, at 1:39 PM, pinskia at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61928 > > Andrew Pinski changed: > > What|Removed |Added > >Version|unknown |4.9.0 > > --- Comment #1 from Andrew Pinski --- > You are not linking with the linpack library. > > -- > You are receiving this mail because: > You reported the bug.
[Bug fortran/61928] a fortran90 program compiles on hopper at NERSC but not under gfortran 4.9.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61928 --- Comment #4 from Kevin Cahill --- Thanks. That sounds sensible. I will check it. Best wishes, Kevin Kevin Cahill Professor of Physics & Astronomy Physics Dept. 1919 Lomas NE, MSC 07 4220 University of New Mexico Albuquerque, NM 87131-0001 kevinecah...@gmail.com cah...@unm.edu 505 205 5448 On Jul 27, 2014, at 3:10 PM, jvdelisle at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61928 > > Jerry DeLisle changed: > > What|Removed |Added > > CC||jvdelisle at gcc dot gnu.org > > --- Comment #3 from Jerry DeLisle --- > With you attachment, I am getting this: > > /tmp/ccBACux5.o: In function `dgefa.2334': > pr61928.f90:(.text+0x1282): undefined reference to `idamax_' > /tmp/ccBACux5.o: In function `dgedi.2345': > pr61928.f90:(.text+0x19fa): undefined reference to `dscal_' > pr61928.f90:(.text+0x1aba): undefined reference to `daxpy_' > pr61928.f90:(.text+0x1c2d): undefined reference to `daxpy_' > pr61928.f90:(.text+0x1cbd): undefined reference to `dswap_' > collect2: error: ld returned 1 exit status > > I did not link this with anything. The four last listed procedures listed are > not defined in the attachment, although used. > > In subroutine dgefa, idamax is defined as an integer. If I delete that line, > the undefined reference to idamax_ goes away. The last four references I > suspect are in the BLAS library that I am not linked to at the moment. > > -- > You are receiving this mail because: > You reported the bug.
