public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-1420] testsuite: add verify-sarif-file to some testcases that were missing it Date: Tue, 30 May 2023 22:58:27 +0000 (GMT) [thread overview] Message-ID: <20230530225827.9D4813858D20@sourceware.org> (raw) https://gcc.gnu.org/g:e4c8f7024f02d8e223c6df7bd117e7615a553918 commit r14-1420-ge4c8f7024f02d8e223c6df7bd117e7615a553918 Author: David Malcolm <dmalcolm@redhat.com> Date: Tue May 30 18:57:57 2023 -0400 testsuite: add verify-sarif-file to some testcases that were missing it gcc/testsuite/ChangeLog: * gcc.dg/analyzer/malloc-sarif-1.c: Add missing verify-sarif-file directive. * gcc.dg/analyzer/sarif-pr107366.c: Likewise. Signed-off-by: David Malcolm <dmalcolm@redhat.com> Diff: --- gcc/testsuite/gcc.dg/analyzer/malloc-sarif-1.c | 2 ++ gcc/testsuite/gcc.dg/analyzer/sarif-pr107366.c | 1 + 2 files changed, 3 insertions(+) diff --git a/gcc/testsuite/gcc.dg/analyzer/malloc-sarif-1.c b/gcc/testsuite/gcc.dg/analyzer/malloc-sarif-1.c index 3d141b53f47..3d798e687e6 100644 --- a/gcc/testsuite/gcc.dg/analyzer/malloc-sarif-1.c +++ b/gcc/testsuite/gcc.dg/analyzer/malloc-sarif-1.c @@ -12,6 +12,8 @@ void test_1 (void) /* Verify SARIF output. + { dg-final { verify-sarif-file } } + The threadFlowLocation objects should have "kinds" properties reflecting the meanings of the events: { dg-final { scan-sarif-file "\"kinds\": \\\[\"acquire\", \"memory\"\\\]" } } diff --git a/gcc/testsuite/gcc.dg/analyzer/sarif-pr107366.c b/gcc/testsuite/gcc.dg/analyzer/sarif-pr107366.c index 997cf56586d..ee156d4df23 100644 --- a/gcc/testsuite/gcc.dg/analyzer/sarif-pr107366.c +++ b/gcc/testsuite/gcc.dg/analyzer/sarif-pr107366.c @@ -18,3 +18,4 @@ hwloc_apply_diff_one() { } } +/* { dg-final { verify-sarif-file } } */
reply other threads:[~2023-05-30 22:58 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230530225827.9D4813858D20@sourceware.org \ --to=dmalcolm@gcc.gnu.org \ --cc=gcc-cvs@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).