This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [RFC] Replace Java with Go in default languages

From: Jeff Law <law at redhat dot com>
To: Andi Kleen <andi at firstfloor dot org>
Cc: GCC <gcc at gcc dot gnu dot org>
Date: Mon, 11 Nov 2013 13:12:26 -0700
Subject: Re: [RFC] Replace Java with Go in default languages
Authentication-results: sourceware.org; auth=none
References: <527D63DB dot 3090801 at redhat dot com> <87a9hb80mg dot fsf at tassilo dot jf dot intel dot com>

On 11/11/13 07:38, Andi Kleen wrote:

Jeff Law <law@redhat.com> writes:

Thoughts or comments?


If noone tests java completely then it will quickly bitrot won't it?

So ideally some bot would still regularly build/test it.
If you don't do that you could as well just remove the code.

There's no reason to remove the front-end. It's not much different thanthe situation with Ada, or how we deal with backends.

If bitrot appears, but goes unnoticed for long periods of time, thenthat's an indication bits need to be removed.

If bitrot appears and is fixed regularly, that's an indication thatbuilding & testing Java should continue to be part of the standardsubmission process.


Perhaps it would make more sense to just split the required tests :

[ ... ]

You could easily look at moving Java out of the required languages tobuild/test as one step in this direction.


Jeff

References:
- [RFC] Replace Java with Go in default languages
  - From: Jeff Law
- Re: [RFC] Replace Java with Go in default languages
  - From: Andi Kleen

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]