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, 19 Oct 2020 22:33:13 +0000	[thread overview]
Message-ID: <bug-94169-4-zKaorT8AX9@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

--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
Yes.  The recent proposal to change their signature to return const char* was 
rejected in WG14 thanks to source compatibility concerns:

http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2526.htm
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2565.pdf

I'm thinking of extending attribute access to annotate function return types
similarly to function arguments.  Another useful attribute is one that says:
the function returns a pointer passed to it by argument N, plus some offset
(with the offset being optional, and also specified by an argument).

      parent reply	other threads:[~2020-10-19 22:33 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 ` [Bug middle-end/94169] " msebor at gcc dot gnu.org
2020-03-16 19:34 ` 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 [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-94169-4-zKaorT8AX9@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).