public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/107366] ICE with -fanalyzer with -fdiagnostics-format=sarif-file or sarif-stderr
Date: Mon, 24 Oct 2022 20:49:19 +0000	[thread overview]
Message-ID: <bug-107366-4-WtoIQggovi@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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by David Malcolm <dmalcolm@gcc.gnu.org>:

https://gcc.gnu.org/g:2e8a0553918adc919f98ac5c0224fc6ce1fef68d

commit r13-3469-g2e8a0553918adc919f98ac5c0224fc6ce1fef68d
Author: Martin Liska <mliska@suse.cz>
Date:   Mon Oct 24 16:40:00 2022 -0400

    diagnostics: fix ICE in sarif output with NULL filename [PR107366]

    gcc/ChangeLog:
            PR analyzer/107366
            * diagnostic-format-sarif.cc
            (sarif_builder::maybe_make_physical_location_object): Gracefully
            reject locations with NULL filename.

    gcc/testsuite/ChangeLog:
            PR analyzer/107366
            * gcc.dg/analyzer/sarif-pr107366.c: New test.

    Signed-off-by: David Malcolm <dmalcolm@redhat.com>

  parent reply	other threads:[~2022-10-24 20:49 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 ` [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 [this message]
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-WtoIQggovi@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).