public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "carlosgalvezp at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109642] False Positive -Wdangling-reference with std::span-like classes Date: Thu, 27 Apr 2023 19:20:36 +0000 [thread overview] Message-ID: <bug-109642-4-83yypF8FUN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109642-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109642 --- Comment #4 from Carlos Galvez <carlosgalvezp at gmail dot com> --- While I can do that on my own code, I cannot add that suppression on third-party code, like Eigen (which I also get a lot of false positives in similar code), even if I include the header via -isystem - since the warnings are on the client side. Is this really the expected behavior of a warning belonging to -Wall? Has this warning been tested on large projects to evaluate the false positive rate? Would you consider perhaps reducing the scope of the warning in order to reduce the false positive rate, alternatively move it out of Wall? It's sad that a lot of work and effort was put into creating this warning and it will just probably be disabled on most projects. When a tool produces a lot of false positives, there is high risk that developers stop trusting the tool and true positives are ignored.
next prev parent reply other threads:[~2023-04-27 19:20 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-27 6:36 [Bug c++/109642] New: " carlosgalvezp at gmail dot com 2023-04-27 7:03 ` [Bug c++/109642] " pinskia at gcc dot gnu.org 2023-04-27 7:09 ` carlosgalvezp at gmail dot com 2023-04-27 15:49 ` mpolacek at gcc dot gnu.org 2023-04-27 19:20 ` carlosgalvezp at gmail dot com [this message] 2023-04-28 13:00 ` mpolacek at gcc dot gnu.org 2023-04-28 14:08 ` carlosgalvezp at gmail dot com 2023-05-02 19:49 ` cvs-commit at gcc dot gnu.org 2023-06-21 18:43 ` pinskia at gcc dot gnu.org 2023-06-21 18:51 ` mpolacek at gcc dot gnu.org 2023-06-21 19:06 ` barry.revzin at gmail dot com 2024-01-17 12:16 ` miro.palmu at helsinki dot fi 2024-01-19 17:35 ` mpolacek at gcc dot gnu.org 2024-01-19 23:32 ` mpolacek at gcc dot gnu.org 2024-01-22 20:52 ` mpolacek at gcc dot gnu.org 2024-01-22 21:16 ` cvs-commit at gcc dot gnu.org 2024-01-30 18:32 ` mpolacek at gcc dot gnu.org 2024-01-30 18:38 ` lopresti at gmail dot com 2024-01-30 18:42 ` mpolacek at gcc dot gnu.org 2024-03-01 20:55 ` cvs-commit at gcc dot gnu.org 2024-05-01 17:18 ` pinskia 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-109642-4-83yypF8FUN@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: linkBe 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).