public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rainer.keller@hs-esslingen.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/107366] New: -fanalyzer with -fdiagnostics-format=sarif-file or sarif-stderr Date: Sun, 23 Oct 2022 12:15:15 +0000 [thread overview] Message-ID: <bug-107366-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107366 Bug ID: 107366 Summary: -fanalyzer with -fdiagnostics-format=sarif-file or sarif-stderr Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: rainer.keller@hs-esslingen.de Target Milestone: --- Created attachment 53760 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53760&action=edit Compilation of -freport-bug Compiling hwloc-2.8.0 with -fanalyzer and either -fdiagnostics-format=sarif-file or -fdiagnostics-format=sarif-stderr produces: during IPA pass: analyzer Please submit a full bug report, with preprocessed source (by using -freport-bug). See <https://gcc.gnu.org/bugs/> for instructions. Unfortunately I wasn't able to produce a MWE. Steps to reproduce: wget https://download.open-mpi.org/release/hwloc/v2.8/hwloc-2.8.0.tar.bz2 tar xf hwloc-2.8.0.tar.bz2 && cd hwloc-2.8.0 mkdir BUILD && cd $_ ../configure --prefix=$PWD/usr make CFLAGS="-fanalyzer -fdiagnostics-format=sarif-stderr" fails in hwloc/diff.c Using -fdiagnostics-format=json-stderr and -file works. The above does not seem to be related to https://gcc.gnu.org/PR106703 Attached is the -freport-bug of same file. Thanks
next reply other threads:[~2022-10-23 12:15 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-23 12:15 rainer.keller@hs-esslingen.de [this message] 2022-10-24 7:38 ` [Bug analyzer/107366] " marxin at gcc dot gnu.org 2022-10-24 7:46 ` marxin at gcc dot gnu.org 2022-10-24 7:47 ` marxin at gcc dot gnu.org 2022-10-24 15:13 ` [Bug analyzer/107366] ICE with " dmalcolm at gcc dot gnu.org 2022-10-24 20:49 ` cvs-commit at gcc dot gnu.org 2022-10-24 21:02 ` 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-107366-4@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).