interprocedural-analysis
Skill17 starsChanged 9 months agoApache-2.0View on GitHub
A skill for analyzing programs across function/procedure boundaries, enabling whole-program analysis.
In this repository98 other files it gives its agents.
- abstract-interpretation-engineSkill
- abstract-machineSkill
- acsl-annotation-assistantSkill
- actor-model-implementerSkill
- algebraic-effectsSkill
- alias-and-points-to-analysisSkill
- axiomatic-semanticsSkill
- bidirectional-type-checkingSkill
- bisimulation-checkerSkill
- capability-systemSkill
- closure-converterSkill
- common-subexpression-eliminatorSkill
- concurrency-verifierSkill
- constant-propagation-passSkill
- contextual-equivalenceSkill
- control-flow-analysisSkill
- coq-proof-assistantSkill
- cps-transformerSkill
- dafny-verifierSkill
- dataflow-analysis-frameworkSkill
- dead-code-eliminatorSkill
- defunctionalizationSkill
- denotational-semantics-builderSkill
- dependent-type-implementerSkill
- dsl-embeddingSkill
- effect-handlers-implementerSkill
- effect-systemSkill
- effect-type-systemSkill
- escape-analysisSkill
- existential-typesSkill
- ffi-designerSkill
- fuzzer-generatorSkill
- gadt-implementerSkill
- garbage-collector-implementerSkill
- graalvm-truffle-implementerSkill
- gradual-typing-implementerSkill
- higher-order-abstract-syntaxSkill
- hoare-logic-verifierSkill
- incremental-computationSkill
- information-flow-analyzerSkill
- inline-expanderSkill
- invariant-generatorSkill
- jit-compiler-builderSkill
- lambda-calculus-interpreterSkill
- language-server-protocolSkill
- lean-proverSkill
- lexer-generatorSkill
- linear-type-implementerSkill
- liveness-analysisSkill
- llvm-backend-generatorSkill
- lock-free-data-structureSkill
- loop-optimizerSkill
- loop-termination-proverSkill
- macro-expanderSkill
- memory-allocatorSkill
- message-passing-systemSkill
- mlir-dialect-designerSkill
- model-checkerSkill
- module-systemSkill
- monad-transformerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
Context Sensitivity: Call strings, cloning approaches
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Interprocedural Analysis
Domain: Static Analysis / Programming Languages
Overview
A skill for analyzing programs across function/procedure boundaries, enabling whole-program analysis.
Capabilities
- Build call graphs and interprocedural control flow
- Perform context-sensitive analysis
- Handle function pointers and virtual calls
- Implement summary-based analysis
- Solve interprocedural data flow equations
Techniques
- Call Graph Construction: Direct/indirect calls, virtual dispatch
- Context Sensitivity: Call strings, cloning approaches
- Summary Functions: Pre/post conditions for procedures
- Pointer Analysis: Alias analysis integration
- Whole-Program Analysis: Linking and incremental solving
Use Cases
- Security vulnerability detection
- Program verification
- Compiler optimization (inlining, constant propagation)
- Bug finding across module boundaries
References
See: ../dataflow-analysis-framework, ../control-flow-analysis, ../alias-and-points-to-analysis, ../taint-analysis
Research Tools & Artifacts
Real-world interprocedural analysis tools:
| Tool | Why It Matters |
| Soot | Java interprocedural analysis |
| WALA | IBM's analysis framework |
| LLVM | Whole-program analysis |
| Frama-C | C interprocedural |
| CodeQL | GitHub's security analysis |
Key Systems
- Soot: Java bytecode analysis
- WALA: Analysis framework
Research Frontiers
Current interprocedural analysis research:
| Direction | Key Papers | Challenge |
| Scalability | "Scalable Analysis" | Large codebases |
| Incremental | "Incremental IPA" | Change impact |
| Soundness | "Sound IPA" | Unknown calls |
Hot Topics
- AI for call graphs: Learning call graph construction
- Wasm analysis: Binary interprocedural
Implementation Pitfalls
Common interprocedural bugs:
| Pitfall | Real Example | Prevention |
| Indirect calls | Function pointers | Points-to |
| Virtual dispatch | OOP calls | Class analysis |
| Reflection | Java reflection | Model reflection |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.