public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "konqueror at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/26483] New: Wrong parsing of doubles when interpreted
Date: Mon, 27 Feb 2006 16:18:00 -0000 [thread overview]
Message-ID: <bug-26483-3744@http.gcc.gnu.org/bugzilla/> (raw)
I tried to run the attached test case on IA64 native and interpreted. The bad
news is that both give totally different results:
Native:
mkoch@merulo:~$ gcj-4.0 DoubleTest.java -o doubleTest --main=DoubleTest -g
mkoch@merulo:~$ ./doubleTest
5.0E-324
Interpreted:
mkoch@merulo:~$ gij-4.0 DoubleTest
8.881784197001252E-16
The interpreted case is wrong. This seems to be a bug in fdlibm as
jamvm/classpath has the same bug. This bug only happens on IA64 as far as I
know. E.g. it makes building GNU classpath fail with ecj. I wonder what GCJ
does that makes this work in the native case ...
--
Summary: Wrong parsing of doubles when interpreted
Product: gcc
Version: 4.0.3
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libgcj
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: konqueror at gmx dot de
GCC build triplet: ia64-linux-gnu
GCC host triplet: ia64-linux-gnu
GCC target triplet: ia64-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26483
next reply other threads:[~2006-02-27 16:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 16:18 konqueror at gmx dot de [this message]
2006-02-27 16:20 ` [Bug libgcj/26483] " konqueror at gmx dot de
2006-02-27 17:03 ` pinskia at gcc dot gnu dot org
2006-02-27 17:26 ` konqueror at gmx dot de
2006-02-28 3:25 ` wilson at gcc dot gnu dot org
2006-02-28 21:15 ` joseph at codesourcery dot com
2006-02-28 21:40 ` schwab at suse dot de
2006-02-28 21:50 ` joseph at codesourcery dot com
2006-02-28 22:02 ` schwab at suse dot de
2006-03-06 17:08 ` [Bug libgcj/26483] Wrong parsing of doubles when interpreted on ia64 tromey at gcc dot gnu dot org
2006-03-08 0:46 ` wilson at gcc dot gnu dot org
2006-03-08 0:51 ` wilson at gcc dot gnu dot org
2006-04-04 19:07 ` tromey at gcc dot gnu dot org
2006-04-04 20:22 ` wilson at tuliptree dot org
2006-04-04 20:24 ` wilson at gcc dot gnu dot org
2006-04-04 20:46 ` andreast at gcc dot gnu dot org
2006-04-07 23:01 ` wilson at tuliptree dot org
2006-04-07 23:04 ` wilson at gcc dot gnu dot org
2006-04-12 22:10 ` wilson at gcc dot gnu dot org
2006-04-12 22:21 ` wilson at gcc dot gnu dot org
2006-04-12 22:22 ` wilson at gcc dot gnu dot org
2006-05-26 14:58 ` konqueror at gmx dot de
2006-06-01 22:36 ` wilson at gcc dot gnu dot org
2006-06-17 1:01 ` tromey at gcc dot gnu dot org
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-26483-3744@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=java-prs@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).