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 analyzer/102471] RFE: add support to analyzer testsuite for running SAMATE/SARD tests (e.g. Juliet Test Suite) Date: Wed, 01 Dec 2021 17:39:18 +0000 [thread overview] Message-ID: <bug-102471-4-v3y2hNm3ZK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102471-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102471 David Malcolm <dmalcolm at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #3 from David Malcolm <dmalcolm at gcc dot gnu.org> --- I've got a primitive workflow of running the Juliet 1.3 testsuite, and a script for testing results here: https://github.com/davidmalcolm/juliet-harness Currently I've only run it on the: C/testcases/CWE415_Double_Free/s01 sudirectory, with: # of passes 130 # of failures 103 I'm looking through the failures.
next prev parent reply other threads:[~2021-12-01 17:39 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-23 13:26 [Bug analyzer/102471] New: " dmalcolm at gcc dot gnu.org 2021-09-24 6:15 ` [Bug analyzer/102471] " rguenther at suse dot de 2021-09-24 6:33 ` rguenth at gcc dot gnu.org 2021-10-26 0:16 ` pinskia at gcc dot gnu.org 2021-12-01 15:52 ` dmalcolm at gcc dot gnu.org 2021-12-01 17:39 ` dmalcolm at gcc dot gnu.org [this message] 2021-12-01 23:21 ` cvs-commit at gcc dot gnu.org 2022-05-17 18:04 ` dmalcolm at gcc dot gnu.org 2023-01-18 16:17 ` dmalcolm at gcc dot gnu.org 2023-01-19 19:01 ` 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-102471-4-v3y2hNm3ZK@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).