From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 35469 invoked by alias); 24 Nov 2015 21:22:25 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 35456 invoked by uid 89); 24 Nov 2015 21:22:24 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.5 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-oi0-f45.google.com Received: from mail-oi0-f45.google.com (HELO mail-oi0-f45.google.com) (209.85.218.45) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Tue, 24 Nov 2015 21:22:23 +0000 Received: by oies6 with SMTP id s6so18183442oie.1 for ; Tue, 24 Nov 2015 13:22:21 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.202.187.198 with SMTP id l189mr21870388oif.49.1448400141612; Tue, 24 Nov 2015 13:22:21 -0800 (PST) Received: by 10.76.72.3 with HTTP; Tue, 24 Nov 2015 13:22:21 -0800 (PST) In-Reply-To: <5654D042.3060803@redhat.com> References: <5654C1BB.4070501@redhat.com> <5654CC79.4000705@redhat.com> <5654D042.3060803@redhat.com> Date: Tue, 24 Nov 2015 22:38:00 -0000 Message-ID: Subject: Re: Pinging patches From: "H.J. Lu" To: Jeff Law Cc: GCC Patches Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2015-11/txt/msg02969.txt.bz2 On Tue, Nov 24, 2015 at 1:01 PM, Jeff Law wrote: > On 11/24/2015 01:55 PM, H.J. Lu wrote: >>> >>> I believe hte interrupt patches really need to wait for the next stage1. >>> jeff >>> >> >> X86 interrupt attribute was first submitted in September and it >> is limited to x86 backend, except for >> >> TARGET_FUNCTION_INCOMING_ARG_RTL >> >> which is no-op for other backends. We really like to enable it >> in GCC 6. > > I realize all of that, but I think we need to make some changes to the > FUNCTION_ARGS interface to do this cleanly, and I don't want to push > something like that during stage3. > Who will make changes to the FUNCTION_ARGS interface? -- H.J.