public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: Basile Starynkevitch <basile@starynkevitch.net>
Cc: jit@gcc.gnu.org, "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: Four jit backports to gcc 5 branch
Date: Wed, 01 Jul 2015 14:57:00 -0000	[thread overview]
Message-ID: <1435762163.24803.14.camel@surprise> (raw)
In-Reply-To: <1435669264.13727.213.camel@surprise>

On Tue, 2015-06-30 at 09:01 -0400, David Malcolm wrote:
> On Tue, 2015-06-30 at 08:43 +0200, Basile Starynkevitch wrote:
> > On Mon, Jun 29, 2015 at 11:44:31AM -0400, David Malcolm wrote:
> > > I've gone over the changes to the gcc/jit and gcc/testsuite/jit.dg
> > > directories in trunk since gcc 5 and backported the following 4 changes
> > > from trunk to the gcc-5-branch:
> > > 
> > 
> > 
> > I'll be delighted if switch statements ability would be backported to
> > GCC 5.  (Its absence is IMHO a severe bug in GCCJIT, but perhaps GCC rules
> > forbid backporting new features, even when they correct a huge
> > deficiency and when the patch adding them is probably quite small).
> 
> I don't agree with your characterization of the severity of this, but I
> do think we ought to fix it if possible.
> 
> I don't know of any rules about what is and what isn't suitable for
> backporting.  The jit work as a whole is relatively new and has been
> messaged as "experimental".
> 
> I'm the jit maintainer, and I believe the patch is reasonable to
> backport: it doesn't break API or ABI (although it extends it), it has
> docs and test coverage, and doesn't touch anything outside of the jit
> (beyond adding the new header gcc/typed-splay-tree.h, which is only used
> by the jit).  
> 
> Hence I intend to backport it to gcc-5-branch, but I've got to get it
> into trunk first :)  (hopefully later today)

Switch statements for the jit are now in gcc-5-branch, as of r225255.

  reply	other threads:[~2015-07-01 14:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-29 15:58 David Malcolm
2015-06-29 20:59 ` Dibyendu Majumdar
2015-06-29 21:46   ` Thinking about libgccjit SONAME bump for gcc 5.2 (was Re: Four jit backports to gcc 5 branch) David Malcolm
2015-06-29 21:55     ` Dibyendu Majumdar
2015-06-29 22:57     ` Ulrich Drepper
2015-06-30  2:05       ` David Malcolm
2015-06-30  6:46 ` Four jit backports to gcc 5 branch Basile Starynkevitch
2015-06-30 13:13   ` David Malcolm
2015-07-01 14:57     ` David Malcolm [this message]
2015-07-01 14:55 ` Eight more " David Malcolm

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=1435762163.24803.14.camel@surprise \
    --to=dmalcolm@redhat.com \
    --cc=basile@starynkevitch.net \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jit@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).