public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/21714] [4.0/4.1/4.2/4.3 Regression] libjava bootstrap failure in java/lang/natConcreteProcess.cc
Date: Thu, 17 Jan 2008 22:25:00 -0000	[thread overview]
Message-ID: <20080117222507.13793.qmail@sourceware.org> (raw)
In-Reply-To: <bug-21714-497@http.gcc.gnu.org/bugzilla/>



------- Comment #9 from tromey at gcc dot gnu dot org  2008-01-17 22:25 -------
>From comment #6:

> What are the problems with the old implementation?  Would it make
> sense to resurrect it as natProcessNoThread.c or something?

See PR 11801 for the problems with the old implementation.
Resurrecting the old code for BSD, or trying to fix it, is fine by me.
However, if you don't have threads, very few java programs will actually work.


-- 


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


  parent reply	other threads:[~2008-01-17 22:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-21714-497@http.gcc.gnu.org/bugzilla/>
2005-10-13 19:22 ` [Bug libgcj/21714] [4.0/4.1 " pinskia at gcc dot gnu dot org
2005-10-30 23:32 ` pinskia at gcc dot gnu dot org
2006-02-28 20:37 ` [Bug libgcj/21714] [4.0/4.1/4.2 " mmitchel at gcc dot gnu dot org
2006-05-25  2:45 ` mmitchel at gcc dot gnu dot org
2007-02-14  9:33 ` [Bug libgcj/21714] [4.0/4.1/4.2/4.3 " mmitchel at gcc dot gnu dot org
2008-01-17 22:25 ` tromey at gcc dot gnu dot org [this message]
2008-07-04 16:54 ` [Bug libgcj/21714] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org
2009-03-31 18:48 ` [Bug libgcj/21714] [4.3/4.4/4.5 " jsm28 at gcc dot gnu dot org
2009-08-04 12:28 ` rguenth at gcc dot gnu dot org
2010-05-22 18:12 ` [Bug libgcj/21714] [4.3/4.4/4.5/4.6 " rguenth 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=20080117222507.13793.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).