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

2014-02-07 Thread ubizjak at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 Uroš Bizjak ubizjak at gmail dot com changed: What|Removed |Added Status|WAITING |RESOLVED

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

2014-02-07 Thread thatcadguy at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #23 from Jacob Abel thatcadguy at gmail dot com --- If it helps at all, the following produces the same problem under gcc: #include quadmath.h #include stdlib.h int main(void) { __float128 *ptr = NULL; int i; if (ptr =

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

2014-02-06 Thread dominiq at lps dot ens.fr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 Dominique d'Humieres dominiq at lps dot ens.fr changed: What|Removed |Added Status|UNCONFIRMED |WAITING

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

2014-02-06 Thread dominiq at lps dot ens.fr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #10 from Dominique d'Humieres dominiq at lps dot ens.fr --- This could be a duplicate of pr50201.

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

2014-02-06 Thread thatcadguy at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #11 from Jacob Abel thatcadguy at gmail dot com --- The culprit that -march=native activates on my Core i7 laptop is -mavx. Compiling with -mavx causes the segfault, without is fine. Unfortunately, that flag was not set on my other

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

2014-02-06 Thread thatcadguy at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #12 from Jacob Abel thatcadguy at gmail dot com --- Created attachment 32074 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=32074action=edit NEW smaller simpler file to create the segfault

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

2014-02-06 Thread thatcadguy at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #13 from Jacob Abel thatcadguy at gmail dot com --- The following file: SUBROUTINE test(N) IMPLICIT NONE INTEGER, INTENT(IN) :: N REAL(KIND=16) :: array(N) array = 0 END SUBROUTINE test PROGRAM main IMPLICIT NONE CALL test(10) END

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

2014-02-06 Thread kargl at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #14 from kargl at gcc dot gnu.org --- (In reply to Jacob Abel from comment #8) Seriously? Look, you falsely assumed it was mingw only. Yes, with the information I had at the time, I thought the problem was mingw specific. No wonder

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

2014-02-06 Thread jouko.orava at iki dot fi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 Jouko Orava jouko.orava at iki dot fi changed: What|Removed |Added CC||jouko.orava at iki

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

2014-02-06 Thread thatcadguy at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #16 from Jacob Abel thatcadguy at gmail dot com --- Still segfaults, at least on MinGW: C:\Users\Jake\Downloadsgfortran -march=native -Wl,-uquadmath_snprintf newtest.f 90 C:\Users\Jake\Downloadsa Program received signal SIGSEGV:

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

2014-02-06 Thread jouko.orava at iki dot fi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #18 from Jouko Orava jouko.orava at iki dot fi --- Addendum: the unaligned access causing the segfault seems to occur because __libc_malloc returns an address aligned to 8 bytes, but it is used as if it was aligned to 16 bytes. The

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

2014-02-06 Thread thatcadguy at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #19 from Jacob Abel thatcadguy at gmail dot com --- jake@Jake-E1505:~/Desktop$ gfortran -static -march=native -Wl,-uquadmath_snprintf newtest.f90 -o newtest jake@Jake-E1505:~/Desktop$ gdb newtest GNU gdb (GDB)

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

2014-02-06 Thread jouko.orava at iki dot fi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #17 from Jouko Orava jouko.orava at iki dot fi --- I asked and received the details from Jacob Abel off-list, to find out if this bug #60088 is related to bug #50201. They do not seem to be. The instruction causing the segfault in

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

2014-02-06 Thread jouko.orava at iki dot fi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #20 from Jouko Orava jouko.orava at iki dot fi --- Apologies, Jacob; my advice was faulty. Could you please retest using the following? Compile the binary using gfortran -march=native -ggdb newtest.f90 -o newtest then start gdb,

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

2014-02-06 Thread jouko.orava at iki dot fi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #21 from Jouko Orava jouko.orava at iki dot fi --- This bug is a duplicate of #55916.

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

2014-02-05 Thread jvdelisle at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 Jerry DeLisle jvdelisle at gcc dot gnu.org changed: What|Removed |Added CC||jvdelisle at

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

2014-02-05 Thread sgk at troutmask dot apl.washington.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #5 from Steve Kargl sgk at troutmask dot apl.washington.edu --- On Thu, Feb 06, 2014 at 02:25:27AM +, thatcadguy at gmail dot com wrote: If you bothered to look at the gcc output file, you'd see that I tested it on Linux as

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

2014-02-05 Thread thatcadguy at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #6 from Jacob Abel thatcadguy at gmail dot com --- (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.

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

2014-02-05 Thread kargl at gcc dot gnu.org
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

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

2014-02-05 Thread thatcadguy at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 --- Comment #8 from Jacob Abel thatcadguy at gmail dot com --- Seriously? Look, you falsely assumed it was mingw only. Jerry reproduced the problem on linux as well. Excuse me for not knowing to post the backtrace. I come here to post a legitimate