public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Hughes <gnu.andrew@redhat.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Andrew Haley <aph@redhat.com>, Matthias Klose <doko@ubuntu.com>,
	       Tom Tromey <tom@tromey.com>, Jeff Law <law@redhat.com>,
	       Uros Bizjak <ubizjak@gmail.com>,
	gcc-patches@gcc.gnu.org,        java-patches@gcc.gnu.org
Subject: Re: [PATCH, libjava/classpath]: Fix overriding recipe for target 'gjdoc' build warning
Date: Thu, 20 Aug 2015 22:32:00 -0000	[thread overview]
Message-ID: <996021585.13493962.1440109937617.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <3CB72092-59D0-4110-ADAB-5112AEB62A69@gmail.com>



----- Original Message -----
> On August 20, 2015 7:35:37 PM GMT+02:00, Andrew Hughes
> <gnu.andrew@redhat.com> wrote:
> >----- Original Message -----
> >> snip...
> >> > 
> >> > Having classpath (with binary files!) In the GCC SVN (or future
> >git)
> >> > repository is a significant burden, not to mention the size of the
> >> > distributed source tarball.
> >> > 
> >> > If we can get rid of that that would be a great step in reducing
> >the
> >> > burden.
> >> > 
> >> > Iff we can even without classpath build enough of java to be useful
> >(do you
> >> > really need gcj or only gij for bootstrapping openjdk? After all
> >ecj is
> >> > just
> >> > a drop-in to gcc as well).
> >> 
> >> All the Java compilers are written in Java (ecj & javac). So to run
> >them, you
> >> need a JVM and its class library.
> >> 
> >> It's those binary files which allow gcj to bootstrap the stack. If
> >OpenJDK
> >> had a minimal binary class library, it would be able to bootstrap
> >itself.
> >> 
> >> But, as things stand, you need enough of the JDK to run a Java
> >compiler
> >> and build the OpenJDK class libraries. GCJ currently fulfils that
> >need
> >> where there isn't already an OpenJDK installation available.
> >> --
> >
> >Actually, this makes me think...
> >
> >IcedTea already depends on CACAO and JamVM for alternate builds of
> >OpenJDK. We could instead include the bytecode binaries for GNU
> >Classpath
> >in IcedTea, bootstrap JamVM and use that to bootstrap OpenJDK. That
> >would remove our dependency on gcj and make IcedTea largely
> >self-sufficient.
> >It would also mean we could drop a bunch of conditional code which
> >depends
> >on what the system bootstrap JDK is, because it would always be the
> >in-tree
> >solution.
> >
> >We'd still need more than six months to make this transition though,
> >as such a change really needs time for testing.
> 
> OK, so how about deprecating Java for GCC 6 by removing it from the default
> languages and removing it for GCC 7 or before we switch to git (whatever
> happens earlier?)
> 

Yeah, that's what I suggested at the end of [0] so +1 from me.

As Joseph says, I don't think the move to git is relevant to this. If it
had happened sooner, though, I'd have properly merged GNU Classpath more
frequently... ;)

> Richard.
> 
> 
> 

[0] https://gcc.gnu.org/ml/java-patches/2015-q3/msg00029.html
-- 
Andrew :)

Senior Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

PGP Key: ed25519/35964222 (hkp://keys.gnupg.net)
Fingerprint = 5132 579D D154 0ED2 3E04  C5A0 CFDA 0F9B 3596 4222

PGP Key: rsa4096/248BDC07 (hkp://keys.gnupg.net)
Fingerprint = EC5A 1F5E C0AD 1D15 8F1F  8F91 3B96 A578 248B DC07

  parent reply	other threads:[~2015-08-20 22:32 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07 11:22 Uros Bizjak
2015-08-11 18:03 ` Uros Bizjak
2015-08-11 18:54   ` Jeff Law
2015-08-11 19:24     ` Andrew Haley
2015-08-11 19:34       ` Jeff Law
2015-08-12  2:48     ` Tom Tromey
2015-08-12 14:44       ` Jeff Law
2015-08-12 14:57         ` Andrew Haley
2015-08-12 16:23           ` Ian Lance Taylor
2015-08-12 16:21         ` Tom Tromey
2015-08-12 16:24           ` Ian Lance Taylor
2015-08-12 16:47             ` Jeff Law
2015-08-12 16:59               ` Ian Lance Taylor
2015-08-13 10:00               ` Richard Biener
2015-08-13 21:31                 ` Jeff Law
2015-08-14  7:44                   ` Richard Biener
2015-08-14  9:24                     ` Andrew Haley
2015-08-20  2:35       ` Andrew Hughes
2015-08-20  4:37         ` Tom Tromey
2015-08-20  8:24           ` Matthias Klose
2015-08-20  8:32             ` Andrew Haley
2015-08-20 14:57               ` Andrew Hughes
2015-08-20 15:27                 ` Andrew Haley
2015-08-20 15:47                   ` Jeff Law
2015-08-20 16:03                     ` Andrew Hughes
2015-08-20 16:08                       ` Andrew Haley
2015-08-20 16:26                         ` Andrew Hughes
2015-08-20 16:38                         ` Richard Biener
2015-08-20 16:39                           ` Andrew Haley
2015-08-20 17:35                       ` Jeff Law
2015-08-20 17:39                         ` Andrew Hughes
2015-08-20 15:52                   ` Andrew Hughes
2015-08-20 16:34                     ` Richard Biener
2015-08-20 16:59                       ` Andrew Hughes
2015-08-20 17:35                         ` Andrew Hughes
2015-08-20 18:05                           ` Richard Biener
2015-08-20 21:06                             ` Joseph Myers
2015-08-20 22:32                             ` Andrew Hughes [this message]
2015-08-24 16:39                               ` Jeff Law
2015-08-20 14:58           ` Andrew Hughes
2015-08-20  2:48   ` Andrew Hughes
2015-08-20  6:20     ` Uros Bizjak

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=996021585.13493962.1440109937617.JavaMail.zimbra@redhat.com \
    --to=gnu.andrew@redhat.com \
    --cc=aph@redhat.com \
    --cc=doko@ubuntu.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=java-patches@gcc.gnu.org \
    --cc=law@redhat.com \
    --cc=richard.guenther@gmail.com \
    --cc=tom@tromey.com \
    --cc=ubizjak@gmail.com \
    /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).