# Intel® Fortran Compiler 2024.0 Available **URL:** \ **Category:** Announcements\ **Created:** [November 20, 2023, 10:15pm UTC](https://fortran-lang.discourse.group/t/intel-fortran-compiler-2024-0-available/6840 "2023-11-20T22:15:20Z")\ **Posts on this page:** 18\ **Page:** 1
**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:** [November 20, 2023, 10:15pm UTC](https://fortran-lang.discourse.group/t/intel-fortran-compiler-2024-0-available/6840/1 "2023-11-20T22:15:20Z")
Intel launched the 2024.0 versions of our Intel Software Developer Tools. The announcement is posted [here](https://community.intel.com/t5/Intel-Fortran-Compiler/AVAILABLE-NOW-Intel-Software-Developer-Tools-2024-0/m-p/1545780) on our [User Forum](https://community.intel.com/t5/Intel-Fortran-Compiler/bd-p/fortran-compiler). **Intel Software Developer Tools 2024.0 Highlights** - Intel developer tools now maximize performance on upcoming Intel 5th Generation Xeon Scalable Processors (formerly known as Emerald Rapids) and the Intel® Core Ultra processors (formerly known as Meteor Lake). - Improved installation directory layout provides faster environment setup. More specifically for Fortran: - Intel® Fortran Compiler significantly improves productivity by adding popular LLVM sanitizers allowing developers to catch Fortran, OpenMP, OpenMP offload address, memory leak, uninitialized memory, thread data races, deadlocks and undefined behavior on CPU. - Intel® Fortran Compiler adds initial Fortran 2023 standards support and enhances OpenMP 5.0, 5.1 standards compliance. ---
**Author:** ![Shahid](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/shahid/32/3672_2.png) [@Shahid](https://fortran-lang.discourse.group/u/Shahid)\ **Post date:** [November 21, 2023, 4:09pm UTC](https://fortran-lang.discourse.group/t/intel-fortran-compiler-2024-0-available/6840/2 "2023-11-21T16:09:14Z")
I just updated it. It just took me around 30 minutes. It was also incredibly smooth! ---
**Author:** ![Harper](https://avatars.discourse-cdn.com/v4/letter/h/b5ac83/32.png) [@Harper](https://fortran-lang.discourse.group/u/Harper)\ **Post date:** [November 21, 2023, 10:09pm UTC](https://fortran-lang.discourse.group/t/intel-fortran-compiler-2024-0-available/6840/3 "2023-11-21T22:09:18Z")
It was indeed much easier to download and install than previous ifort versions but my first test of f2023 features revealed that the `AT` and `LZP` edit descriptors had not been implemented, and neither had the input/output keyword `LEADING_ZERO`. ---
**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:** [November 21, 2023, 10:18pm UTC](https://fortran-lang.discourse.group/t/intel-fortran-compiler-2024-0-available/6840/4 "2023-11-21T22:18:44Z")
We post a webpage, updated at each release and update, with current feature sets. [Here](https://www.intel.com/content/www/us/en/developer/articles/technical/fortran-language-and-openmp-features-in-ifx.html) we will roll out F23 over a couple of years. I’ll take back your ask for AT and LZP edit descriptors and put them up near the top in the priority list. ---
**Author:** ![rwmsu](https://avatars.discourse-cdn.com/v4/letter/r/48db29/32.png) [@rwmsu](https://fortran-lang.discourse.group/u/rwmsu)\ **Post date:** [November 21, 2023, 11:25pm UTC](https://fortran-lang.discourse.group/t/intel-fortran-compiler-2024-0-available/6840/5 "2023-11-21T23:25:46Z")
Is GPU offload to non-Intel GPUs supported in latest ifort/ifx openMP. How about openACC? ---
**Author:** ![Harper](https://avatars.discourse-cdn.com/v4/letter/h/b5ac83/32.png) [@Harper](https://fortran-lang.discourse.group/u/Harper)\ **Post date:** [November 23, 2023, 3:21am UTC](https://fortran-lang.discourse.group/t/intel-fortran-compiler-2024-0-available/6840/6 "2023-11-23T03:21:20Z")
Although the latest ifort works fine, and I appear to have ifx also available, I do not understand the error message I got when trying to use it, possibly because I haven’t knowingly used llvm. ```auto /opt/intel/oneapi/compiler/2024.0/bin/compiler/clang-offload-bundler: error: unable to find 'llvm-objcopy' in path ``` What library is llvm-objcopy supposed to be in? ---
**Author:** ![mhulsen](https://avatars.discourse-cdn.com/v4/letter/m/ea666f/32.png) [@mhulsen](https://fortran-lang.discourse.group/u/mhulsen)\ **Post date:** [November 28, 2023, 7:37am UTC](https://fortran-lang.discourse.group/t/intel-fortran-compiler-2024-0-available/6840/7 "2023-11-28T07:37:26Z")
It is a bug and will most likely be fixed in the next release. See [Intel Forum](https://community.intel.com/t5/Intel-Fortran-Compiler/Error-message-from-clang-with-ifx-2024-0/m-p/1548003#M169473). ---
**Author:** ![rgaelzer](https://avatars.discourse-cdn.com/v4/letter/r/8491ac/32.png) [@rgaelzer](https://fortran-lang.discourse.group/u/rgaelzer)\ **Post date:** [November 28, 2023, 12:05pm UTC](https://fortran-lang.discourse.group/t/intel-fortran-compiler-2024-0-available/6840/8 "2023-11-28T12:05:11Z")
Dear Ron. I know this is not the correct venue, but I’ve been complaining about this bug in the oneAPI forum since July and still there is no resolution. I’ve been unable to update the oneAPI suite in my Fedora Core using the official rpm packages provided by Intel. This is the URL of the thread: > **[Re:Error updating OneAPI with dnf system](https://community.intel.com/t5/oneAPI-Registration-Download/Error-updating-OneAPI-with-dnf-system/m-p/1533220/emcs_t/S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufExOTkswWTBIR1YzSjZRfDE1MzMyMjB8U1VCU0NSSVBUSU9OU3xoSw)** > > We cannot see this issue on our side anymore, Can you try updating now and see if you are still seeing it. This should work now, if you upgrade to one of these products: intel-renderkit intel-iotkit intel-hpckit intel-basekit intel-aikit Now that oneAPI 2024.0 is incorporating the new features of the 2023 standard, I would really like to be able to update the suite. Thanks. ---
**Author:** ![msz59](https://avatars.discourse-cdn.com/v4/letter/m/3d9bf3/32.png) [@msz59](https://fortran-lang.discourse.group/u/msz59)\ **Post date:** [December 13, 2023, 1:29pm UTC](https://fortran-lang.discourse.group/t/intel-fortran-compiler-2024-0-available/6840/9 "2023-12-13T13:29:48Z")
Taking into account that `ifort` is apparently not being enhanced anymore (left on 2021.11.0 version) I’ve given the `ifx` a try. First thing I’ve found, which might be useful for other users, those on Linux machines, is that an `ifx`-compiled executable (no extra options given) depends on shared libraries located in OneAPI tree. This is not the case for `ifort`. It means that outside of Intel environment (setup by sourcing `/opt/intel/oneapi/setvars.sh` file) the executable won’t work. There is a simple fix, however, one has to add `-Wl,-rpath=/opt/intel/oneapi/compiler/2024.0/lib` option to `ifx` invocation. Without that, one is getting: ```plaintext >ldd a.out linux-vdso.so.1 (0x00007ffd598c5000) libimf.so => not found libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f3a2d75f000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f3a2d400000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f3a2d73f000) /lib64/ld-linux-x86-64.so.2 (0x00007f3a2d864000) ``` even on _hello world_ program _EDIT:_ Apparently the above trick is fixing the lack of “libimf.so” file but not the other libraries which have both `.so` and `.so.N` files, e.g. libintlc.so.5. I had to add also “-L /opt/intel/oneapi/compiler/2024.0/lib” option to ifx to fix that. ---
**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, 7:22pm UTC](https://fortran-lang.discourse.group/t/intel-fortran-compiler-2024-0-available/6840/10 "2023-12-13T19:22:51Z")
Would that (runtime dependence) be resolved if you linked with linker flags [static](https://www.intel.com/content/www/us/en/docs/fortran-compiler/developer-guide-reference/2024-0/static-002.html), [static-intel](https://www.intel.com/content/www/us/en/docs/fortran-compiler/developer-guide-reference/2024-0/static-intel.html), [static-libgcc](https://www.intel.com/content/www/us/en/docs/fortran-compiler/developer-guide-reference/2024-0/static-libgcc.html), [static-libstdc++](https://www.intel.com/content/www/us/en/docs/fortran-compiler/developer-guide-reference/2024-0/static-libstdc.html)? ---
**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, 9:52pm UTC](https://fortran-lang.discourse.group/t/intel-fortran-compiler-2024-0-available/6840/11 "2023-12-13T21:52:18Z")
-static-intel would be my recommendation. If the code uses OpenMP you’ll need -qopenmp-link=static in addition to -static-intel. [qopenmp-link](https://www.intel.com/content/www/us/en/docs/fortran-compiler/developer-guide-reference/2023-1/qopenmp-link.html) [static-intel](https://www.intel.com/content/www/us/en/docs/fortran-compiler/developer-guide-reference/2023-1/static-intel.html) ---
**Author:** ![msz59](https://avatars.discourse-cdn.com/v4/letter/m/3d9bf3/32.png) [@msz59](https://fortran-lang.discourse.group/u/msz59)\ **Post date:** [December 14, 2023, 9:06am UTC](https://fortran-lang.discourse.group/t/intel-fortran-compiler-2024-0-available/6840/12 "2023-12-14T09:06:29Z")
Using `-static-intel` option fixes the problem. Well, actually it is not very much of a problem. I have just noticed the difference between `ifort` and `ifx`. Looks like `ifort` has this option ON by default. Incidentally, the man pages of **both** `ifort` and `ifx` state that the Intel libraries are linked statically by default (which makes sense!), with the exception of `openMP` and `coarray` runtime libraries. Apparently this is not true for `ifx` so maybe it should be updated in the documentation. ---
**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 14, 2023, 3:38pm UTC](https://fortran-lang.discourse.group/t/intel-fortran-compiler-2024-0-available/6840/13 "2023-12-14T15:38:32Z")
I think you found a bug in our ifx driver. the default SHOULD BE static. and if you compile with -dryrun or -# to dump all the driver settings you will see that MOST of the Intel libraries are proceeded by -Bstatic. libimf might have slipped through the cracks. I will research this and correct it. Thank you for bringing this to my attention. ---
**Author:** ![msz59](https://avatars.discourse-cdn.com/v4/letter/m/3d9bf3/32.png) [@msz59](https://fortran-lang.discourse.group/u/msz59)\ **Post date:** [December 14, 2023, 6:28pm UTC](https://fortran-lang.discourse.group/t/intel-fortran-compiler-2024-0-available/6840/14 "2023-12-14T18:28:26Z")
You’re welcome 😉 There is another one, `libintlc` if I remember correctly. That one has appeared on “not found” list after adding `-rpath` option and required additional `-L` option. The difference I see is that `libimf.so` is full-size library file but for the other one, the `so` file is neither full-size nor symbolic link to `so.5`. Instead, it contains “INPUT libintlc.so.5” directive, apparently not recognised properly by the loader. ---
**Author:** ![msz59](https://avatars.discourse-cdn.com/v4/letter/m/3d9bf3/32.png) [@msz59](https://fortran-lang.discourse.group/u/msz59)\ **Post date:** [December 20, 2023, 9:24am UTC](https://fortran-lang.discourse.group/t/intel-fortran-compiler-2024-0-available/6840/15 "2023-12-20T09:24:06Z")
As of the latest, 2024.0.2 version, it is still so: ```plaintext $ ifx hello.f90 $ ldd a.out [...] libimf.so => /opt/intel/oneapi/compiler/2024.0/lib/libimf.so libintlc.so.5 => /opt/intel/oneapi/compiler/2024.0/lib/libintlc.so.5 ``` ---
**Author:** ![msz59](https://avatars.discourse-cdn.com/v4/letter/m/3d9bf3/32.png) [@msz59](https://fortran-lang.discourse.group/u/msz59)\ **Post date:** [December 20, 2023, 9:35am UTC](https://fortran-lang.discourse.group/t/intel-fortran-compiler-2024-0-available/6840/16 "2023-12-20T09:35:24Z")
> [@greenrongreen](#): > > Intel launched the 2024.0 versions of our Intel Software Developer Tools. The announcement is posted [here](https://community.intel.com/t5/Intel-Fortran-Compiler/AVAILABLE-NOW-Intel-Software-Developer-Tools-2024-0/m-p/1545780) on our [User Forum](https://community.intel.com/t5/Intel-Fortran-Compiler/bd-p/fortran-compiler). Just FYI, there are two almost identically titled Intel pages with Fortran Compiler(s) Release Notes: 1. [Intel® Fortran Compiler Release Notes and New Features](https://www.intel.com/content/www/us/en/developer/articles/release-notes/fortran-compiler-release-notes-2023.html) - pretending to be the “Latest” but dated July 10th, 2023 and ending with `ifx` 2023.2 and `ifort` 2021.10.0 2. [Intel® Fortran Compiler and Intel® Fortran Compiler Classic Release Notes](https://www.intel.com/content/www/us/en/developer/articles/release-notes/oneapi-fortran-compiler-release-notes.html) - really the latest, up to `ifx` 2024.0.2 and `ifort` 2021.11.1. Guess which one I was directed to by a web search 🙂 Yet, apparently the AI behind the search is learning quickly, as it now points to the right one. ---
**Author:** ![wyphan](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/wyphan/32/632_2.png) [@wyphan](https://fortran-lang.discourse.group/u/wyphan)\ **Post date:** [December 24, 2023, 9:44pm UTC](https://fortran-lang.discourse.group/t/intel-fortran-compiler-2024-0-available/6840/17 "2023-12-24T21:44:10Z")
IIRC the classic compilers `icc`, `icpc`, ~~and `ifort`~~ are no longer included in the Intel oneAPI stacks in the 2024.0 distribution. The several previous versions prior to this have been spewing out deprecation warnings if you tried to use them. Edit: The official deprecation announcement can be accessed here on the Intel forum: > **[DEPRECATION NOTICE Intel® Fortran Compiler Classic (ifort)](https://community.intel.com/t5/Intel-Fortran-Compiler/DEPRECATION-NOTICE-Intel-Fortran-Compiler-Classic-ifort/td-p/1545789)** > > Intel® Fortran Compiler Classic (ifort) is now deprecated and will be discontinued in late 2024. Intel recommends that customers transition now to using the LLVM-based Intel® Fortran Compiler (ifx) for continued Windows\* and Linux\* support, new... The deprecation warning looks like this: ```auto $ which ifort /opt/intel/oneapi/compiler/2024.0/bin/ifort $ ifort --version ifort: remark #10448: Intel(R) Fortran Compiler Classic (ifort) is now deprecated and will be discontinued late 2024. Intel recommends that customers transition now to using the LLVM-based Intel(R) Fortran Compiler (ifx) for continued Windows* and Linux* support, new language support, new language features, and optimizations. Use '-diag-disable=10448' to disable this message. ifort (IFORT) 2021.11.1 20231117 Copyright (C) 1985-2023 Intel Corporation. All rights reserved. ``` ---
**Author:** ![VladimirF](https://avatars.discourse-cdn.com/v4/letter/v/e9a140/32.png) [@VladimirF](https://fortran-lang.discourse.group/u/VladimirF)\ **Post date:** [December 25, 2023, 2:05pm UTC](https://fortran-lang.discourse.group/t/intel-fortran-compiler-2024-0-available/6840/18 "2023-12-25T14:05:05Z")
I have to confess that the way the OneAPI is distributed in repositories for Linux is a source of constant pain. The dependencies in the repositories are weird and any upgrade is heavy to do right on its own even if there were no other issues. But even worse are the issues with the public key for the signatures of the packages. I try to delete the repository and add it again with the hope of the key getting sorted but it really is a pain.