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 middle-end/94169] warn for modifying getenv() result Date: Mon, 16 Mar 2020 19:10:02 +0000 [thread overview] Message-ID: <bug-94169-4-9eYysEvOuD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94169-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94169 Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks|88781 | --- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> --- On second thought, rather than extending -Wstringop-overflow it might be better to diagnoses this under "modifying a const object" as requested in 90404. In addition, rather than diagnosing only built-in functions (and growing the list GCC would have to recognize just to detect bugs), providing an attribute to let users denote pointers to non-modifiable objects would be a better solution. It could be an entirely new attribute or it could be done by extending the existing access attribute read_only to apply also to pointers returned from functions and even to data members. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88781 [Bug 88781] [meta-bug] bogus/missing -Wstringop-truncation warnings
next prev parent reply other threads:[~2020-03-16 19:10 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-13 16:12 [Bug middle-end/94169] New: " msebor at gcc dot gnu.org 2020-03-16 19:10 ` msebor at gcc dot gnu.org [this message] 2020-03-16 19:34 ` [Bug middle-end/94169] " msebor at gcc dot gnu.org 2020-10-19 20:47 ` dmalcolm at gcc dot gnu.org 2020-10-19 22:33 ` 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-94169-4-9eYysEvOuD@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: 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).