public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "folkert at vanheusden dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/58669] New: does not detect all cpu cores/threads
Date: Wed, 09 Oct 2013 15:54:00 -0000	[thread overview]
Message-ID: <bug-58669-8172@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 58669
           Summary: does not detect all cpu cores/threads
           Product: gcc
           Version: 4.8.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: java
          Assignee: unassigned at gcc dot gnu.org
          Reporter: folkert at vanheusden dot com

Created attachment 30970
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30970&action=edit
example code

When a java program compiled with gcj asks how many processing units are in the
system, it always returns 1.

folkert@belle:~$ cat test2.java
class test2 {
        public static void main(String [] args) {
                System.out.println("" +
Runtime.getRuntime().availableProcessors());
        }
}
folkert@belle:~$ javac test2.java
folkert@belle:~$ java test2
12
folkert@belle:~$ gcj --main=test2 test2.java
folkert@belle:~$ ./a.out
1


             reply	other threads:[~2013-10-09 15:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-09 15:54 folkert at vanheusden dot com [this message]
2013-10-09 16:27 ` [Bug java/58669] " gnu_andrew at member dot fsf.org
2013-10-09 16:35 ` gnu_andrew at member dot fsf.org
2013-10-09 16:36 ` folkert at vanheusden dot com
2013-10-09 18:36 ` gnu_andrew at member dot fsf.org
2013-10-09 18:36 ` gnu_andrew at member dot fsf.org
2013-10-18  1:17 ` gnu_andrew at member dot fsf.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-58669-8172@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).