# Help requested in reviewing Fortran tools
**URL:** https://fortran-lang.discourse.group/t/help-requested-in-reviewing-fortran-tools/10958
**Category:** Uncategorized
**Created:** [June 9, 2026, 5:40pm UTC](https://fortran-lang.discourse.group/t/help-requested-in-reviewing-fortran-tools/10958 "2026-06-09T17:40:57Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@Beliavsky](https://fortran-lang.discourse.group/u/Beliavsky)
#### Post date: [June 9, 2026, 5:40pm UTC](https://fortran-lang.discourse.group/t/help-requested-in-reviewing-fortran-tools/10958/1 "2026-06-09T17:40:57Z")
The following are new Fortran tools, but I would like someone to confirm that they are useful before adding them to my [tools list](https://github.com/Beliavsky/Fortran-Tools).
**[Flang Modernization Advisor for Legacy Fortran](https://github.com/Puneeth-R-140/Flang-Modernization-Advisor-for-Legacy-Fortran)**
A comprehensive static analysis framework and interactive web dashboard designed to detect obsolete Fortran constructs, validate cross-file structural layouts (like `COMMON` blocks), verify subroutine/module call graphs, and generate prioritized modernization refactoring plans.
**[Flang-Multi-Stage-Compilation-Pipeline-Tracer](https://github.com/spk-22/Flang-Multi-Stage-Compilation-Pipeline-Tracer)**
Traces Fortran source constructs through every stage of Flang’s unique multi-level compilation pipeline — Parse Tree, Semantics, FIR, HLFIR, LLVM IR — producing an annotated cross-level view showing how each source construct is represented and transformed at every stage.
**[
preserf](https://github.com/grAItools/preserf)**
Python preprocessor that expands `!$SER` directives in Fortran source into explicit serialization calls.
**[Fortran-C-Cross-Language-Interface-Validator](https://github.com/ajayrm04/Fortran-C-Cross-Language-Interface-Validator)**
Static analysis tool that automatically detects **ABI mismatches** between Fortran `BIND(C)` interfaces and their corresponding C header declarations. It catches bugs that compilers silently accept but cause crashes, data corruption, or silent wrong results at runtime.
**[Col6Forge](https://github.com/Kilnexus/Col6Forge)**
Modern Fortran frontend and compiler driver written in Zig. It parses legacy and free-form Fortran, emits LLVM IR, and leverages zig cc for seamless cross-platform compilation.
**[f90c](https://github.com/SirPigari/f90c)**
single executable Fortran 90 compiler written in Rust. It can compile, link, and run Fortran 90 sources, supporting object files, optimizations, warnings, and multiple subcommands.
**[
fortran-analyzer](https://github.com/markusroellig/fortran-analyzer)**
Comprehensive tool for analyzing Fortran source code to identify variable sources, assignments, and cross-references with global variables.
## **Features**
- **Whole-codebase scanning** : Scans an entire directory to build a complete map of all modules and global variables before analysis.
- **Procedure-level analysis** : Separate analysis for each subroutine and function.
- **Variable scope classification** : Identifies global, local, and imported variables with codebase-wide context.
- **Assignment pattern detection** : Categorizes different types of variable assignments
- **Cross-reference analysis** : Shows relationships between variables across files
- **Flexible output** : Complete lists by default, with optional truncation for large codebases
---
### Author:  [@btrettel](https://fortran-lang.discourse.group/u/btrettel)
#### Post date: [June 10, 2026, 3:52am UTC](https://fortran-lang.discourse.group/t/help-requested-in-reviewing-fortran-tools/10958/2 "2026-06-10T03:52:10Z")
I am curious, is there a reason you want a second opinion on these tools in particular? I looked at them and it appears that all heavily used LLMs for coding. I personally wouldn’t exclude such projects if I were maintaining your list, opting more for comprehensiveness over curation.
* * *
Anyhow, while I’m posting, I would suggest adding my repository for the old [Toolpack](https://github.com/btrettel/toolpack) set of Fortran 77 tools to your list. The main changes I made were to get all the tools to compile on modern Linux and attempt to make a Python script to massage Fortran 77 code into a form more likely to be accepted by Toolpack, as it is brittle. There are a ton of tools here, but unfortunately the documentation in the repository is not great.
---
### Author:  [@Beliavsky](https://fortran-lang.discourse.group/u/Beliavsky)
#### Post date: [June 10, 2026, 10:57am UTC](https://fortran-lang.discourse.group/t/help-requested-in-reviewing-fortran-tools/10958/3 "2026-06-10T10:57:31Z")
I am spending less time updating my tools and codes lists than before, and going forward I will primarily add tools and codes that are announced or recommended here, rather than searching on GitHub myself.
I added Toolpack, thanks.
---
### Author:  [@nv\_epshteyn](https://fortran-lang.discourse.group/u/nv_epshteyn)
#### Post date: [June 10, 2026, 2:11pm UTC](https://fortran-lang.discourse.group/t/help-requested-in-reviewing-fortran-tools/10958/4 "2026-06-10T14:11:42Z")
> [@Beliavsky](#):
>
> Flang Modernization Advisor for Legacy Fortran
This appears to be someone’s college class project. It looks cool, but (1) it doesn’t have a license file and (2) it may be a one-off project that may not be supported in the future.
In general, I wouldn’t list any tools that don’t include some kind of licensing information.
---
### Author:  [@jwmwalrus](https://fortran-lang.discourse.group/u/jwmwalrus)
#### Post date: [June 10, 2026, 3:16pm UTC](https://fortran-lang.discourse.group/t/help-requested-in-reviewing-fortran-tools/10958/5 "2026-06-10T15:16:57Z")
> [@nv\_epshteyn](#):
>
> In general, I wouldn’t list any tools that don’t include some kind of licensing information.
That’s a pretty good general advice. I always check the license (or lack thereof), whenever I visit a new repo.
The copyleft licenses are especially cumbersome to deal with, even more so if you lean towards static linking.
And btw, welcome to the forum!
---
### Author:  [@hellohistory](https://fortran-lang.discourse.group/u/hellohistory)
#### Post date: [August 21, 2026, 11:01am UTC](https://fortran-lang.discourse.group/t/help-requested-in-reviewing-fortran-tools/10958/6 "2026-08-21T11:01:00Z")
Hi, I’m the author of Col6Forge. Like many modern software projects, AI tools have been used as part of the development workflow, but architecture decisions, testing strategy, compiler design, and validation remain manually driven.