public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bartoldeman at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org>
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	[thread overview]
Message-ID: <bug-101683-4-3oR5yVgIbE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101683-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101683

--- 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 underlying
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.

  parent reply	other threads:[~2021-07-30 11:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-30  2:30 [Bug target/101683] New: " bartoldeman at users dot sourceforge.net
2021-07-30  2:40 ` [Bug rtl-optimization/101683] " pinskia at gcc dot gnu.org
2021-07-30  2:41 ` pinskia at gcc dot gnu.org
2021-07-30  2:47 ` pinskia at gcc dot gnu.org
2021-07-30  6:17 ` rguenth at gcc dot gnu.org
2021-07-30  6:24 ` pinskia at gcc dot gnu.org
2021-07-30 11:25 ` bartoldeman at users dot sourceforge.net [this message]
2021-08-02 14:47 ` cvs-commit at gcc dot gnu.org
2021-08-02 14:49 ` pinskia at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-101683-4-3oR5yVgIbE@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).