public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "bonzini at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/23283] Sun's JIT faster than gcc for Random.nextDouble
Date: Tue, 23 Aug 2005 14:51:00 -0000 [thread overview]
Message-ID: <20050823145143.2575.qmail@sourceware.org> (raw)
In-Reply-To: <20050808100453.23283.netzberg@gmail.com>
------- Additional Comments From bonzini at gcc dot gnu dot org 2005-08-23 14:51 -------
> It looks like the problem is that we don't remove the synchronization
> for nextDouble() even though the test case is single-threaded.
If we can remove even only half of the synchronization overhead, by
synchronizing just once per nextDouble() call, it's a win.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23283
prev parent reply other threads:[~2005-08-23 14:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 10:04 [Bug java/23283] New: Java interpreter significantly faster than gcc?! netzberg at gmail dot com
2005-08-08 13:32 ` [Bug java/23283] Sun's JIT faster than gcc pinskia at gcc dot gnu dot org
2005-08-08 13:33 ` [Bug java/23283] Sun's JIT faster than gcc for Random.nextDouble pinskia at gcc dot gnu dot org
2005-08-23 14:15 ` tromey at gcc dot gnu dot org
2005-08-23 14:31 ` mark at klomp dot org
2005-08-23 14:48 ` bonzini at gcc dot gnu dot org
2005-08-23 14:51 ` bonzini at gcc dot gnu dot org [this message]
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=20050823145143.2575.qmail@sourceware.org \
--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).