From: Jeff Law <law@redhat.com>
To: "roger@nextmovesoftware.com" <roger@nextmovesoftware.com>,
java-patches@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [JAVA PATCH] Enable more array bounds check elimination
Date: Mon, 22 Feb 2016 18:18:00 -0000 [thread overview]
Message-ID: <56CB50EC.1000006@redhat.com> (raw)
In-Reply-To: <4F362C11-3DAA-4A9A-AEAB-089C20B3590C@nextmovesoftware.com>
On 02/22/2016 11:10 AM, roger@nextmovesoftware.com wrote:
>
> It has been a while since my last contribution.
It has been. I ran into some of your eyesopen.com colleagues a couple
years back at SC12 or SC13. It'd obviously be great to have you
contributing regularly again.
Note that we're rapidly approaching the gcc-6 release; since this isn't
a regression bugfix, it'll be tabled until gcc-7 is open for development.
Jeff
next prev parent reply other threads:[~2016-02-22 18:18 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 [this message]
2016-07-13 20:07 ` Jeff Law
2016-07-14 17:12 ` Andrew Hughes
2016-07-14 17:43 ` Andrew Haley
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=56CB50EC.1000006@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--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).