public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: java-patches@gcc.gnu.org
Subject: Re: [JAVA PATCH] Enable more array bounds check elimination
Date: Thu, 14 Jul 2016 17:43:00 -0000	[thread overview]
Message-ID: <5787CF36.90705@redhat.com> (raw)
In-Reply-To: <1888240340.4921666.1468516370115.JavaMail.zimbra@redhat.com>

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.



  reply	other threads:[~2016-07-14 17:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-22 18:10 roger
2016-02-22 18:13 ` Andrew Haley
2016-02-22 18:18 ` Jeff Law
2016-07-13 20:07 ` Jeff Law
2016-07-14 17:12   ` Andrew Hughes
2016-07-14 17:43     ` Andrew Haley [this message]
2016-02-22 23:02 Roger Sayle
2016-02-23  9:56 ` Andrew Haley
2016-02-23 17:45   ` Andrew Hughes
2016-02-24  1:11     ` Roger Sayle
2016-02-24  3:23       ` Andrew Hughes
2016-02-24  9:53       ` 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=5787CF36.90705@redhat.com \
    --to=aph@redhat.com \
    --cc=java-patches@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).