This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
It's attached, but probably not very informative; __java_double is understood by the front end. But it's a bit hard for me to follow what it does with it, or why it exists as a type distinct from double. Hans > -----Original Message----- > From: Andrew Haley [mailto:aph@cambridge.redhat.com] > Sent: Tuesday, April 09, 2002 9:37 AM > To: Boehm, Hans > Cc: 'java@gcc.gnu.org'; 'tromey@redhat.com' > Subject: Problem with interpreted double operations on IA64 > > > Boehm, Hans writes: > > Could someone point me at a description of exactly how > type __java_double > > should differ from double? As far as I can tell, > __java_double is used > > primarily by the interpreter? On X86 this seems to work > correctly. On IA64 > > (and perhaps other 64-bit platforms?), it seems to get > confused about the > > low order bits. This means that "double precision" results in the > > interpreter are computed at most to single precision > accuracy. Here's a C++ > > example to demonstrate the issue. Gij runs into the same > problems, causing > > scimark to fail, etc. (This is with a very recent 3.1 tree.) > > Weird. Could you please run gcc with '-save-temps -dD' and let us > have the double.ii file you get? > > Andrew. >
Attachment:
double.ii
Description: Binary data
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |