public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/47642] real(kind=16) - libquadmath - segfault on amd64 FreeBSD
Date: Mon, 14 Feb 2011 14:34:00 -0000 [thread overview]
Message-ID: <bug-47642-4-ii2xsgL7AS@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 #19 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-02-14 14:29:12 UTC ---
THe output depends. I get:
1.234500e+06
1.234500e+06
333333.3333333333333
333333.3333333333333
1.7
1.7
1.7e+36
1.7e+36
0x1.2d644p+20
0x1.2d644p+20
0X1.4585555555555P+18
0X1.4585555555555P+18
0x1.b333333333333333333333333333p+0
0x1.b333333333333p+0
0X1.476878AP+120
0X1.476878AP+120
1.234500e+06
333333.3333333333333
1.7
1.7e+36
0x1.2d644p+20
0X1.4585555555555P+18
0x1.b333333333333333333333333333p+0
0X1.476878AP+120
for the 23313 testcase and
12340000000000.100000
12340000000000.100000
12,340,000,000,000.100000
12,340,000,000,000.100000
12.340.000.000.000,100000
12.340.000.000.000,100000
12 340 000 000 000,100000
12 340 000 000 000,100000
1.234000e+13
1.234000e+13
۱٫۲۳۴۰۰۰e+۱۳
۱٫۲۳۴۰۰۰e+۱۳
for the 23316 testcase. But, the first part of the 23313 testcase relies on
printf hook support which is not present on targets other than Linux, so
you'll see there something different (e.g. %Qe etc. instead, for odd lines),
only the second part which uses quadmath_snprintf should be the same.
And the 23316 testcase is a testcase for localization, which you likely don't
have either (and is not written to use quadmath_snprintf anyway).
next prev parent reply other threads:[~2011-02-14 14:29 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
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 [this message]
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-ii2xsgL7AS@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).