Deutsch English Français Italiano |
<l9afemFkuuaU1@mid.individual.net> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!weretis.net!feeder9.news.weretis.net!feeder8.news.weretis.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Steve Lionel <steve@seesignature.invalid> Newsgroups: comp.lang.fortran Subject: Re: Intel oneAPI compiler not happy with AVX512 Date: Mon, 29 Apr 2024 16:49:25 -0400 Lines: 27 Message-ID: <l9afemFkuuaU1@mid.individual.net> References: <uvb0kh$29ndd$1@dont-email.me> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net vi5Out9yC+084mPTAm/5IwjsStImjqUOxRk/X6VrbOLcuAN6HN Cancel-Lock: sha1:79r0O7vzd07PLo1ul1uCEBpAfrY= sha256:MPKv8WwodSyCpOdh/u8r7SyvWEp7ugxdm7v5QY8d2IA= User-Agent: Mozilla Thunderbird Content-Language: en-US In-Reply-To: <uvb0kh$29ndd$1@dont-email.me> Bytes: 2155 On 4/12/2024 5:58 AM, Woozy Song wrote: > I have a package that contains nearly 500 f90 files. I noticed that in > the makefile, it was using -ax (automatic dispatch ) up to AVX2. I added > COMMON-AVX512 to the options. One thing I noticed was that compilation > is now slower. It seemed to stop for 30 seconds when it hit one > particular subroutine. But main problem was that after a few hundred > files, it aborted with unexpected internal error. The offending file > wasn't doing anything exotic, mostly a linear regression. > This is 2024.1 version of the compiler, pretty much the latest. > Has anybody else compiled for AVX512? Please report this in https://community.intel.com/t5/Intel-Fortran-Compiler/bd-p/fortran-compiler and provide a reproducer. Internal Compiler Error is always a compiler bug. But before you do, try ifx instead of ifort, as it has an entirely different code generator and is the path forward for Intel. Bugs that are ifort-only are unlikely to get fixed. -- Steve Lionel ISO/IEC JTC1/SC22/WG5 (Fortran) Convenor Retired Intel Fortran developer/support Email: firstname at firstnamelastname dot com Twitter: @DoctorFortran LinkedIn: https://www.linkedin.com/in/stevelionel Blog: https://stevelionel.com/drfortran WG5: https://wg5-fortran.org