goblint / goblint/analyzer

See if insights about Juliet from IKOS carry over

Open
#1,968 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

precision student-job sv-comp
Dominant language
OCaml
Stars
252
Forks
90
Avg merge
4d 1m
Merged PRs (30d)
19

Description

There is a new study where they study the precision of IKOS on Juliet: https://ieeexplore.ieee.org/abstract/document/11431352

This study details the specific coding patterns that cause false negatives—such as wide character usage and widening techniques in loops—providing insights for practitioners selecting the IKOS analysis tool and researchers improving static analysis precision.

This could be interesting for a BSc student to read and see if any of these things also apply to Goblint.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read the linked study first, focusing on the Juliet patterns reported to cause IKOS false negatives. Then inspect Goblint's existing analyses and Juliet-related tests, if present, to check whether the same patterns are handled. Done means documenting which findings carry over to Goblint and which do not.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, ocaml
Domain
compilers
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.