public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/106805] [13 Regression] Undue optimisation of floating-point comparisons Date: Fri, 13 Jan 2023 11:28:20 +0000 [thread overview] Message-ID: <bug-106805-4-OKsvnAdAyq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106805-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106805 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 |P1
next prev parent reply other threads:[~2023-01-13 11:28 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-106805-4@http.gcc.gnu.org/bugzilla/> 2022-11-30 19:30 ` pinskia at gcc dot gnu.org 2022-12-02 12:48 ` jakub at gcc dot gnu.org 2022-12-02 12:49 ` jakub at gcc dot gnu.org 2022-12-05 10:55 ` cvs-commit at gcc dot gnu.org 2022-12-20 14:55 ` rguenth at gcc dot gnu.org 2023-01-13 11:27 ` rguenth at gcc dot gnu.org 2023-01-13 11:28 ` rguenth at gcc dot gnu.org [this message] 2023-01-13 16:56 ` vincent-gcc at vinc17 dot net 2023-02-03 9:23 ` jakub at gcc dot gnu.org 2023-02-27 9:14 ` [Bug middle-end/106805] " rguenth 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-106805-4-OKsvnAdAyq@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).