public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mexas at bristol dot ac.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/47642] real(kind=16) - libquadmath - segfault on amd64 FreeBSD
Date: Wed, 09 Feb 2011 00:54:00 -0000 [thread overview]
Message-ID: <bug-47642-4-AIFOvdnXIw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47642-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47642
--- Comment #8 from Anton Shterenlikht <mexas at bristol dot ac.uk> 2011-02-09 00:43:07 UTC ---
With Gerald's patch (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47649)
I got gcc46 installed on FreeBSD sparc64,
and there I don't get segfault:
QOF> uname -a
FreeBSD mech-anton240.men.bris.ac.uk 9.0-CURRENT FreeBSD 9.0-CURRENT #1
r216048: Mon Nov 29 15:19:12 GMT 2010
root@mech-anton240.men.bris.ac.uk:/usr/obj/usr/src/sys/QOF sparc64
QOF> cat kind16.f90
program z
implicit none
real(kind=16) :: q
q=1.0e39_16
write(*,*)q
write(*,*)nearest(q,1.0)
write(*,*)nearest(q,1.0)-q
end program z
QOF> gfortran46 -Wl,-rpath=/usr/local/lib/gcc46 kind16.f90
QOF> ./a.out
1.00000000000000000000000000000000000E+0039
1.00000000000000000000000000000000013E+0039
131072.00000000000000000000000000000
QOF>
next prev parent reply other threads:[~2011-02-09 0:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 9:56 [Bug fortran/47642] New: " mexas at bristol dot ac.uk
2011-02-08 10:44 ` [Bug fortran/47642] " dominiq at lps dot ens.fr
2011-02-08 12:51 ` jvdelisle at gcc dot gnu.org
2011-02-08 12:54 ` jakub at gcc dot gnu.org
2011-02-08 13:37 ` jvdelisle at gcc dot gnu.org
2011-02-08 14:06 ` jakub at gcc dot gnu.org
2011-02-08 18:28 ` burnus at gcc dot gnu.org
2011-02-08 20:25 ` jvdelisle at gcc dot gnu.org
2011-02-09 0:54 ` mexas at bristol dot ac.uk [this message]
2011-02-09 9:03 ` jakub at gcc dot gnu.org
2011-02-12 12:03 ` jakub at gcc dot gnu.org
2011-02-12 12:07 ` jakub at gcc dot gnu.org
2011-02-12 12:08 ` jakub at gcc dot gnu.org
2011-02-12 12:10 ` jakub at gcc dot gnu.org
2011-02-12 12:49 ` jakub at gcc dot gnu.org
2011-02-12 14:57 ` jakub at gcc dot gnu.org
2011-02-14 11:52 ` dominiq at lps dot ens.fr
2011-02-14 11:57 ` jakub at gcc dot gnu.org
2011-02-14 12:56 ` dominiq at lps dot ens.fr
2011-02-14 14:34 ` jakub at gcc dot gnu.org
2011-02-14 15:35 ` dominiq at lps dot ens.fr
2011-02-14 15:45 ` jakub at gcc dot gnu.org
2011-02-17 13:42 ` jakub at gcc dot gnu.org
2011-02-17 14:25 ` jakub at gcc dot gnu.org
2014-04-16 15:46 ` mexas at bristol dot ac.uk
2014-04-17 6:53 ` ubizjak at gmail dot com
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-47642-4-AIFOvdnXIw@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).