public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug d/109221] std.math.floor, core.math.ldexp, std.math.poly poor inlining Date: Tue, 21 Mar 2023 01:37:29 +0000 [thread overview] Message-ID: <bug-109221-4-jo9siT8jX2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109221-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109221 --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- With -ffast-math -mfpmath=387,sse (or -mavx512f instead of -mfpmath=387 as there is a avx512f instruction too) added, ldexp gets inlined.
next prev parent reply other threads:[~2023-03-21 1:37 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-21 1:09 [Bug d/109221] New: " witold.baryluk+gcc at gmail dot com 2023-03-21 1:15 ` [Bug d/109221] " witold.baryluk+gcc at gmail dot com 2023-03-21 1:18 ` witold.baryluk+gcc at gmail dot com 2023-03-21 1:26 ` pinskia at gcc dot gnu.org 2023-03-21 1:37 ` pinskia at gcc dot gnu.org [this message] 2023-03-21 7:19 ` crazylht at gmail dot com
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-109221-4-jo9siT8jX2@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).