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**2] [PATCH, ARM] Further improve stack usage on sha512 (PR 77308)
Date: Thu, 24 Nov 2016 14:24:00 -0000	[thread overview]
Message-ID: <AM4PR0701MB216219490616DE0583294216E4B60@AM4PR0701MB2162.eurprd07.prod.outlook.com> (raw)
In-Reply-To: <AM4PR0701MB2162C9AE8C2D2FE5F07CD373E4BE0@AM4PR0701MB2162.eurprd07.prod.outlook.com>

Hi,

this patch is still waiting for review:

[PATCH, ARM] Further improve stack usage on sha512 (PR 77308)
https://gcc.gnu.org/ml/gcc-patches/2016-11/msg00523.html


Thanks
Bernd.

  reply	other threads:[~2016-11-24 14:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-16 17:28 [PING] " Bernd Edlinger
2016-11-24 14:24 ` Bernd Edlinger [this message]
2016-12-05 13:41   ` Bernd Edlinger
2016-12-12  5:59     ` [PING**2] " Bernd Edlinger
2016-12-19  8:22       ` Bernd Edlinger
2016-12-27 14:13         ` [PING**3] " Bernd Edlinger
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-09-04 14:52       ` Kyrill Tkachov
2017-09-05  8:47         ` Christophe Lyon
2017-09-05 14:25           ` Bernd Edlinger
2017-09-05 15:02             ` Wilco Dijkstra
2017-09-05 17:48               ` Bernd Edlinger
2017-09-05 17:53                 ` Kyrill Tkachov
2017-09-05 18:20                   ` Christophe Lyon
2017-09-06  7:35                     ` Christophe Lyon
2017-09-05 21:28                 ` Wilco Dijkstra
2017-09-06  9:31                   ` Bernd Edlinger
2017-09-05 17:45             ` Kyrill Tkachov

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=AM4PR0701MB216219490616DE0583294216E4B60@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).