public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "weslley.pereira at ucdenver dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/107753] gfortran returns NaN in complex divisions (x+x*I)/(x+x*I) and (x+x*I)/(x-x*I) Date: Fri, 18 Nov 2022 23:47:08 +0000 [thread overview] Message-ID: <bug-107753-4-sWfLZBaWvb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107753-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107753 --- Comment #8 from Weslley da Silva Pereira <weslley.pereira at ucdenver dot edu> --- Created attachment 53927 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53927&action=edit Test case with many examples of complex division Test code used in LAPACK 3.11.0. Code extracted from https://github.com/Reference-LAPACK/lapack/blob/master/INSTALL/test_zcomplexdiv.f
next prev parent reply other threads:[~2022-11-18 23:47 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-18 19:32 [Bug fortran/107753] New: " weslley.pereira at ucdenver dot edu 2022-11-18 19:50 ` [Bug fortran/107753] " anlauf at gcc dot gnu.org 2022-11-18 20:50 ` kargl at gcc dot gnu.org 2022-11-18 21:26 ` anlauf at gcc dot gnu.org 2022-11-18 22:05 ` kargl at gcc dot gnu.org 2022-11-18 23:24 ` sgk at troutmask dot apl.washington.edu 2022-11-18 23:32 ` sgk at troutmask dot apl.washington.edu 2022-11-18 23:45 ` weslley.pereira at ucdenver dot edu 2022-11-18 23:47 ` weslley.pereira at ucdenver dot edu [this message] 2022-11-19 0:25 ` sgk at troutmask dot apl.washington.edu 2022-11-19 19:11 ` kargl at gcc dot gnu.org 2022-11-19 20:14 ` anlauf at gcc dot gnu.org 2022-11-20 0:54 ` sgk at troutmask dot apl.washington.edu 2022-12-07 21:16 ` anlauf at gcc dot gnu.org 2022-12-07 21:50 ` kargl at gcc dot gnu.org 2022-12-07 22:31 ` anlauf 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-107753-4-sWfLZBaWvb@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: linkBe 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).