From: Jeff Law <law@redhat.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][RFA/RFC] Stack clash mitigation patch 03/08
Date: Mon, 17 Jul 2017 17:39:00 -0000 [thread overview]
Message-ID: <f436cfd4-b392-0987-14cd-1889b53e0b2b@redhat.com> (raw)
In-Reply-To: <20170717162824.GL13471@gate.crashing.org>
On 07/17/2017 10:28 AM, Segher Boessenkool wrote:
> 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.
THanks. Fixed for next update.
I nearly posted V2 last night, but wanted to take a stab at the aarch64
bits again :-)
jeff
prev parent reply other threads:[~2017-07-17 17:39 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
2017-07-17 17:39 ` Jeff Law [this message]
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=f436cfd4-b392-0987-14cd-1889b53e0b2b@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.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).