From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 1AB81386100A; Fri, 30 Jul 2021 11:25:43 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1AB81386100A From: "bartoldeman at users dot sourceforge.net" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/101683] Floating point exception for double->unsigned conversion on avx512 only Date: Fri, 30 Jul 2021 11:25:42 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rtl-optimization X-Bugzilla-Version: 10.3.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: bartoldeman at users dot sourceforge.net X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: pinskia at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jul 2021 11:25:43 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D101683 --- Comment #6 from bartoldeman at users dot sourceforge.net --- "really not many people care about floating point exceptions". I think more people should :) but this is indeed the context. We found this issue on a supercomputer running OpenFOAM (which can enable FP exceptions, see https://cpp.openfoam.org/v3/a02284.html), and a small simple MPI program with FP exceptions enabled. Even then it crashed in an underlyi= ng library, and not OpenFOAM itself, see https://github.com/ComputeCanada/software-stack/issues/74 In the end the combination of MPI and FP exceptions easily triggers it, but= the vast majority of jobs don't crash, so even on our cluster this is very rare indeed. And many other clusters don't compile the UCX library with avx512 optimizations enabled or use precompiled binaries without those enabled.=