From: Andrew Haley <aph@redhat.com>
To: java@gcc.gnu.org
Subject: Re: Multithreading via GCJ
Date: Fri, 24 Feb 2012 17:36:00 -0000 [thread overview]
Message-ID: <4F47CA9D.5080600@redhat.com> (raw)
In-Reply-To: <20120224173135.26160@gmx.net>
On 02/24/2012 05:31 PM, dornenteufel@gmx.net wrote:
> the last days I worked a little bit with the GCJ compiler and my
> Java programs. I have two question and hope that someone has the
> right answers for me :-).
>
> 1.) How does the scheduling change when I compile my program via
> gcj? Is there a special scheduling algorithm or will there only be
> the OS scheduling used?
The OS scheduling is used. This is generally true for Java
implementations these days.
> 2.) Everytime I compile my programs, I get multiple times this
> warning "GC Warning: Thread stack pointer 0x7ffac960 out of range,
> pushing everything" What does that mean? Additionally I have the
> problem that my program crash with settings which work under eclipse
> wonderfully.
This means that the garbage collector isn't finding the threads. This
is a bug.
Andrew.
prev parent reply other threads:[~2012-02-24 17:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 17:32 dornenteufel
2012-02-24 17:36 ` Andrew Haley [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=4F47CA9D.5080600@redhat.com \
--to=aph@redhat.com \
--cc=java@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).