From: Peter <peter.spamcatcher@rimuhosting.com>
Cc: xen-devel@lists.xensource.com, Reuben Kabel <kabel@us.ibm.com>
Subject: Re: Java Problems
Date: Sat, 13 Aug 2005 09:29:39 +1200 [thread overview]
Message-ID: <42FD14C3.9000203@rimuhosting.com> (raw)
In-Reply-To: <42FD03F7.4080901@rimuhosting.com>
Oh. And to just simplify this test case a little more I bypass Java
altogether and use this little C gem. It also triggers the problem.
#include <stdio.h>
float s_i = 0.75;
void test(float i) {
if(i!=s_i) {
printf("error\n");
}
}
int main(char **args) {
printf("Starting\n");
long i=0;
for (i = 0;i<100000000; i++) {
test(s_i);
}
return 0;
}
Starting
errorStarting
Starting
Starting
Starting
errorerrorerrorerrorStarting
errorStarting
errorStarting
Starting
Starting
Starting
errorerrorerrorStarting
Peter wrote:
> Hi.
>
> I don't have a 2.0.7 to test on at the moment. I will try again when I do.
>
> I got rid of the object allocation inside the loop. And I retested. I
> don't hit the problem with int's on the call stack. I do hit the
> problem with floats and doubles.
>
> The problem is quite easily reproducible (for me). Is someone there
> with knowledge of register/stack handle able to take a look with gdb or
> which ever tool you use?
>
> Regards, Peter
> http://rimuhosting.com - Xen VPS Hosting
>
next prev parent reply other threads:[~2005-08-12 21:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF8DAF4393.0622A224-ON8525705B.004B18C0-8525705B.004B6D78@us.ibm.com>
2005-08-12 20:17 ` Java Problems Peter
2005-08-12 21:29 ` Peter [this message]
2005-08-13 11:57 ` Keir Fraser
2005-08-14 0:29 ` Peter
2005-08-12 13:31 David_Wolinsky
-- strict thread matches above, loose matches on Subject: below --
2005-08-12 10:12 Ian Pratt
2005-08-12 8:16 Ian Pratt
2005-08-12 9:35 ` Peter
2005-08-12 3:03 Peter
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=42FD14C3.9000203@rimuhosting.com \
--to=peter.spamcatcher@rimuhosting.com \
--cc=kabel@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.