From: Jakub Jelinek <jakub@redhat.com>
To: Steve Ellcey <sellcey@marvell.com>,
"sellcey@cavium.com" <sellcey@cavium.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
rguenther@suse.de, richard.sandiford@arm.com
Subject: Re: [Patch 4/4][Aarch64] v2: Implement Aarch64 SIMD ABI
Date: Fri, 11 Jan 2019 11:30:00 -0000 [thread overview]
Message-ID: <20190111113007.GK30353@tucnak> (raw)
In-Reply-To: <87ef9j30bw.fsf@arm.com>
On Fri, Jan 11, 2019 at 11:22:59AM +0000, Richard Sandiford wrote:
> Steve Ellcey <sellcey@marvell.com> writes:
> > If this looks good to you can I go ahead and check it in? I know
> > we are in Stage 3 now, but my recollection is that patches that were
> > initially submitted during Stage 1 could go ahead once approved.
>
> Yeah, like you say, this was originally posted in stage 1 and is the
> last patch in the series. Not committing it would leave the work
> incomplete in GCC 9. The problem is that we're now in stage 4 rather
> than stage 3.
>
> I don't think I'm neutral enough to make the call. Richard, Jakub?
I'm ok with accepting this late as an exception, if it can be committed
reasonably soon (within a week or at most two).
Jakub
next prev parent reply other threads:[~2019-01-11 11:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 17:55 Steve Ellcey
2018-12-06 12:25 ` Richard Sandiford
2019-01-04 23:57 ` Steve Ellcey
2019-01-07 17:39 ` Richard Sandiford
2019-01-08 23:42 ` Steve Ellcey
2019-01-09 10:01 ` Richard Sandiford
2019-01-10 0:19 ` Steve Ellcey
2019-01-10 9:16 ` Richard Sandiford
2019-01-11 0:13 ` Steve Ellcey
2019-01-11 11:23 ` Richard Sandiford
2019-01-11 11:30 ` Jakub Jelinek [this message]
2019-01-11 14:03 ` [EXT] " Steve Ellcey
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=20190111113007.GK30353@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
--cc=richard.sandiford@arm.com \
--cc=sellcey@cavium.com \
--cc=sellcey@marvell.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).