http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58913
--- Comment #10 from Rodrigo Rodrigues <rrodrigues at poli dot ufrj.br> --- (In reply to Steve Kargl from comment #8) > On Tue, Oct 29, 2013 at 08:39:15PM +0000, rrodrigues at poli dot ufrj.br > wrote: > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58913 > > > > --- Comment #7 from Rodrigo Rodrigues <rrodrigues at poli dot ufrj.br> --- > > Here goes the backtrack: > > > > #0 0x00000000 in ?? () > > #1 0x0042d483 in output_float_FMT_G_16 (comp_d=<optimized out>, > > zero_flag=<optimized out>, sign_bit=<optimized out>, > > size=<optimized out>, buffer=<optimized out>, m=<optimized out>, > > f=0x22fb6c, dtp=<optimized out>) > > at ../../../gcc-4.8.0-mingw/libgfortran/io/write_float.def:1112 > > #2 write_float (dtp=dtp@entry=0x22fcf8, f=f@entry=0x22fbbc, > > source=source@entry=0x22fe70 "", len=len@entry=16, > > comp_d=comp_d@entry=1) > > at ../../../gcc-4.8.0-mingw/libgfortran/io/write_float.def:1259 > > Unfortnately, your trace suggests to me that this is MingW > specific. I can't help beyond this point. Prehaps, ping > the MingW developers? Well, as I got gfortran binaries from http://www.equation.com/ I've contacted the Equation Team and they confirmed that that is a platform specific bug. They addressed this bug and recommended to not use real128 float numbers. So I think that this bug report can be closed here. Thank you for the attention.
