# Problem with Intel's ifx compiler

**URL:** <https://fortran-lang.discourse.group/t/problem-with-intels-ifx-compiler/6959>\
**Category:** Uncategorized\
**Created:** [December 8, 2023, 8:36pm UTC](https://fortran-lang.discourse.group/t/problem-with-intels-ifx-compiler/6959 "2023-12-08T20:36:37Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![general\_rishkin](https://avatars.discourse-cdn.com/v4/letter/g/a9a28c/32.png) [@general\_rishkin](https://fortran-lang.discourse.group/u/general_rishkin)\
**Post date:** [December 8, 2023, 8:36pm UTC](https://fortran-lang.discourse.group/t/problem-with-intels-ifx-compiler/6959/1 "2023-12-08T20:36:37Z")

</div>

I have just installed the latest standalone Intel Fortran compiler. I then created a directory with fpm and set the compiler to ifx. The run failed with being unable to find llvm-copy but after some googling https://community.intel.com/t5/Intel-Fortran-Compiler/ifx-missing-clang-rt-msan-to-link-Fortran-program-in-debug-build/m-p/1533430, I installed the standalone DPC++ compiler.

Now, the simple Hello program runs successfully but spits out this error at the end:

> Uninitialized bytes in write at offset 0 inside [0x725000000000, 13)  
> ==37228==WARNING: MemorySanitizer: use-of-uninitialized-value

The link above says to do `-check all,nouninit` but I don’t know where to include this.

Currently, I just add `source setvars.sh` and `source vars.sh` in my .bashrc file.

---

<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:** [December 8, 2023, 9:34pm UTC](https://fortran-lang.discourse.group/t/problem-with-intels-ifx-compiler/6959/2 "2023-12-08T21:34:52Z")

</div>

Either you add it to your compilation command:

```txt
$ ifx -check all,nouninit ...

```

or you add it to the `ifx.cfg` config file.

Note that due to the `all`, this command turns on other runtime checks.

---

<div class="post-metadata">

**Author:** ![general\_rishkin](https://avatars.discourse-cdn.com/v4/letter/g/a9a28c/32.png) [@general\_rishkin](https://fortran-lang.discourse.group/u/general_rishkin)\
**Post date:** [December 9, 2023, 1:14am UTC](https://fortran-lang.discourse.group/t/problem-with-intels-ifx-compiler/6959/3 "2023-12-09T01:14:29Z")

</div>

Thanks. That worked.

---

<div class="post-metadata">

**Author:** ![greenrongreen](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/greenrongreen/32/1249_2.png) [@greenrongreen](https://fortran-lang.discourse.group/u/greenrongreen)\
**Post date:** [December 13, 2023, 10:21pm UTC](https://fortran-lang.discourse.group/t/problem-with-intels-ifx-compiler/6959/4 "2023-12-13T22:21:53Z")

</div>

sorry you hit [this bug](https://community.intel.com/t5/Intel-Fortran-Compiler/Known-bug-with-check-all-or-check-uninit-in-ifx-2024-0-0-for/td-p/1545825).

our first implementaton of LLVM Memory Sanitizer could have been better. We have a redesign in the works to get around this bug. It involves renaming the msan versions of the FRTl along with driver changes to ifx. That redesign will show up in 2024 Update 1.

---

<div class="post-metadata">

**Author:** ![shahmoradi](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/shahmoradi/32/3151_2.png) [@shahmoradi](https://fortran-lang.discourse.group/u/shahmoradi)\
**Post date:** [December 13, 2023, 11:26pm UTC](https://fortran-lang.discourse.group/t/problem-with-intels-ifx-compiler/6959/5 "2023-12-13T23:26:06Z")

</div>

I have encountered this bug too. Spent an hour trying to find the uninit variable with no success. I look forward to installing the patch for this bug.