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/108722] gcc.dg/analyzer/file-CWE-1341-example.c fails on power 9 BE Date: Fri, 14 Apr 2023 03:10:26 +0000 [thread overview] Message-ID: <bug-108722-4-c1Lw212sHW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108722-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108722 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jiu Fu Guo <guojiufu@gcc.gnu.org>: https://gcc.gnu.org/g:edc6659c97c4a747123b1150b372dc8e7a83a824 commit r13-7176-gedc6659c97c4a747123b1150b372dc8e7a83a824 Author: Jiufu Guo <guojiufu@linux.ibm.com> Date: Wed Apr 12 10:12:58 2023 +0800 testsuite: filter out warning noise for CWE-1341 test The case file-CWE-1341-example.c checkes [CWE-1341](`double-fclose`). While on some systems, besides [CWE-1341], a message of [CWE-415] is also reported. On those systems, attribute `malloc` may be attached on fopen: ``` # 258 "/usr/include/stdio.h" 3 4 extern FILE *fopen (const char *__restrict __filename, const char *__restrict __modes) __attribute__ ((__malloc__)) __attribute__ ((__malloc__ (fclose, 1))) ; or say: __attribute_malloc__ __attr_dealloc_fclose __wur; ``` See (PR analyzer/108722) for future fix in the analyzer. This workaround patch adds -Wno-analyzer-double-free to this case. gcc/testsuite/ChangeLog: PR analyzer/108722 * gcc.dg/analyzer/file-CWE-1341-example.c: Update.
next prev parent reply other threads:[~2023-04-14 3:10 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-08 17:46 [Bug target/108722] New: " seurer at gcc dot gnu.org 2023-04-02 15:04 ` [Bug target/108722] " danglin at gcc dot gnu.org 2023-04-11 9:23 ` guojiufu at gcc dot gnu.org 2023-04-13 7:38 ` [Bug analyzer/108722] " rguenth at gcc dot gnu.org 2023-04-14 3:10 ` cvs-commit at gcc dot gnu.org [this message] 2024-03-04 13:00 ` [Bug analyzer/108722] [13/14 Regression] " rguenth at gcc dot gnu.org 2024-03-08 15:39 ` law at gcc dot gnu.org 2024-03-08 22:17 ` seurer 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-108722-4-c1Lw212sHW@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).