public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/105959] new test case c-c++-common/diagnostic-format-sarif-file-4.c from r13-967-g6cf276ddf22066 fails
Date: Thu, 16 Mar 2023 22:08:04 +0000	[thread overview]
Message-ID: <bug-105959-4-lNdLUN47zZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105959-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to David Malcolm from comment #7)

[...snip...]

> There some variation due to json::object using a hash_map for the key/value
> pairs, which means (annoyingly) it outputs things in arbitrary order,
> leading to non-determinism in the .sarif content.

I've filed this as PR 109163.

[...snip...]

  parent reply	other threads:[~2023-03-16 22:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13 19:50 [Bug testsuite/105959] New: " seurer at gcc dot gnu.org
2022-07-19 21:39 ` [Bug testsuite/105959] " seurer at gcc dot gnu.org
2022-07-29 17:55 ` danglin at gcc dot gnu.org
2023-02-16 16:16 ` hp at gcc dot gnu.org
2023-03-13 20:53 ` dmalcolm at gcc dot gnu.org
2023-03-14  2:47 ` hp at gcc dot gnu.org
2023-03-14  3:04 ` hp at gcc dot gnu.org
2023-03-16 21:52 ` dmalcolm at gcc dot gnu.org
2023-03-16 21:58 ` dmalcolm at gcc dot gnu.org
2023-03-16 22:08 ` dmalcolm at gcc dot gnu.org [this message]
2023-03-17  2:55 ` hp at gcc dot gnu.org
2023-03-17 14:26 ` dmalcolm at gcc dot gnu.org
2023-03-17 15:35 ` dmalcolm at gcc dot gnu.org
2023-03-17 18:34 ` dmalcolm at gcc dot gnu.org
2023-03-18  0:57 ` hp at gcc dot gnu.org
2023-03-20 22:10 ` dmalcolm at gcc dot gnu.org
2023-03-22 20:50 ` cvs-commit at gcc dot gnu.org
2023-03-22 20:54 ` 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-105959-4-lNdLUN47zZ@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).