[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 sgk at troutmask dot apl.washington.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50201 --- Comment #16 from Steve Kargl --- On Sat, Dec 05, 2015 at 08:13:25AM +, jouko.orava at iki dot fi wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50201 > > --- Comment #14 from Jouko Orava --- > (In reply to Steve Kargl from

[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 kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50201 --- Comment #17 from kargl at gcc dot gnu.org --- Author: kargl Date: Sat Dec 5 18:12:26 2015 New Revision: 231320 URL: https://gcc.gnu.org/viewcvs?rev=231320=gcc=rev Log: 2015-12-05 Juoko Orava PR fortran/50201

[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 dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50201 --- Comment #15 from Dominique d'Humieres --- > The patch with a testcase is ok. Beware that some platforms don't support -static, e.g., darwin.

[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 kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50201 --- Comment #18 from kargl at gcc dot gnu.org --- Author: kargl Date: Sat Dec 5 23:33:23 2015 New Revision: 231323 URL: https://gcc.gnu.org/viewcvs?rev=231323=gcc=rev Log: 2015-12-05 Juoko Orava PR fortran/50201

[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 kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50201 kargl at gcc dot gnu.org changed: What|Removed |Added Status|WAITING |RESOLVED

[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 dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50201 --- Comment #10 from Dominique d'Humieres --- Any progress?

[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=edit Untested patch to fix the bug.

[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

[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 sgk at troutmask dot apl.washington.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50201 --- Comment #13 from Steve Kargl --- On Sat, Dec 05, 2015 at 12:26:14AM +, jouko.orava at iki dot fi wrote: > I suspect the bug occurs because libgfortran uses the weak symbol version of > quadmath_snprintf(). Unfortunately, I don't have the

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

[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 dominiq at lps dot ens.fr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50201 --- Comment #7 from Dominique d'Humieres dominiq at lps dot ens.fr --- Confirmed. The second test case still segfaults when run if compiled with -static in Linux 3.8.0 x86_64 kernel on Ubuntu 12.04.4 LTS, using gfortran 4.6.3 (Ubuntu/Linaro

[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 jouko.orava at iki dot fi --- 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/.

[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 jouko.orava at iki dot fi --- 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 =

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

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

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

2011-08-26 Thread kargl at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50201 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org ---

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

2011-08-26 Thread longb at cray dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50201 --- Comment #2 from Bill Long longb at cray dot com 2011-08-26 21:00:04 UTC --- OS is Linux SLES 11. From the output in the test, it looks like you tried only the scalar case, which I agree works. The array case (second test code) is the one

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

2011-08-26 Thread sgk at troutmask dot apl.washington.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50201 --- Comment #3 from Steve Kargl sgk at troutmask dot apl.washington.edu 2011-08-26 21:09:42 UTC --- On Fri, Aug 26, 2011 at 09:00:04PM +, longb at cray dot com wrote: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50201 --- Comment #2 from

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

2011-08-26 Thread sgk at troutmask dot apl.washington.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50201 --- Comment #4 from Steve Kargl sgk at troutmask dot apl.washington.edu 2011-08-26 21:29:41 UTC --- On Fri, Aug 26, 2011 at 09:09:42PM +, sgk at troutmask dot apl.washington.edu wrote: ==4791== Conditional jump or move depends on