public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/105899] RFE: -fanalyzer could complain about misuses of standard C string APIs
Date: Thu, 24 Aug 2023 14:27:23 +0000 [thread overview]
Message-ID: <bug-105899-4-3GSBPCbWcX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105899-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105899
--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by David Malcolm <dmalcolm@gcc.gnu.org>:
https://gcc.gnu.org/g:bbdc0e0d0042ae16aa4d09ceb52c71e746d9139d
commit r14-3469-gbbdc0e0d0042ae16aa4d09ceb52c71e746d9139d
Author: David Malcolm <dmalcolm@redhat.com>
Date: Thu Aug 24 10:24:40 2023 -0400
analyzer: implement kf_strcat [PR105899]
gcc/analyzer/ChangeLog:
PR analyzer/105899
* call-details.cc
(call_details::check_for_null_terminated_string_arg): Split into
overloads, one taking just an arg_idx, the other a new
"include_terminator" param.
* call-details.h: Likewise.
* kf.cc (class kf_strcat): New.
(kf_strcpy::impl_call_pre): Update for change to
check_for_null_terminated_string_arg.
(register_known_functions): Register kf_strcat.
* region-model.cc
(region_model::check_for_null_terminated_string_arg): Split into
overloads, one taking just an arg_idx, the other a new
"include_terminator" param. When returning an svalue, handle
"include_terminator" being false by subtracting one.
* region-model.h
(region_model::check_for_null_terminated_string_arg): Split into
overloads, one taking just an arg_idx, the other a new
"include_terminator" param.
gcc/ChangeLog:
PR analyzer/105899
* doc/invoke.texi (Static Analyzer Options): Add "strcat" to the
list of functions known to the analyzer.
gcc/testsuite/ChangeLog:
PR analyzer/105899
* gcc.dg/analyzer/strcat-1.c: New test.
Signed-off-by: David Malcolm <dmalcolm@redhat.com>
next prev parent reply other threads:[~2023-08-24 14:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 15:00 [Bug analyzer/105899] New: " dmalcolm at gcc dot gnu.org
2023-08-11 22:09 ` [Bug analyzer/105899] " cvs-commit at gcc dot gnu.org
2023-08-11 23:16 ` dmalcolm at gcc dot gnu.org
2023-08-22 1:16 ` cvs-commit at gcc dot gnu.org
2023-08-22 1:16 ` cvs-commit at gcc dot gnu.org
2023-08-22 22:38 ` cvs-commit at gcc dot gnu.org
2023-08-24 14:26 ` cvs-commit at gcc dot gnu.org
2023-08-24 14:26 ` cvs-commit at gcc dot gnu.org
2023-08-24 14:26 ` cvs-commit at gcc dot gnu.org
2023-08-24 14:27 ` cvs-commit at gcc dot gnu.org
2023-08-24 14:27 ` cvs-commit at gcc dot gnu.org
2023-08-24 14:27 ` cvs-commit at gcc dot gnu.org
2023-08-24 14:27 ` cvs-commit at gcc dot gnu.org [this message]
2023-08-29 14:59 ` cvs-commit at gcc dot gnu.org
2023-09-06 13:33 ` cvs-commit at gcc dot gnu.org
2023-09-06 13:33 ` cvs-commit 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-105899-4-3GSBPCbWcX@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).