public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/105564] Bad error for -ftrivial-auto-var-init without a choice argument
Date: Thu, 16 Jun 2022 06:23:21 +0000	[thread overview]
Message-ID: <bug-105564-4-0QvCJXYe3X@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105564-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105564

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Liska <marxin@gcc.gnu.org>:

https://gcc.gnu.org/g:ab66fd016d8efa250c471692f826b07e4a55e237

commit r13-1128-gab66fd016d8efa250c471692f826b07e4a55e237
Author: Martin Liska <mliska@suse.cz>
Date:   Wed May 11 16:07:25 2022 +0200

    opts: improve option suggestion

    In case where we have 2 equally good candidates like
    -ftrivial-auto-var-init=
    -Wtrivial-auto-var-init

    for -ftrivial-auto-var-init, we should take the candidate that
    has a difference in trailing sign symbol.

            PR driver/105564

    gcc/ChangeLog:

            * spellcheck.cc (test_find_closest_string): Add new test.
            * spellcheck.h (class best_match): Prefer a difference in
            trailing sign symbol.

  parent reply	other threads:[~2022-06-16  6:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11 11:41 [Bug driver/105564] New: " redi at gcc dot gnu.org
2022-05-11 12:21 ` [Bug driver/105564] " marxin at gcc dot gnu.org
2022-05-11 12:25 ` jakub at gcc dot gnu.org
2022-05-11 13:51 ` marxin at gcc dot gnu.org
2022-06-16  6:23 ` cvs-commit at gcc dot gnu.org [this message]
2022-06-16  6:24 ` marxin at gcc dot gnu.org
2022-06-16  8:30 ` redi at gcc dot gnu.org

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=bug-105564-4-0QvCJXYe3X@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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: 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).