public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/97622] ubsan '  unterminated quote character ''' in format
Date: Fri, 30 Oct 2020 14:52:12 +0000	[thread overview]
Message-ID: <bug-97622-4-jxsC0yYKXj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97622-4@http.gcc.gnu.org/bugzilla/>

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

Martin Sebor <msebor at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|INVALID                     |---
           Keywords|                            |diagnostic
                 CC|                            |msebor at gcc dot gnu.org
             Status|RESOLVED                    |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |msebor at gcc dot gnu.org

--- Comment #5 from Martin Sebor <msebor at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #4)
> No.
> If it is the -Wformat-diag warning, just ignore it.  It has been added
> without any attempt to resolve the warnings and warns for many things that
> are just fine.

Without any attempt?  Hardly.  I committed a 12 patch series to resolve most
instances when I introduced the warning:
  https://gcc.gnu.org/pipermail/gcc-patches/2019-May/521567.html
And then proceeded to clean up more here:
  https://gcc.gnu.org/pipermail/gcc-patches/2019-May/522333.html
and more still here:
  https://gcc.gnu.org/pipermail/gcc-patches/2019-June/523281.html

Others have cleaned up a bunch more later that either remained or crept in
because the warning doesn't trigger errors.  See r272607, r272608, r272789,
r273468, r273475, and more.

The few outstanding instances should be fixed and the error suppression for the
warning removed.  The one in comment #0 can be worked around with by making the
quote an argument to a %c.  An an arguably more robust solution would be to
introduce another attribute that doesn't enforce some of the rules for
pp_printf().

Let me take care of this.

  parent reply	other threads:[~2020-10-30 14:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29  0:22 [Bug bootstrap/97622] New: " euloanty at live dot com
2020-10-29  8:47 ` [Bug bootstrap/97622] " jakub at gcc dot gnu.org
2020-10-29  8:55 ` marxin at gcc dot gnu.org
2020-10-29 17:24 ` euloanty at live dot com
2020-10-29 17:24 ` euloanty at live dot com
2020-10-29 17:42 ` jakub at gcc dot gnu.org
2020-10-29 19:56 ` euloanty at live dot com
2020-10-30 14:52 ` msebor at gcc dot gnu.org [this message]
2020-10-30 15:13 ` jakub at gcc dot gnu.org
2020-11-25  1:11 ` msebor at gcc dot gnu.org
2020-11-25 22:01 ` cvs-commit at gcc dot gnu.org
2020-11-25 22:05 ` msebor 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-97622-4-jxsC0yYKXj@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).