public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-6444] driver: toplev: Fix a typo Date: Fri, 3 Mar 2023 11:25:38 +0000 (GMT) [thread overview] Message-ID: <20230303112538.65C0F3858D33@sourceware.org> (raw) https://gcc.gnu.org/g:6703f490cd802650cf5a5a8ada6c5077316547dd commit r13-6444-g6703f490cd802650cf5a5a8ada6c5077316547dd Author: Xi Ruoyao <xry111@xry111.site> Date: Fri Mar 3 16:50:53 2023 +0800 driver: toplev: Fix a typo The driver emits a warning when -fstack-check and -fstack-clash-protection are used together, but the message refers to "-fstack-clash_protection" (underline instead of dash). gcc/ChangeLog: * toplev.cc (process_options): Fix the spelling of "-fstack-clash-protection". Diff: --- gcc/toplev.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/toplev.cc b/gcc/toplev.cc index 4c15d4f542e..109c9d58cbd 100644 --- a/gcc/toplev.cc +++ b/gcc/toplev.cc @@ -1580,7 +1580,7 @@ process_options (bool no_backend) if (flag_stack_check != NO_STACK_CHECK && flag_stack_clash_protection) { warning_at (UNKNOWN_LOCATION, 0, - "%<-fstack-check=%> and %<-fstack-clash_protection%> are " + "%<-fstack-check=%> and %<-fstack-clash-protection%> are " "mutually exclusive; disabling %<-fstack-check=%>"); flag_stack_check = NO_STACK_CHECK; }
reply other threads:[~2023-03-03 11:25 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230303112538.65C0F3858D33@sourceware.org \ --to=xry111@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.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: linkBe 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).