public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia 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
Date: Mon, 08 Aug 2005 13:32:00 -0000	[thread overview]
Message-ID: <20050808133230.31562.qmail@sourceware.org> (raw)
In-Reply-To: <20050808100453.23283.netzberg@gmail.com>


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-08-08 13:32 -------
Actually for me Sun's java and GCJ take about the same at the default settings (well for GCJ compiled at 
-O3).

Now if I change Sun's java to use the server tuned JIT, Sun's java is 2 seconds while GCJ is still 4.5 or so.


timecopper:~>time ./a.out
4999358.6586720785
4.900u 0.070s 0:06.12 81.2%     0+0k 0+0io 148pf+0w
copper:~>javac X.java
java Xcopper:~>java X
5001132.020866861
copper:~>time java X
5000974.98115474
4.791u 0.037s 0:04.88 98.7%     0+0k 0+0io 0pf+0w
copper:~>time java -server X
5000248.791328681
3.290u 0.061s 0:03.91 85.6%     0+0k 0+0io 54pf+0w

This with keeping and printing out the return value for nextDouble.

This might be startup/shut down time taking into account.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Java interpreter            |Sun's JIT faster than gcc
                   |significantly faster than   |
                   |gcc?!                       |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23283


  reply	other threads:[~2005-08-08 13:32 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 ` pinskia at gcc dot gnu dot org [this message]
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

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=20050808133230.31562.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).