public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: gcc@gcc.gnu.org, java@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org
Subject: PATCH RFA: Do not build java by default
Date: Sun, 31 Oct 2010 19:09:00 -0000	[thread overview]
Message-ID: <mcrocaa18nt.fsf@google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1880 bytes --]

Currently we build the Java frontend and libjava by default.  At the GCC
Summit we raised the question of whether should turn this off, thus only
building it when java is explicitly selected at configure time with
--enable-languages.  Among the people at the summit, there was general
support for this, and nobody was opposed to it.

Here is a patch which implements that.  I'm sending this to the mailing
lists gcc@ and java@, as well as the relevant -patches@ lists, because
it does deserve some broader discussion.

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.
A supporting argument is since Sun has released their Java tools under
the GPL, community interest seems to have shifted toward the Sun tools;
gcc's Java frontend is in maintenance mode, with little new development
currently planned.

This patch should not of course change whether or not distros choose to
package the Java compiler; undoubtedly they would continue to do so,
just as they package the Ada compiler today.

Comments?  Approvals?

Ian


gcc/java/ChangeLog:

2010-10-31  Ian Lance Taylor  <iant@google.com>

	* config-lang.in (build_by_default): Set to no.

gcc/ChangeLog:

2010-10-31  Ian Lance Taylor  <iant@google.com>

	* doc/install.texi (Configuration): Note in two places that Java
	is not enabled by default.



[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: java --]
[-- Type: text/x-diff, Size: 1520 bytes --]

Index: gcc/java/config-lang.in
===================================================================
--- gcc/java/config-lang.in	(revision 166080)
+++ gcc/java/config-lang.in	(working copy)
@@ -36,5 +36,7 @@ gtfiles="\$(srcdir)/java/java-tree.h \$(
 
 target_libs=${libgcj_saved}
 lang_dirs="fastjar"
-#build_by_default=no
 lang_requires=c++
+
+# Do not build java by default.
+build_by_default=no
Index: gcc/doc/install.texi
===================================================================
--- gcc/doc/install.texi	(revision 166080)
+++ gcc/doc/install.texi	(working copy)
@@ -1320,7 +1309,7 @@ Currently, you can use any of the follow
 Building the Ada compiler has special requirements, see below.
 If you do not pass this flag, or specify the option @code{all}, then all
 default languages available in the @file{gcc} sub-tree will be configured.
-Ada and Objective-C++ are not default languages; the rest are.
+Java, Ada and Objective-C++ are not default languages; the rest are.
 Re-defining @code{LANGUAGES} when calling @samp{make} @strong{does not}
 work anymore, as those language sub-directories might not have been
 configured!
@@ -1763,7 +1741,9 @@ tools.
 
 @subheading Java-Specific Options
 
-The following option applies to the build of the Java front end.
+The following option applies to the build of the Java front end.  Note
+that the Java front end is not built by default; in order to build it,
+use the @option{--enable-languages} option described above.
 
 @table @code
 @item --disable-libgcj

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

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-31 19:09 Ian Lance Taylor [this message]
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
2010-10-31 19:33 Steven Bosscher
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

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=mcrocaa18nt.fsf@google.com \
    --to=iant@google.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=java-patches@gcc.gnu.org \
    --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).