public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jeff Law <law@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][RFA/RFC] Stack clash mitigation patch 03/08
Date: Mon, 17 Jul 2017 16:28:00 -0000	[thread overview]
Message-ID: <20170717162824.GL13471@gate.crashing.org> (raw)
In-Reply-To: <f2c77cd1-8b20-5178-ed01-73e00b968efa@redhat.com>

Hi,

Just some typos:

On Tue, Jul 11, 2017 at 03:20:38PM -0600, Jeff Law wrote:
> +/* If debugging dumps are requested, dump infomation about how the

Typo ("information").

> +   target handled -fstack-check=clash for the prologue.
> +
> +   PROBES describes what if any probes were emitted.
> +
> +   RESIDUALS indicates if the prologue had any residual allocation
> +   (ie total allocation was not a multiple of PROBE_INTERVAL.  */

Missing closing paren; i.e.


Segher

  reply	other threads:[~2017-07-17 16:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-11 21:20 Jeff Law
2017-07-17 16:28 ` Segher Boessenkool [this message]
2017-07-17 17:39   ` Jeff Law

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=20170717162824.GL13471@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --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).