https://fortran.sh3d.com.au/tags/migration/ Recent content in Migration on Fortran 2026 Hugo en https://fortran.sh3d.com.au/expertise/migration-32-to-64/ Mon, 01 Jan 0001 00:00:00 +0000 https://fortran.sh3d.com.au/expertise/migration-32-to-64/ <p>Moving a real Fortran ERP from 32-bit to 64-bit is rarely a recompile. Pointer sizes, integer kinds, file formats, third-party libraries, and decades of implicit assumptions all have to be found and fixed without breaking business logic that has been correct for thirty years.</p> <p>We have done this on a production ERP — see <a href="https://fortran.sh3d.com.au/projects/profitool/">Projects → Profitool</a> — and we know what to look for.</p> <h2 id="where-we-add-value">Where we add value<a class="td-heading-self-link" href="#where-we-add-value" aria-label="Heading self-link"></a></h2> <ul> <li><strong>Auditing the codebase</strong> for 32-bit assumptions: integer kinds, pointer arithmetic, record sizes, common blocks, EQUIVALENCE.</li> <li><strong>Driving the translation</strong> with <a href="https://fortran.sh3d.com.au/tools/promula/">Promula / gmFortran</a> and hand-tuned changes where the tool can&rsquo;t decide.</li> <li><strong>Locking the result with tests</strong> so the 64-bit build provably matches the 32-bit one before you cut over — see <a href="testing/">Expertise → Testing</a>.</li> <li><strong>Operational cutover</strong>: data file formats, on-disk layouts, third-party library upgrades, and rollback plans.</li> </ul> <h2 id="talk-to-us">Talk to us<a class="td-heading-self-link" href="#talk-to-us" aria-label="Heading self-link"></a></h2> <p><a href="mailto:simon@unisolve.com.au">simon@unisolve.com.au</a> or <a href="mailto:scottp@dd.com.au">scottp@dd.com.au</a></p>