Parallel Performance Wizard (PPW) is a performance analysis tool designed for UPC, MPI, and SHMEM programs. It features an easy-to-use interface and tight integration with GAS programming models via the GASP interface. It is known to work on many platforms. This project is part of a study of existing and emerging performance analysis theory and tools, current and future HPC architectures, and usability and user productivity preferences and methods, along with various programming models.
Gnasher alleviates developers from having to execute maven builds with the "-o" option (offline) to avoid accessing external repositories' metadata files. The SHA1 hash files and the missing pom metadata files for dependencies are created if they are missing. The next time the build is run, external repositories are not accessed and the build runs faster.
Autodia is a command line Perl application that generates UML class diagrams from source code, SQL, and database connections. It supports multiple programming languages including SQL, and can output images (using GraphViz/VCG/SpringGraph), Dia XML and Umbrello XML, or custom formats using templates.
Oink is a collaboration of backends for the Elsa C and C++ frontend. It aims to be industrial-strength for immediate utility in finding bugs, extensible for ease in adding backends, and composable for ease in combining existing ones. It computes expression-level and type-level data flow, and statement-level intra-procedural control flow (by delegating to Elsa). It's easy to get started by using the two demo backends that print graphs of these flows. It also comes with a client of the data flow analysis that does type qualifier inference: Cqual++, a C/C++ frontend for Cqual. Whole-program analyses may be attempted using the linker imitator.
Ccide reads C, C++, BASIC, or bash source code containing embedded decision tables from stdin, expands the tables, copies the remaining statements, and forms a compilable C or C++ source module, executable bash script, or interpretable BASIC program. Erratic side effects are avoided by evaluating all condition expressions at exactly the same time, and by performing all evaluations and actions in the original sequence.