public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jeff Law <law@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: Pinging patches
Date: Tue, 24 Nov 2015 22:38:00 -0000	[thread overview]
Message-ID: <CAMe9rOoY=bNADnPbHUJ3aM3krmpNBg6dr-3Mt+DGCjqkxK6Pcg@mail.gmail.com> (raw)
In-Reply-To: <5654D042.3060803@redhat.com>

On Tue, Nov 24, 2015 at 1:01 PM, Jeff Law <law@redhat.com> 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.

      reply	other threads:[~2015-11-24 21:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-24 20:01 Jeff Law
2015-11-24 20:44 ` H.J. Lu
2015-11-24 20:47   ` Jeff Law
2015-11-24 21:01     ` H.J. Lu
2015-11-24 21:01       ` Jeff Law
2015-11-24 22:38         ` H.J. Lu [this message]

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='CAMe9rOoY=bNADnPbHUJ3aM3krmpNBg6dr-3Mt+DGCjqkxK6Pcg@mail.gmail.com' \
    --to=hjl.tools@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@redhat.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).