KhronosGroup / KhronosGroup/SPIRV-Tools

spirv-fuzz: Make facts context-dependent

Open
#3,696 0 comments 0 reactions 0 assignees View on GitHub
component:fuzzer
Dominant language
C++
Stars
1.4k
Forks
709
Avg merge
1d 22h
Merged PRs (30d)
28

Description

Currently, every fact holds everywhere in the module. For example, if some pointer is marked with `PointeeValueIsIrrelevant`, you can insert `OpStore`s anywhere as long as domination rules are satisfied.

It might be good to consider context-dependent facts. For example, we could have a fact saying that some variable is not being read from after this point in the function and, thus, we can use `OpStore`s to alter the variable's value. This is essentially an equivalent of `PointeeValueIsIrrelevant` but with the knowledge of the program's semantics.

A benefit of having these facts is that we can alter original variables in the module as well.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing how existing facts such as PointeeValueIsIrrelevant are represented and applied across a SPIR-V module. Define the program points and semantics for a context-dependent fact about later reads before determining how it would enable valid OpStore insertion and affect original variables.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
compilers
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.