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 c/61579] -Wwrite-strings does not behave as a warning option
Date: Wed, 22 Jul 2020 17:32:24 +0000	[thread overview]
Message-ID: <bug-61579-4-hc8G1x0O0t@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61579-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |msebor at gcc dot gnu.org
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=90404

--- Comment #9 from Martin Sebor <msebor at gcc dot gnu.org> ---
pr90404 is somewhat related to this: it requests a new warning option to flag
attempts to modify a const object of any type/kind.  In my prototype
implementation of it that I hope to submit for GCC 11 I call the option
-Wwrite-const.  It's implemented in the middle end so it detects all such
attempts, including for instance things like '*strchr("x", 'x') = 0', and
avoids triggering on provably unreachable code.  It's just as capable as other
late warnings, but, of course, also subject to just as many false positives and
negatives as they are.

      parent reply	other threads:[~2020-07-22 17:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-21 11:34 [Bug c/61579] New: " bugdal at aerifal dot cx
2014-06-21 15:45 ` [Bug c/61579] " manu at gcc dot gnu.org
2014-07-22 16:50 ` mpolacek at gcc dot gnu.org
2020-07-22 13:22 ` david at westcontrol dot com
2020-07-22 13:42 ` manu at gcc dot gnu.org
2020-07-22 17:32 ` msebor at gcc dot gnu.org [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=bug-61579-4-hc8G1x0O0t@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).