public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tlange at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/105898] RFE: -fanalyzer should complain about overlapping args to memcpy and mempcpy
Date: Fri, 12 Aug 2022 13:02:40 +0000	[thread overview]
Message-ID: <bug-105898-4-aYrFc0Jqbj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105898-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Tim Lange <tlange at gcc dot gnu.org> ---
This checker is nearly finished, but is blocked by:
  https://gcc.gnu.org/pipermail/gcc/2022-July/239213.html

tl;dr: the current draft of the C standard does include new examples of how the
restrict keyword should be handled and states that two restrict-qualified
parameters are allowed to alias if they are never written in the body. Neither
my checker nor Wrestrict does check that at the moment. We yet have to decide
how to proceed with this checker.

  parent reply	other threads:[~2022-08-12 13:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08 14:56 [Bug analyzer/105898] New: " dmalcolm at gcc dot gnu.org
2022-06-08 17:54 ` [Bug analyzer/105898] " egallager at gcc dot gnu.org
2022-07-02 19:23 ` tlange at gcc dot gnu.org
2022-08-12 13:02 ` tlange at gcc dot gnu.org [this message]
2024-02-22 15:27 ` dmalcolm at gcc dot gnu.org
2024-02-26 18:09 ` [Bug analyzer/105898] RFE: -fanalyzer should complain about overlapping args to mempcpy, wmemcpy, and wmempcpy egallager 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-105898-4-aYrFc0Jqbj@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).