public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/107366] -fanalyzer with -fdiagnostics-format=sarif-file or sarif-stderr
Date: Mon, 24 Oct 2022 07:38:59 +0000	[thread overview]
Message-ID: <bug-107366-4-ad3ZJ71fIY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107366-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107366

Martin Liška <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
                 CC|                            |marxin at gcc dot gnu.org
   Last reconfirmed|                            |2022-10-24
             Status|UNCONFIRMED                 |NEW

--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Reduced test-case:

$ cat pr107366.c
typedef enum {
  HWLOC_TOPOLOGY_DIFF_OBJ_ATTR_INFO
} hwloc_topology_diff_obj_attr_type_t;
enum { HWLOC_TOPOLOGY_DIFF_OBJ_ATTR } hwloc_apply_diff_one_diff_0_0;

void
hwloc_apply_diff_one() {
  switch (hwloc_apply_diff_one_diff_0_0)
  case HWLOC_TOPOLOGY_DIFF_OBJ_ATTR: {
    hwloc_topology_diff_obj_attr_type_t obj_attr_2_0_0;
    switch (obj_attr_2_0_0)
    case HWLOC_TOPOLOGY_DIFF_OBJ_ATTR_INFO: {
      unsigned ii = 0;
    }
  }
}

  reply	other threads:[~2022-10-24  7:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-23 12:15 [Bug c/107366] New: " rainer.keller@hs-esslingen.de
2022-10-24  7:38 ` marxin at gcc dot gnu.org [this message]
2022-10-24  7:46 ` [Bug analyzer/107366] " 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-ad3ZJ71fIY@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: link
Be 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).