From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [patch] bpf: Fix double whitespace warning
Date: Wed, 15 Feb 2023 11:49:43 +0100 [thread overview]
Message-ID: <87r0urjj94.fsf@oracle.com> (raw)
In-Reply-To: <20230215100202.lrjn2dpk2xuwht6a@lug-owl.de> (Jan-Benedict Glaw's message of "Wed, 15 Feb 2023 11:02:02 +0100")
> Hi!
>
> Since a recent commit, the BPF target produces a new warning due to
> two consecutive non-quoted spaces in a message. This'll fix it:
>
> gcc/
> * config/bpf/bpf.cc (bpf_option_override): Fix doubled space.
>
>
> Ok?
OK. Thanks for the patch.
(Sorry I didn't fix this when you first reported it. My TODO list is
long atm :/)
> MfG, JBG
>
> diff --git a/gcc/config/bpf/bpf.cc b/gcc/config/bpf/bpf.cc
> index b268801d00c..d8693f8cfbe 100644
> --- a/gcc/config/bpf/bpf.cc
> +++ b/gcc/config/bpf/bpf.cc
> @@ -258,7 +258,7 @@ bpf_option_override (void)
> {
> inform (input_location,
> "%<-fstack-protector%> does not work "
> - " on this architecture");
> + "on this architecture");
> flag_stack_protect = 0;
> }
> }
prev parent reply other threads:[~2023-02-15 10:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 16:25 [COMMITTED] bpf: disable -fstack-protector in BPF Jose E. Marchesi
2023-01-28 14:12 ` Jan-Benedict Glaw
2023-02-15 10:02 ` [patch] bpf: Fix double whitespace warning Jan-Benedict Glaw
2023-02-15 10:49 ` Jose E. Marchesi [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=87r0urjj94.fsf@oracle.com \
--to=jose.marchesi@oracle.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jbglaw@lug-owl.de \
/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).