https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107750
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2022-11-18
--- Comment #2 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
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 having
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 some
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.
