From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org, dj@redhat.com,
neroden@gcc.gnu.org, aoliva@redhat.com,
Ralf.Wildenhues@gmx.de, green@redhat.com
Subject: Re: Toplevel cleanup: disable Java when libffi not supported
Date: Thu, 28 Apr 2011 13:40:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1104281334280.28618@digraph.polyomino.org.uk> (raw)
In-Reply-To: <4DB90A6A.1040009@gnu.org>
On Thu, 28 Apr 2011, Paolo Bonzini wrote:
> Do you plan to finish the switch to unsupported_languages instead of
> noconfigdirs soon )for Java)?
I plan one further patch to simplify the libgcj-disabling logic (and in
particular to eliminate the disabling for *-*-*), but not to convert it
completely to unsupported_languages. I also plan to split the
newlib/libgloss logic out of the general case statement over targets, as
part of further simplifications there. I don't plan to work on the
general elimination of target-libiberty.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2011-04-28 13:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 15:50 Toplevel cleanup: split out libgcj disabling Joseph S. Myers
2011-04-27 16:34 ` Toplevel cleanup: disable Java when libffi not supported Joseph S. Myers
2011-04-27 16:38 ` Andrew Haley
2011-04-28 6:34 ` Paolo Bonzini
2011-04-28 13:40 ` Joseph S. Myers [this message]
2011-04-28 16:18 ` Toplevel cleanup: reduce libgcj disabling Joseph S. Myers
2011-04-28 16:41 ` Paolo Bonzini
2011-04-29 16:26 ` Toplevel cleanup: disable Java when libffi not supported Tom Tromey
2011-04-29 22:57 ` Joseph S. Myers
2011-05-03 15:16 ` Tom Tromey
2011-04-27 17:31 ` Toplevel cleanup: split out libgcj disabling Mike Stump
2011-04-28 6:31 ` Paolo Bonzini
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=Pine.LNX.4.64.1104281334280.28618@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=aoliva@redhat.com \
--cc=bonzini@gnu.org \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=green@redhat.com \
--cc=java-patches@gcc.gnu.org \
--cc=neroden@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).