xymus / pep8analysis

Tools to statically analyze Pep/8 programs

Pep/8 Analysis has moved!

The Pep/8 Analysis tool has been merged in the official Nit repository under the /contrib/pep8analysis/ folder.

Link: https://github.com/privat/nit/tree/master/contrib/pep8analysis

This repository is left available for historical purposes and redirection. Latest and future updates will be made available there, or in my fork at: https://github.com/xymus/nit/tree/master/contrib/pep8analysis

---

Pep/8 Analysis

This project provides tools to statically analyze Pep/8 programs in order to detect bugs or bad programming practices.

For more information about the Pep/8 assembly language visit http://code.google.com/p/pep8-1/.

Installation

Make sure you have a Nit compiler installed (http://nitlanguage.org) and the environment variable NIT_DIR correctly set to the Nit installation directory.

Clone the source from http://github.com/xymus/pep8analysis.git and compile with make.

Usage

For basic results, execute on the Pep/8 program prog.pep with bin/pep8analyzer prog.pep.

Call bin/pep8analyer --help for a description of the available (and up to date) options.

The tools provides its results in two ways, the final report and an annotated CFG (usually created in the out directory).

Analyses

Dead code and possible execution of data

The tools analyses statically the program according to possbile branches and function calls to find wrongfully placed instructions and directives. It reports dead code blocks and possibly executed data blocks.

Range analysis

The range analysis reports the value of registers and memory on the annotated CFG.

Reaching definitions

The reaching definitions analysis tracks what lines may have assigned values to register and memory. Its results are on the anotated CFG. They can be used to better understand a program.

Types analysis

The types analysis detects wrongful use of types or of uninitialized data. It reports possible errors in the final report.