public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rrodrigues at poli dot ufrj.br" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/58913] Segmentation fault on real128 array
Date: Tue, 12 Nov 2013 11:46:00 -0000 [thread overview]
Message-ID: <bug-58913-4-QdLs0pnxS3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58913-4@http.gcc.gnu.org/bugzilla/>
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.
next prev parent reply other threads:[~2013-11-12 11:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-58913-4@http.gcc.gnu.org/bugzilla/>
2013-10-29 19:36 ` kargl at gcc dot gnu.org
2013-10-29 19:40 ` kargl at gcc dot gnu.org
2013-10-29 19:47 ` rrodrigues at poli dot ufrj.br
2013-10-29 19:54 ` sgk at troutmask dot apl.washington.edu
2013-10-29 20:02 ` rrodrigues at poli dot ufrj.br
2013-10-29 20:21 ` sgk at troutmask dot apl.washington.edu
2013-10-29 20:39 ` rrodrigues at poli dot ufrj.br
2013-10-29 20:55 ` sgk at troutmask dot apl.washington.edu
2013-10-30 3:41 ` rrodrigues at poli dot ufrj.br
2013-11-12 11:46 ` rrodrigues at poli dot ufrj.br [this message]
2013-11-25 0:57 ` kargl at gcc dot gnu.org
2013-11-25 2:13 ` rrodrigues at poli dot ufrj.br
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-58913-4-QdLs0pnxS3@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).