public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub 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: Thu, 28 Apr 2022 07:51:10 +0000 [thread overview] Message-ID: <bug-105414-4-1afkveGTRE@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 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Yeah, TREE_REAL_CST can't be used on @0 if it isn't a REAL_CST which nothing guarantees.
next prev parent reply other threads:[~2022-04-28 7:51 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 [this message] 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 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-1afkveGTRE@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).