From: Andrew Hughes <gnu.andrew@redhat.com>
To: Andrew Haley <aph@redhat.com>
Cc: Roger Sayle <roger@nextmovesoftware.com>, java-patches@gcc.gnu.org
Subject: Re: [JAVA PATCH] Enable more array bounds check elimination
Date: Tue, 23 Feb 2016 17:45:00 -0000 [thread overview]
Message-ID: <991292478.26327859.1456249539216.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <56CC2CB2.8020301@redhat.com>
----- Original Message -----
> On 22/02/16 23:02, Roger Sayle wrote:
> > Please point me towards any relevant postings (of yours) on the subject of
> > gcj bounds check elimination, as I'd love to catch up on current thinking.
>
> I'm not sure that there are any, really. The discussions I can
> remember were all done in person, and I didn't get positive
> feedback about the idea of adding to the type system in GCC's
> middle end.
>
> Incidentally, we have been talking about EOL for GCJ for some years
> now. GCC 6 will very likely be the last GCJ.
Yes, I believe we agreed to regard it as deprecated in 6 and remove it
during the lifetime of 7 [0]. As such, this patch probably needs to
go to the 6 branch too if it's ever going to see the light of day.
>
> Andrew.
>
>
[0] https://gcc.gnu.org/ml/java-patches/2015-q3/msg00041.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
next prev parent reply other threads:[~2016-02-23 17:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 23:02 Roger Sayle
2016-02-23 9:56 ` Andrew Haley
2016-02-23 17:45 ` Andrew Hughes [this message]
2016-02-24 1:11 ` Roger Sayle
2016-02-24 3:23 ` Andrew Hughes
2016-02-24 9:53 ` Andrew Haley
-- strict thread matches above, loose matches on Subject: below --
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
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=991292478.26327859.1456249539216.JavaMail.zimbra@redhat.com \
--to=gnu.andrew@redhat.com \
--cc=aph@redhat.com \
--cc=java-patches@gcc.gnu.org \
--cc=roger@nextmovesoftware.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).