Codee

Faster analysis, smoother workflows — Codee 2025.4 is here! 💡 Incremental Static Analysis cuts runtime by re-analyzing only what changed. 🧠 New correctness & security checks 🧩 Fixed-Form Fortran formatting now in Beta 🔗Explore what’s new: codee.com/codee-2025-4-r…

Did you know there’s an asteroid named after #Fortran? ☄️(9548) Fortran – ~5.4 km wide – Larger than 99% of asteroids Fortran isn’t just used to simulate the universe. It’s part of it. spacereference.org/asteroid/9548-… 👀Is this Fortran’s most underrated feature?

Your climate model runs. But inside the code: → global variables → missing INTENT → memory & vectorization issues We analyzed 𝗜𝗖𝗢𝗡 (667K lines, 23K checks). Not bad code. Just normal scientific code. The hard part isn’t fixing it. It’s seeing it clearly first.

We ran Codee Analyzer on #PHASTA, a CFD solver for large-scale fluid simulations. 📊 64K lines analyzed ⚙️ 718 functions | 1,456 loops 🔎 14,463 checks in ~19 min Static analysis quickly reveals structural issues impacting correctness and maintainability in HPC codes.

Fortran still powers critical simulations. But subtle correctness issues can stay hidden for years. Examples: uninitialized variables and implicit SAVE. How static analysis detects them 👇 codee.com/improving-fort… #HPC #simulation #Fortran #C #Cpp #software

We ran our latest release on 𝗤𝘂𝗮𝗻𝘁𝘂𝗺𝗘𝗦𝗣𝗥𝗘𝗦𝗦𝗢 7.3.1 (~629K LOC). Full analysis in ~1 hour. Key patterns: • Encapsulation evolving • OpenMP scoping • Memory layout drives performance Even mature HPC codes accumulate complexity. DM for the report. #Fortran #QE

Who is Codee for? Scientific software (Fortran / C / C++) has two pressure points: 👩‍💻 Developers → structural feedback ⚙️ CI / DevOps → enforceable standards Codee connects both. In scientific computing, quality isn’t cosmetic. It’s structural.

LLMs for HPC optimization? A GMU & ORNL study found strong instruction-following — but also correctness limitations in complex scenarios.🔗dl.acm.org/doi/10.1145/37… LLMs can assist. They shouldn’t be trusted alone. They also evaluated Codee, breakdown here: codee.com/codee-analyzer…

Scientific software was built for performance. Now it must also be built for security. Aligning static analysis with CWE, ISO/IEC 24772-8, and SEI CERT helps bring structured security reasoning to legacy Fortran systems. More in our webinar: codee.com/webinars/fortr…

Fortran code can compile — and still be wrong. Our whitepaper compares correctness detection across Codee, GFortran, and Fortitude. Focus: uninitialized variables. 📄 Methodology & results → → codee.com/use-case-corre…

In HPC, tooling survives when it respects existing build systems. Scientific software evolves around compilers, scripts, and long-standing workflows — rarely from scratch. Static analysis only works if it fits into that reality. See Codee integrations: #breakdown" target="_blank" rel="nofollow noopener">codee.com/pricing/#break…

Locality of reference isn’t a single optimization — it’s a way of reasoning about #memory access over time. It often surfaces indirectly through analysis, not as an explicit goal. 🔗 open-catalog.codee.com/Glossary/Local…

Stop re-analyzing everything. Analyze what actually changed. Most scientific codebases don’t change entirely between commits, but traditional static analysis treats them as if they did. Codee’s Incremental Static Analysis keeps feedback fast in large HPC projects. 🎥 Demo ↓

Loop tiling is the most searched concept in our Open Catalog. A reminder that performance is still about reasoning well about data locality. See #PWR040 → consider loop tiling to improve locality of reference. 🔗 open-catalog.codee.com/Checks/PWR040/ #HPC #Fortran #Performance #Computing

How does Codee Formatter compare to other Fortran #formatters? 📌 Codee Formatter offers broader, more fine-grained control for CI-driven workflows and mixed legacy/modern Fortran codebases. 🔗 Free download: codee.com/codee-formatte…

Defining Fortran coding guidelines is easy. Enforcing them consistently is not. We look at how automated formatting and static analysis with Codee help apply coding guidelines in practice. 🔗 Read more: codee.com/applying-fortr… 🔽 Codee Formatter: codee.com/codee-formatte…

If you missed our latest #webinar, it’s now available on demand → "Automated Fortran code review with Codee in CI/CD pipelines" 🔗Watch it here: codee.com/webinars/autom…

@saen_dev @saen_dev Absolutely. That’s exactly where Codee fits in: automating the repeatable checks (correctness, security...) directly in CI/CD, so reviewers can focus on architecture, domain logic, and edge cases. Hybrid workflows scale better, especially in long-lived Fortran codebases

@codee_com manual code reviews are slow but ad-hoc reviews catch things automated checks miss. context, business logic, edge cases. the win is hybrid: automate the obvious stuff (formatting, security patterns, test coverage) so humans focus on architecture and logic decisions.

Quick insight from our last Fortran CI/CD webinar 👇 Among respondents, ad-hoc or manual code reviews are still the most common approach. ✔️This shows the value of automating repeatable CI/CD quality checks to reduce review overhead. Watch the webinar: codee.com/webinars/autom…

An experienced Codee Formatter user summed it up well 👇 AI can format code. But can you trust what it changes? When it comes to scientific and long-lived codebases, #predictability matters more than cleverness. 📌 Download Codee Formatter here: codee.com/codee-formatte…

Santa, there has to be a better way 😉 Happy Holidays from Codee! 🍾 💜 #HappyHolidays #Codee #Fortran #C #Cpp