From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: ARM Patch Ping
Date: Sun, 03 Sep 2017 09:12:00 -0000 [thread overview]
Message-ID: <AM5PR0701MB2657174CE2EB5D21924F5B46E4900@AM5PR0701MB2657.eurprd07.prod.outlook.com> (raw)
In-Reply-To: <59a21f0e-7741-f692-8c6d-1d42e5d8f428@hotmail.de>
Ping...
it would be nice if this could be reviewed before next stage 3.
Thanks
Bernd.
On 08/01/17 16:32, Bernd Edlinger wrote:
> Hi,
>
> I would like to kindly remind you of the following patches,
> which are already waiting for over 6 months:
>
> [PATCH, ARM] correctly encode the CC reg data flow
> https://gcc.gnu.org/ml/gcc-patches/2017-01/msg01351.html
>
> [PATCH, ARM] Further improve stack usage in sha512 (PR 77308)
> https://gcc.gnu.org/ml/gcc-patches/2017-04/msg01567.html
>
> [PATCH, ARM] Further improve stack usage in sha512, part 2 (PR 77308)
> https://gcc.gnu.org/ml/gcc-patches/2017-04/msg01568.html
>
>
> I boot-strapped and reg-tested the patches on last week's snapshot to
> verify they still apply.
>
>
> Thanks
> Bernd.
next parent reply other threads:[~2017-09-03 9:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <59a21f0e-7741-f692-8c6d-1d42e5d8f428@hotmail.de>
2017-09-03 9:12 ` Bernd Edlinger [this message]
2022-01-20 11:27 [committed 0/7] Arm: mitigation for AES erratum on Cortex-a57 and Cortex-A72 Richard Earnshaw
2022-01-20 11:27 ` [PATCH 3/7] arm: Add option for mitigating against Cortex-A CPU erratum for AES Richard Earnshaw
2022-01-27 10:07 ` Jakub Jelinek
2022-02-03 13:20 ` ARM patch ping Jakub Jelinek
2022-02-03 13:28 ` Richard Biener
-- strict thread matches above, loose matches on Subject: below --
2021-02-19 10:45 Jakub Jelinek
2021-02-19 11:45 ` Kyrylo Tkachov
2017-08-01 14:33 ARM Patch Ping Bernd Edlinger
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=AM5PR0701MB2657174CE2EB5D21924F5B46E4900@AM5PR0701MB2657.eurprd07.prod.outlook.com \
--to=bernd.edlinger@hotmail.de \
--cc=gcc-patches@gcc.gnu.org \
/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).