public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth 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: Thu, 13 Apr 2023 07:38:26 +0000 [thread overview] Message-ID: <bug-108722-4-sJtdwCjGPo@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 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |testsuite-fail Assignee|unassigned at gcc dot gnu.org |dmalcolm at gcc dot gnu.org Target|powerpc64-linux-gnu |powerpc64-linux-gnu |hppa-linux-gnu |hppa-linux-gnu | |x86_64-unknown-linux-gnu CC| |dmalcolm at gcc dot gnu.org Component|target |analyzer --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- also seeing this on x86_64, it's dependent on the glibc version (I have 2.37). The bug is in the analyzer I think, it implements FILE open/close tracking so it should suppress itself from diagnosing malloc/free diagnostic on FILEs.
next prev parent reply other threads:[~2023-04-13 7:38 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 ` rguenth at gcc dot gnu.org [this message] 2023-04-14 3:10 ` [Bug analyzer/108722] " cvs-commit at gcc dot gnu.org 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-sJtdwCjGPo@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).