public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "harald at gigawatt dot nl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/114363] inconsistent optimization of pow(x,2)+pow(y,2) Date: Sat, 16 Mar 2024 10:37:24 +0000 [thread overview] Message-ID: <bug-114363-4-IbrhylVCEu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114363-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114363 Harald van Dijk <harald at gigawatt dot nl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |harald at gigawatt dot nl --- Comment #1 from Harald van Dijk <harald at gigawatt dot nl> --- This is, I believe, correct. Before C++11, calling std::pow with float and int arguments, it returned a float. As of C++11, it returns a double. If the result of pow(x,2) is immediately converted to float, then it is a valid optimisation to convert it to x*x: that is guaranteed to produce the exact same result. But if it isn't, then converting to x*x loses accuracy and alters the result. You can call std::powf instead of std::pow to avoid the promotion to double.
next prev parent reply other threads:[~2024-03-16 10:37 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-16 9:31 [Bug tree-optimization/114363] New: " vincenzo.innocente at cern dot ch 2024-03-16 10:37 ` harald at gigawatt dot nl [this message] 2024-03-16 11:26 ` [Bug tree-optimization/114363] " xry111 at gcc dot gnu.org 2024-03-16 12:58 ` jakub at gcc dot gnu.org 2024-03-16 15:06 ` vincenzo.innocente at cern dot ch
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-114363-4-IbrhylVCEu@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).