public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dimitri at ouroboros dot rocks" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/107582] - -Wanalyzer-use-of-uninitialized-value false positive using pthread_cond_timedwait Date: Tue, 08 Nov 2022 21:43:11 +0000 [thread overview] Message-ID: <bug-107582-4-twc1ZAK7P1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107582-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107582 dimitri at ouroboros dot rocks changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #53852|0 |1 is obsolete| | Attachment #53853|0 |1 is obsolete| | --- Comment #3 from dimitri at ouroboros dot rocks --- Created attachment 53854 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53854&action=edit simpler test case Got a simpler reproducer. gcc -c -fanalyzer test_if_else_pthread_min.c also reproduces the issue. It's probably the pthread_cleanup handlers (macros) with an internal while loop that cause the issue rather than the pthread_cond_timedwait.
next prev parent reply other threads:[~2022-11-08 21:43 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-08 20:54 [Bug analyzer/107582] New: " dimitri at ouroboros dot rocks 2022-11-08 21:05 ` [Bug analyzer/107582] " dimitri at ouroboros dot rocks 2022-11-08 21:10 ` dimitri at ouroboros dot rocks 2022-11-08 21:43 ` dimitri at ouroboros dot rocks [this message] 2022-11-18 20:07 ` [Bug analyzer/107582] - -Wanalyzer-use-of-uninitialized-value false positive with while loop in pthread_cleanup_push dmalcolm at gcc dot gnu.org 2022-11-18 20:20 ` dmalcolm at gcc dot gnu.org 2022-11-19 0:40 ` cvs-commit at gcc dot gnu.org 2022-11-19 0:44 ` dmalcolm at gcc dot gnu.org 2022-11-19 0:46 ` dmalcolm at gcc dot gnu.org 2022-11-19 0:47 ` dmalcolm at gcc dot gnu.org 2022-11-19 21:29 ` dimitri at ouroboros dot rocks 2023-03-29 18:18 ` cvs-commit at gcc dot gnu.org 2023-03-29 19:26 ` dmalcolm 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-107582-4-twc1ZAK7P1@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).