public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rootkea at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/103533] Enable "taint" state machine with -fanalyzer without requiring -fanalyzer-checker=taint
Date: Tue, 22 Mar 2022 18:36:55 +0000 [thread overview]
Message-ID: <bug-103533-4-mU1MKERheC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103533-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103533
Avinash Sonawane <rootkea at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rootkea at gmail dot com
--- Comment #5 from Avinash Sonawane <rootkea at gmail dot com> ---
Since we are not quite there yet we should remove (comment out) the tainted-*
checkers listed under -fanalyzer in docs which says "Enabling this option
effectively enables the following warnings:".
Also, the wording in docs suggest that `-fanalyzer -fanalyzer-checker=taint`
enables the taint checkers *in addition* to the default checkers but currently,
enabling -fanalyzer-checker=taint stops other checkers. I came to know about
this after finding none of other checkers working. We should document this.
I just submitted a patch which documents the above fact and comments out the
tainted-* checkers under -fanalyzer.
When this issue gets fixed we can simply remove the .texi comment commands and
drop the line saying other checkers not working with taint checker.
https://gcc.gnu.org/pipermail/gcc-patches/2022-March/592144.html
next prev parent reply other threads:[~2022-03-22 18:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 18:49 [Bug analyzer/103533] New: " dmalcolm at gcc dot gnu.org
2021-12-06 23:37 ` [Bug analyzer/103533] " cvs-commit at gcc dot gnu.org
2022-01-07 15:17 ` dmalcolm at gcc dot gnu.org
2022-01-12 15:00 ` cvs-commit at gcc dot gnu.org
2022-03-18 23:22 ` cvs-commit at gcc dot gnu.org
2022-03-22 18:36 ` rootkea at gmail dot com [this message]
2022-03-25 0:57 ` cvs-commit at gcc dot gnu.org
2022-03-25 9:57 ` cvs-commit at gcc dot gnu.org
2023-11-14 20:55 ` cvs-commit at gcc dot gnu.org
2023-11-14 21:02 ` dmalcolm at gcc dot gnu.org
2023-12-01 13:52 ` 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-103533-4-mU1MKERheC@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).