From: Jakub Jelinek <jakub@redhat.com>
To: Bernd Edlinger <bernd.edlinger@hotmail.de>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Andrew Haley <aph@redhat.com>,
Marek Polacek <polacek@redhat.com>
Subject: Re: [PATCH] Delete GCJ
Date: Sat, 29 Oct 2016 09:13:00 -0000 [thread overview]
Message-ID: <20161029091314.GX3541@tucnak.redhat.com> (raw)
In-Reply-To: <AM4PR0701MB2162A11F26F374BEBBC5C169E4AC0@AM4PR0701MB2162.eurprd07.prod.outlook.com>
On Sat, Oct 29, 2016 at 09:07:42AM +0000, Bernd Edlinger wrote:
> > Things we may want to remove:
> >
> > - references to java in contrib (download_ecj, gcc_update,
> > patch_tester.sh, update-copyright.py)
> > - GCJ, GCJ_FOR_BUILD, GCJ_FOR_TARGET in Makefiles.tpl and configure.ac
> > - LIBGCJ_SONAME in config/i386/{cygwin.h,mingw32.h}
> > - references to java in install.texi
>
> Probably also gcc/jit/* and gcc/testsuite/jit.dg/* ?
?? gccjit has nothing to do with Java, it is a general purpose GIT for
whatever program wants to use it.
Jakub
next prev parent reply other threads:[~2016-10-29 9:13 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-29 9:07 Bernd Edlinger
2016-10-29 9:13 ` Jakub Jelinek [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-09-05 23:20 Bernd Edlinger
2016-09-06 0:24 ` Eric Gallager
2016-09-05 15:29 Andrew Haley
2016-09-05 15:31 ` Matthias Klose
2016-09-05 15:32 ` Andrew Haley
2016-09-05 18:38 ` Eric Gallager
2016-09-05 15:55 ` Matthew Fortune
[not found] ` <FB08E20B-5ED1-45BA-BFA0-11E7807840D2@gmail.com>
2016-09-05 16:26 ` Andrew Haley
2016-09-06 9:08 ` Richard Biener
2016-09-06 9:11 ` Jakub Jelinek
2016-09-06 21:24 ` Jeff Law
2016-09-07 11:52 ` Richard Earnshaw (lists)
2016-09-09 11:47 ` Ian Lance Taylor
2016-09-05 16:35 ` Gerald Pfeifer
2016-09-05 18:58 ` Eric Gallager
2016-09-30 16:11 ` Andrew Haley
2017-01-22 18:00 ` Gerald Pfeifer
2017-01-22 18:42 ` Per Bothner
2017-01-23 9:03 ` Andrew Haley
2017-01-23 9:10 ` Jakub Jelinek
2017-01-23 13:04 ` Per Bothner
2017-01-23 13:49 ` Jakub Jelinek
2017-01-23 15:05 ` Andrew Haley
2017-01-22 18:41 ` Gerald Pfeifer
2016-09-10 12:22 ` NightStrike
2016-09-11 13:03 ` Andrew Haley
2016-09-30 10:42 ` Marek Polacek
2016-09-30 13:11 ` Andrew Haley
2016-10-02 13:27 ` Andreas Schwab
2016-10-02 16:51 ` Andrew Haley
2016-10-28 20:57 ` Eric Botcazou
2017-01-22 23:06 ` Gerald Pfeifer
2016-10-03 23:12 ` Matthias Klose
2016-10-04 8:40 ` Rainer Orth
2016-10-04 8:41 ` Andrew Haley
2016-10-04 17:23 ` Mike Stump
2016-10-04 17:25 ` Andrew Pinski
2016-10-04 18:40 ` Iain Sandoe
2016-10-05 16:28 ` Jeff Law
[not found] ` <2b5de569-1efd-f407-49c2-c9fa84cc5315@ubuntu.com>
2016-10-06 16:16 ` Matthias Klose
2016-10-06 16:43 ` Rainer Orth
2016-10-06 16:47 ` Iain Sandoe
2016-10-06 16:54 ` Matthias Klose
2016-10-06 16:56 ` Rainer Orth
2016-10-06 17:10 ` Iain Sandoe
2016-10-06 18:01 ` Mike Stump
2016-10-06 23:59 ` Matthias Klose
2016-10-07 8:31 ` Iain Sandoe
2016-10-10 4:03 ` Matthias Klose
2016-10-10 7:58 ` Iain Sandoe
2016-11-20 20:42 ` Matthias Klose
2016-11-21 5:34 ` Sandra Loosemore
2016-11-21 10:24 ` Iain Sandoe
2016-11-21 12:57 ` Matthias Klose
2016-11-21 16:23 ` Sandra Loosemore
2016-11-21 16:40 ` Matthias Klose
2016-11-21 17:16 ` Peter Bergner
2016-11-21 17:16 ` Rainer Orth
2016-11-21 23:23 ` Matthias Klose
2016-11-22 17:13 ` Sandra Loosemore
2016-11-29 21:23 ` Jeff Law
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=20161029091314.GX3541@tucnak.redhat.com \
--to=jakub@redhat.com \
--cc=aph@redhat.com \
--cc=bernd.edlinger@hotmail.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=polacek@redhat.com \
--cc=schwab@linux-m68k.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).