public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager 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 mempcpy, wmemcpy, and wmempcpy
Date: Mon, 26 Feb 2024 18:09:44 +0000 [thread overview]
Message-ID: <bug-105898-4-H7MLOeXrOV@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
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|RFE: -fanalyzer should |RFE: -fanalyzer should
|complain about overlapping |complain about overlapping
|args to memcpy and mempcpy |args to mempcpy, wmemcpy,
| |and wmempcpy
--- Comment #5 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to David Malcolm from comment #4)
> I implemented this a different way, for memcpy, in r14-3556-g034d99e81484fb
> (by special-casing it).
>
> We don't yet check mempcpy, wmemcpy, or wmempcp; keeping bug open to handle
> those.
Retitling.
prev parent reply other threads:[~2024-02-26 18:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 14:56 [Bug analyzer/105898] New: RFE: -fanalyzer should complain about overlapping args to memcpy and mempcpy 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
2024-02-22 15:27 ` dmalcolm at gcc dot gnu.org
2024-02-26 18:09 ` egallager 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-105898-4-H7MLOeXrOV@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).