From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21553 invoked by alias); 5 Feb 2019 22:57:42 -0000 Mailing-List: contact jit-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Subscribe: Sender: jit-owner@gcc.gnu.org Received: (qmail 21399 invoked by uid 89); 5 Feb 2019 22:57:41 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Checked: by ClamAV 0.100.2 on sourceware.org X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,KAM_SHORT,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=month X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,KAM_SHORT,SPF_HELO_PASS autolearn=ham version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on sourceware.org X-Spam-Level: X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 05 Feb 2019 22:57:40 +0000 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 7375D19E83; Tue, 5 Feb 2019 22:57:39 +0000 (UTC) Received: from ovpn-116-177.phx2.redhat.com (ovpn-116-177.phx2.redhat.com [10.3.116.177]) by smtp.corp.redhat.com (Postfix) with ESMTP id 06FA069188; Tue, 5 Feb 2019 22:57:38 +0000 (UTC) Message-ID: <1549407458.29992.26.camel@redhat.com> Subject: Re: Patch apply status From: David Malcolm To: akrl , jit@gcc.gnu.org Date: Tue, 01 Jan 2019 00:00:00 -0000 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Tue, 05 Feb 2019 22:57:39 +0000 (UTC) X-IsSubscribed: yes X-SW-Source: 2019-q1/txt/msg00060.txt.bz2 On Thu, 2019-01-31 at 13:41 +0000, akrl wrote: > Hi all, > I wanted to ask about the status of application of the recent patches > submitted here (thread-local and gcc_jit_context_add_driver_option). > I'm not much familiar with gcc development flow but I guess it would > be > nice to know, if we are writing another patch is good to know if it > has to apply on top of these or not. The gcc_jit_context_add_driver_option patch is in trunk as of r268563; thanks! Marc's thread-local patch is waiting for some legal paperwork; it also has conflicts with the above patch (due to ABI numbering); I can't remember if it had other issues. Jakub (one of the release managers) gave me some discretion to commit jit features in gcc 9 stage 4: https://gcc.gnu.org/ml/jit/2019-q1/msg00056.html in the next month or so if the paperwork comes through on the other patch, or if there are other patches that are reasonable for gcc 9. I hope this answers your question. Dave