From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 45E08384D9B1; Fri, 18 Nov 2022 13:29:53 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 45E08384D9B1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1668778193; bh=EaRUc0SdWHVa3YJ2FexnhfKCToh2PHfJLH7CmKn2FtI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=TrWAoeH8WODW1sCtcHIGDIfGQxjKvTledST51cyt7nuh4zykv1Qvr6Y22RvUAcwei Ffe21/yuqGQs7Gzos9cj9TQ9q3lQwzdBQT8rdfc+yb7maofS0W8JOUe/WDYXWfAm1D dZkFLn3EWU/sqSmydgZxXlaPN8tx9ugkJscUP+CU= From: "dmalcolm at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/107750] Many gcc.dg/analyzer/fd-*.c tests FAIL Date: Fri, 18 Nov 2022 13:29:52 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: analyzer X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: testsuite-fail X-Bugzilla-Severity: normal X-Bugzilla-Who: dmalcolm at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org X-Bugzilla-Target-Milestone: 13.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: everconfirmed bug_status cf_reconfirmed_on Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107750 David Malcolm changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2022-11-18 --- Comment #2 from David Malcolm --- Sorry about the breakage; thanks for filing this, and for the patch. Looking at: FAIL: gcc.dg/analyzer/fd-access-mode-target-headers.c (test for warnings, line 53) it looks like the analyzer was able to figure out the values of O_RDONLY and O_WRONLY in your headers, but not of O_ACCMODE. I suspect it might be havi= ng issues with SOCK_STREAM and SOCK_DGRAM also. How are these values defined in your headers? The analyzer has gained some ability to try to e.g. scrape macro values from the C frontend, but only so= me cases are supported. There's a way of debugging this using -fdump-analyzer, but I'm looking at adding a way to make such issues show up more clearly in the DejaGnu logs, which hopefully should make them easier to track down.=