public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steven Bosscher <stevenb.gcc@gmail.com>
To: gcc@gcc.gnu.org, java@gcc.gnu.org, Ian Lance Taylor <iant@google.com>
Subject: Re: PATCH RFA: Do not build java by default
Date: Sun, 31 Oct 2010 19:33:00 -0000	[thread overview]
Message-ID: <AANLkTikPP+=RS4BL_NQFaENvFtvvk9ughpP3kWvWT25A@mail.gmail.com> (raw)

Hello,

Ian Lance Taylor wrote:
> This is not a proposal to remove the Java frontend nor is it leading up
> to that.  It is a proposal to not build the frontend by default, putting
> Java in the same category as Ada and Objective C++.  The main argument
> in favor of this proposal is twofold: 1) building libjava is a large
> component of gcc bootstrap time, and thus a large component in the
> amount of time it takes to test changes; 2) it is in practice very
> unusual for middle-end or back-end changes to cause problems with Java
> without also causing problems for C/C++, thus building and testing
> libjava does not in practice help ensure the stability of the compiler.

The argument against disabling java as a default language always was
that there should be at least one default language that requires
non-call exceptions. I recall testing many patches without trouble if
I did experimental builds with just C, C++, and Fortran, only to find
lots of java test suite failures in a complete bootstrap+test cycle.
So the second point is, IMVHO, not really true.

Is it possible to build and test java without all of libjava?

Ciao!
Steven

             reply	other threads:[~2010-10-31 19:33 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-31 19:33 Steven Bosscher [this message]
2010-10-31 19:47 ` Gerald Pfeifer
2010-11-01  3:48   ` Andrew Pinski
2010-11-01 10:11     ` Dave Korn
2010-11-01  4:06 ` Geert Bosch
2010-11-01  4:30   ` Joern Rennecke
2010-11-01 10:35     ` Geert Bosch
2010-11-01 10:46       ` Joern Rennecke
2010-11-02 10:48         ` Paolo Bonzini
2010-11-02 16:43           ` David Daney
2010-11-01 17:46 ` Tom Tromey
2010-11-01 17:50   ` Andrew Haley
  -- strict thread matches above, loose matches on Subject: below --
2010-10-31 19:09 Ian Lance Taylor
2010-11-01  8:59 ` Andrew Haley
2010-11-02 10:14   ` Laurent GUERBY
2010-11-02 15:32     ` Tom Tromey
2010-11-01 10:31 ` Dave Korn
2010-11-01 17:36   ` Ian Lance Taylor
2010-11-01 18:16 ` Diego Novillo
2010-11-01 18:58   ` Andrew Haley
2010-11-01 19:35     ` H.J. Lu
2010-11-02  3:39   ` Jeff Law
2010-11-02  3:58     ` H.J. Lu
2010-11-02  8:22     ` Eric Botcazou
2010-11-02 15:31     ` Tom Tromey
2010-11-02 16:25       ` Jeff Law
2010-11-02  5:12 ` Matthias Klose
2010-11-11 23:20 ` Ian Lance Taylor
2010-11-18  9:23   ` Mark Mitchell
2010-11-18 10:47     ` Andrew Haley
2010-11-18 13:42       ` H.J. Lu
2010-11-18 15:37       ` Mark Mitchell
2010-11-18 16:02         ` Diego Novillo
2010-11-18 15:23     ` Jeff Law
2010-11-18 17:19     ` Ian Lance Taylor
2010-11-18 17:58       ` Dave Korn
2010-11-18 20:53       ` Mark Wielaard

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='AANLkTikPP+=RS4BL_NQFaENvFtvvk9ughpP3kWvWT25A@mail.gmail.com' \
    --to=stevenb.gcc@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=iant@google.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).