This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug target/60088] Segfault when using quad precision and -march=native on gfortran


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088

--- Comment #7 from kargl at gcc dot gnu.org ---
(In reply to Jacob Abel from comment #6)
> (In reply to Steve Kargl from comment #5)
> > What output file?  gcc_flags.txt does not show a segfault
> > or a debugger backtrace.
> 
> It shows that I was not using MinGW, as you assumed.

No.  It showed that you ran 'gcc -v' on a linux system, and
it showed that you ran some other 'gcc -march=native yada'
command line.  It did not show a segfault or a backtrace.
It did not show any problem with linux and it did not
show a problem on mingw.

> Here's the gdb output:

Oh, here's the missing information.

> jake@Jake-E1505:~/Downloads$ gdb sip_test
> GNU gdb (GDB) 7.5.91.20130417-cvs-ubuntu
> Copyright (C) 2013 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "i686-linux-gnu".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>...
> Reading symbols from /home/jake/Downloads/sip_test...done.
> (gdb) start
> Temporary breakpoint 1 at 0x8048ec0: file sip_test.f90, line 1.
> Starting program: /home/jake/Downloads/sip_test 
> 
> Temporary breakpoint 1, MAIN__ () at sip_test.f90:1
> 1	PROGRAM main
> (gdb) continue
> Continuing.
> 
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x0804a9bb in sip (as=..., aw=..., ao=..., ae=..., an=..., s=..., x=...,
> n=40, 
>     k=1600, alp=<error reading variable>, tol=<error reading variable>, 
>     lim=200, show=.TRUE., fail=.FALSE.) at sip.f90:19
> 19	b = zero; c = zero; d = zero; e = zero; f = zero
> (gdb) 

Too bad you forgot to at least type bt at the (gdb) prompt.


> 
> And the normal output:
> jake@Jake-E1505:~/Downloads$ ./sip_test 
> 
> 
> Program received signal SIGSEGV: Segmentation fault - invalid memory
> reference.
> 
> Backtrace for this error:
> #0  0xB76C3CAB
> #1  0xB76C42FC
> #2  0xB77C33FF
> #3  0x804A9BB in sip_ at sip.f90:19 (discriminator 6)
> #4  0x804A411 in MAIN__ at sip_test.f90:45
> Segmentation fault (core dumped)
> 
> 
> As I stated, if you take away the -march=native compile flag, it's fine.


And, I stated it works fine of 2 different architectures, and yes,
I used the options that you provided.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]