public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>,
	Richard Earnshaw	<richard.earnshaw@arm.com>,
	Ramana Radhakrishnan	<ramana.radhakrishnan@arm.com>
Subject: [PING**3] [PATCH, ARM] Further improve stack usage on sha512 (PR 77308)
Date: Tue, 27 Dec 2016 14:13:00 -0000	[thread overview]
Message-ID: <AM4PR0701MB2162ABF31904AC1333F801F4E4690@AM4PR0701MB2162.eurprd07.prod.outlook.com> (raw)
In-Reply-To: <AM4PR0701MB2162CA4276E53ED7B7140302E4910@AM4PR0701MB2162.eurprd07.prod.outlook.com>

Ping...

On 12/19/16 06:49, Bernd Edlinger wrote:
> Ping...
>
> On 12/12/16 06:59, Bernd Edlinger wrote:
>> Ping...
>>
>> On 12/05/16 14:41, Bernd Edlinger wrote:
>>> Hi,
>>>
>>> this was the latest version of my patch:
>>> https://gcc.gnu.org/ml/gcc-patches/2016-11/msg02796.html
>>>
>>>
>>> Thanks
>>> Bernd.

  reply	other threads:[~2016-12-27 14:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-16 17:28 [PING] " Bernd Edlinger
2016-11-24 14:24 ` [PING**2] " Bernd Edlinger
2016-12-05 13:41   ` [PING] " Bernd Edlinger
2016-12-12  5:59     ` [PING**2] " Bernd Edlinger
2016-12-19  8:22       ` Bernd Edlinger
2016-12-27 14:13         ` Bernd Edlinger [this message]
2017-01-05  9:11           ` [PING**4] " Bernd Edlinger
  -- strict thread matches above, loose matches on Subject: below --
2016-11-06 14:18 Bernd Edlinger
2016-11-25 11:30 ` Ramana Radhakrishnan
2016-11-28 19:42   ` Bernd Edlinger
2017-04-29 19:17     ` [PING**2] " Bernd Edlinger
2017-05-12 16:51       ` [PING**3] " 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=AM4PR0701MB2162ABF31904AC1333F801F4E4690@AM4PR0701MB2162.eurprd07.prod.outlook.com \
    --to=bernd.edlinger@hotmail.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kyrylo.tkachov@foss.arm.com \
    --cc=ramana.radhakrishnan@arm.com \
    --cc=richard.earnshaw@arm.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).