[Bug fortran/55916] Alignment issues with real(16) on i686

2015-12-06 Thread jouko.orava at iki dot fi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55916 --- Comment #13 from Jouko Orava --- (In reply to Joost VandeVondele from comment #12) > I'm wondering if you had a working patch at some point. Not a comprehensive one, no. I recall modifying libgfortran/runtime/memory.c was not sufficient. I

[Bug fortran/50201] gfortran with -static causes seg fault at runtime for writing double prec array with precision increased to kind=16

2015-12-05 Thread jouko.orava at iki dot fi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50201 --- Comment #14 from Jouko Orava --- (In reply to Steve Kargl from comment #13) > I've tested your patch on i386-*-freebsd. It works. Excellent, thank you. > Do you have commit privilege for the source tree? > The patch with a testcase is ok.

[Bug fortran/50201] gfortran with -static causes seg fault at runtime for writing double prec array with precision increased to kind=16

2015-12-04 Thread jouko.orava at iki dot fi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50201 --- Comment #12 from Jouko Orava --- I suspect the bug occurs because libgfortran uses the weak symbol version of quadmath_snprintf(). Unfortunately, I don't have the resources to verify this in the near future. If you could recompile gcc/gfortr

[Bug fortran/50201] gfortran with -static causes seg fault at runtime for writing double prec array with precision increased to kind=16

2015-12-04 Thread jouko.orava at iki dot fi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50201 --- Comment #11 from Jouko Orava --- Created attachment 36931 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36931&action=edit Untested patch to fix the bug.

[Bug fortran/61261] [OOP] Segfault on source-allocating polymorphic variables

2014-05-21 Thread jouko.orava at iki dot fi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61261 Jouko Orava changed: What|Removed |Added CC||jouko.orava at iki dot fi --- Comment #6

[Bug fortran/55916] Alignment issues with real(16) on i686

2014-02-08 Thread jouko.orava at iki dot fi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55916 --- Comment #11 from Jouko Orava --- Just in case there are users who encounter this bug report, here is the single-file workaround. Save the following as nosegfault.c, and follow the instructions in the comments. It can be compiled into a shared

[Bug fortran/55916] Alignment issues with real(16) on i686

2014-02-08 Thread jouko.orava at iki dot fi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55916 --- Comment #10 from Jouko Orava --- (In reply to Dominique d'Humieres from comment #9) > I can do the testing on darwin (intel d10 and d13, ppc d9). That would be very much appreciated. I've put a tarball and some background info on my web page

[Bug fortran/55916] Alignment issues with real(16) on i686

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

[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 --- This bug is a duplicate of #55916.

[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 --- 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, gdb newtest and run unt

[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 --- 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 disassembly is 80493a0: e8

[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 --- 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 this bug #60088 is 66 0f

[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 changed: What|Removed |Added CC||jouko.orava at iki dot fi --- Comment #15

[Bug fortran/50201] gfortran with -static causes seg fault at runtime for writing double prec array with precision increased to kind=16

2014-02-06 Thread jouko.orava at iki dot fi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50201 --- Comment #9 from Jouko Orava --- It turns out that while fdp2.f90, PROGRAM fdp2 IMPLICIT none INTEGER, PARAMETER :: b128 = SELECTED_REAL_KIND(33, 1000) REAL(KIND=b128) :: x(4) x = 3.4_b128 PRINT *, KI

[Bug fortran/50201] gfortran with -static causes seg fault at runtime for writing double prec array with precision increased to kind=16

2014-02-06 Thread jouko.orava at iki dot fi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50201 --- Comment #8 from Jouko Orava --- I confirm, still occurs with 4.7.3 and 4.8.1. For simplicity, I obtained the 4.7 and 4.8 versions from Ubuntu toolchain test builds' PPA, https://launchpad.net/~ubuntu-toolchain-r/. GNU Fortran 4.7.3 (Ubuntu/L

[Bug fortran/50201] gfortran with -static causes seg fault at runtime for writing double prec array with precision increased to kind=16

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