# Improving Fortran Results in the Julia Micro-benchmarks

**URL:** <https://fortran-lang.discourse.group/t/improving-fortran-results-in-the-julia-micro-benchmarks/198>\
**Category:** Help\
**Created:** [July 8, 2020, 2:39pm UTC](https://fortran-lang.discourse.group/t/improving-fortran-results-in-the-julia-micro-benchmarks/198 "2020-07-08T14:39:56Z")\
**Posts on this page:** 1\
**Showing post:** 40

<div class="post-metadata">

**Author:** ![mecej4](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/mecej4/32/855_2.png) [@mecej4](https://fortran-lang.discourse.group/u/mecej4)\
**Post date:** [June 21, 2022, 8:35pm UTC](https://fortran-lang.discourse.group/t/improving-fortran-results-in-the-julia-micro-benchmarks/198/40 "2022-06-21T20:35:59Z")

</div>

Whether you request optimization or not, the compiler may determine that an expression that is to be output may be calculated entirely at compile time, store that value in the EXE/a.out, and simply output that previously computed value.

Obviously, the result of the first loop is N+4, and it appears that the Intel compiler did not have to place code in the executable to calculate that result (elapsed time = 0).

We have seen an [extreme example](https://fortran-lang.discourse.group/t/computing-at-compile-time/3044/32) of such compile time calculation in a recent thread.

---

_[View the full topic](https://fortran-lang.discourse.group/t/improving-fortran-results-in-the-julia-micro-benchmarks/198)._