# Errors using certain Fortran compilers in CRAN checks

**URL:** <https://fortran-lang.discourse.group/t/errors-using-certain-fortran-compilers-in-cran-checks/8124>\
**Category:** Help\
**Created:** [June 1, 2024, 10:06pm UTC](https://fortran-lang.discourse.group/t/errors-using-certain-fortran-compilers-in-cran-checks/8124 "2024-06-01T22:06:50Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![ivanpribec](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/ivanpribec/32/3290_2.png) [@ivanpribec](https://fortran-lang.discourse.group/u/ivanpribec)\
**Post date:** [June 8, 2024, 11:55am UTC](https://fortran-lang.discourse.group/t/errors-using-certain-fortran-compilers-in-cran-checks/8124/16 "2024-06-08T11:55:45Z")

</div>

> [@jomulder](#):
>
> The problem for me is that it is really not easy to debug under these different compilers.

Catching such kinds of dimension errors at runtime is possible. You need to use the flags:

- for gfortran: [`-fcheck=all`](https://gcc.gnu.org/onlinedocs/gfortran/Code-Gen-Options.html#index-fcheck) (includes `-fcheck=bounds`)
- for ifort/ifx: [`-check all`](https://www.intel.com/content/www/us/en/docs/fortran-compiler/developer-guide-reference/2024-1/check.html) (includes `-check bounds`)

In the particular case of ifx v2024.0 use `-check all,nouninit` to bypass a [compiler bug.](https://fortran-lang.discourse.group/t/use-of-uninitialized-value-warning-with-check-all-option-of-ifx/6823/5)

---

_[View the full topic](https://fortran-lang.discourse.group/t/errors-using-certain-fortran-compilers-in-cran-checks/8124)._