public inbox for jit@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: Antoni Boucher <bouanto@zoho.com>,
	gcc-patches@gcc.gnu.org, jit@gcc.gnu.org,
	 Richard Biener <rguenther@suse.de>,
	jakub@redhat.com
Subject: Re: rustc_codegen_gcc and libgccjit for GCC 12 ?
Date: Tue, 12 Apr 2022 17:59:10 -0400	[thread overview]
Message-ID: <cbe4bc7f3fe11d854ad8aa80762a16d853842e5f.camel@redhat.com> (raw)
In-Reply-To: <977a1abd031f63b14685feb552e679c39e7d1013.camel@redhat.com>

On Mon, 2022-04-11 at 19:56 -0400, David Malcolm wrote:
> On Fri, 2022-04-08 at 16:37 -0400, Antoni Boucher wrote:
> > On Fri, 2022-04-08 at 15:36 -0400, David Malcolm wrote:
> 
> [...snip...]
> 
> > 
> > 
> 
> > > So I think I'm waiting on an updated version of the sized-
> > > integer-
> > > types
> > > patch, and some nit-fixes for the other patches (but am
> > > disappearing
> > > on
> > > vacation on 18th - 22nd).
> > 
> > I'll update the patches to address your review over the weekend.
> > Thanks!
> 
> Thanks.
> 
> I've been working through them today, fixing things up so they commit
> cleanly, and fixing a few more nits, but it's clear I'm not going to
> be
> done tonight.
> 
> I hope to push the 5 jit patches to trunk for GCC 12 tomorrow
> (assuming
> my tests pass).

I've now pushed the 5 jit patches to trunk for GCC 12, as 
  r12-8116-gaf80ea97b61847
through:
  r12-8120-g6e5ad1cc24a315
after successful bootstrap and regression testing on x86_64-pc-linux-
gnu; see various other recent mails to the gcc-patches/jit mailing
lists for the details of the specific patches.

Hopefully that's everything that will be needed for gcc 12 for a
version of rustc_codegen_gcc to be able to use upstream gcc 12
libgccjit (and that I didn't break anything).

I'm working on a wwwdocs patch for the GCC 12 release notes (for these
libgccjit API extensions).

Thanks again for all the patches
Dave


  reply	other threads:[~2022-04-12 21:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 19:36 David Malcolm
2022-04-08 20:37 ` Antoni Boucher
2022-04-11 23:56   ` David Malcolm
2022-04-12 21:59     ` David Malcolm [this message]
2022-04-11  6:00 ` Richard Biener

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=cbe4bc7f3fe11d854ad8aa80762a16d853842e5f.camel@redhat.com \
    --to=dmalcolm@redhat.com \
    --cc=bouanto@zoho.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=jit@gcc.gnu.org \
    --cc=rguenther@suse.de \
    /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).