From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 104041 invoked by alias); 14 Jul 2016 17:43:23 -0000 Mailing-List: contact java-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-patches-owner@gcc.gnu.org Received: (qmail 104031 invoked by uid 89); 14 Jul 2016 17:43:22 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.2 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=Hughes, hughes, skills, life X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Thu, 14 Jul 2016 17:43:21 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id AC02E562A5 for ; Thu, 14 Jul 2016 17:43:20 +0000 (UTC) Received: from zebedee.pink (ovpn-116-53.ams2.redhat.com [10.36.116.53]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u6EHhIZG005412; Thu, 14 Jul 2016 13:43:19 -0400 Subject: Re: [JAVA PATCH] Enable more array bounds check elimination To: java-patches@gcc.gnu.org References: <4F362C11-3DAA-4A9A-AEAB-089C20B3590C@nextmovesoftware.com> <1888240340.4921666.1468516370115.JavaMail.zimbra@redhat.com> From: Andrew Haley Message-ID: <5787CF36.90705@redhat.com> Date: Thu, 14 Jul 2016 17:43:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 In-Reply-To: <1888240340.4921666.1468516370115.JavaMail.zimbra@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2016-q3/txt/msg00008.txt.bz2 On 14/07/16 18:12, Andrew Hughes wrote: > snip... > >> At a very high level, you should be aware of a general belief that GCJ's >> life is limited. There's been various calls to deprecate it. So >> spending a lot of time optimizing GCJ's output may not be the best use >> of your skills :-) > > Unless things have changed since it was last discussed, the plan was > for it to be deprecated in GCC 6 and removed in 7. If that's the case, > these changes may sadly not see a release. > > It does seem that no-one has bitten the bullet of removing it yet though. It's on my list. The first thing to do before removing the sources is to change the top-level autoconf and automake scripts not to resurse into the gcj scripts, but my automake-fu is rather rusty. Andrew.