public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <bonzini@gnu.org>
To: "Joseph S. Myers" <joseph@codesourcery.com>
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
Subject: Re: Toplevel cleanup: reduce libgcj disabling
Date: Thu, 28 Apr 2011 16:41:00 -0000	[thread overview]
Message-ID: <4DB998B8.6020606@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1104281616330.32215@digraph.polyomino.org.uk>

On 04/28/2011 06:17 PM, Joseph S. Myers wrote:
> This patch cleans up the libgcj-disabling case statement at toplevel,
> removing the default disabling for *-*-* (which allows other empty
> cases to be removed) and disabling based on architecture, or most
> cases of architecture-OS combination where the OS previously had
> libgcj built for other architectures.
>
> I left the logic restricting libgcj on Darwin to certain targets, but
> removed that relating to FreeBSD and NetBSD targets (given the removal
> of support for a.out NetBSD, and that there was never such support for
> a.out FreeBSD, I doubt the reliability of the lists of targets that
> were present).  target-libffi disabling for arm-*-elf* | arm*-*-eabi*
> was removed (given that there*is*  libffi support for those targets),
> and target-zlib disabling for hppa*64*-*-linux* was changed to disable
> Java.
>
> This is the last cleanup I plan for this libgcj-disabling logic.  This
> patch is*not*  conservatively safe; the idea is that if it turns out
> that there are problems building some Java library on a
> libffi-supporting target where the library was not previously built,
> appropriate disabling should be added *with a comment explaining the
> problem and probably pointing to a relevant PR*.
>
> OK to commit?
>

Ok.

Paolo

  reply	other threads:[~2011-04-28 16:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27 15:50 Toplevel cleanup: split out " 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
2011-04-28 16:18   ` Toplevel cleanup: reduce libgcj disabling Joseph S. Myers
2011-04-28 16:41     ` Paolo Bonzini [this message]
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=4DB998B8.6020606@gnu.org \
    --to=bonzini@gnu.org \
    --cc=Ralf.Wildenhues@gmx.de \
    --cc=aoliva@redhat.com \
    --cc=dj@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=java-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    --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).