https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102471
--- Comment #1 from rguenther at suse dot de <rguenther at suse dot de> --- On Thu, 23 Sep 2021, dmalcolm at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102471 > > Bug ID: 102471 > Summary: RFE: add support to analyzer testsuite for running > SAMATE/SARD tests (e.g. Juliet Test Suite) > Product: gcc > Version: 12.0 > Status: UNCONFIRMED > Severity: normal > Priority: P3 > Component: analyzer > Assignee: dmalcolm at gcc dot gnu.org > Reporter: dmalcolm at gcc dot gnu.org > CC: rguenth at gcc dot gnu.org > Target Milestone: --- > > See: > https://www.nist.gov/itl/ssd/software-quality-group/samate > https://samate.nist.gov/SARD/testsuite.php > > The links above have various promising-looking testsuites e.g. > - Juliet Test Suite > - Klocwork test suite > - ITC-Benchmarks > etc > > It would be good to be able to (somehow) automatically run them as part of > regression testing of the analyzer - either by turning them directly into > DejaGnu tests, or by wrapping the suite's own harness in a way that we can > invoke it during "make check". It might be also feasible to think of on-the-side CI runs of external testsuites on buildbots or similar and have results reported on gcc.gnu.org.
