public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/105414] constant folding for fmin/max(snan, snan) is wrong Date: Wed, 11 May 2022 01:32:43 +0000 [thread overview] Message-ID: <bug-105414-4-JBo9kjd8Qk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105414-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105414 --- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by HaoChen Gui <guihaoc@gcc.gnu.org>: https://gcc.gnu.org/g:344e425340e3c8e4539b43bf8f661e02c5a5b9a0 commit r13-280-g344e425340e3c8e4539b43bf8f661e02c5a5b9a0 Author: Haochen Gui <guihaoc@gcc.gnu.org> Date: Mon May 9 17:34:23 2022 +0800 This patch skips constant folding for fmin/max when either argument is sNaN. According to C standard, fmin(sNaN, sNaNï¼= qNaN, fmin(sNaN, NaN) = qNaN. gcc/ PR target/105414 * match.pd (minmax): Skip constant folding for fmin/fmax when both arguments are sNaN or one is sNaN and another is NaN. gcc/testsuite/ PR target/105414 * gcc.dg/pr105414.c: New.
next prev parent reply other threads:[~2022-05-11 1:32 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-28 1:25 [Bug tree-optimization/105414] New: " guihaoc at gcc dot gnu.org 2022-04-28 1:28 ` [Bug tree-optimization/105414] " pinskia at gcc dot gnu.org 2022-04-28 1:31 ` guihaoc at gcc dot gnu.org 2022-04-28 3:07 ` guihaoc at gcc dot gnu.org 2022-04-28 7:07 ` rguenth at gcc dot gnu.org 2022-04-28 7:51 ` jakub at gcc dot gnu.org 2022-04-28 8:10 ` guihaoc at gcc dot gnu.org 2022-04-28 8:18 ` jakub at gcc dot gnu.org 2022-04-29 10:02 ` guihaoc at gcc dot gnu.org 2022-04-29 10:06 ` jakub at gcc dot gnu.org 2022-04-29 12:21 ` rguenth at gcc dot gnu.org 2022-05-11 1:32 ` cvs-commit at gcc dot gnu.org [this message] 2022-05-12 2:54 ` guihaoc at gcc dot gnu.org 2022-09-28 10:05 ` cvs-commit at gcc dot gnu.org 2022-11-07 4:48 ` 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-105414-4-JBo9kjd8Qk@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).